Movie is blank in PS3

[pkho]

I have done some Full Disc BD25 and Movie Only BD5. They works fine with HTPC and Sony S550 but not PS3. Disc start up fine with menus and all but when the movie start it is just blank with sound goes on. Is this a known issue or is there a simple fix?

[Ch3vr0n]

don't think the ps3 can read bd5's

[pkho]

PS3 works if the disc is build in Movie Only mode. I have many made in the past and they still works fine. My newly created disc are all black with sound going on. Too bad I can't start up those older versions of BDRebilder to test as they all expired.

[pkho]

I have done a test with the BD5. I demux the BDMV created by BDRebuilder with HDBRStreamExtractor, use mkvmerge to make a MKV file, put this MKV file into multiavchd and create another movie only disc. This time it works in PS3. I suspect something is wrong with the newer version of BDRebuilder as disc created by older versions still works.

[jdobbs]

I have done a test with the BD5. I demux the BDMV created by BDRebuilder with HDBRStreamExtractor, use mkvmerge to make a MKV file, put this MKV file into multiavchd and create another movie only disc. This time it works in PS3. I suspect something is wrong with the newer version of BDRebuilder as disc created by older versions still works.What version of BD-RB are you using? There was an issue with PS3 movie-only -- but it was fixed.

[pkho]

What version of BD-RB are you using? There was an issue with PS3 movie-only -- but it was fixed.

Thanks jdobbs. Just finished a new Movie Only job with the latest 32.05 and it works fine with PS3 now. Believe I have problem with the last 2 versions. Is the issue with Full Disc also fixed? Will try and see.

[jdobbs]

Thanks jdobbs. Just finished a new Movie Only job with the latest 32.05 and it works fine with PS3 now. Believe I have problem with the last 2 versions. Is the issue with Full Disc also fixed? Will try and see.There were some issues with an updated X264 NAL-HRD patch in the last couple of releases. I had to disable it and go with the baseline X264 for v0.32.05.

[shon3i]

There were some issues with an updated X264 NAL-HRD patch in the last couple of releases. I had to disable it and go with the baseline X264 for v0.32.05.
jdobbs, can you test with recent bulid 1.32 of HRD, previous versions had some problems, this lastest version follow BD specs, and pass verificators fine. As i saw someone alredy confirm that Panasonic players work with lastest HRD patch. Just please dont use tsMuxer to do this, because is realy mess

[jdobbs]

I don't mind telling you that I'm a lot more than hesitant. Those last couple of patched releases have gotten me more BD Rebuilder hate mail than anything I've done since I started this thing, and I don't have a panasonic player to test it...

I don't think I realized what a dumbass I was until all the "reminders" I've recently gotten (on this and the people who install non-working codec packs and then tell me its my fault, or refuse to use the versions of HAALI, FFDSHOW, and AVISYNTH I posted and then flame me in other forums).

[Discoboy]

I don't mind telling you that I'm a lot more than hesitant. Those last couple of patched releases have gotten me more BD Rebuilder hate mail than anything I've done since I started this thing, and I don't have a panasonic player to test it...

jdobbs, if you want to make a version of BD_RB that uses the newer NAL-HRD 1.32 build patched into a version of x264 with the NAL-HRD disabled in tsMuxer I can test on my Panasonic BD35 for you

[jdobbs]

jdobbs, if you want to make a version of BD_RB that uses the newer NAL-HRD 1.32 build patched into a version of x264 with the NAL-HRD disabled in tsMuxer I can test on my Panasonic BD35 for youCould you try this version. (http://www.jdobbs.net/freeware/BD-RBV03206.zip) It has NAL-HRD enabled and includes the latest Rack04 build with the 1.32 NAL-HRD patch. Please report back as soon as you have tested it.

Thanks.

[no.1_dark_knight]

Does the NAL-HRD patch add anything? the ps3 had problems with the prev. versions as well and thanks for the great work :)

[jdobbs]

Yes. While TSMUXER will add the information as it muxes -- it is not fully BD compliant. I've yet to find a player that noticed the difference... but it is still important that you remain as compliant as possible. You don't want to create a disc that you can't play in a couple of years when your next player suddenly gets strict. I doubt that will happen -- but I like to be careful.

If you wouldn't mind testing the new version (above) on the PS3 I'd appreciate it. I don't want to update the first post of the Bug Thread until I know for sure it isn't going to come back to bite me.

By the way, for those who want to avoid it anyway, the NAL-HRD command can always be disabled with the "USE_NAL_HRD=0" hidden option.

[Discoboy]

Could you try this version. (http://www.jdobbs.net/freeware/BD-RBV03206.zip) It has NAL-HRD enabled and includes the latest Rack04 build with the 1.32 NAL-HRD patch. Please report back as soon as you have tested it.

Thanks.

- V0.32.06 (beta) = NO Panasonic BD35 SAP playability (plays ok in pc based powerDVD 9) (movie only encode project) same prob as before it will not start to play just stays/hangs as the time duration of 0:00:00 :(

[jdobbs]

Thanks. Glad I checked... I've removed the link -- no sense letting it get out and cause more headaches.

[shon3i]

Hmm something wrong smells here.

Only thing that can be different from previous HRD bulds and maybe posssible reason is pic struct.

jdobbs can you make one more test buld and send directly to Discoboy (if he wants) to test it. This time add and --pic-struct to x264 command line.

[pkho]

There were some issues with an updated X264 NAL-HRD patch in the last couple of releases. I had to disable it and go with the baseline X264 for v0.32.05.

Great! Thanks. Full disc works again with 32.05 and PS3.

[jdobbs]

Hmm something wrong smells here.

Only thing that can be different from previous HRD bulds and maybe posssible reason is pic struct.

jdobbs can you make one more test buld and send directly to Discoboy (if he wants) to test it. This time add and --pic-struct to x264 command line. That can be done with the tweak command. I'm not sure what "--pic-struct" does though???

@Discoboy

Can you try the downloaded version again but add these lines to the "[Options]" area of the INI file?

TWEAK_PASS_ONE=--pic-struct
TWEAK_PASS_TWO=--pic-struct

It would be appreciated. Maybe we can find out what is making the Panasonic so problematic with NAL-HRD.

[Capsbackup]

jdobbs;
It appears there may be an issue with BD-RB when some subtitles are removed from the original order while others are kept, as I have now experienced this again with The Matrix Reloaded.
If all subtitles are kept, then the subs for the main video work correctly, and when I select to play the PiP secondary video/audio the subs for that audio track are correct.
If, however, I remove the several non-english subs after the main video's subs but before the secondary PiP subs, the PiP subs do not work, and are never displayed regardles if I select them from the remote or thru the menu.
EDIT:
I see these non Sony players are making things challenging for you right now, so sorry to bring up a different issue, not my intent to distract. :cool:
EDIT 2:
whoops! This was meant for the bug reports thread, sorry I misplaced.

[Discoboy]

That can be done with the tweak command. I'm not sure what "--pic-struct" does though???

@Discoboy

Can you try the downloaded version again but add these lines to the "[Options]" area of the INI file?

TWEAK_PASS_ONE=--pic-struct
TWEAK_PASS_TWO=--pic-struct

It would be appreciated. Maybe we can find out what is making the Panasonic so problematic with NAL-HRD.

Hi jdobbs and shon3i,

Project now completed using v0.32.06 (beta) 1-pass CFR encode with the following [option] lines added to the INI file for you:
TWEAK_PASS_ONE=--pic-struct
TWEAK_PASS_TWO=--pic-struct

- V0.32.06 (beta) = still NO Panasonic BD35 SAP playability (plays ok in pc based powerDVD 9) (movie only encode project) same prob as before it will not start to play just stays/hangs as the time duration of 0:00:00

BUT very interestingly I’ve have just tested for Atak a sample download he has made available for everyone to download that is using his very latest Ripbot264 a AVCHD sample made using the latest x264 and v1.32 nal-hrd enabled and this produced a playable AVCHD on my Panasonic BD35 SAP. :)

So this question is, what is difference between both BD_RB and Ripbot’s implementation and use of the latest x264 and latest v1.32 nal-hrd enabled to make one application produce a playable AVCHD and the other not?

[deank]

In his sample you can see the encoding settings:


Writing library : x264 core 89 r1471M 1144615
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3
:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16
/ chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 /
chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / nr=0 / decimate=1 / interla
ced=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / d
irect=1 / wpredb=1 / wpredp=2 / keyint=300 / keyint_min=30 / scenecut=40 / intra
_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=3425 / ratetol=1.0
/ qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_
maxrate=25000 / vbv_bufsize=25000 / ip_ratio=1.40 / aq=1:1.00 / pulldown=0 / nal
_hrd=vbr

Not to mention that there is no such resolution allowed in AVCHD/BD (or there is?):

Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16/9
Frame rate : 29.970 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Progressive

[Atak_Snajpera]

Not to mention that there is no such resolution allowed in AVCHD/BD (or there is?):
http://en.wikipedia.org/wiki/AVCHD#AVCHD_Lite

[shon3i]

Blu-ray support that combination only as secondary video, but not with that silly GOP ;).

Anyway i found one more important difference between that two.

BDRebulder use MKV as output for encoding which is bad because MKV muxer strip AUD data.

I reenode one BD overnight with V0.32.06, and resulting stream contain tons of errors, i chechek with BDQuest verifier. Stream is missing lot of data. Some players probably need this. When i encode i newer have these errors in video stream.

First AU in a GOP doesn't contain ordered NAL units
Error N.A. BDMV/STREAM/AU[23] 9.5.6 PES packet [22] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[24] 9.5.6 First byte of PES packet [23] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[24] 9.5.6 PES packet [24] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[25] 9.5.6 First byte of PES packet [24] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[25] 9.5.6 PES packet [25] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[26] 9.5.6 First byte of PES packet [25] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[26] 9.5.6 PES packet [26] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[27] 9.5.6 First byte of PES packet [26] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[27] 9.5.6 PES packet [27] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[28] 9.5.6 First byte of PES packet [27] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[28] 9.5.6 PES packet [28] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[29] 9.5.6 First byte of PES packet [28] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[29] 9.5.6 PES packet [29] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[30] 9.5.6 First byte of PES packet [29] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[30] 9.5.6 PES packet [30] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[31] 9.5.6 First byte of PES packet [30] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[31] 9.5.6 PES packet [31] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[32] 9.5.6 First byte of PES packet [31] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[32] 9.5.6 PES packet [32] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[33] 9.5.6 First byte of PES packet [32] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[33] 9.5.6 PTS and DTS are same, payload contains B picture, PTS_DTS_flag expected (2), found (3)
Error N.A. BDMV/STREAM/AU[33] 9.5.6 PES packet [33] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[34] 9.5.6 First byte of PES packet [33] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[34] 9.5.6 PES packet [34] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[35] 9.5.6 First byte of PES packet [34] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[35] 9.5.6 PES packet [35] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[36] 9.5.6 First byte of PES packet [35] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[36] 9.5.6 PES packet [36] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[37] 9.5.6 First byte of PES packet [36] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[37] 9.5.6 PTS and DTS are same, payload contains B picture, PTS_DTS_flag expected (2), found (3)
Error N.A. BDMV/STREAM/AU[37] 9.5.6 PES packet [37] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[38] 9.5.6 First byte of PES packet [37] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[38] 9.5.6 PES packet [38] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[39] 9.5.6 First byte of PES packet [38] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[39] 9.5.6 PES packet [39] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[40] 9.5.6 First byte of PES packet [39] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[40] 9.5.6 PES packet [40] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[41] 9.5.6 First byte of PES packet [40] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[41] 9.5.6 PTS and DTS are same, payload contains B picture, PTS_DTS_flag expected (2), found (3)
Error N.A. BDMV/STREAM/AU[41] 9.5.6 PES packet [41] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[42] 9.5.6 First byte of PES packet [41] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[42] 9.5.6 PES packet [42] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[43] 9.5.6 First byte of PES packet [42] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[43] 9.5.6 PES packet [43] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[44] 9.5.6 First byte of PES packet [43] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[44] 9.5.6 PES packet [44] contain more than 1 video access unit
Error N.A. BDMV/STREAM/AU[45] 9.5.6 First byte of PES packet [44] payload is not the first byte of video access unit
Error N.A. BDMV/STREAM/AU[45] 9.5.6 PTS and DTS are same, payload contains B picture, PTS_DTS_flag expected (2), found (3)

@jdobbs, please one more test buld that output encode as raw .264 stream instead MKV?
@Discoboy please if you can test agiain

I think that's why somebody with BD35 says that everything workfine

EDIT: i found http://forum.doom9.org/showthread.php?p=1380101#post1380101

[Atak_Snajpera]

Blu-ray support that combination only as secondary video, but not with that silly GOP
Silly GOP? x264 by default uses keyint=250 / keyint_min=25. I use keyint=fps*10 / keyint_min=fps. So you claim that x264 developers decided to use silly defaults?

[shon3i]

Do you when encode follow H264 or BD standard? for BD/AVCHD

If for BD (and maybe for AVCHD) here what is allowed.

http://tom.niko.users.sbb.rs/gop.jpg

Full stop.

[Atak_Snajpera]

Do you when encode follow H264 or BD standard? for BD/AVCHD
AVCHD (level 4.0) seems to be less strict than you think. As you can see this resolution with this frame-rate is not mentioned anywhere. Also this 'silly GOP' should not be supported either. However it still works on Sony,Samsung and Panasonic blu-ray players. Blu-ray standard seems to be more 'silly' in this matter. Slices , short GOP and other stupid s**t.

[jdobbs]

Blu-ray support that combination only as secondary video, but not with that silly GOP ;).

Anyway i found one more important difference between that two.

BDRebulder use MKV as output for encoding which is bad because MKV muxer strip AUD data.

I reenode one BD overnight with V0.32.06, and resulting stream contain tons of errors, i chechek with BDQuest verifier. Stream is missing lot of data. Some players probably need this. When i encode i newer have these errors in video stream.



@jdobbs, please one more test buld that output encode as raw .264 stream instead MKV?
@Discoboy please if you can test agiain

I think that's why somebody with BD35 says that everything workfine

EDIT: i found http://forum.doom9.org/showthread.php?p=1380101#post1380101 I just wonder why that problem would only occur in the NAL-HRD version?

The intermediate file can be changed to .264 by adding this line to the "[Options]" area of the INI file:

MKV_INTERMEDIATE=0

@Discoboy

Want to give it a try?

Thanks...

[shon3i]

Because Tsmuxer replace all data need for BD compilacy, AUD, SPS NAL's everything. if you feed stream with partial data tsmuxer will not rewrite stream and it mux stream with broken AUD's. If you feed completly clean stream tsmuxer will add NAL-HRD, AUD, SPS completly new.

[jdobbs]

AVCHD (level 4.0) seems to be less strict than you think. As you can see this resolution with this frame-rate is not mentioned anywhere. Also this 'silly GOP' should not be supported either. However it still works on Sony,Samsung and Panasonic blu-ray players. Blu-ray standard seems to be more 'silly' in this matter. Slices , short GOP and other stupid s**t.

The rules are that the GOP should be no longer than 1 second but lowered bitrate can make it longer:

"... allows a GOP whose period is longer than 1 second (*1) on condition that the
maximum bit-rate of an MPEG-4 AVC stream is less than or equal to 15*10^6 bits/second. In this case,
length of GOP can be up to 2 seconds (*2)."

It's safest to set the keyint to 1 second intervals.

[jdobbs]

Because Tsmuxer replace all data need for BD compilacy, AUD, SPS NAL's everything. if you feed stream with partial data tsmuxer will not rewrite stream and it mux stream with broken AUD's. If you feed completly clean stream tsmuxer will add NAL-HRD, AUD, SPS completly new.Hmmm... makes sense I guess. But what's confusing is that previous X264 versions with the NAL-HRD patch (e.g. r1376) worked with no issues on the Panasonic and PS3 with an MKV intermediate.

[shon3i]

Well maybe that you use Trahald HRD which completly different that current HRD which is more strict. Beside this BDQuest report one more error which i don't like

This error is not present if i mux raw streams with Tsmuxer directly form WORKFILES folder, and or with Sonic Scenarist.

Error N.A. BDMV/STREAM/00000.m2ts->PMT 9.3.4 Incorrect 'descriptor_tag' found (0xa) This error show's with MKV and RAW, i suppose something added/pached after muxing.

[jdobbs]

Well maybe that you use Trahald HRD which completly different that current HRD which is more strict. Beside this BDQuest report one more error which i don't like

This error is not present if i mux raw streams with Tsmuxer directly form WORKFILES folder, and or with Sonic Scenarist.

This error show's with MKV and RAW, i suppose something added/pached after muxing. It wouldn't be added by BD-RB... the only thing I would ever touch in the M2TS after muxing might be to fix SCR, PTS & DTS in special circumstances -- and even that would only happen very, very rarely -- and never on a movie-only encode.

You may want to try using the "MUX_MOVIE_ONLY.meta" file to do the TSMUXER direct mux and see if it acts differently.

[Discoboy]

I just wonder why that problem would only occur in the NAL-HRD version?

The intermediate file can be changed to .264 by adding this line to the "[Options]" area of the INI file:

MKV_INTERMEDIATE=0

@Discoboy

Want to give it a try?

Thanks...

Testing now, back within 1 hour with the results for you...

[shon3i]

It wouldn't be added by BD-RB... the only thing I would ever touch in the M2TS after muxing might be to fix SCR, PTS & DTS in special circumstances -- and even that would only happen very, very rarely -- and never on a movie-only encode.

You may want to try using the "MUX_MOVIE_ONLY.meta" file to do the TSMUXER direct mux and see if it acts differently.

I found, it's not caused by BDRebulder, aslo this error present in Source BD

now we wait moment of truth :)

[jdobbs]

@shon3i

I'm looking for things that might make BD-RB's output different from a standard done-by-hand TSMUXER blu-ray mux. One thing I just thought of... in BD-RB the source is actually run through TSMUXER twice when doing a movie-only encode. Once immediately following encode to create an M2TS and CLPI file pair (because it uses code that is common to non-movie-only), and then again to create the movie-only structure. The second one uses the first M2TS as its input.

Do you think some goofiness may be introduced by the two steps (using TSMUXER output as TSMUXER input) that is only seen with NAL-HRD?

[Discoboy]

I just wonder why that problem would only occur in the NAL-HRD version?

The intermediate file can be changed to .264 by adding this line to the "[Options]" area of the INI file:

MKV_INTERMEDIATE=0

@Discoboy

Want to give it a try?

Thanks...

@ jdobbs and @shon3i

Project now completed using v0.32.06 (beta) 1-pass CFR encode with the following [option] line added to the INI file for you:
MKV_INTERMEDIATE=0

- V0.32.06 (beta) = OK Panasonic BD35 SAP .... Success at last :)

Now looking forward to the offical release of V0.32.07 (beta)... ;)

[jdobbs]

Thanks shon3i and Discoboy for helping find this.

Interesting that the reason I changed the intermediate file to MKV was because of another player that had sync issues when .264 was used. That one, though, was definitely an issue on the player side, not BD-RB. I moved it to MKV because I thought it could do no harm... so much for assumptions. :) I'll leave the MKV_INTERMEDIATE hidden setting in the options settings, but will change the default to "0" and NAL-HRD will not be used when it is selected.

[shon3i]

@shon3i

I'm looking for things that might make BD-RB's output different from a standard done-by-hand TSMUXER blu-ray mux. One thing I just thought of... in BD-RB the source is actually run through TSMUXER twice when doing a movie-only encode. Once immediately following encode to create an M2TS and CLPI file pair (because it uses code that is common to non-movie-only), and then again to create the movie-only structure. The second one uses the first M2TS as its input.

Do you think some goofiness may be introduced by the two steps (using TSMUXER output as TSMUXER input) that is only seen with NAL-HRD?
Its completly same because in frist you mux MKV that alredy strip AUD's to M2TS, and second remux M2TS to M2TS which is totaly lossless :) So nothing wrong here.

Interesting that the reason I changed the intermediate file to MKV was because of another player that had sync issues when .264 was used. This can be only happend because raw 264 file not contain fps, and tsmuxer assume 23.976, so if that guy have movie with for example 24fps or some other fps.

- V0.32.06 (beta) = OK Panasonic BD35 SAP .... Success at last
Btw, i am glad we finaly solove this mistery :) Thanks both you so much :)

[shon3i]

And you should put --pic-struct as default, is not mandatory for progressive encodes but verifiers generate error for it.

[Sharc]

If we eventually get a blu-ray compliant .h264 stream with latest x264 builds, will it be preserved by the muxing with TSmuxeR or will it alter again the AUD and NAL-HRD ...?

[shon3i]

If we eventually get a blu-ray compliant .h264 stream with latest x264 builds, will it be preserved by the muxing with TSmuxeR or will it alter again the AUD and NAL-HRD ...?
Yes, if you use lastest possible version of tsmuxer (1.10.6), in earlier version tsmuxer automaticly replace HRD/AUD, now detect first stream if not present then add, but can fix partialy streams like we have here :). tsmuxer if change something in stream, automatcy inform user with messages:

H264 bitstream changed: insert nal unit delimiters
H264 bitstream changed: insert pict timing and buffering period SEI units

So if you get one these messages during mux, you know that tsmuxer change stream, which is not good if you know that stream is completly BD compilant.

[Sharc]

Thank you for explaining.

[jdobbs]

@Discoboy

The bug thread has the new version posted.

[Discoboy]

And you should put --pic-struct as default, is not mandatory for progressive encodes but verifiers generate error for it.

@jdobbs,

What about shon3i’s suggestion to still include --pic-struct as default?

[Discoboy]

@Discoboy

The bug thread has the new version posted.

@jdobbs,
Am testing now..

[jdobbs]

@jdobbs,

What about shon3i’s suggestion to still include --pic-struct as default? I want to take one step at a time (that and I didn't notice that post till you quoted it :)).