BD Rebuilder Beta - Bug Reports Only

[drmih]

HI!
Thanks for the advice, point taken! But as stated its a bug report, and its not a pirated copy so I dont see the problem. In the future i will wait until the official release date to post any bug i may encounter, I'm sorry for wasting space in this issue.

I'll report back if the problem is still there on September 1st. Again sorry for the confusion!

I've also just had a quick look at Gladiator and it does seem to be fine on the original but bd-rb seems to have problems - as this may be something 'new' I thought I'd supply the information I gathered incase jdobbs can see anything obvious. Basically as soon as you open the directory you get an error (I have copied the error to the top of the log file). I did continue and the encoding process had no issues until the rebuild when it failed trying to integrate the files - the actual m2ts files created are all fine within the WORKFILES directory.

If you can see if this matches your findings it would help.

[DaMacFunkin]

Are they actually blanked? There is a setting to treat field based sources via mkvmerge but if this is not the default then any sources will be blanked.

Dunno m8, they don't show the "blank" image, just black screen.

[Kakashi Sensei]

I've also just had a quick look at Gladiator and it does seem to be fine on the original but bd-rb seems to have problems - as this may be something 'new' I thought I'd supply the information I gathered incase jdobbs can see anything obvious. Basically as soon as you open the directory you get an error (I have copied the error to the top of the log file). I did continue and the encoding process had no issues until the rebuild when it failed trying to integrate the files - the actual m2ts files created are all fine within the WORKFILES directory.

If you can see if this matches your findings it would help.

I honestly didn't want to cause anymore probs in the bug report. I didn't finish the encode as you stated it couldn't rebuild. I'm not sure why I'm getting the error as soon as it loads up the files. I did notice it didn't have an AUXDATA folder and added a blank one myself so it'll play in TMT3 or PowerDVD.

really thats the only thing i can tell other then that they didn't use 2 different M2TS files for regular/Extended cut. It seems all mixed up like a puzzle.

KS

[drmih]

I honestly didn't want to cause anymore probs in the bug report. I didn't finish the encode as you stated it couldn't rebuild. I'm not sure why I'm getting the error as soon as it loads up the files. I did notice it didn't have an AUXDATA folder and added a blank one myself so it'll play in TMT3 or PowerDVD.

really thats the only thing i can tell other then that they didn't use 2 different M2TS files for regular/Extended cut. It seems all mixed up like a puzzle.

KS

The disc is fine and plays fine in TMT3 once ripped to a pc HDD. The way they have done it is that rather than being the 'director's cut' this is the theatrical and extended versions - therefore there are just extra scenes put into the theatrical version. Rather than waste space (and theoretically quality) they have broken the original and extended scenes into individual m2ts files and then the playlist just picks up the required files so that you don't have any duplication. The encode that bd-rb did seems fine and the relevant m2ts files are redone and in the WORKFILES directory along with their clpi files.

It suprising as this has been done in conjunction with a new cinema release which is digitally remastered that the quality is perhaps not the best.

All I was asking was for you to confirm the same error codes as I have listed - once the attached file is approved.

[Kakashi Sensei]

The disc is fine and plays fine in TMT3 once ripped to a pc HDD. The way they have done it is that rather than being the 'director's cut' this is the theatrical and extended versions - therefore there are just extra scenes put into the theatrical version. Rather than waste space (and theoretically quality) they have broken the original and extended scenes into individual m2ts files and then the playlist just picks up the required files so that you don't have any duplication. The encode that bd-rb did seems fine and the relevant m2ts files are redone and in the WORKFILES directory along with their clpi files.

It suprising as this has been done in conjunction with a new cinema release which is digitally remastered that the quality is perhaps not the best.

All I was asking was for you to confirm the same error codes as I have listed - once the attached file is approved.
Yeah for sure! i dont mind at all. Sorry about that, little misunderstanding :P

[Furiousflea]

The disc is fine and plays fine in TMT3 once ripped to a pc HDD. The way they have done it is that rather than being the 'director's cut' this is the theatrical and extended versions - therefore there are just extra scenes put into the theatrical version. Rather than waste space (and theoretically quality) they have broken the original and extended scenes into individual m2ts files and then the playlist just picks up the required files so that you don't have any duplication. The encode that bd-rb did seems fine and the relevant m2ts files are redone and in the WORKFILES directory along with their clpi files.

It suprising as this has been done in conjunction with a new cinema release which is digitally remastered that the quality is perhaps not the best.

All I was asking was for you to confirm the same error codes as I have listed - once the attached file is approved.

There's nothing "new" going on, most "Director's Cut" discs use the method of having multiple m2ts with 1 playlist referencing extra scenes.

Director's Cut = Extended Cut ;) in 95% of cases. Sure there are some lazy discs with 2 seperate versions but that's the exception.

[drmih]

There's nothing "new" going on, most "Director's Cut" discs use the method of having multiple m2ts with 1 playlist referencing extra scenes.

Director's Cut = Extended Cut ;) in 95% of cases. Sure there are some lazy discs with 2 seperate versions but that's the exception.

The 'new' thing going on is that it causes a bug in bd-rb when it tries to scan the directory - this has been identified by at least two different sources - not the breakdown of the m2ts files which I was explaining for Kakashi Sensei's benefit. Please read the original post rather than jumping in half way on the wrong thing.

[Kakashi Sensei]

There's nothing "new" going on, most "Director's Cut" discs use the method of having multiple m2ts with 1 playlist referencing extra scenes.

Director's Cut = Extended Cut ;) in 95% of cases. Sure there are some lazy discs with 2 seperate versions but that's the exception.

LOL cool thats good to know, i guess its just "new" to me. All the other disc's I have were done that way, Coraline for 3d (i guess it had to be done that way) Golden Compass. Trust me i prefer the multiple nultiple M2TS way as it saves space for better video. I always wondered why they would do 2 of the same movie on one disc, guess it is lazy.

I'm new to BD Authoring but i'm not that new ;)

[Chefkoch_ico]

Hi.

Win7 is really a pain in the ***. In MPC the WMVideo DMO Filter for m2ts with VC1 is loaded normally. Also Haali is loaded.

But not for AVS. There Haali is loaded but the script times out (if opened via x264 or MPC).

I tried alot of things suggested here or on other sites (I have not yet tried with other filters than WMVideo DMO, since it works with MPC)

If you could NOT overwrite the AVS file when an encode is started, when it already exists, we could prepare our own AVS scripts (for example with a working graph file).

Thx and best regards

[Furiousflea]

The 'new' thing going on is that it causes a bug in bd-rb when it tries to scan the directory - this has been identified by at least two different sources - not the breakdown of the m2ts files which I was explaining for Kakashi Sensei's benefit. Please read the original post rather than jumping in half way on the wrong thing.

Think you'll find I was the 1st person to report the problem with Gladiator last week ;)

The breakdown of the m2ts files is likely not the problem since BDRB has backed up similar discs with no problem in the past (King Kong for example uses this method). The problem most likely is an unintentional authoring error, the disc as a whole feels very badly made with "AUXDATA" folder missing etc.

edit - looks like your saying the same thing...sorry about that...there's me jumping the gun again.

[Furiousflea]

Hi.

Win7 is really a pain in the ***. In MPC the WMVideo DMO Filter for m2ts with VC1 is loaded normally. Also Haali is loaded.

But not for AVS. There Haali is loaded but the script times out (if opened via x264 or MPC).

I tried alot of things suggested here or on other sites (I have not yet tried with other filters than WMVideo DMO, since it works with MPC)

If you could NOT overwrite the AVS file when an encode is started, when it already exists, we could prepare our own AVS scripts (for example with a working graph file).

Thx and best regards

Not supported yet

[Kakashi Sensei]

Think you'll find I was the 1st person to report the problem with Gladiator last week ;)

The breakdown of the m2ts files is likely not the problem since BDRB has backed up similar discs with no problem in the past (King Kong for example uses this method). The problem most likely is an unintentional authoring error, the disc as a whole feels very badly made with "AUXDATA" folder missing etc.

edit - looks like your saying the same thing...sorry about that...there's me jumping the gun again.
Not meaning to go off topic but the funny thing is these are supposed to be "sapphire edition" releases from Paramount which they are boasting to have extra care taken to create the Blurays and have superior video quality, I think they missteped with this one. I'm dreading to see what they do with Braveheart and Forrest Gump :(

[GaPony]

Hi.

Win7 is really a pain in the ***. In MPC the WMVideo DMO Filter for m2ts with VC1 is loaded normally. Also Haali is loaded.

But not for AVS. There Haali is loaded but the script times out (if opened via x264 or MPC).

I tried alot of things suggested here or on other sites (I have not yet tried with other filters than WMVideo DMO, since it works with MPC)

If you could NOT overwrite the AVS file when an encode is started, when it already exists, we could prepare our own AVS scripts (for example with a working graph file).

Thx and best regards

If you use Windows 7, you probably use a dual boot system of some sort. Just put BD Rebuilder on your other system and wait for Win 7 to be supported after its official release.

It doesn't make alot of sense reporting problem with an OS that isn't supported at the moment and pre or post processing just eliminates any potential for jdobbs to even consider advising on the subject. It has absolutely nothing to do with bugs in BD Rebuilder... you're just out there on your own for now.

[Groucho2004]

It doesn't make alot of sense reporting problem with an OS that isn't supported at the moment

...and hasn't even been released yet! JDobbs should probably put a note in the first post listing the supported OS's. In bold. In the first paragraph. And even then some people will still ignore it, I guess.

[Chefkoch_ico]

...and hasn't even been released yet! JDobbs should probably put a note in the first post listing the supported OS's. In bold. In the first paragraph. And even then some people will still ignore it, I guess.

I know Win7 is not supported yet. Anyway its not a BD-RB problem, its in DirectShow. Thats why I decided to post it here and point out a way how an experienced user could make it work.

BD-RB itself works fine with Win7.

If you want to know, I have a MSDN account and I was able to get the final Version from there.

Its basically its the only problem I ran into when using this OS, so if jdobbs decides to support this OS somewhen its good to know, where the problems are.

Bye

[Groucho2004]

If you want to know, I have a MSDN account and I was able to get the final Version from there.

You're missing the point. Most people are using public betas or realease candidates of W7.

There are plenty of API changes in W7 which a developer has to consider. The fact that BD-RB works for you on W7 doesn't mean that it will behave the same way in all situations and configurations as it would on XP.

However, I suppose it would be helpful for jdobbs if someone who is actually running the RTM build of W7 reported problems with BD-RB for future reference.

[Furiousflea]

You're missing the point. Most people are using public betas or realease candidates of W7.

There are plenty of API changes in W7 which a developer has to consider. The fact that BD-RB works for you on W7 doesn't mean that it will behave the same way in all situations and configurations as it would on XP.

However, I suppose it would be helpful for jdobbs if someone who is actually running the RTM build of W7 reported problems with BD-RB for future reference.

Yep pretty much. I've been using the RTM for the past month with the usual problem of Windows 7 insisting on using it's own h264 decoder along with VC1 decoding not working because it's not supported outside of media player. With the known registry edit there are no problems at all using Windows 7 - But that's up to the user to sort out, like you say.

There really aren't any changes in Windows 7 that cause any serious issues that aren't resolvable with some pretty basic meddling that is fully documented.

Although I'm with you in that this isn't jdobbs problem and really wish the ignorant (no offense) would at least do a bit of googleing to sort out the issue themselves. It's just plain annoying, it just appears lazy really.

[Imperial Zeppelin]

BD-RB has locked up 3X on this in the same spot. I used AnyDVD HD to rip to disc. I tried 2X with new rips from one disc and then got another disc and ripped that. All locked up at the same point.

I have been successful backing up multiple BD-25s including the 1st 2 Pirate BDs as well as BD-5s with this setup so it's not hardware/drivers/software.

Anyone got any ideas?

Here's the log:

[05:03:00] BD Rebuilder v0.28.03 (beta)
- Source: PIRATES3
- Input BD size: 41.93 GB
- Approximate total content: [03:05:16.980]
- Target BD size: 22.46 GB
[05:03:05] PHASE ONE, Encoding
- [05:03:05] Extracting A/V streams [VID_00001]
- [05:15:38] Reencoding: VID_00001 (1 of 14)
- [14:07:30] Extracting A/V streams [VID_00002]
- [14:07:31] Reencoding: VID_00002 (2 of 14)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[14:07:33] - Failed video encode, aborted

Here's the INF file:
[Status]
LABEL=PIRATES3
VERSION=v0.28.03 (beta)
SOURCE_SIZE=45025676366
SOURCE_VIDEO_SIZE=44407148544
TARGET_SIZE=24117248000
REDUCTION=.529165257136849
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=0
QUICK=0
ENCODE_STEP=2
COMPLETED=1
[00001]
AUDIO=1100
PGS=10000
M2TS_TARGET=21956407025
RATE=7910
NSIZE=20763838464
FLINK=0
MLINK=0
[00002]
AUDIO=
PGS=
M2TS_TARGET=19507
RATE=500

[GaPony]

Beta v.23.04 is the current version. You might try using that.

I copied all the POTC movies back in January or February (Movie Only to BD9), so it must be a setting someplace.

Did you happen to try restarting the process (resume)?

[Furiousflea]

More than likely just a case of the m2ts being too small to be encoded properly...look through changes.txt for how to set the minimum m2ts size to encode.

I've done all 3 POTC films on BD25 with no issues.

[setarip_old]

I'm sure "GaPony" meant v.28.04 and not v.23.04 ;>}

[Imperial Zeppelin]

v.28.03 and the previous version did puke on it. I'll try 28.04, but I'm not holding by breath. I'm wondering if an older version may be the ticket. I may also try movie only if I can't get past this impasse...

Yes, I've tried resuming when getting the error and it immediately errors again.

[Capsbackup]

Anyone got any ideas?



VID_00002.m2ts is a 0.04 MB blank clip, and is part of the .mpls of VID_00001.m2ts, so BD-RB wants to reencode it to make sure it is compliant. I don't believe you can set MIN_M2TS_SIZE for this instance.
I thought this problem was corrected. :confused:
You should not have a problem with movie only.
You might try the High-Speed Option, One Pass (CRF) Encoding, and "Quicker" Encode for Extras with BD-RBV02804, just in case it does not work again you will find this out quicker. :(

[Imperial Zeppelin]

28.04 puked too so the problem has not been resolved. Will try Movie Only I guess, but will give One Pass a shot first...

Thanks Folks!

UPDATE: The One Pass / High Speed / Quicker Encode for Extras worked fine. I'll try the INI suggestion listed below and report back.

[Capsbackup]

28.04 puked too so the problem has not been resolved. Will try Movie Only I guess, but will give One Pass a shot first...

Thanks Folks!

I don't know if this will have any benefit, but others have reported doing full movie backups to BD-25 successfully before, and as of v0.22.01, BD-RB did make this change:
( BD-RB now uses the MKV intermediate file format as
the default for rebuilds. If for some reason you
wish to force the use of .264 files as the default
(as in prior BD-RB releases) add this switch to
the config (.INI) file: "MKV_INTERMEDIATE=0")
So you could test "MKV_INTERMEDIATE=0".
Probably will have no consequence, but worth a shot.

[setarip_old]

@jdobbs

Hi!

Regarding "Watchmen", you said,I'm pretty sure it is a TSMUXER issue.That may not be the case. If you read my post #4863 to this thread, you'll see that by using "MakeMKV" to rip the 44 chapter, no subs movie-only (Which is actually bigger in filesize than the so-called "Director's Cut" video, which contains only 13 chapters, while covering close to the same running time as the movie-only) and using "tsMuxeR" (v.1.10.6) to convert to a BluRay "package", you'll have a perfectly performing (Chapter jumps and all) "package" containing a 27.4Gb M2TS file ready to be processed by BD-RB ;>}

Since it's obvious that the movie-only and the Director's Cut share some A/V data (Otherwise the disc would be over 60Gb in total combined filesize, including extras), the difficulties being encountered may have to do with this.

BTW - I'd suggest you watch the "Director's Cut", as I believe it uses "unusual" techniques for using this "shared" data.

[Race Guy]

Just did a full "HQ/fast on extras", v28.04 backup to BD-25 of "Live From Abbey Road".

All the "functions" work perfectly on the BU. The issue is the quality of the video. The flick is a BBC TV show, done using hand held & robotic cameras, so there's a LOT of "pans & zooms". It's a VERY "nervous" production!

Watching the BU on my Oppo, when they do certain pans, there's a "stutter" to the video. It's VERY distracting! When the camera is steady or zooming, it's beautiful, indistinguishable from the original.

It seems to happen the most on medium speed pans. It's almost like a "strobe" effect. The camera starts moving, the picture "defocuses" with "motion blur", then it seems to freeze & snap into focus for a frame or two, then it defocuses, etc...., etc. It's hard to gauge timing between "stutters", 'cause the pans don't last very long, but I'd guess 4 to 5 times per second. It is NOT a good look, I'd even go so far as to say it's "unwatchable"! If I spin my original, there's no hint of it.

I'd guess it's an x264 issue, but since it's part of the "package" I'd say it's DEFINITELY a bug! According to the Oppo's info, it calls the video "AVC BDMV" @ 29.97fps.

Any thoughts on how to eliminate the stutter?

[drmih]

Just did a full "HQ/fast on extras", v28.04 backup to BD-25 of "Live From Abbey Road".

All the "functions" work perfectly on the BU. The issue is the quality of the video. The flick is a BBC TV show, done using hand held & robotic cameras, so there's a LOT of "pans & zooms". It's a VERY "nervous" production!

Watching the BU on my Oppo, when they do certain pans, there's a "stutter" to the video. It's VERY distracting! When the camera is steady or zooming, it's beautiful, indistinguishable from the original.

It seems to happen the most on medium speed pans. It's almost like a "strobe" effect. The camera starts moving, the picture "defocuses" with "motion blur", then it seems to freeze & snap into focus for a frame or two, then it defocuses, etc...., etc. It's hard to gauge timing between "stutters", 'cause the pans don't last very long, but I'd guess 4 to 5 times per second. It is NOT a good look, I'd even go so far as to say it's "unwatchable"! If I spin my original, there's no hint of it.

I'd guess it's an x264 issue, but since it's part of the "package" I'd say it's DEFINITELY a bug! According to the Oppo's info, it calls the video "AVC BDMV" @ 29.97fps.

Any thoughts on how to eliminate the stutter?

When you look at the stream info in bd-rb are there asterisks against some of the video streams? I have found that the BBC Blu-Ray discs require the use of mkvmerge (before that the vc-1 tweak was the only solution). I thought it was me being over-sensitive but I have seen something similar in BBC discs I've done.

[MikeyBK]

Just experieinced the same chapter navigation issue with the Bluray State of Play... playlist mpls is only 186 bytes and I can't navigate forward at all.

[worknstiff]

I just did same movie and it's weird because it does not have the multiple m2ts files that Watchmen has. I noticed that it does let me FF and when attempting to Chapter skip it just throws up a Operation Disabled message and continues to play. Before it gave no message and either froze or jumped to the beginning. I did a Movie Only BD9 and used Default Quality with Higher AVCH compatability checked. Guess I will try the Clown_BD solution first and redo in BD_RBLD and see if it helps.

[By-Tor]

28.04 puked too so the problem has not been resolved. Will try Movie Only I guess, but will give One Pass a shot first...

Thanks Folks!

UPDATE: The One Pass / High Speed / Quicker Encode for Extras worked fine. I'll try the INI suggestion listed below and report back.

I've had this problem a couple of months ago and was advised by DK to use dvdfab hd decrypter and this worked on all three films
i had this problem using anydvd hd so i hope this helps you;)

[Capsbackup]

Just experieinced the same chapter navigation issue with the Bluray State of Play... playlist mpls is only 186 bytes and I can't navigate forward at all.

I just did same movie and it's weird because it does not have the multiple m2ts files that Watchmen has. I noticed that it does let me FF and when attempting to Chapter skip it just throws up a Operation Disabled message and continues to play. Before it gave no message and either froze or jumped to the beginning. I did a Movie Only BD9 and used Default Quality with Higher AVCH compatability checked. Guess I will try the Clown_BD solution first and redo in BD_RBLD and see if it helps.

I had NO problems with this disc, FF/RW and chapter advance work perfectly. Movie only to BD-5.
Did you both use the default playlist that BD-RB selects?
There are three playlists: two that are 2:07:08 (00000.mpls & 00001.mpls ) and one that is 2:07:01 ( 01056.mpls )
BD-RB defaults to 01056.mpls. This playlist has only 1 chapter. Playlist 00000.mpls has 21 chapters. Playlist 00001.mpls has 2 chapters.
Playlist 00000.mpls and 00001.mpls brings up two .m2ts files (00010.m2ts and 00083.m2ts) to reencode.
Playlist 01056.mpls brings up only one .m2ts (00010.m2ts).
I selected playlist 00000.mpls.
MikeyBK, my playlist is 466 bytes.

[worknstiff]

Hi, Capsbackup, I am really going to have to start looking at the other alternative playlists. I had no idea that this movie was split up so many ways. How do you find out how many chapters that a specific playlist has? Do you just always try Clown_BD or do you have another way to check? When I play it in a DVD player it shows chapters but not the playlist it is playing from. thanks for the info! :D

[Capsbackup]

I first look at BD-RB and check the alternative playlist options. Then just use tsMuxeR and open the .mpls file, not the .m2ts file. You can then click the chapter tab in tsMuxeR and see what it displays for chapters.
You can also use BDInfo for the available options/.mpls/.m2ts files.
I have only used ClownBD on a few movies, since normally BD-RB does just fine. Also, if I use ClownBD first, I would never report a bug if things dont work properly. ( Preprocessing )

[Race Guy]

When you look at the stream info in bd-rb are there asterisks against some of the video streams? I have found that the BBC Blu-Ray discs require the use of mkvmerge (before that the vc-1 tweak was the only solution). I thought it was me being over-sensitive but I have seen something similar in BBC discs I've done.

If you mean the log drmih, there's nothing out of the ordinary there.

The disc has 2 "parts" which means there's two separate, m2ts files, probably 17GB each. I can "grab" either of those 2 files with tsMuxeR & build it into a BD-25. If I burn & play that, it's SMOOTH as BUTTER, so it's not the de/remux.

I'm thinking "BBC stuff" was originally shot "PAL" & it was then converted to NTSC (25 to 29.97fps??). Now you mess with it with x264, & it makes your SAP go HAYWIRE!

I'm gonna ask Oppo what would make the vid stutter so bad.

[MikeyBK]

I had NO problems with this disc, FF/RW and chapter advance work perfectly. Movie only to BD-5.
Did you both use the default playlist that BD-RB selects?
There are three playlists: two that are 2:07:08 (00000.mpls & 00001.mpls ) and one that is 2:07:01 ( 01056.mpls )
BD-RB defaults to 01056.mpls. This playlist has only 1 chapter. Playlist 00000.mpls has 21 chapters. Playlist 00001.mpls has 2 chapters.
Playlist 00000.mpls and 00001.mpls brings up two .m2ts files (00010.m2ts and 00083.m2ts) to reencode.
Playlist 01056.mpls brings up only one .m2ts (00010.m2ts).
I selected playlist 00000.mpls.
MikeyBK, my playlist is 466 bytes.

Yes, I did check 1056.mpls because I did not want the MPAA message... but did not realize they'd throw a BS playlist with screwed up playlists... seems like something they are doing on purpose to throw off copying programs?>?

I guess we need to definately pay attention to make sure we check to see if they are placing BS playlists in there on purpose.

Thanks Bro, will be on my toes for sure now.;):sly:

[setarip_old]

@jdobbs

Regarding the hidden "trigger" code for HDDVD compliance that you added in 0.28.04 (instead of directly entering the two lines of code), you said only the following:- Added a specialized hidden setting that is meant for special circumstances. "HDDVD_COMPLIANT=1" in the "[Options]" area of the INI will force certain parameters to be used and will limit bitrate to that legal for HD-DVD playback. Note: This does NOT mean you can playback your output on an HD-DVD player. It only means the stream will be encoded
in a way that is compliant for certain post BD-RB software packages to use it in creating HD-DVDs. If selecting this option with BD-25, it is likely you will undersize due to bitrate constraints.

It might be worthwhile to reiterate that this will only function properly if two-pass modes are selected (Selecting ANY one-pass mode [including "One pass CRF encoding"] will negate this function).

[MikeyBK]

I had NO problems with this disc, FF/RW and chapter advance work perfectly. Movie only to BD-5.
Did you both use the default playlist that BD-RB selects?
There are three playlists: two that are 2:07:08 (00000.mpls & 00001.mpls ) and one that is 2:07:01 ( 01056.mpls )
BD-RB defaults to 01056.mpls. This playlist has only 1 chapter. Playlist 00000.mpls has 21 chapters. Playlist 00001.mpls has 2 chapters.
Playlist 00000.mpls and 00001.mpls brings up two .m2ts files (00010.m2ts and 00083.m2ts) to reencode.
Playlist 01056.mpls brings up only one .m2ts (00010.m2ts).
I selected playlist 00000.mpls.
MikeyBK, my playlist is 466 bytes.

Yes, I did check 1056.mpls because I did not want the MPAA message... but did not realize they'd throw a BS playlist with screwed up playlists... seems like something they are doing on purpose to throw off copying programs?>?

I guess we need to definately pay attention to make sure we check to see if they are placing BS playlists in there on purpose.

Thanks Bro, will be on my toes for sure now.;):sly:

Thanks Caps, I TSMuxed the 00000 playlist and took the 466 byte mpls file from that output, and replaced the 186 byte mpls in the BDRB BD-9... and it now plays perfect... So an easy fix since BD-RB & x264 already did a superb job on the encoding, just had to get the new mpls from TSMuxer using the 00000 playlist...;)

[leChameleon]

WINDOWS XP PRO 32-BIT
FDDSHOW=VC-1 disabled (using WMV11 instead of WMV9).
Ripped using ANYDVD HD 6.5.7.4

*.LOG
-------------------------------------------
[09:17:44] BD Rebuilder v0.26.03 (beta)
- Source: SPY_GAME
- Input BD size: 32.46 GB
- Approximate total content: [02:06:38.591]
- Target BD size: 22.46 GB
- MOVIE-ONLY mode enabled
[09:17:44] PHASE ONE, Encoding
- [09:17:44] Extracting A/V streams [VID_00010]
- [09:28:48] Collecting video information [00010]
- Video: 1920x1080, 23.976fps, 182,184 frames
- Bitrate: 18,793 Kbs
- [09:28:48] Reencoding: VID_00010, Pass 1 of 2
- [15:14:37] Reencoding: VID_00010, Pass 2 of 2
- [21:13:07] Video Encode complete
- [21:13:07] Reencoding audio tracks (if req'd)
- [21:13:07] Multiplexing M2TS
[21:20:27]PHASE ONE complete
[21:20:27]PHASE TWO - Rebuild Started
- [21:20:27] Rebuilding BD file Structure
[21:30:17] - Encode and Rebuild complete
[21:30:17]JOB: SPY_GAME finished.

*.INI
-------------------------------------------
[Options]
RESIZE=0
MODE=0
TARGET_SIZE=23000
VERBOSE_STATUS=1
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
ENCODE_QUALITY=3
QUICK_EXTRAS=1
[Paths]
SOURCE_PATH=G:\TEMP - SPY GAME (2001)\SPY_GAME\
WORKING_PATH=K:\BD25 4\SPY GAME (2001)\


Question:
Even when "MOVIE ONLY" is selected shouldn't BD-RB output a CERTIFICATE folder and it's contents?
It only output the K:\Bd25 4\Spy Game (2001)\SPY_GAME\BDMV.

It was my understanding that a Blu-ray disc requires the CERTIFICATE folder and contents as well, no?

[MikeyBK]

Just experieinced the same chapter navigation issue with the Bluray State of Play... playlist mpls is only 186 bytes and I can't navigate forward at all.

I had NO problems with this disc, FF/RW and chapter advance work perfectly. Movie only to BD-5.
Did you both use the default playlist that BD-RB selects?
There are three playlists: two that are 2:07:08 (00000.mpls & 00001.mpls ) and one that is 2:07:01 ( 01056.mpls )
BD-RB defaults to 01056.mpls. This playlist has only 1 chapter. Playlist 00000.mpls has 21 chapters. Playlist 00001.mpls has 2 chapters.
Playlist 00000.mpls and 00001.mpls brings up two .m2ts files (00010.m2ts and 00083.m2ts) to reencode.
Playlist 01056.mpls brings up only one .m2ts (00010.m2ts).
I selected playlist 00000.mpls.
MikeyBK, my playlist is 466 bytes.

I just checked Fighting and it also has four playlists, with two playlists, one extended and one theatrical, that has only two chapters....while the other two, one extended and one theatrical, that has the full array of chapters.
This seems to be a new tactic or method they are using. All so far have been VC-1.

Hopefully this is welcome info for JD. It appears that BD-RB, 'and' TSMuxer was indeed doing their jobs, just the extra bogus playlists seem to be what's causing the chapter navigation issues.

[GaPony]

It was my understanding that a Blu-ray disc requires the CERTIFICATE folder and contents as well, no?

BD-Rebuilder doesn't create a CERTIFICATE, BDMV\AUXDATA, BDMV\META, BDMV\JAR, or BDMV\BDJO folders when you enable (check the block) for "Strict compliance with AVCHD for Movie Only Copies"

You created an AVCHD disc, not a Blu-Ray disc. If you want the \CERTIFICATE folder, either uncheck the block, or enable ImgBurn to create it.

Its been discussed a dozen times in this thread...

[drmih]

If you mean the log drmih, there's nothing out of the ordinary there.

The disc has 2 "parts" which means there's two separate, m2ts files, probably 17GB each. I can "grab" either of those 2 files with tsMuxeR & build it into a BD-25. If I burn & play that, it's SMOOTH as BUTTER, so it's not the de/remux.

I'm thinking "BBC stuff" was originally shot "PAL" & it was then converted to NTSC (25 to 29.97fps??). Now you mess with it with x264, & it makes your SAP go HAYWIRE!

I'm gonna ask Oppo what would make the vid stutter so bad.

Not in the Log. If you select your source and then chose the 'Stream' tab, it shows all of the parts it is going to encode. If there are asterisks against any of the video streams then it will be using mkvmerge.

[leChameleon]

BD-Rebuilder doesn't create a CERTIFICATE, BDMV\AUXDATA, BDMV\META, BDMV\JAR, or BDMV\BDJO folders when you enable (check the block) for "Strict compliance with AVCHD for Movie Only Copies"

You created an AVCHD disc, not a Blu-Ray disc. If you want the \CERTIFICATE folder, either uncheck the block, or enable ImgBurn to create it.

Its been discussed a dozen times in this thread...Hi GaPony, Thank you for your comment. I guess what was not clear to me was it the output was set to BD25 then BD-RB would result in blu-ray however if BD-9 was selected then AVCHD would be the result. i.e. One could enable "Strict..." in the Settings and depending on the output size then it would take affect or not.

Perhaps at some point it may be advantagous to document this more clearly and post/print it in the setup/help files.

[worknstiff]

I just checked Fighting and it also has four playlists, with two playlists, one extended and one theatrical, that has only two chapters....while the other two, one extended and one theatrical, that has the full array of chapters.
This seems to be a new tactic or method they are using. All so far have been VC-1.

Hopefully this is welcome info for JD. It appears that BD-RB, 'and' TSMuxer was indeed doing their jobs, just the extra bogus playlists seem to be what's causing the chapter navigation issues.

GREAT CATCH, MikeyBK & Capsbackup, Finally I know what is going on with these titles that caused a big reject stack on my desk. WOW! I hate to waste even one and lately I have wasted a lotof them. I will preview from now on. Adding 15 minutes of prep time on the front end is better than wasting 10 hours on the back. Thanks Again! Congrats to Both of You & Jdobbs too. :thanks:

[jdobbs]

@jdobbs

Regarding the hidden "trigger" code for HDDVD compliance that you added in 0.28.04 (instead of directly entering the two lines of code), you said only the following:

It might be worthwhile to reiterate that this will only function properly if two-pass modes are selected (Selecting ANY one-pass mode [including "One pass CRF encoding"] will negate this function). Hmmm... I'll go back and look at it and correct it to work with single pass modes (if possible).

[GaPony]

Hi GaPony, Thank you for your comment. I guess what was not clear to me was it the output was set to BD25 then BD-RB would result in blu-ray however if BD-9 was selected then AVCHD would be the result. i.e. One could enable "Strict..." in the Settings and depending on the output size then it would take affect or not.

Perhaps at some point it may be advantagous to document this more clearly and post/print it in the setup/help files.

Documentation? You got documentation? Real men never read that stuff. :D

The best thing you can do is search this thread for whatever it is you're looking for. You may have to use a few different keywords, and several searches, but eventually you'll find what you need.

Given the early development of the program, I'm sure jdobbs would rather concentrate on stability and functionality, than on writing documentation and specs, at the moment. Which makes alot of sense, since there's always a huge possibility that fundemental changes will occur.

[jdobbs]

I just checked Fighting and it also has four playlists, with two playlists, one extended and one theatrical, that has only two chapters....while the other two, one extended and one theatrical, that has the full array of chapters.
This seems to be a new tactic or method they are using. All so far have been VC-1.

Hopefully this is welcome info for JD. It appears that BD-RB, 'and' TSMuxer was indeed doing their jobs, just the extra bogus playlists seem to be what's causing the chapter navigation issues. I'll pick up a copy of "Fighting" and do some investigating. Maybe I can programmatically pick this out and save the manual labor...

By the way, this is very definitely not related to the issue I found in WATCHMEN. It only has two choices, the movie and the commentary.

[leChameleon]

Documentation? You got documentation? Real men never read that stuff. :D

The best thing you can do is search this thread for whatever it is you're looking for. You may have to use a few different keywords, and several searches, but eventually you'll find what you need.

Given the early development of the program, I'm sure jdobbs would rather concentrate on stability and functionality, than on writing documentation and specs, at the moment. Which makes alot of sense, since there's always a huge possibility that fundemental changes will occur.Based on the result it would appear that the BD25 iso I made and played in a Sony BDP-350 shows that it is not AVCHD format it is BD format. When I ran the same test and burned a DVD9 dvd that shows the AVCHD format.

So either there is a bug that if [x] Strict... is set and either output size should be AVCHD format as you say then its not being encoded that way. Otherwise if you're incorrect and only when the DVD9 size is selected then it will encode AVCHD, and when BD25 is selected it will disregard the setting and output blu-ray format.

[jdobbs]

Based on the result it would appear that the BD25 iso I made and played in a Sony BDP-350 shows that it is not AVCHD format it is BD format. When I ran the same test and burned a DVD9 dvd that shows the AVCHD format.

So either there is a bug that if [x] Strict... is set and either output size should be AVCHD format as you say then its not being encoded that way. Otherwise if you're incorrect and only when the DVD9 size is selected then it will encode AVCHD, and when BD25 is selected it will disregard the setting and output blu-ray format. Please take this kind of irrelevent stuff to another thread, ok? It's not a bug, and that has been explained to you.

Your player says that because of the disc type (BD-25) -- Sony players are notorious for being wrong. Hell, my player can't even make up its mind between two discs of the same type. BTW -- this has also been discussed further back in this thread.

[setarip_old]

@jdobbs

Regarding HD-DVD compatibility:Hmmm... I'll go back and look at it and correct it to work with single pass modes (if possible).Although that would be wonderful, in my personal opinion, don't take time away from your efforts regarding "real" bugs. Considering what I presume will be the limited usage of this particular capability, I'd suggest that rather than spending your time trying to enhance it, you simply have your program generate an "informational popup notice" if someone attempts to select both a one pass mode and the HDDVD compatibility "trigger"...