BD Rebuilder Beta - Bug Reports Only

[Capsbackup]

jdobbs:

I noticed that if I open 00000.m2ts (main movie) on the original batman begins disc using tsmuxergui all the audio tracks are flagged with timeshift=125ms. On the backup I made using BD-RB the 00000.m2ts does not have that flag. Is that on purpose?

I mean, is BD-RB compensating for the timeshift?

@PurpleMan;
I commented on this to you back on 8-22-08, post #4725 (page 237)


I am curious, if you burn your backup to BD-R/RE media and play it back on a standalone, does the movie have the audio in sync?
Mine was off by 250ms, very noticeable and not enjoyable to watch. It took some adjusting to finally get the audio in sync, but the backup looks great!
My region A original Batman Begins shows 83ms audio delay for all audio tracks. I and others (Furiousflea at least) have also reported this issue.
I was only able to get the audio in sync by doing a manual backup of 00000.m2ts by command line with the meta file from BD-RB, inserting timeshift = 250 in that meta file, rebuilding that 00000.m2ts file individually, and substituting it in place of the BD-RB version upon rebuild. ( 83ms did not correctly fix the async)
Tedious, yes, but the backup plays in sync now. ( I can be determined at times :p )
I reported this way back, and at that time seems like one of those rare discs that are troublesome. But timing is everything. :) I did not want to present jdobbs with an issue that is rare and not highly reported as a bug. ( not sure it is)
I believe jdobbs reported that audio delays are corrected with BD-RB, but not sure when. It would not have mattered with this disc anyway, since the actual 83ms delay was not enough to correct the async anyway.

[Aratar]

Another thing:

you can find out about the field order by evaluating movement using the avisynth command:

DirectshowSource("00xxx.m2ts", fps=29.97, framecount=10328, audio=false)
AssumeBFF().SeparateFields() <-- BFF if movement is fluent
#AssumeTFF().SeperateFields() <-- TFF if movement is fluent
ConvertToYV12()

as well as swap the field order for encoding with

SwapFields()

so I guess there'd be no need for a patched x264 version.

[jdobbs]

Another thing:

you can find out about the field order by evaluating movement using the avisynth command:

DirectshowSource("00xxx.m2ts", fps=29.97, framecount=10328, audio=false)
AssumeBFF().SeparateFields() <-- BFF if movement is fluent
#AssumeTFF().SeperateFields() <-- TFF if movement is fluent
ConvertToYV12()

as well as swap the field order for encoding with

SwapFields()

so I guess there'd be no need for a patched x264 version. Uhhh... and I'm supposed to make a program do that how???? Or were you suggesting that I put a person in the BD-RB zip file for distribution to look at the output?

Also, doing what you are suggesting would make it playback correctly on an output device. But it gets frame-served to the encoder, and if an encoder will only do one type (e.g. TFF) or it has nothing telling it that the field order and it is getting fed frames for encoding, this won't do a thing. This first example doesn't change the position of the lines in the frame in any way. Swapfields actually will change the fields assuming you know when it is wrong -- but they are now out of position (line 2 is now above line 1, etc.) and what do you do when you have hybrid streams or changing field orders?

[Edit] By the way -- I have no idea how X264 detects or outputs interlaced field order, so please don't quote me as saying it does it one way or the other.

[jdobbs]

When you see combing on interlaced encoded material then your playback filter/software isn't properly deinterlacing the interlaced material. There are several 'methods' to deinterlace the picture for a progressive screen playback. Not all of them 'reveal' field order issues. The issue I was talking about looks like that:

http://www.100fps.com/wrongfieldorder.avi
(taken from http://www.climaxtek.com/Faq/Deinterlacing.htm)

As I said, I encode interlaced material with the keep_interlacing=1 function (reason I mentioned earlier) and the output looks just like that on my standalone player as well as proper playback software like 'powerdvd 9' (deinterlacing is set to hardware).
I remember using mpeg2 encoding it was even possible to change the field order interpretation 'after' the encoding with a bitstream modifier (like pulldown.exe, restream or whatever) but I doubt that's possible with mpeg4 derivates. You can change the field order to what you want by shifting up or down one line. That's how CCE does it with its MPEG encoding. You can't change the order after encoding (pulldown.exe isn't related to that in any way, it works to change a framerate by using RFF/TFF flags to insert pseudoframes).

As I've said (several times now) the problem isn't in the changing of field order-- it is in the detection of field order. Just because a stream starts with one field order, there is no guarantee it stays that way. In fact you will find sources that also embed progressive content with pulldown in random places throughout the stream. I am trying to avoid having to do a 40GB scan of every source... I can do that very easily and simply by decombing the source. Which (surprise, surprise) is exactly what the default setting already does.

You're suggesting manual interface solutions as a solution and are making the assumption that since you can look at a screen and say "that doesn't look right" it should be easy to program the same. That very definitely isn't the case.

[jdobbs]

To all,

Enough on this interlacing subject. I appreciate the help, but I understand very well how all this all works. I'll work on it and do it the way I think is best. No more suggestions... let's please get back to bug reports.

[PurpleMan]

@PurpleMan;
I commented on this to you back on 8-22-08, post #4725 (page 237)


My region A original Batman Begins shows 83ms audio delay for all audio tracks. I and others (Furiousflea at least) have also reported this issue.
I was only able to get the audio in sync by doing a manual backup of 00000.m2ts by command line with the meta file from BD-RB, inserting timeshift = 250 in that meta file, rebuilding that 00000.m2ts file individually, and substituting it in place of the BD-RB version upon rebuild. ( 83ms did not correctly fix the async)
Tedious, yes, but the backup plays in sync now. ( I can be determined at times :p )
I reported this way back, and at that time seems like one of those rare discs that are troublesome. But timing is everything. :) I did not want to present jdobbs with an issue that is rare and not highly reported as a bug. ( not sure it is)
I believe jdobbs reported that audio delays are corrected with BD-RB, but not sure when. It would not have mattered with this disc anyway, since the actual 83ms delay was not enough to correct the async anyway.

You are mistaken, the only audio track with a 83ms delay is the secondary audio for the PiP. the rest of the tracks have a 125ms delay, and as far as I can tell when I delay the audio of my backup for 125ms it puts the movie in sync.
I might be wrong tho. Either way, this is an issue that needs to be addressed, so I think it's best we'll let jdobbs have a look at it, as he has the disc himself.

[jdobbs]

Okey dokey, thanx for looking into that. If I may be so cheeky, if you do have "The Matrix" (or any of the trilogy I would assume since they were released with matching extras) would you be so kind as to have a look at the main making of documentary with\without with "KEEP_INTERLACIN=1".

If you could then go to a bit that is live action behind the scenes and tell me if you can see the film look you get as you would in a main movie Vs how it looks on the original.

I guess there really is no way around it then, but I'm greatful for you having a good look at it as you have.

Cheers, Rob There's always a way around it, even if we don't yet know what it is yet... which (of the many) videos are you referencing? They all look like "making of" to me. If you know the M2TS, that would make it a lot easier.

[gandalf027]

Hey jdobbs,

Been a long time user of dvd rebuilder .. trying the br version ;)
I tried with The Shawshank Redemption movie only and i got this .. it seems it's the famous error.
I am runing on Windows 7.
Maybe it's the cause of the problem?
Thanks

[00:20:14] PHASE ONE, Encoding
- [00:20:14] Extracting A/V streams [VID_00002]
- [00:30:52] Reencoding: VID_00002 (1 of 1)
- [00:30:52] Collecting video information
- Video: 1920x1080, 23,976fps, 205.076 frames
- Bitrate: 6.431 Kbs
- [00:30:52] Reencoding: VID_00002, Pass 1 of 2
- [00:31:53] GUI issue, no hWnd returned.
- Encode failed. Retrying.

[Capsbackup]

You are mistaken, the only audio track with a 83ms delay is the secondary audio for the PiP. the rest of the tracks have a 125ms delay, and as far as I can tell when I delay the audio of my backup for 125ms it puts the movie in sync.
I might be wrong tho. Either way, this is an issue that needs to be addressed, so I think it's best we'll let jdobbs have a look at it, as he has the disc himself.

My Region A version is 83ms for ALL audio tracks. If yours is region A, then this will prove interesting!
I exhausted myself on this disc, and 83ms did not correct the async for me.
I agree that if jdobbs can address/confirm that any and all audio delays are corrected by BD-RB, this would be welcome.
As a side note, my BD-RB backup, if viewing the .m2ts file or the .mpls file, shows 0ms delay. The original .m2ts and .mpls files show the 83ms delay. If BD-RB does correct this delay, I am curious when and where. For most of my backups, I select do not reencode audio files, and keep HD audio for BD-25 backups. Thus the original audio file is kept. So where is the audio delay being corrected if not the .mpls, maybe the clpi? :confused:

[jdobbs]

Hey jdobbs,

Been a long time user of dvd rebuilder .. trying the br version ;)
I tried with The Shawshank Redemption movie only and i got this .. it seems it's the famous error.
I am runing on Windows 7.
Maybe it's the cause of the problem?
Thanks

[00:20:14] PHASE ONE, Encoding
- [00:20:14] Extracting A/V streams [VID_00002]
- [00:30:52] Reencoding: VID_00002 (1 of 1)
- [00:30:52] Collecting video information
- Video: 1920x1080, 23,976fps, 205.076 frames
- Bitrate: 6.431 Kbs
- [00:30:52] Reencoding: VID_00002, Pass 1 of 2
- [00:31:53] GUI issue, no hWnd returned.
- Encode failed. Retrying. What version are you using? I have to assume it's not that latest since that error is fixed now. I also noticed that you've stripped it from your post of the log.

[jointer]

Hi all

I have been tring to back up my new BD Grand Torino and State of Play and am having a fit. I've been using BD Rebuilder for almost a year without any issue now I've tried everthing and keep getting the error pasted below. As you can see I've tried the last 3 versions of BD Rebuilder with the same results. Any Ideas?

I've uninstalled and reinstalled the lates software posted here with no results.

I started using BD Rebuilder on Windows 7 beta x64 and now am using Windows 7 RC x64 I have not had any issues untill Grand Torino.

Any help would be greatly appreciated.

jointer


[18:51:09] BD Rebuilder v0.29.01 (beta)
- Source: GRAN_TORINO
- Input BD size: 27.67 GB
- Approximate total content: [01:56:34.779]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[18:51:10] PHASE ONE, Encoding
- [18:51:10] Extracting A/V streams [VID_00004]
- [19:00:37] Reencoding: VID_00004 (1 of 1)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[19:03:47] - Failed video encode, aborted
-----------------------
[19:37:50] BD Rebuilder v0.29.02 (beta)
- Source: GRAN_TORINO
- Input BD size: 27.67 GB
- Approximate total content: [01:56:34.779]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[19:37:55] PHASE ONE, Encoding
- [19:37:55] Extracting A/V streams [VID_00004]
- [19:47:20] Reencoding: VID_00004 (1 of 1)
- [19:47:31] GUI issue, no hWnd returned.

[22:00:19] BD Rebuilder v0.29.03 (beta)
- Source: GRAN_TORINO
- Input BD size: 27.67 GB
- Approximate total content: [01:56:34.779]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[22:00:22] PHASE ONE, Encoding
- [22:00:22] Extracting A/V streams [VID_00004]
- [22:09:49] Reencoding: VID_00004 (1 of 1)
- [22:10:50] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [22:11:51] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [22:12:52] GUI issue, no hWnd returned.
- Reached retry limit. Aborting.
[22:12:53] - Failed video encode, aborted
-----------------------
[22:27:27] BD Rebuilder v0.29.03 (beta)
- Source: GRAN_TORINO
- Input BD size: 27.67 GB
- Approximate total content: [01:56:34.779]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[22:27:30] PHASE ONE, Encoding
- [22:27:30] Extracting A/V streams [VID_00004]
- [22:36:55] Reencoding: VID_00004 (1 of 1)
- [22:37:55] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [22:38:57] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [22:39:58] GUI issue, no hWnd returned.
- Reached retry limit. Aborting.
[22:39:59] - Failed video encode, aborted
-----------------------
[20:19:03] BD Rebuilder v0.29.03 (beta)
- Source: STATE_OF_PLAY
- Input BD size: 27.36 GB
- Approximate total content: [02:07:08.037]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[20:19:10] PHASE ONE, Encoding
- [20:19:10] Extracting A/V streams [VID_00010]
- [20:27:34] Reencoding: VID_00010 (1 of 2)
- [20:28:34] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [20:29:40] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- [20:30:42] GUI issue, no hWnd returned.
- Reached retry limit. Aborting.
[20:30:43] - Failed video encode, aborted

[Status]
LABEL=GRAN_TORINO
VERSION=v0.29.03 (beta)
SOURCE_SIZE=29708101632
SOURCE_VIDEO_SIZE=29708101632
TARGET_SIZE=8294236160
REDUCTION=.279191052418707
RESIZE_1080=0
AUDIO_TO_KEEP=eng
SUBS_TO_KEEP=all
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=1
[00004]
AUDIO=10000
PGS=10000000
M2TS_TARGET=8294236160
RATE=8068

[Status]
LABEL=STATE_OF_PLAY
VERSION=v0.29.03 (beta)
SOURCE_SIZE=29373247488
SOURCE_VIDEO_SIZE=29373247488
TARGET_SIZE=8294236160
REDUCTION=.282373822076993
RESIZE_1080=0
AUDIO_TO_KEEP=eng
SUBS_TO_KEEP=all
BACKUP_MODE=1
QUICK=0
ENCODE_STEP=1
[00010]
AUDIO=1000
PGS=10000
M2TS_TARGET=8292249694
RATE=7326

[Race Guy]

You make a good point. The answer is "No." And that's an issue I have to fix for the next version. Even though every player I know of will play 1080p/29.97 -- it isn't in the BD standard.

OK jdobbs, I think we've have "CLARITY" now!

Guess what?!?! The Oppo WILL NOT "process" 1080p/29.97, obviously 'cause "it isn't in the BD standard". My guess is, it sees "29.97fps" & goes "this needs to be deinterlaced". It then does that & out comes "trashed" video to my screen.

BUT........, all is NOT lost! In the Oppo setup menu, we have: "Video Setup >> Output Resolution". Then you get a list where you choose your screen's "native rez". At the bottom of the list, there's "Source Direct". Choosing that, bypasses the player's internal processing/deinterlacer.

So I choose that and BOOM, my Samsung screen can read "1080p/29.97" & my "unwatchable" disc now looks pretty much just like the original! If that's what you mean by "every player I know of will play 1080p/29.97", I guess the Oppo "plays it" too!

The BIG question is, WHERE do you go from here? Outputting "non BD standard" vid seems wrong on the face of it. I'll BET the Flea's "Matrix Extras" cause his player to "choke" the same way mine did. Let me guess, 480p/29.97 isn't "BD standard" either.

Once I get a few spare CPU cycles, I'm gonna try the "KEEP_INTERLACING=1" switch, let Mr. Oppo deinterlace it & we'll see what I get.

See ya!

[vsj023]

jdobbs

i posted this earlier and i know your very busy with this program that is awesome, updated to the newest version and everytime i try to backup my copy of "Sunshine" it gives me the following:
[22:01:29] BD Rebuilder v0.29.03 (beta)
- Source: SUNSHINE_US
- Input BD size: 36.79 GB
- Approximate total content: [03:45:18.805]
- Target BD size: 22.46 GB
[22:01:30] PHASE ONE, Encoding
- [22:01:30] Extracting A/V streams [VID_00001]
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: E:\VIDEOS\BLU-RAY\SUNSHINE_US\BDMV\STREAM\00001.m2ts
- Error in attempt to extract audio/subs.
- Reading buffer overflow. Possible container streams are not syncronized. Please, verify stream fps. File name: E:\VIDEOS\BLU-RAY\SUNSHINE_US\BDMV\STREAM\00001.m2ts
[22:01:37] - Failed to retrieve audio, aborted

Here's the INI:
[Options]
RESIZE=0
MODE=0
PRIORITY_CLASS=0
TARGET_SIZE=23000
ENCODE_QUALITY=5
QUICK_EXTRAS=0
AUDIO_TO_KEEP=eng;spa;
SUBS_TO_KEEP=eng;spa;
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450
ONEPASS_ENCODING=0
VERBOSE_STATUS=1
[Paths]
SOURCE_PATH=E:\VIDEOS\BLU-RAY\SUNSHINE_US\
WORKING_PATH=C:\WORKING\

I re-installed latest ffdshow_rev2661_20090207_clsid, latest Haali app and Avisynth_257 and i kee getting the same error. I have used this app from the beginning and i've never had problems until this version of BD Rebuilder. Any suggestions? I would really appreciate the help. Thanks.

[Furiousflea]

There's always a way around it, even if we don't yet know what it is yet... which (of the many) videos are you referencing? They all look like "making of" to me. If you know the M2TS, that would make it a lot easier.

Any of the 480i\60 m2ts will be fine as long as they contain "live action" video AND film too.

This results in...

1. zig-zags everywhere. (KEEP_INTERLACING=1)

OR

2. Juddering. (KEEP_INTERLACING=0)

(This is apparent on all discs I have checked in parts that were originally 480i\60)

If you run the m2ts through an encoding frontend like "Ripbot264" and set your output to 60fps AND de-interlace. You will see what the original looks like. Sure the 60fps might be interpolated technically from the fields, but it's how all live action video is output to get that 60fps look.

I'm just trying to retain that look.

[astraub]

Hi,

just tried to process Die hard 4 with BR RB - unfortunaely it tells me that the (decrypted) copy is not in BD format. I had a closer look and found that the main movie is 00020.m2ts instead of the usual 00001.mts. The first two numbers (00001.m2ts and 00002.m2ts) are completely missing on the disk !?

Any idea what could be done?

[jdobbs]

Hi,

just tried to process Die hard 4 with BR RB - unfortunaely it tells me that the (decrypted) copy is not in BD format. I had a closer look and found that the main movie is 00020.m2ts instead of the usual 00001.mts. The first two numbers (00001.m2ts and 00002.m2ts) are completely missing on the disk !?

Any idea what could be done? That means exactly what it says. The path you chose isn't properly formatted for BD. You are either missing M2TS, MPLS, or CLPI file(s) -- or one of the required directories. It was either a bad rip or files have been deleted. Sometimes people point to the wrong directory and cause this as well.

The directory isn't required to have 00001.m2ts or 00002.m2ts. It is only required to have some m2ts.

[jdobbs]

Any of the 480i\60 m2ts will be fine as long as they contain "live action" video AND film too.

This results in...

1. zig-zags everywhere. (KEEP_INTERLACING=1)

OR

2. Juddering. (KEEP_INTERLACING=0)

(This is apparent on all discs I have checked in parts that were originally 480i\60)

If you run the m2ts through an encoding frontend like "Ripbot264" and set your output to 60fps AND de-interlace. You will see what the original looks like. Sure the 60fps might be interpolated technically from the fields, but it's how all live action video is output to get that 60fps look.

I'm just trying to retain that look. Juddering?

I don't have a clue what outputting to 60fps has to do with anything... but I can assure you there is no BD standard for it.

[jdobbs]

OK jdobbs, I think we've have "CLARITY" now!

Guess what?!?! The Oppo WILL NOT "process" 1080p/29.97, obviously 'cause "it isn't in the BD standard". My guess is, it sees "29.97fps" & goes "this needs to be deinterlaced". It then does that & out comes "trashed" video to my screen.

BUT........, all is NOT lost! In the Oppo setup menu, we have: "Video Setup >> Output Resolution". Then you get a list where you choose your screen's "native rez". At the bottom of the list, there's "Source Direct". Choosing that, bypasses the player's internal processing/deinterlacer.

So I choose that and BOOM, my Samsung screen can read "1080p/29.97" & my "unwatchable" disc now looks pretty much just like the original! If that's what you mean by "every player I know of will play 1080p/29.97", I guess the Oppo "plays it" too!

The BIG question is, WHERE do you go from here? Outputting "non BD standard" vid seems wrong on the face of it. I'll BET the Flea's "Matrix Extras" cause his player to "choke" the same way mine did. Let me guess, 480p/29.97 isn't "BD standard" either.

Once I get a few spare CPU cycles, I'm gonna try the "KEEP_INTERLACING=1" switch, let Mr. Oppo deinterlace it & we'll see what I get.

See ya! I'm making some changes for the next release. When I'm done all interlaced sources will be decombed and output as interlaced.

[jdobbs]

Okey dokey, thanx for looking into that. If I may be so cheeky, if you do have "The Matrix" (or any of the trilogy I would assume since they were released with matching extras) would you be so kind as to have a look at the main making of documentary with\without with "KEEP_INTERLACIN=1".

If you could then go to a bit that is live action behind the scenes and tell me if you can see the film look you get as you would in a main movie Vs how it looks on the original.

I guess there really is no way around it then, but I'm greatful for you having a good look at it as you have.

Cheers, Rob I see what you mean. The extras in "The Matrix" are exceptionally ugly. I'm working on it to see if there's anything I can do.

[OEM]

My apologies if this is a known problem, I did a search and couldn't find anything;

I've had no problems with 1080p/DVD9, but I recently tried the 720p resize option with mixed results (on Windows 7). I tried the following movies:

The Happening (Region A)
Max Payne (Region B)
The Mirror (Region B)
Bedtime Stories (Region B)

Only Bedtime Stories came out at 720p, the rest were all 1080p. I tried again on a different computer running Vista 64 with the exact same results. I also tried older versions of BD Rebuilder again with no luck. I then tried The Dark Knight (Region B), and it came out at 720p. So that's two out of five movies that worked so far.

This is no big deal. BD Rebuilder is a terrific piece of software, and this is a minor problem. But I thought I'd mention it anyway. Could there be something wrong with my setup ?

[Sharc]

@OEM
Interesting; the same happened to me recently: I enabled resize to 720p, but the encode came out as 1080p (although the .log confirmed the resizing to 720p). Don't know if this may happen only when the BD contains PIP (secondary video).

[jdobbs]

My apologies if this is a known problem, I did a search and couldn't find anything;

I've had no problems with 1080p/DVD9, but I recently tried the 720p resize option with mixed results (on Windows 7). I tried the following movies:

The Happening (Region A)
Max Payne (Region B)
The Mirror (Region B)
Bedtime Stories (Region B)

Only Bedtime Stories came out at 720p, the rest were all 1080p. I tried again on a different computer running Vista 64 with the exact same results. I also tried older versions of BD Rebuilder again with no luck. I then tried The Dark Knight (Region B), and it came out at 720p. So that's two out of five movies that worked so far.

This is no big deal. BD Rebuilder is a terrific piece of software, and this is a minor problem. But I thought I'd mention it anyway. Could there be something wrong with my setup ? I don't know how that could happen... I'll take a look at it.

If may very well be that I disabled the resize when there is PiP (I seem to recall doing so), but I'll have to check.

[jdobbs]

Okey dokey, thanx for looking into that. If I may be so cheeky, if you do have "The Matrix" (or any of the trilogy I would assume since they were released with matching extras) would you be so kind as to have a look at the main making of documentary with\without with "KEEP_INTERLACIN=1".

If you could then go to a bit that is live action behind the scenes and tell me if you can see the film look you get as you would in a main movie Vs how it looks on the original.

I guess there really is no way around it then, but I'm greatful for you having a good look at it as you have.

Cheers, Rob I gotta tell you, for all the space that is available on BD, there is absolutely no excuse for how bad the quality is on the extras of "The Matrix" -- and I'm talking about the original disc, here, not the backup... it's a blocky mess.

[gandalf027]

What version are you using? I have to assume it's not that latest since that error is fixed now. I also noticed that you've stripped it from your post of the log.

Well i think it was Windows7 .. tried on a Vista 64b and no problem so far.

I'll give more feedback once it's finished.

cheers

[setarip_old]

@gandalf027

I believe "jdobbs" is asking you which version of BD Rebuilder you are using, not which O/S...

[gandalf027]

@gandalf027

I believe "jdobbs" is asking you which version of BD Rebuilder you are using, not which O/S...

It's the last version .. with windows7 it gave me te error .. with windows vista 64b all went well.

[astraub]

In the latest version the program does not automatically select the languages and subtitles, which have been selected in the programs preferences, anymore.

[Willobee]

@astraub

I am not having this problem. Automatic selection of langauges and subtitles is working for the BD's I have been rebuilding. Is this a problem on all of your BD's or just a single one?

Using v0.29.03 you can double click the subtitles and languages to toggle them off and on if the automatic slection does not work.

[samtroy]

@jdobbs

Is there a bug in the latest version? I'm doing tests with my purchased copy of ST and choose 2 different AC3 audiotracks (english and italian). I also choose 'Do not reencode AC3 streams'.

But BD Rebuilder DOES reencode the AC3 audiotracks! Afterwards there are *four* (not two!) AC3 files in the workfolder of almost the same size and similar names.

Why is that? Is this normal?

Here are the relevant ini settings:

RESIZE=0
MODE=1
TARGET_SIZE=8300
...
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=0
AVCHD=0
REMOVE_WORKFILES=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=8300
[Paths]
...

Thanks for your help.

[jdobbs]

@jdobbs

Is there a bug in the latest version? I'm doing tests with my purchased copy of Sweeney Todd and choose 2 different AC3 audiotracks (english and italian). I also choose 'Do not reencode AC3 streams'.

But BD Rebuilder DOES reencode the AC3 audiotracks! Afterwards there are *four* (not two!) AC3 files in the workfolder of almost the same size and similar names.

Why is that? Is this normal?

Here are the relevant ini settings:

RESIZE=0
MODE=1
TARGET_SIZE=8300
...
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=0
AVCHD=0
REMOVE_WORKFILES=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=8300
[Paths]
...

Thanks for your help. No bug that I know of. Are you using BATCH mode? In BATCH, the settings are stored when you add it to the queue, and any changes made later has no effect on the BATCH encode.

Also, are you sure two of the tracks aren't secondary audio tracks? You said "similar names", which would be the case if that were so.

[edit] I just went back and looked at the code and it is implemented correctly. I did a couple of tests, and they appear to have worked correctly also.

[jdobbs]

I have just updated the link of the first page of this thread to a new version of BD-RB (v0.29.04). Changes for this version: - Made one more adjustment to prevent "GUI Issue,
no hWnd returned". I think this may be gone for
good now. It finally became clear as to what was
causing this to randomly occur.
- Fixed an error in which progressive output could
under some circumstances be created at an illegal
(29.97fps, 25fps) framerate.
- Changed the default processing for interlaced
sources. All sources that are interlaced now are
kept interlaced in the output. This means the
"KEEP_INTERLACING" INI setting has been removed
(as unnecessary)
- Added a "DEINTERLACING=" hidden option, see the
description in HIDDENOPTS.TXT for details.
- Changed the type of AVISYNTH preprocessing used to
ensure comb-free deinterlacing. Interlaced sources
should be more crisp, and free of jagged edges now.
- Corrected a "Selected source is not BD format" error
that could happen on very small sources.
- Added a "quick search" function to identify sources
that are Bottom Field First (BFF) interlaced.
- Added code to scan all M2TS files and find audio
streams that have delayed PTS times (for correction).
- Other minor corrections and cosmetic fixes.

[chudm]

I have just updated the link of the first page of this thread to a new version of BD-RB (v0.29.04). Changes for this version: - Made one more adjustment to prevent "GUI Issue,
no hWnd returned". I think this may be gone for
good now. It finally became clear as to what was
causing this to randomly occur.
- Fixed an error in which progressive output could
under some circumstances be created at an illegal
(29.97fps, 25fps) framerate.
- Changed the default processing for interlaced
sources. All sources that are interlaced now are
kept interlaced in the output. This means the
"KEEP_INTERLACING" INI setting has been removed
(as unnecessary)
- Added a "DEINTERLACING=" hidden option, see the
description in HIDDENOPTS.TXT for details.
- Changed the type of AVISYNTH preprocessing used to
ensure comb-free deinterlacing. Interlaced sources
should be more crisp, and free of jagged edges now.
- Corrected a "Selected source is not BD format" error
that could happen on very small sources.
- Added a "quick search" function to identify sources
that are Bottom Field First (BFF) interlaced.
- Added code to scan all M2TS files and find audio
streams that have delayed PTS times (for correction).
- Other minor corrections and cosmetic fixes.

great news man! thx! :)

[PurpleMan]

- Added code to scan all M2TS files and find audio
streams that have delayed PTS times (for correction).

Is this refering to the Batman Begins timeshift bug? If so, could you elaborate what exactly was the problem and how we're working around it?

Thanks for the excellent work!

[jdobbs]

Is this refering to the Batman Begins timeshift bug? If so, could you elaborate what exactly was the problem and how we're working around it?

Thanks for the excellent work! Yes. In looking at the M2TS file, I noticed that the first Presentation Time Stamp (PTS) for the audio track doesn't start until 83ms after the first PTS for the video. That's where the sync error came from. I just added a routine that scans all M2TS files looking for the starting PTS for video/audio tracks and accounted for any delta. If there is one, I then put a corrective "timeshift=XXms" in the meta when demuxing the audio.

Interestingly, this is pretty rare -- I could only find one other disc of my standard working/test set that had an offset, and it wasn't enough to matter (about 6ms). But you have to cover all scenarios. The new scan will probably add a couple of seconds to the initial scan of most discs when you select the source path.

As long as I was scanning anyway -- I also added code that looks for the TFF flag on video streams -- so I can sense when a source was BFF (but not pulldown)... which, by the way, turned out to be part of the the issue with the "Making Of" extras on "The Matrix".

[Capsbackup]

Yes. In looking at the M2TS file, I noticed that the first Presentation Time Stamp (PTS) for the audio track doesn't start until 83ms after the first PTS for the video. That's where the sync error came from. I just added a routine that scans all M2TS files looking for the starting PTS for video/audio tracks and accounted for any delta. If there is one, I then put a corrective "timeshift=XXms" in the meta when demuxing the audio.

Interestingly, this is pretty rare -- I could only find one other disc of my standard working/test set that had an offset, and it wasn't enough to matter (about 6ms). But you have to cover all scenarios. The new scan will probably add a couple of seconds to the initial scan of most discs when you select the source path.

As long as I was scanning anyway -- I also added code that looks for the TFF flag on video streams -- so I can sense when a source was BFF (but not pulldown)... which, by the way, turned out to be part of the the issue with the "Making Of" extras on "The Matrix".

I agree, there are not many discs I have come across that have audio delays. However, could you clarify the correction.
If the original .mpls/m2ts shows a delay, for example Batman Begins 83ms, should BD-RB's backup also show a delay in the same mpls/m2ts?
If one chooses to keep HD audio and do not reencode ac3, will this delay be maintained per example above? Or is there another method for you to correct/address the delay?
I guess I am just curious how to determine that the delay is correct besides the visual check I always perform anyway. :p

[jdobbs]

I agree, there are not many discs I have come across that have audio delays. However, could you clarify the correction.
If the original .mpls/m2ts shows a delay, for example Batman Begins 83ms, should BD-RB's backup also show a delay in the same mpls/m2ts?
If one chooses to keep HD audio and do not reencode ac3, will this delay be maintained per example above? Or is there another method for you to correct/address the delay?
I guess I am just curious how to determine that the delay is correct besides the visual check I always perform anyway. :p No. Not normally. The audio stream is corrected to include the delay. For example, if you have an 83ms delay you would put 83ms of silence at the beginning of the audio stream. I'm actually letting TSMUXER do the adjustment during the demux by using the timeshift command -- but that would be my guess as to how it does it. Since the delay is added during the demux, it would carry through any reencode, or be there already if you do keep the HD original.

[Capsbackup]

No. Not normally. The audio stream is corrected to include the delay. For example, if you have an 83ms delay you would put 83ms of silence at the beginning of the audio stream. I'm actually letting TSMUXER do the adjustment during the demux by using the timeshift command -- but that would be my guess as to how it does it. Since the delay is added during the demux, it would carry through any reencode, or be there already if you do keep the HD original.

Interesting. Is there any way to tell if tsMuxer applies the delay to the demux?
My experiment with Batman Begins, doing just this and remuxing it back into BD-RB would still not bring the audio in sync.
Only after editing the BD-RB meta file for this m2ts file to "time shift=250",( 83ms was not enough) then rebuilding that m2ts thru the command line, and then substituting this new m2ts into the BD-RB rebuild was I able to get the audio in sync.
I noticed that when checking this new mpls/m2ts created with BD-RB with tsMuxeR, it now also showed the 250ms delay.
This worked for me for this disc, be it cumbersome, audio was now in sync.
So, not to be a bother, but this method of timeshift within the BD-RB meta file also works, and seems to reflect the original mpls/m2ts as well.

[jdobbs]

Interesting. Is there any way to tell if tsMuxer applies the delay to the demux?
My experiment with Batman Begins, doing just this and remuxing it back into BD-RB would still not bring the audio in sync.
Only after editing the BD-RB meta file for this m2ts file to "time shift=250",( 83ms was not enough) then rebuilding that m2ts thru the command line, and then substituting this new m2ts into the BD-RB rebuild was I able to get the audio in sync.
I noticed that when checking this new mpls/m2ts created with BD-RB with tsMuxeR, it now also showed the 250ms delay.
This worked for me for this disc, be it cumbersome, audio was now in sync.
So, not to be a bother, but this method of timeshift within the BD-RB meta file also works, and seems to reflect the original mpls/m2ts as well. Hmmm... I'm doing "Batman Begins" right now -- I'll let you know how it turns out. If it doesn't work like I thought, I can add the delay during the remux (which is what I'm guessing you did).

[Capsbackup]

Hmmm... I'm doing "Batman Begins" right now -- I'll let you know how it turns out. If it doesn't work like I thought, I can add the delay during the remux (which is what I'm guessing you did).

Correct. I inserted/edited BD-RB's meta file for that m2ts with "timeshift=250ms" in the appropriate location within that meta file.
However, just editing and saving this meta file inside the Workfiles folder was not working. Upon rebuild, BD-RB would change/correct my edits to back to the original meta. I had to run that edited meta from the command line, and then substitute this new m2ts/clpi into the BD-RB Workfiles folder for a new rebuild. ( Using a creative rebuild, canceling the rebuild just after the final m2ts is created, substituting the new m2ts/clpi for the ones BD-RB just rebuilt, and then selecting rebuild again and letting BD-RB just integrate all those m2ts/clpi/mpls files into the new BluRay structure. :)
EDIT:
I will be curious if you have audio sync this first time try. Though 83ms is the original delay, this was not enough to correct the async for me. Only after several tests/burns to BD-RE did I finally get audio sync, but it took 250ms. Definately an odd disc!

[jdobbs]

Correct. I inserted/edited BD-RB's meta file for that m2ts with "timeshift=250ms" in the appropriate location within that meta file.
However, just editing and saving this meta file inside the Workfiles folder was not working. Upon rebuild, BD-RB would change/correct my edits to back to the original meta. I had to run that edited meta from the command line, and then substitute this new m2ts/clpi into the BD-RB Workfiles folder for a new rebuild. ( Using a creative rebuild, canceling the rebuild just after the final m2ts is created, substituting the new m2ts/clpi for the ones BD-RB just rebuilt, and then selecting rebuild again and letting BD-RB just integrate all those m2ts/clpi/mpls files into the new BluRay structure. :)
EDIT:
I will be curious if you have audio sync this first time try. Though 83ms is the original delay, this was not enough to correct the async for me. Only after several tests/burns to BD-RE did I finally get audio sync, but it took 250ms. Definately an odd disc! I just tested it. 83ms is the correct value on my system, it synched up perfectly (after I did it right)... but in the release I did it ass-backwards. The "timeshift" parameter has to be (as you did it) on the mux, not the demux.

I've corrected it for the next release. Luckily there aren't very many discs out there that need it.

[Capsbackup]

I just tested it. 83ms is the correct value on my system, it synched up perfectly (after I did it right)... but in the release I did it ass-backwards. The "timeshift" parameter has to be (as you did it) on the mux, not the demux.

I've corrected it for the next release. Luckily there aren't very many discs out there that need it.

Great! Thankfully there are not many discs made with audio delays of significance, but when there is, you have it covered. :p :thanks:

[samtroy]

No bug that I know of. Are you using BATCH mode? In BATCH, the settings are stored when you add it to the queue, and any changes made later has no effect on the BATCH encode.

Also, are you sure two of the tracks aren't secondary audio tracks? You said "similar names", which would be the case if that were so.

[edit] I just went back and looked at the code and it is implemented correctly. I did a couple of tests, and they appear to have worked correctly also.

No, I didn't use batch mode but the normal movie-only mode. But I will do some more tests later on and let you know more specifics tomorrow.

Thanks for checking and generally for your awsome program :thanks:.

[chudm]

hi guys tried to do a rip and cant do it, says target is too small to continue, i wrote on the ini the force encode =1 option, but still had the same problem with the lastest 2 beta, any suggestion?

[jdobbs]

hi guys tried to do a rip and cant do it, says target is too small to continue, i wrote on the ini the force encode =1 option, but still had the same problem with the lastest 2 beta, any suggestion? It means that all the audio and subtitle selections you have made combined are already too big to fit on the output disc size you've chosen -- even without the video. The only way you can fix it is to either choose a bigger output size or select fewer audio/subs to keep. FORCE_ENCODE won't help becaus you can't reencode to a negative size... this is most likely seen when LPCM or lossless tracks exist and you're trying to output to BD-5/9.

[chudm]

It means that all the audio and subtitle selections you have made combined are already too big to fit on the output disc size you've chosen -- even without the video. The only way you can fix it is to either choose a bigger output size or select fewer audio/subs to keep. FORCE_ENCODE won't help becaus you can't reencode to a negative size... this is most likely seen when LPCM or lossless tracks exist and you're trying to output to BD-5/9.

im doing full backup to bd25

[Sharc]

I just tested it. 83ms is the correct value on my system, it synched up perfectly (after I did it right)... but in the release I did it ass-backwards. The "timeshift" parameter has to be (as you did it) on the mux, not the demux.

I've corrected it for the next release. Luckily there aren't very many discs out there that need it.
Looks like this would also solve the sync problem which I reported earlier for "DOUBT". It was actually the only disc I ever had a sync problem with :)

[Race Guy]

This bug is called "The Case Of The Missing Menu Text". But I don't think it's really a bug!

I've had 3 rebuilds that have ended up "stuck in an endless loop" on the top menu, because the "button text" is not there. I'm talking about the "Play", "Audio Select", "Special Features"....., etc "buttons".

On one of them (Elton 60), I'm able to use my player's "Go-To" button & then manually select the main title & then the disc takes off & plays fine. Even the pop up menu works to navigate chapter to chapter.

The other two, (Dave Matthews Radio City & Baraka) wont allow me to do that. On the latest one to fail, (Baraka) I did a little investigation With BD Info & found the culprit. The "interactive graphics stream (IGS)" is missing from the rebuilt menu video's remux.

Here's the Original:

Name_________Time In_______Length
00012.M2TS___0:00:00.000___0:08:45.525

STREAM DIAGNOSTICS:

File___________PID___________Type___Codec
00012.M2TS___4113 (0x1011)___0xEA___VC-1
00012.M2TS___4352 (0x1100)___0x81___AC3
00012.M2TS___4353 (0x1101)___0x81___AC3
00012.M2TS___5120 (0x1400)___0x91___IGS

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

Here's the Rebuild:

Name_________Time In_______Length
00012.M2TS___0:00:00.000___0:08:45.525

STREAM DIAGNOSTICS:

File___________PID___________Type___Codec
00012.M2TS___4113 (0x1011)___0xEA___VC-1
00012.M2TS___4352 (0x1100)___0x81___AC3

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

So then I reopened the project in BD-RB & discovered that it's not really a "bug"! I have my config setup to keep all English subs only. That IGS (for whatever reason???) had 3 "languages", 2 English & 1 Spanish. With my config, Spanish is eliminated which eliminated the WHOLE IGS!

Unfortunately, I dumped my workfiles, so for the helluvit, & rebuilt that menu vid again, this time with all the audio & all the sub languages. I then replaced those "corrected" m2ts & clpi files in the structure. I burned it to RE & it appears that I "saved" the project! The menu now comes up & functions & it appears all is good now!

Is what I did there really a "good" fix jdobbs?

I think the moral of this story is "keep ALL your subs"!!!

[chudm]

This bug is called "The Case Of The Missing Menu Text". But I don't think it's really a bug!

I've had 3 rebuilds that have ended up "stuck in an endless loop" on the top menu, because the "button text" is not there. I'm talking about the "Play", "Audio Select", "Special Features"....., etc "buttons".

On one of them (Elton 60), I'm able to use my player's "Go-To" button & then manually select the main title & then the disc takes off & plays fine. Even the pop up menu works to navigate chapter to chapter.

The other two, (Dave Matthews Radio City & Baraka) wont allow me to do that. On the latest one to fail, (Baraka) I did a little investigation With BD Info & found the culprit. The "interactive graphics stream (IGS)" is missing from the rebuilt menu video's remux.

Here's the Original:

Name_________Time In_______Length
00012.M2TS___0:00:00.000___0:08:45.525

STREAM DIAGNOSTICS:

File___________PID___________Type___Codec
00012.M2TS___4113 (0x1011)___0xEA___VC-1
00012.M2TS___4352 (0x1100)___0x81___AC3
00012.M2TS___4353 (0x1101)___0x81___AC3
00012.M2TS___5120 (0x1400)___0x91___IGS

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

Here's the Rebuild:

Name_________Time In_______Length
00012.M2TS___0:00:00.000___0:08:45.525

STREAM DIAGNOSTICS:

File___________PID___________Type___Codec
00012.M2TS___4113 (0x1011)___0xEA___VC-1
00012.M2TS___4352 (0x1100)___0x81___AC3

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

So then I reopened the project in BD-RB & discovered that it's not really a "bug"! I have my config setup to keep all English subs only. That IGS (for whatever reason???) had 3 "languages", 2 English & 1 Spanish. With my config, Spanish is eliminated which eliminated the WHOLE IGS!

Unfortunately, I dumped my workfiles, so for the helluvit, & rebuilt that menu vid again, this time with all the audio & all the sub languages. I then replaced those "corrected" m2ts & clpi files in the structure. I burned it to RE & it appears that I "saved" the project! The menu now comes up & functions & it appears all is good now!

Is what I did there really a "good" fix jdobbs?

I think the moral of this story is "keep ALL your subs"!!!

yeap had the same problems with foo fighters bluray, and this elton john bluray

[DK]

I'm having problems with Tomb Raider 1 Region B

==========================
[21:48:28] BD Rebuilder v0.29.03 (beta)
[21:48:28] BEGIN - BATCH SEQUENCE
==========================
-----------------------
[21:48:28] PROCESSING BATCH FILE [1]
-----------------------
[08:06:27] BD Rebuilder v0.29.03 (beta)
- Source: LARA_CROFT_1
- Input BD size: 17,78 GB
- Approximate total content: [01:40:45.456]
- Target BD size: 7,72 GB
- MOVIE-ONLY mode enabled
[08:06:27] PHASE ONE, Encoding
- [08:06:27] Extracting A/V streams [VID_00004]
- [08:13:43] Reencoding: VID_00004 (1 of 2)
- Analyzing 25,42 10,00 18,45 21,28 20,28 20,10 19,95 20,07 20,10 20,09 [20,09]
- [20:32:34] Extracting A/V streams [VID_00006]
- [20:32:36] Reencoding: VID_00006 (2 of 2)
- Error in attempt to multiplex: MUX_00006.meta
- Can't open file: G:\DVD\TR1\WORKFILES\VID_00006.AVS.264
[20:32:45] - Failed to build structure, aborted

-----------------------

[22:32:23] BD Rebuilder v0.29.04 (beta)
- Source: LARA_CROFT_1
- Input BD size: 17,78 GB
- Approximate total content: [01:40:45.456]
- Target BD size: 7,72 GB
- MOVIE-ONLY mode enabled
[22:32:30] PHASE ONE, Encoding
- [22:32:30] Extracting A/V streams [VID_00004]
- [22:38:39] Reencoding: VID_00004 (1 of 2)
- [11:11:51] Extracting A/V streams [VID_00006]
- [11:11:51] Reencoding: VID_00006 (2 of 2)
- Error in attempt to multiplex: MUX_00006.meta
- Can't open file: G:\DVD\TR1\WORKFILES\VID_00006.AVS.264
[11:12:03] - Failed to build structure, aborted


VID_00006.AVS.264 is not present, only:

- VID_00006.AVS
- VID_00006.AVS.MKV
- VID_00006.AVS.MKV.stats

The main movie is:
VID_00004.AVS.264 and this was created properly and completely together with the two sound streams.

Muxing video + audio streams woorked fine via tsmuxer, so the goal was achieved: a movie only backup but i have no idea why bd rebuilder got stuck with two different versions and slightly different settings:
1pass with version 0.28.03 and 2 passes with 0.29.04

[chudm]

about the problems with some musical blurays jdobbs commented once that its caused possibly by lpcm audio or something like that, hope he can fix it sometime :)