Summary of PD10 for AVC 1920 1080/50 or 60p users: Last Edited 25 JAN 2012. I'll keep this updated for as other things come to light

This thread is for AVC (h.264) 1920x1080/50 or 60fps users. Such files are being produced by a range of Camcorders such as the Pana 700, 800 & 900 series, CX560 & CX700, JVC GC-PX10 etc...+ this format is now a formal part of the AVCHD spec http://www.avchd-info.org/format/ (which is a subset of the broader AVC spec http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC ). Here are some notes on PD10:


Rendering Choices: There are three options you can use to produce the final project, and my recommendations (YMMV) at this stage are in order:
1) CPU (Fast video rendering technology unchecked): Slow but the most reliable output. While it does re-encode the Audio and Video streams it keeps everything in sync even with remuxing to other formats
2) Hardware Video Encoder (GPU): Works pretty well on my setup (nvidia) but in PD9 I used an ATI card and it this was not able to produce proper 50 or 60p output. I have not tested an ATI card in PD10 to see if it is fixed. It is quicker than CPU rendering and while the native PD10 output looks good any remuxing brings out an AV Sync issue (I presume there is a timestamp mismatch between the Video encode done with the GPU and the Audio done on the CPU)
3) SVRT: It is very quick and keeps the content identical to the original except for the segments that are altered (eg adding titles, overlays, transitions etc) which is rendered. There has been a great improvement in Patch 1129b with the native output looking good. I'm still hesitant to recoment this however as any remuxing shows issues at the transition points. If you want to use SVRT you may want to try enabling "Allow SVRT on Single...h.264" under the Preference --> Produce tab (note the warning given by PD10).

Other: There are still a couple of things hanging around from PD9 days that need to be addressed:
- SVRT Issue: As mentioned above the issues at the transition points between SVRT and Rendering are still present
- Format: The output file is slightly "non std", I'm not sure if it is the header information in the M2TS container or the stream info (esp the Audio Stream) but some other apps don't like it much. I did create a "FixPD9" batch file that may work if you have any issues with your output but YMMV (see the prior PD9 thread on the topic here - http://forum.cyberlink.com/forum/posts/list/15533.page ).
- Timeline: Unfortunately PD10 is still living in the '80's, and you are still stuck with either PAL (25) or NTSC (30) fps on the timeline so you cannot physically see all your 50/60 frames. This is a broader issue the devs should work on in letting the user specify what fps to use on the timeline as there is more than just 25 or 30 out in the real world.

Creating a Custom Profile using Intelligent SVRT: This is no longer required as from Patch 1129b, PD10 now support 50 and 60p options

Thanks
Nathan


=========== Original Post 2==============
Creating a Custom Profile using Intelligent SVRT: Under the "Produce" tab you can click on "Intelligent SVRT" and it will create a custom profile that matches the details of your clip. And for the most part this works but it has some bugs:
- It can create a Custom Profile that has a higher bitrate than the GUI (eg above 22500) so you cannot edit it.
- The profile has an error on the Audio side with the "Audio Mode" not filled out, and while the file created is 5.1 the description is 2.0. It appears this is a bug and can also cause PD10 to hang at 99% during the rendering. To "fix" this issue, you need to edit in Notepad the Profile.Ini file in "C:\Users\[USERNAME]\AppData\Roaming\CyberLink\PowerDirector\10.0" (note: this may be a hidden folder) and change "<Audio Mode>32" to "<Audio Mode>16"

Rendering Choices: There are three options you can use to produce the final project using the Custom Profile created above:
- SVRT: It is very quick and keeps the content identical to the original except for the segments that are altered (eg adding titles, overlays, transitions etc) which is rendered. This would be my preferred option but unfortunately I cannot recommend this as I see transition issues between the rendered and the SVRT segments of the output. If you want to use SVRT you may want to try enabling "Allow SVRT on Single...h.264" under the Preference --> Produce tab (note the warning given by PD10).
- Hardware Video Encoder: Works pretty well on my setup (nvidia) but in PD9 I used an ATI card and it this was not able to produce proper 50 or 60p output. I have not tested an ATI card in PD10 to see if it is fixed. At this stage, this is what I would recommend this rendering option (at least for nvidia users) as the quality looks good, and the speed is about "real time"
- CPU (Fast video rendering technology unchecked): Quality looks good though it is the slowest of the three options on my PC.

Other: There are still a couple of things hanging around from PD9 days that need to be addressed:
- SVRT Issue: As mentioned above the issues at the transition points between SVRT and Rendering are still present
- Format: The output file is slightly "non std", I'm not sure if it is the header information in the M2TS container or the stream info (esp the Audio Stream) but some other apps don't like it much. I did create a "FixPD9" batch file that may work if you have any issues with your output but YMMV (see the prior PD9 thread on the topic here - http://forum.cyberlink.com/forum/posts/list/15533.page ).
- Timeline: Unfortunately PD10 is still living in the '80's, and you are still stuck with either PAL (25) or NTSC (30) fps on the timeline so you cannot physically see all your 50/60 frames. This is a broader issue the devs should work on in letting the user specify what fps to use on the timeline as there is more than just 25 or 30 out in the real world.


Thanks
Nathan


=========== Original Post 1==============

I must have been in hibernation for a month as I've only just seen PD 10 is out. I'm currently downloading the trail of PD10 to see for us AVC (h264) 1920x1080/50 or 60p users if any of the following has improved:
1) Able to output above 24mbs without manually editing the ini file
2) SVRT working without corruption between the original and rendered segments
3) Better compatibility with the AVC spec for both the header and streams
4) Timeline that lets you go down to 50 or 60 fps (not the outdated PAL or NTSC choice)

I'm sure there were some other things I've forgotten - but I'm sure pj3c will remind me PD 64 Bit-Win10 64 Bit-32GB RAM-80TB HDD
Sony FX6 - 500Mbps 4k/50p AVC-I HLG
Canon XF400 - 150Mbps 4k/50p AVC
GoPro Hero6 Black
Pana HS700-28Mbps 1080/50p AVC (High@L4.2)
Canon HV20-HDV 25Mbps 16:9 1440x1080/25p MPEG