BD Rebuilder Beta - Bug Reports Only

[Furiousflea]

I use the Pioneer BD-203 in an external enclosure and can absolutely recommend it. It is very fast, has one of the best burning qualities on the market and runs very smooth and quiet independant if you use CD, DVD, BD-R or BD-RE. 100% thumbs up from me (after testing several other options as well).

Feel free to delete this, if you consider this too much off-topic.

I'd have deleted it ;)

All bluray burners are much of a muchness and all discs are much of a muchness. We haven't reached the point where companies are at rock bottom margins and most of the cheap discs are utter pants...

[jdobbs]

Got a question for you m8s.
I am in the process of buying a bd burner but i want to be sure that it's going to be the best bet.

I usualy rip or download blu-rays and then i use bd rebuilder to put them in bd9, my ps3 runs them fine.
But i want to go a step further and there are some movies i want to keep the HD audio so for this i think the best bet would be to burn them on bd25.
BD9 as a great Image Quality, can't find a difference on a 40" LCD.

So for keeping DTS, TRUE-DTS etc .. the best bet would be a br burner?

Thanks in advance.Please open another thread... this thread is for bug reports only.

[allright]

Hej

Discovered two zip files in the root of the disc, these zip files contains files in a folder named sync:
083824576\sync\083824576-dts_5_1-eng.iid
083824576\sync\083824576-dts_5_1-eng.syn

If you need more info, please let me know.

//Jesper

Using BD-RB v0.30.02 and trying to do The X-Files I Want to believe region B (Full Movie), but got the following error:

OS: Windows Vista 64 bit
FFDSHOW rev. 2661 (7 feb. 2009)
Haali: 1.9.42.1


[01:12:15] BD Rebuilder v0.30.02 (beta)
- Source: THE.X-FILES.I.WANT.TO.BELIEVE.GER.DC.BLU-RAY.1080P.AVC.DTS-HD.5.1
- Input BD size: 42,52 GB
- Approximate total content: [04:30:26.751]
- Target BD size: 22,46 GB
- Windows Version: 6.0 [6001]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[01:12:16] PHASE ONE, Encoding
- [01:12:16] Extracting A/V streams [VID_00001]
- [01:13:03] Reencoding: VID_00001 (1 of 35)
- [01:13:03] Reencoding secondary video [TRK_02]
- [01:20:39] Extracting A/V streams [VID_00002]
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: D:\THE.X-FILES.I.WANT.TO.BELIEVE.GER.DC.BLU-RAY.1080P.AVC.DTS-HD.5.1\BDMV\STREAM\00002.m2ts
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: D:\THE.X-FILES.I.WANT.TO.BELIEVE.GER.DC.BLU-RAY.1080P.AVC.DTS-HD.5.1\BDMV\STREAM\00002.m2ts
[01:20:50] - Failed to retrieve audio, aborted


[Status]
LABEL=THE.X-FILES.I.WANT.TO.BELIEVE.GER.DC.BLU-RAY.1080P.AVC.DTS-HD.5.1
VERSION=v0.30.02 (beta)
SOURCE_SIZE=45654543097
SOURCE_VIDEO_SIZE=39120009216
TARGET_SIZE=24117248000
REDUCTION=.449455776503465
RESIZE_1080=0
AUDIO_TO_KEEP=dan;eng;
SUBS_TO_KEEP=all
BACKUP_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
[00001]
AUDIO=1001110
PGS=11111111111111111
M2TS_TARGET=267118428
RATE=4811
NSIZE=256536576
FLINK=-1
MLINK=0
[00002]
AUDIO=0000000
PGS=

[marius1]

Hmm BD Rebuilder produced over 4.9GB of files even though I specified DVD-5, so ImgBurn refused to writes the files to disc. Is anyone else running into this problem? I'm re-running the whole thing now with the custom size set to 4.2GB. v0.30.02

[setarip_old]

@marius1

Hi!

I'm guessing you have a BluRay disc with multiple "heavy duty" audiostreams - and have not deleted enough of them to leave sufficient room for the video, making burning to DVD-5 infeasible...

[marius1]

@marius1

Hi!

I'm guessing you have a BluRay disc with multiple "heavy duty" audiostreams - and have not deleted enough of them to leave sufficient room for the video, making burning to DVD-5 infeasible...

Hmmm I only have one DD+ audio stream.. I also just realized that I was using a newer version of x264.exe than the one that came with v30.02. I reverted the binary and trying it again.

[cwh060]

You just have to be careful and not "upgrade" the minute a new version of FFDSHOW is released -- give it some time. I'm currently using Revision 2857 and am not seeing any problems.

@jdobbs, equad, Kakashi Sensei,

Reverting to ffdshow 2857 seems to have restored things back to normal. I have a conversion program that automatically updates ffdshow. I should have known this was the problem.

I backed up the dark knight and the file structure now looks correct.

thanks....cwh

[marius1]

Hmmm I only have one DD+ audio stream.. I also just realized that I was using a newer version of x264.exe than the one that came with v30.02. I reverted the binary and trying it again.

Nope that didn't help at all. Still produced 4.9GB. What could be going wrong?

[DGenerateKane]

I'm going to get another copy and try again soon.

I got a new disc to rip and yet I still get the same result. I have done almost two dozen discs without problems, I have no idea why this one is causing problems. :/

Edit: I just noticed the first Pirates movie failed as well, although it failed at a different spot.

==========================
[15:02:08] BD Rebuilder v0.30.02 (beta)
[15:02:08] BEGIN - BATCH SEQUENCE
==========================
-----------------------
[15:02:08] PROCESSING BATCH FILE [1]
-----------------------
[15:02:09] BD Rebuilder v0.30.02 (beta)
- Source: PIRATES1
- Input BD size: 42.44 GB
- Approximate total content: [03:29:56.241]
- Target BD size: 22.46 GB
- Windows Version: 6.1 [7600]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:02:09] PHASE ONE, Encoding
- [15:02:09] Extracting A/V streams [VID_00002]
- [15:02:09] Reencoding: VID_00002 (1 of 10)
- [15:02:09] Collecting video information
- Video: 1920x1080, 23.976fps, 24 frames
- [15:02:09] Reencoding: VID_00002, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[15:05:11] - Failed video encode, aborted

[GaPony]

Nope that didn't help at all. Still produced 4.9GB. What could be going wrong?

Try using a custom target size of 4300 instead of BD5.

EDIT: I see you already tried that... oops! Just keep lowering it until you get to a number that either works or chokes immediately.

[Wolffe]

@samtroy
@jdobbs

Processing the REGION B version of "WALL-E" (Different than the Region A version) has already been discussed at length in the following thread:

http://forum.doom9.org/showthread.php?p=1276826#post1276826

Try my suggested test/fix detailed in that thread...

Thanks for the replies guys.

I bought the disc used from the local video store so it shouldn't be a Region B disc, but my experience with ripping it seems to suggest it is. Region A discs don't seem to have the issue of being split into so many parts. Very strange!

Regardless, I read the post above which lead me to try a few things. I tried it with MakeMKV on the image I had already ripped via AnyDVD, but I couldn't get TsMuxer to recognise any of the subtitles afterwards.

Instead I just used TsMuxer to open the 0081 playlist and unselected the unnecessary video, audio, and subtitles. This generated a Blu Ray folder structure that seemed to play fine with TotalMedia Theatre and it included the subtitles.

I'm now feeding this into BD Rebuilder as I write this to see what comes out the other end. I realise that use of a modified source is unsupported though.

So is it TsMuxer that generates the really long filename shown in my previous post when going at it directly with BD-Rebuilder? I don't really know enough about this stuff just yet to know if I should be puzzled why it worked through the TsMuxer GUI?!

[turbojet]

I'm not going to use it. I don't want a dependency on the java engine built it. I'm in the process of writing my own code to resize the subtitles -- it's almost done.

I understand the issue relying on java, it also takes some registry checks to get external java programs to work on 64 bit OS's.

Good luck on the venture and I look forward to seeing resize work with subs on virtually everything.

[astraub]

Hi,

I have to come back on the black area encoding problem, as it drives me crazy. The latest BD RB compresses fine now, but whenever I have large areas of black I get compression artifacts of the worst kind. For example compressing a fully black screen results in an encoded mid grey screen (sometimes with very lively artifacts) that only changes to black when enough other picture content comes into the game.

I am sure that this is a problem with the avisynth re-encoding. Most likely any of the prameters used generate the problem? What can I do about this?
(Right now I am trying some parameters in the ffdshow output settings, like turning off the automatic BT601/709 setting and swithing it to ITU-R BT709 and setting the output level to TV/projector instead of computer monitor).

By the way - is there any GUI type interface that I could use only for the video resizing with Avisynth (like FitCD) that can generate the required Avisynth script?

[jdobbs]

Hmmm I only have one DD+ audio stream.. I also just realized that I was using a newer version of x264.exe than the one that came with v30.02. I reverted the binary and trying it again.

Post your .INF file -- it should show the target and actual sizes. Also post your .INI file. It will show your settings.

[jdobbs]

Hi,

I have to come back on the black area encoding problem, as it drives me crazy. The latest BD RB compresses fine now, but whenever I have large areas of black I get compression artifacts of the worst kind. For example compressing a fully black screen results in an encoded mid grey screen (sometimes with very lively artifacts) that only changes to black when enough other picture content comes into the game.

I am sure that this is a problem with the avisynth re-encoding. Most likely any of the prameters used generate the problem? What can I do about this?
(Right now I am trying some parameters in the ffdshow output settings, like turning off the automatic BT601/709 setting and swithing it to ITU-R BT709 and setting the output level to TV/projector instead of computer monitor).

By the way - is there any GUI type interface that I could use only for the video resizing with Avisynth (like FitCD) that can generate the required Avisynth script? I'm guessing you're using the "Fastest (BD-25)" setting. I experienced something similar in backup tests of up my "LOST Season 1" discs. I fixed it by adding CABAC back into the fastest setting. It makes is very slightly slower, but corrects the blockiness in those scenes. You'll see it in the next release.

[marius1]

Post your .INF file -- it should show the target and actual sizes. Also post your .INI file. It will show your settings.

Here's the INI. Where do i get the INF file?

[Options]
MODE=1
QUICK_EXTRAS=0
PRIORITY_CLASS=1
RESIZE=0
ENCODE_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
TRELLIS=0
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=0
AVCHD=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450
[Paths]
SOURCE_PATH=D:\BD\THE_READER\
WORKING_PATH=C:\FAB\REBUILDER\


Keep in mind that this is the first time i've run into this problem. I've rebuilt about a dozen blu-ray discs with success so far.

[chudm]

i tried to rip a friend, wizard of oz, european edition, when trying to extract 003.m2ts tsmuxer.exe closes, and everytime i do it, happens the same thing

[Dark Shikari]

I'm guessing you're using the "Fastest (BD-25)" setting. I experienced something similar in backup tests of up my "LOST Season 1" discs. I fixed it by adding CABAC back into the fastest setting. It makes is very slightly slower, but corrects the blockiness in those scenes. You'll see it in the next release.Sounds like the decoder in the Blu-ray player might have a broken decoder; an extremely common mistake is to forget to realize that CAVLC+8x8dct uses different nnz values for deblocking as it uses for context. This can cause serious artifacting in some cases, and if hardly anyone ever used CAVLC on the device, probably nobody would notice until now.

[elrond81]

Hi!

I unzipped BD_Rebuilder 0.30.02_beta to a folder on my PC and ran it. But it only showed "Beta version expired. Please upgrade to newer version."

Could somebody please tell me what I could do about this?

Cheers

[chudm]

Hi!

I unzipped BD_Rebuilder 0.30.02_beta to a folder on my PC and ran it. But it only showed "Beta version expired. Please upgrade to newer version."

Could somebody please tell me what I could do about this?

Cheers

check the date on your pc

[Wolffe]

Instead I just used TsMuxer to open the 0081 playlist and unselected the unnecessary video, audio, and subtitles. This generated a Blu Ray folder structure that seemed to play fine with TotalMedia Theatre and it included the subtitles.

I'm now feeding this into BD Rebuilder as I write this to see what comes out the other end. I realise that use of a modified source is unsupported though.

Just in case anyone is interested, this seemed to work just fine. The final movie-only Blu-Ray produced by BD-Rebuilder played fine under TotalMedia Theatre. I jumped through various chapters and the audio seemed to be in-sync throughout.

The only odd thing was that the progress bar in TotalMedia Theatre wouldn't work properly. The movie actually ends at about the 1/6 mark as if TotalMedia thinks the movie is about 6 times longer. Clicking the end of the progress bar makes Total Media jump to about 9:45:00. Odd... but I can live with that.

[turbojet]

x264 --fps changes framerate from avs input since r1271. This is OK for the most part except when converting 30 to 60 fps. x264 --fps 30000/1001 is used which outputs a choppy 30 fps stream.

There's many solutions to the problem but since DirectShowSource is the culprit I'd use AssumeFPS immediately after DSS and not use x264 --fps.

[DrKajun]

Had pretty good luck with BDRB thus far, but finally ran into an issue. I think this would be my frist one with HD audio and the file plays fine on the PC but when I put it to a BD and play it on the set-top the audio is slightly out of sync. What am I doing wrong?

Would FFDshow have anything to do with this? cuz I was running a newer verison untill I saw a previous post and have sencie down graded.

[jdobbs]

Sounds like the decoder in the Blu-ray player might have a broken decoder; an extremely common mistake is to forget to realize that CAVLC+8x8dct uses different nnz values for deblocking as it uses for context. This can cause serious artifacting in some cases, and if hardly anyone ever used CAVLC on the device, probably nobody would notice until now.The interesting thing is that it does it both on my PC (with MPC) and on my standalone but CABAC fixed it. Even more interesting is that I didn't see it on any other fade-ins or dark scenes (the bitrate is pretty high because this was a BD-25 encode) -- only the intro to LOST. Maybe because of the contrast of the large moving white letters (the LOST text) on a black background? Don't know.

[jdobbs]

I've just updated the first post of this thread with a link to an update to BD-RB (v0.30.03). Changes for this release are:- Changed default for "High Speed (BD-25)" setting
so that it now uses CABAC. This corrects the
blockiness experienced in fade-ins and low light
scenes.
- Modified settings so the VC-1 video is never set to
be blanked. Removed associated code.
- Added FFMS2.DLL to package. It is automatically
used for decoding when a failure is detected after
on attempt to encode. This should bypass certain
errors when DirectShow filters are misconfigured, or
when the Windows 7 registry fix wasn't completed.
- Added a hidden setting "USE_FFMS2=1". When enabled
this setting uses FFMS2.DLL as the primary method
of frame serving. Note: As of this release FFMS2
does not decode field based VC-1 sources (those marked
with a "**" in the stream list). But I'm hoping a
solution will be found for this soon.
- Removed "--fps" from the X264 command line. The
AVS now sets thet bitrate.
- Added a new hidden option "QUICK_USE_QUALITY=1" in
which, when set, BD-RB will use the currently chosen
quality level in quick extra encodes rather than the
default of "--ultrafast" mode.
- Fixed an error in which the source aspect ratio for
video resized from SD to HD was not being set
properly.
- Other minor corrections and cosmetic fixes.

[DrKajun]

do you think .03 will resolve my sync issue?

[elrond81]

:thanks: CHUDM
Now it's working perfectly!

[chudm]

:thanks: CHUDM
Now it's working perfectly!

not a problem man :)

[lican]

a ringrazziamento to Mr. jobby x its job already I use dvd reb with great esteem .da some day use bd reb, if someone puo to help made me baikap of twilight audio dts but on my play does not feel audio .qualcuno me puo to help use then as it arranges op xp, or pure seven 64 bit would appeal to that it also worked them thanks I am up your news and thanks to the Mr. jobby when I want to leave language dts I put dulls just and on rows configurazzione ce dts =0 and just thus thanks

[Groucho2004]

a ringrazziamento to Mr. jobby x its job already I use dvd reb with great esteem .da some day use bd reb, if someone puo to help made me baikap of twilight audio dts but on my play does not feel audio .qualcuno me puo to help use then as it arranges op xp, or pure seven 64 bit would appeal to that it also worked them thanks I am up your news and thanks to the Mr. jobby when I want to leave language dts I put dulls just and on rows configurazzione ce dts =0 and just thus thanks

Very funny. Did you use Babelfish?

Mr. Jobby, I think he/she likes the program! :)

[lican]

si , mi dispiace non consco l inglese si fa quel che si puo scusate.

[Groucho2004]

si , mi dispiace non consco l inglese si fa quel che si puo scusate.

No need to apologize. You might want to try a different translation engine, the one you used is horrible.

[lican]

aiutare fatto mi |baikap| dei |dts| di audio di crepuscolo ma sul mio dramma non senta l'audio .qualcuno mi |puo| aiutare ad usare poi come esso accomoda |xp| di operazione, o il sette 64 pezzo puro farebbe appello a che li ha lavorato anche ringrazi sono sulle sue notizie e grazie a |jobby| il Sig. quando voglio lasciare i |dts| di lingua che io metto smussi giusto e su spingono i |dts| di |ce| di |configurazzione| =0 ed appena così ringrazi

[lican]

cosi va bene me sa di no

[jdobbs]

@lican -- Rule 13. Also --- please remember this thread is for bug reports only.

[turbojet]

Thanks a lot for the new version. 59.94 and crf extras are much more efficient. However a few things I've noticed that have changed.

- REBUILDER.INI is included in the zip again, which wipes out all settings, is that needed?
- x264 --me umh --psy-rd 1.0:0.2 don't exist any longer in the high settings, could they be used again for higher quality?

[Sharc]

BD-RB v0.30.03, 1-pass CRF mode.
I tried QUICK_USE_EXTRAS=1. It doesn't seem to have an effect. The Extras are still encoded 'ultrafast' -- as indicated by the lastcmd.txt and by analyzing the encoded file with MediaInfo.
I selected "High Quality" (default), which uses --preset medium IIRC, and enabled "Quicker" Encode for Extras. I would expect that QUICK_USE_EXTRAS=1 should now have taken the "High Quality" (i.e. --preset medium) switches.
Did I miss something?

Secondly, is it ok to use a preceding # to disable certain options in the config file for testing?

[turbojet]

BD-RB v0.30.03, 1-pass CRF mode.
I tried QUICK_USE_EXTRAS=1. It doesn't seem to have an effect. The Extras are still encoded 'ultrafast' -- as indicated by the lastcmd.txt and by analyzing the encoded file with MediaInfo.
I selected "High Quality" (default), which uses --preset medium IIRC, and enabled "Quicker" Encode for Extras. I would expect that QUICK_USE_EXTRAS=1 should now have taken the "High Quality" (i.e. --preset medium) switches.
Did I miss something?

QUICK_USE_QUALITY=1 is working for me

Secondly, is it ok to use a preceding # to disable certain options in the config file for testing?

I've never had a problem using it.

[PurpleMan]

@jdobbs:

I think I may have found a new bug with the way BD-Rebuilder handles MPLS files for pip discs.

I did Resident Evil: Extinction and left out the PiP in the full disc (BD25) backup. The result disc would play perfectly in powerdvd7 and tmt3, but would not play in PowerDVD9 (when you click 'play movie', it would show the FBI warnings then get back to the main menu, refusing to even start playing the main m2ts).

I figured this must be a PowerDVD9 bug with the disc, so I tried playing the original one. To my surprise, it played perfectly. So I started to dig - what could possibly make PowerDVD9 not play the bd-rb output? I replaced bd-rb's main-movie MPLS with the original disc MPLS (knowing it will screw up alot of stuff), just wanted to see if powerdvd will then at least start playing, and - IT DID! So I concluded that there's something in the BD-RB outputted MPLS that it did not like.

The original disc MPLS had the IN_TIME set to 00:00:11,650, and I know that BD-RB changes it in the rebuild to correspond with TSMuxer (IN_TIME = 00:10:00,000). Nothing wrong with that, and the chapters have been adjusted accordingly.

Further digging in BDEdit revealed something that is probably wrong. The sub-path chatper-points (used for the pip, I think) only had the IN_TIME adjusted to the new main m2ts IN_TIME (10mins). meaning, for each of the chapters the IN_TIME increased in ~10mins, which is good, but the OUT_TIME was not (and it should have been!). So the OUT_TIME for each of the chapters was BEFORE the IN_TIME (not good!)

I attached two screenshots of BDEdit illustrating this. One of the original disc, and one of the BD-RB output disc. You can see what I'm talking about there.

P.S.
This disc was done with 0.29.03, so if you addressed the bug since then, I apologize.

[turbojet]

PurpleMan: Would fixmpls (http://forums.sagetv.com/forums/showthread.php?t=41722) help you debug it further?

[PurpleMan]

PurpleMan: Would fixmpls (http://forums.sagetv.com/forums/showthread.php?t=41722) help you debug it further?

I tried using fixmpls on the original MPLS file, but fixmpls does not fix sub-path chapter points, only main chapter points. I'm going to hex-edit the bd-rb mpls to fix this myself and see what happens.

Either way, I reckon this should be addressed by our beloved jdobbs :)

[Sharc]

QUICK_USE_QUALITY=1 is working for me
Good to know. Seems like those Extras which are 480i in the original and which I let BD-RB convert to 720p are still encoded 'ultrafast'. Maybe this is intentional?
I will try another disc with a simpler structure.

Added:
I found the 'bug': The correct command is QUICK_USE_QUALITY=1. I put in QUICK_USE_EXTRAS=1 as erroneously documented in the HIDDENOPTS.TXT. :p

[PurpleMan]

Progress report:

I've hex-editted the out_times, and now when I click play movie it indeed starts playing. So that's a winner.

However, if I try to seek or jump through chapters, powerdvd crashes. Which indicates I've either screwed up something in the MPLS while editting it, or that the timing values weren't the only thing wrong with the MPLS to begin with.

:(

[laserfan]

...fixmpls does not fix sub-path chapter points, only main chapter points.What's a "sub-path chapter point"?

Also, what is the magic incantation for downloading fixmpls--all I ever get is "Slow down, you have to wait 17 seconds..."?

[jdobbs]

BD-RB v0.30.03, 1-pass CRF mode.
I tried QUICK_USE_EXTRAS=1. It doesn't seem to have an effect. The Extras are still encoded 'ultrafast' -- as indicated by the lastcmd.txt and by analyzing the encoded file with MediaInfo.
I selected "High Quality" (default), which uses --preset medium IIRC, and enabled "Quicker" Encode for Extras. I would expect that QUICK_USE_EXTRAS=1 should now have taken the "High Quality" (i.e. --preset medium) switches.
Did I miss something?

Secondly, is it ok to use a preceding # to disable certain options in the config file for testing?I typed it wrong in the HIDDENOOPTS.TXT file. It is "QUICK_USE_QUALITY".

[jdobbs]

@jdobbs:

I think I may have found a new bug with the way BD-Rebuilder handles MPLS files for pip discs.

I did Resident Evil: Extinction and left out the PiP in the full disc (BD25) backup. The result disc would play perfectly in powerdvd7 and tmt3, but would not play in PowerDVD9 (when you click 'play movie', it would show the FBI warnings then get back to the main menu, refusing to even start playing the main m2ts).

I figured this must be a PowerDVD9 bug with the disc, so I tried playing the original one. To my surprise, it played perfectly. So I started to dig - what could possibly make PowerDVD9 not play the bd-rb output? I replaced bd-rb's main-movie MPLS with the original disc MPLS (knowing it will screw up alot of stuff), just wanted to see if powerdvd will then at least start playing, and - IT DID! So I concluded that there's something in the BD-RB outputted MPLS that it did not like.

The original disc MPLS had the IN_TIME set to 00:00:11,650, and I know that BD-RB changes it in the rebuild to correspond with TSMuxer (IN_TIME = 00:10:00,000). Nothing wrong with that, and the chapters have been adjusted accordingly.

Further digging in BDEdit revealed something that is probably wrong. The sub-path chatper-points (used for the pip, I think) only had the IN_TIME adjusted to the new main m2ts IN_TIME (10mins). meaning, for each of the chapters the IN_TIME increased in ~10mins, which is good, but the OUT_TIME was not (and it should have been!). So the OUT_TIME for each of the chapters was BEFORE the IN_TIME (not good!)

I attached two screenshots of BDEdit illustrating this. One of the original disc, and one of the BD-RB output disc. You can see what I'm talking about there.

P.S.
This disc was done with 0.29.03, so if you addressed the bug since then, I apologize.Hmmm... good catch. I'll check it out.

[jdobbs]

@PurpleMan

Thanks for the outstanding bug report. The detail was fantastic and pointed me in exactly the right direction.

I just looked at it, and this could be the cause of other problems also. When the new OUT value was rewritten, there was a character mistyped on the line of code that rewrote the value to the MPLS -- and (oddly enough) it didn't cause a compile error because here was another variable by that (mistyped) name. The value was written to the wrong location in the file.

I'm updating it and will post a fix.

[jdobbs]

Thanks a lot for the new version. 59.94 and crf extras are much more efficient. However a few things I've noticed that have changed.

- REBUILDER.INI is included in the zip again, which wipes out all settings, is that needed?
- x264 --me umh --psy-rd 1.0:0.2 don't exist any longer in the high settings, could they be used again for higher quality? "--me umh" is set in both the "High Quality (Default)" and "Highest (Very Slow)" modes as a part of the preset. Are you saying the defaults in X264 have changed? I don't remember seeing anything in the changelogs...

"--psy-rd 1.0:0.0" should be present in all settings except "Good" and "Highest Speed (BD-25)"

[PurpleMan]

@PurpleMan

Thanks for the outstanding bug report. The detail was fantastic and pointed me in exactly the right direction.

I just looked at it, and this could be the cause of other problems also. When the new OUT value was rewritten, there was a character mistyped on the line of code that rewrote the value to the MPLS -- and (oddly enough) it didn't cause a compile error because here was another variable by that (mistyped) name. The value was written to the wrong location in the file.

I'm updating it and will post a fix.

No, thank you!

And I find great pleasure in that I was able to help! Keep up the good work!

To continue our discussion, I wrote a small program that corrected all the OUT_TIMES on the BD-RB MPLS, and like I said, PowerDVD9 then agrees to start playing. Thing is, after only 1 minute of playback, the program crashes. Further digging revealed that it crashes EXACTLY at points where PiP would appear if I hadn't ripped it out with BD-RB. What do you think could cause this?

Maybe it's a bad idea to keep all the PiP info in the MPLS even though it doesn't actually exist on file (references to tracks 1A00 and 1B00, and the long list of sub-path chapter points).

Otherwise, there must be some reason PowerDVD9 crashes on the RB but not the original disc. We could say it's a PDVD9 bug since it's crashing instead of erroring, but it's obvious that it's seeing (or not seeing) something in the MPLS that it's not expecting to. And maybe it crashes because that thing is out-of-spec and the coders didn't think they'd need to handle such a case.

A penny for your thoughts.


Edit:
In addition to the main MPLS (00001.mpls), the disc has another playlist (00060.mpls) that is the same as the first, except it doesn't contain the subpath and pip data. I tried overwriting 00001.mpls with 00060.mpls, and viola - PowerDVD9 plays the disc perfectly, chapter selection works, seeking, and everything else. Could this, perhaps, validate my abovementioned point?

Edit 2:
I can now confirm that the OUT values calculated by 0.30.04 are correct. However, output still crashes on PDVD9 where PiP should be.

[jdobbs]

I've just updated the first post in this thread to include a link to the most recent release (v0.30.04) of BD-RB. Changes:- Corrected an error in which the SubPlayItem OUT
value was not being updated properly in the SubPath
table of the MPLS. This could be the root cause of
several reported inconsistencies.
- Other minor corrections and cosmetic fixes.