Mmmm they all play on my PC fine. Can you post one of the ones that don't play well. 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

Does rendered file from PD11 and patched by FixPD9 plays fine?
Starnge, it does not play on few PCs, also as file from HDD through player OPPO-95.
I checked again, if I use other editing tool, rendered and patched, same file playes fine.
All my files from camcorder play choppy after rendering and patching. The file I sent is one of them, it plays slower (like slow motion) and also not smooth, audio is not smooth too. I wil make a fresh PD11 installation on other PC and will retest again.
Thanks for your efforts.

Here is a different version of "FixPD" that may or may not make any difference (as the file plays fine for me).

The changes are:
- Cleaned up the file structure and batch file to make it easier to see your stuff. Just drop the PD "produce.m2ts" into the FixPD folder and run FixPD. It will create an output.m2ts file that may or may not be any "better"
- Updated eac3to to new version (v3.27)
- Added some timing presets to the tsmuxer meta data

See how it goes and let me know.

Thanks
Nathan 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

Same results. I also tried to render by PD11 on othe PC, pathing with FixPD9 on: a) other PC,b) on same PC.
same results, before patching plays fine, after no smooth play. I am going to try on a third PC, a fresh PD11 installation, not so many SW loaded. i will let you know.

No surprise really. Can you post me one that you have patched (I want to see if it is any different to the one I made). 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

I sent to PM a link to download patched file. let me know please how it plays on your system.

That clip also plays fine for me (though I do sometimes see a stutter in the first few seconds). Unfortunatly the clip is a different one to that you sent me (00012.MTS) so it is hard to compare if they are the same as what I produced! Anyway, it may be quicker and easier for me to send you varous samples and if you could report back which ones play better or worse than the others.

I'll post the links shortly (when they have finished uploading) 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

- NoB.m2ts (No B Frames) : https://dl.dropbox.com/u/59011278/NoB.m2ts
- NoBLBR (Lower Bit Rate and No B Frames): https://dl.dropbox.com/u/59011278/NoBLBR.m2ts
- NoAudio (No Audio Track): https://dl.dropbox.com/u/59011278/No%20Audio.m2ts 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

I appologize for sending different file, uploaded correct one, which is became choppy after patching, sent you a link to PM.
Your three files all play perfectly smoot before patching.
After patching two of them surprisingly still played smooth (NoB, NoBLBR), NoAudio was not possible to patch,message said no second stream. i rechecked agaain my original file withh all the B frames; after patching becomes choppy, yours two with no B frames after patcching still play smooth.

FYI - all files were made in PD11 then run through FixPD. So they all played fine? Let me make a few more (all I need you to do is play them and tell me which ones work and which ones don't).

EDIT - You don't have to run any of these test files through FixPD again 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

OK - I see the issue with the stutter and the slo-mo in the file you uploaded. The "good" news is your output.m2ts file is very different to the same one I produced on my PC. It is smaller, of a different sub type, and missing bits..... are you sure your workflow process is the same as descrived earlier? Also, what is the spec of your PC?

OK - to double check, There are three files we can check (and from the Windows Properties they are XX in size)
00012.MTS (original CAMCorder footage) - 40,796,160 bytes
produce.m2ts (from PD11) - Mine is 42,881,108 bytes ... can you please upload yours
output.m2ts (from FixPD) - Mine is 43,739,136 and yours is only 29,106,560

I am uploading my versions of output and produce.m2ts for you to compare.

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

https://dl.dropbox.com/u/59011278/output.m2ts
https://dl.dropbox.com/u/59011278/Produce.m2ts 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

jmone, to clarify few things regarding your note:
” output.m2ts file is very different to the same one I produced on my PC. It is smaller, of a different sub type, and missing bits..... are you sure your workflow process is the same as descrived earlier? Also, what is the spec of your PC?:
My comment: as you asked I sent (the very first .rar file) exported project. The .rar file had PD11 project file and the 00012.MTS (original CAMCorder footage),ut the problem was that in the PD time line I cut few last frames, just to have some kind of processing. When I last time uploaded output.m2ts (from FixPD) it was done by using same saved project file (very first upload in .rar) and rendered with PD11, hence few last frames were cut. It made file a bit smaller. But on top you made a type in specifying file length:
“output.m2ts (from FixPD) - Mine is 43,739,136 and yours is only 29,106,560”
Mine is actually 39,106,560 not the 29,xxx. Your typo.it is 4.6Mb smaller since few frames cut.
My PC has i5 Core, Win7, 6MB RAM. I actually installed PD11 demo on a third PC, same results.

I tested your last uploaded files: produce.m2ts works fine, output.m2ts is slow/choppy.

We are getting there. Making a step back and keeping everything in order:
I uploaded two files, sent links to PM.
They made by using same file as you have, full length, nothing cut this time:
“00012.MTS (original CAMCorder footage) - 40,796,160 bytes”
The two uploaded files made on my third PC using PD11 demo:
“produce.m2ts (from PD11) on Bordo PC.m2ts” - 40,102,468 bytes
“ output.m2ts (from FixPD) on Bordo PC.m2ts” - 40,728,576 bytes

I tested them the produce works fine, the output (from FixPD) is not smooth, same as yours.

OK - so with some luck we should all have the same files so we can confidently compare results (downloading now). Can you pls confirm how the five files I sent you play (pls don't process just test the playback):
- NoB.m2ts (No B Frames) :
- NoBLBR (Lower Bit Rate and No B Frames):
- NoAudio (No Audio Track):
- output.m2ts
- Produce.m2ts 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

OK one step at a time. We are producing differnt files from PD11- My produce is still significantly larger, I get a file 42,907,616. My process is.
- Open PD11 with a blank project. Make sure the Edit --> Preferences are set to NTSC and Use drop frame timecode with 5.1 Surround. On Edit --> Produce I have Reduce video blocky artifacts checked.
- I then drag 00012.MTS in PD then onto the timeline.
- I then go to the Produce Tab, click the Intelligent SVRT button and select the AVC1920x1080/60p (28 Mbps) profile (and it shows the Frame Rate as 59.94).
- I Unckeck "fast video rendering"
- I make sure "Dolby Digital 5.1 is checked"

Press Start. This time the file is 42,960,632 (no idea why each time they are a little different but they are all larger than your process by 5%). 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

Checking the five files you sent playback:
- NoB.m2ts (No B Frames) : plays OK
- NoBLBR (Lower Bit Rate and No B Frames): plays OK
- NoAudio (No Audio Track): plays OK
- output.m2ts: plays NOT smoothly, slowmotion
- Produce.m2ts: plays OK

Next step, rendered as per your reccomendations, also my process on Edit --> Produce I have Unchecked "Allow SVRT on single IDR H.264 video".
Rendered file Produce.m2ts is 42,885,056 bytes, larger than before. Before I always was using Chkecked "fast video rendering".
It was rendering much faster.
The playing results as follows:
Produce.m2ts is - 42,885,056 bytes - plays OK
output.m2ts (from FixPD) is - 43,665,408 bytes - plays NOT smoothly, slowmotion
Actually same results as on your uploaded files.


Made one more experiment, on Edit --> Produce changed to Checked "Allow SVRT on single IDR H.264 video".
Rendered file a bit bigger 42,907,052 bytes, after FixPD still bad play.

Another experiment, I Chkecked "fast video rendering" got bigger file 40,128,036 bytes, after FixPD not smooth play.

OK - Time to try a custom profile (eg the No B frames from the begining of this thread but in 60P).
1) Go to the produce tab as normal and select the AVC 1920 x 1080/60P (28Mbps) the press the "+" button to create a new Profile.
2) Give it a name and description that you like (you will notice on the "Profile Name" tab the GOP Pattern is "IBBPBBPBBPBBP" but to change this we need to:
3) Close PD11
4) open this file in Note Pad: "C:\Users\[USERNAME]\AppData\Roaming\CyberLink\PowerDirector\11.0\Profile.ini
5) locate the "<Pattern>" for your new profile and change it to "IPPPPP"
6) Save the file

Go back into PD11 and on the Produce Tab --> Profile Type (Select CUSTOM), and you new profile should be selectable in "Profile Name". If you click the details button you can check the correct GOP structure is there.

Try making a file with that one and let me know how it goes. It should be the same result as the "NoB.m2ts" that plays OK once run through FixPD 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

I take it you PD 11 is up to date with the latest verions (241? 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

Quote: Gents - Try this. I wrote a simple batch file that uses eac3to to demux the contents of the "produce.m2ts" file then remux it correctly with tsmuxer. Just place the output from PD in the extracted FIXPD9 folder then run the "Fix PD9.BAT" file and see how the output.m2ts file plays on the PS3. It should be more compliant but I'd suggest that you use CPU only in PD11 (eg no SVRT or GPU acceleration) but you will need to create the custom profile ealier in the thread to aviod transoding issues.

https://dl.dropbox.com/u/59011278/FixPD9.zip

You may also want to read this thread esp on the bit on changes in the PS3 settings http://forum.cyberlink.com/forum/posts/list/17145.page;jsessionid=006FE7467F54E79255033880BBEDC48C

del output.m2ts eac3to.exe produce.m2ts 1: Video.h264 2: Audio.AC3 Pause tsmuxer pd9.meta output.m2ts pause del video.h264 del audio.ac3

When I use FixPD9 the Video & Audio is out of sync.
I have now solved the problem.
VideoReDo H264
Tools
QuickStream Fix

jmone, thanks for your help. Followed your recommendations, created and patched file with no B frames - now it plays fine and smoothly.
Yes, on two PC was tha latest PD11, on the third one was PD11 free demo, all three work in the same way.

dhnj, thanks for pinting tho this tool. I tried VideoReDo TV H264 demo. It does not fix neither PD11 rendered or FixPD output files. I creates a small file, and quits working. But what it does good, it allows to cu/joint original CAM files and smart-render them. After rendered file can be used straight to multiAVCH with no any additonal pathnig by FixPD needed. Authore files play smoothly as well.

I know that this is not the right place to talk about it. I just want to sare what I have found so far as working solution for smart rendering 1080p60 CAM files. I aslo tried one more tool: TMPGEnc MPEG Smart Renderer 4. Renered file needs to be "processed" by FixPD before inputting in to multiACHD. But it patches file nicely. Autored file play with no problems. I read and seen in mneu options, TMPGEnc MPEG Smart Renderer 4 can also author AVCHD 2.0. but it creates BDAV folders. I will try to burn them to DVD-R and test on my BD player. But I am not sure if BDAV files structe is reaaly accoroidng to AVHD spec. It is no AVCHxx folder in it. Some AVCHD player might not play this.