Hi everyone,

Build 2403, the latest beta, has fixed the SVRT issue in 'Create Disc'. Projects fly through now just as they should.

Cheers,

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

Still seems to produce CLPI/MPLS using 240 headers. 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: Looks to me as if clpi and mpls issues are fixed with NTSC but not PAL. SVRT won't work in either as "Produce" uses a 3, 13 GOP structure and "Create Disc" uses a 3, 16 GOP structure. For NTSC you can create a proper GOP profile with a edit of profile.ini, and then SVRT will work in "Create Disc". Have not played with PAL profiles. Not sure of the CL intent behind using different GOP structure between "Produce" and "Create Disc" for the same default profile.

The "Create Disc" feature in patch 2403 now creates a 3, 13 GOP (IPBBPBBPBBPBB) structure when creating 1920x1080 50p PAL or 60p NTSC BD's, so it now agrees with the "Produce" output specifications of the same formats.

Apparently there was no CL intent to using different GOP lengths between "Produce" and "Create Disc" for the same default profile, just a hack perhaps and now changed in patch 2403. Shorter length GOP's usually desirable during fast transitions or quick camera pans.

Jeff

Quick test producing 1080/50p BD post the patch (CPU Encoding)

Using my Original 1080/50p Camcorder Footage the output was the same structure GOP (24): IBBPBBPBBPBBPBBPBBPBBPBB
Using a Still Picture (ballon.jpg) and then "Boats.wmv" the output was the same as before GOP (16): IPBBPBBPBBPBBPBB

I'm guessing that PD will adjust the GOP to match that of the input where it can ???
1) Andrew is seeing SVRT Work any my input now matches my output for AVC content
2) Jeff is getting a different GOP Structure (Jeff was is the GOP of the source file in your test?) and I get the std one they used before with non AVC content.

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

Quote: I'm guessing that PD will adjust the GOP to match that of the input where it can ???

Based on what I have gleaned over the years from various footage, to my knowledge it appears to.

Quote: 1) Andrew is seeing SVRT Work any my input now matches my output for AVC content
2) Jeff is getting a different GOP Structure (Jeff was is the GOP of the source file in your test?) and I get the std one they used before with non AVC content.

My observation was that PD was not consistent with itself, this created an issue when one has mixed footage and "Produces" several segments matching desired final output format to build a final product with, only to have everything encoded again. Now what one "Produces" in format 50p/60p will just go to disc with SVRT in "Create Disc" and not be encoded again, essentially your balloon and boats test.

Jeff

Quote: Hi,
I have no official comment, I did have a reply that made an observation which I will share.

We followed the latest BD spec we got to make the profile. As explained previously (see previous post), current BD player or tools may just follow current "official" spec to verify the disc, it is expected that errors happen.

We don't know what will be the effects if using tools to modify the header. It might make the disc can not be played back in the BD player, which support 50P/60P BD disc, in the future.

That's all I have.
Dafydd

FYI - I passed the info on the "new" header values to the the Developer of LAV Filters and these disks now play.

So it looks like you will only need my patcher if your player does not support the 240 headers for CLPI/MPLS and you are unable to update it, eg for SW/HW that is no longer being developed/supported (eg TMT, BDEdit, some HW players).

Thanks for following up Dafydd.

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

PD 13 I can burn AVCHD disc 1920x1080/50P and it works fine both sound and picture with bd player.
I can burn Blu-ray H264 1920x1080/50P and it works fine with computer bd player but only sound work and no video with home bd player.
please can any one help hj

Hi,

jmone has posted a fix on page 5 for this. Give it a try and let us know how you get on.

Cheers,

Andrew Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

Quote: OK, I have found the incompatibility issue on the CLPI/MPLS created using PD's BD 1080/50 or 60p profile. From what I understand (and as I don't have the standard I could be wrong!);

Blu-ray file headers are typically
- index.bdmv: INDX0200
- MovieObject.bdmv: MOBJ0200
- PLAYLIST *.mpls: MPLS0200
- CLIPINF *.clpi: HDMV0200

AVCHD file headers are typically
- index.bdmv: INDX0100
- MovieObject.bdmv: MOBJ0100
- PLAYLIST *.mpls: MPLS0100
- CLIPINF *.clpi: HDMV0100

When using the BD 1080/50 or 60p profile, PD is creating the file headers as follows
- index.bdmv: INDX0200
- MovieObject.bdmv: MOBJ0200
- PLAYLIST *.mpls: MPLS0240
- CLIPINF *.clpi: HDMV0240

I can find no reference to what the "0240" header value may be related to, it could be a simple error on CLink's part, or.... for all I know, CLink is aware of a new header value that has not hit the public domain yet..

Anyway, it is clear some disk readers are hitting this unknown header value and producing an error, yet others ignore it and push on.

If I edit these headers back to "0200" using a Hex Editor then all is good and the disks play as they should and the rest of the meta data is correct. This is the only change needed.

I've attached:
- BD50p.zip : BD 1080/50p as created by PD
- BD50p - Fixed.zip : BD 1080/50p as created by PD with the header values edited back to 0200

Hope this helps.
Thanks
Nathan

===========================================

Happy New Year everybody and thanks Nathan.

I assume this is good for 50 an 60P and needs to be re installed after every PD update?

Eugene


73s, WA6JZN ex DL9GC
CYBERLINK PLEASE ADD UHD BLU RAY BURNING SOFTWARE
PD14,
Win10,64bit.CPU i7 6700,16GB ,C= 480 GB SSD ,GPU GTX1060 6GB 1 fan. Plus 3 int, 4 ext HDD's for video etc.LG WH16NS40 reads UHD.
4K 24" ViewSonic monitor.Camera Sony FDR-A

Hi,

I created 50GB disc, I can copy from the created disc but I cant add to it and if I follow the instruction and

Copy the "BDMV" and "Certificate" folders of BD I created to be "fixed" directly under the the "BD_To_Fix" subfolder
and run "BD50_60p_fix.bat" will this automatically fix the files in the disc itself or please explain in simple terms the procedure. thank you.
hj

Hi,

I created 50GB disc, I can copy from the created disc but I cant add to it and if I follow the instruction and

Copy the "BDMV" and "Certificate" folders of BD I created to be "fixed" directly under the the "BD_To_Fix" subfolder
and run "BD50_60p_fix.bat" will this automatically fix the files in the disc itself or please explain in simple terms the procedure. thank you.
"

hj

Hi haj52,
The workflow would be:
- First, Output your project to a directory on your HDD (not a BD)
- Then apply the BD_To_Fix
- Then burn these folders to your physcial BD (you will need a prog like ImgBurn to do this

See how that goes then in your player

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

Quote:
I assume this is good for 50 an 60P and needs to be re installed after every PD update?

Hi Eugen, this fix does not change how PD creates the output but actually modifies the Headers on the files created by PD and will work on both 60 and 50p. Eg you have to apply it each time you create a final output prior to burning to disk. 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: PD 13 I can burn AVCHD disc 1920x1080/50P and it works fine both sound and picture with bd player.
I can burn Blu-ray H264 1920x1080/50P and it works fine with computer bd player but only sound work and no video with home bd player.
please can any one help

FYI... if all your players work with the AVCHD option then you can just use this profile instead of the Blu-ray one. Both contain the same high quality bitrate & progressive encoding of the video, it is just the "disk structure" that is different (not the content).

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

hi,

AVCHD uses DVD max 8.5Gb can burn only for 40 min max while Blu-ray uses 50GB where you can add more videos hj

True - though have a read of the posts on the first page of this thread on how to create larger sized AVCHD projects. 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 Output to a directory on HDD

copied BDMV and Certificate Folders to BD_To_fix folder

run BD50_60p_fix.bat

used XVI32.exe and checked
PLAYLIST *.mpls: MPLS0200
- CLIPINF *.clpi: HDMV0200

- Then burn these folders to BD using prog ImgBurn

result audio only no video

hj

Hi,

I created larger sized AVCHD project as mentioned and when I play bd disc either in computer or bd player warning this is AVCHD 2.0 format and this media player does not currently support hj

So it seems your best bet is to use the AVCHD profile with one of the workarounds to burn to BD media (as from what you say it appears to work on your player).

It may be your BD player does not like 50p BD even with the header edits, but it could be a different issue however (eg when burning the AVCHD that works did you use any different settings like HW Acceleration On / Off or Menu On / Off etc?). What happens if you just take the main M2TS file and try to play it on the BD player? 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: Hi,

I created larger sized AVCHD project as mentioned and when I play bd disc either in computer or bd player warning this is AVCHD 2.0 format and this media player does not currently support

sorry missed this when posting above. To confirm, have you had any 1080/50p disk work on your BD Player? 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

yes I did hj