BD Rebuilder Beta - Bug Reports Only

[diver90]

Having trouble with CARS - Trying to make a movie only copy on BD-R 25G disk. Here are the log files and a big thank you for any help you can provide...

-----------------------
[08:49:34] BD Rebuilder v0.36.02 (beta)
- Source: CARS_USA
- Input BD size: 27.21 GB
- Approximate total content: [01:56:35.988]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- X264 Tweak(s) enabled
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[08:49:37] PHASE ONE, Encoding
- [08:49:37] Extracting A/V streams [VID_00060]
- [09:14:26] Reencoding: VID_00060 (1 of 1)
- [09:14:26] Collecting video information
- [09:14:26] Keeping original video (no reencode)
- [09:14:26] Reencoding audio tracks (if req'd)
- [09:20:44] Multiplexing M2TS
[09:38:18]PHASE ONE complete
[09:38:18]PHASE TWO - Rebuild Started
- [09:38:18] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Pes packet len too large ( >100Mb). Bad stream or invalid codec speciffed.
[10:06:31] - Failed to REBUILD

[jdobbs]

Originally Posted by diver90

Having trouble with CARS - Trying to make a movie only copy on BD-R 25G disk. Here are the log files and a big thank you for any help you can provide...

-----------------------
[08:49:34] BD Rebuilder v0.36.02 (beta)
- Source: CARS_USA
- Input BD size: 27.21 GB
- Approximate total content: [01:56:35.988]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- X264 Tweak(s) enabled
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[08:49:37] PHASE ONE, Encoding
- [08:49:37] Extracting A/V streams [VID_00060]
- [09:14:26] Reencoding: VID_00060 (1 of 1)
- [09:14:26] Collecting video information
- [09:14:26] Keeping original video (no reencode)
- [09:14:26] Reencoding audio tracks (if req'd)
- [09:20:44] Multiplexing M2TS
[09:38:18]PHASE ONE complete
[09:38:18]PHASE TWO - Rebuild Started
- [09:38:18] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Pes packet len too large ( >100Mb). Bad stream or invalid codec speciffed.
[10:06:31] - Failed to REBUILD

I've done that exact disc as least 5-10 times with no issues. What X264 tweaks are enabled?

[diver90]

Originally Posted by jdobbs

I've done that exact disc as least 5-10 times with no issues. What X264 tweaks are enabled?

TWEAK_PASS_ONE=--force-cfr
TWEAK_PASS_TWO=--force-cfr

Turn LAVF off?

[jdobbs]

Originally Posted by diver90

TWEAK_PASS_ONE=--force-cfr
TWEAK_PASS_TWO=--force-cfr

Turn LAVF off?

You need to get rid of those. In v0.36.02 that parameter is already in the command line when it needs to be, and it shouldn't be there for sources that aren't using LAVF. A note to remember is that even though you may have LAVF selected -- there are times when it won't be used (out of necessity).

I have no idea if that is related to your problem, though (probably not).

[diver90]

Originally Posted by jdobbs

You need to get rid of those. In v0.36.02 that parameter is already in the command line when it needs to be, and it shouldn't be there for sources that aren't using LAVF. A note to remember is that even though you may have LAVF selected -- there are times when it won't be used (out of necessity).

I have no idea if that is related to your problem, though (probably not).

I have removed them and will try again with LAVF on and then off. Any other ideas in the interim?

[jdobbs]

Originally Posted by diver90

I have removed them and will try again with LAVF on and then off. Any other ideas in the interim?

Post the contents of you BDREBUILDER.INI file (in the BD-RB installation folder) so I can see if anything stands out as a possible cause.

[diver90]

Originally Posted by jdobbs

Post the contents of you BDREBUILDER.INI file (in the BD-RB installation folder) so I can see if anything stands out as a possible cause.

Thanks in advance for your assistance.

[Options]
MODE=1
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
TARGET_SIZE=23500
AUTO_BURN=1
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=0
DTS_REENCODE=1
AC3_REENCODE=1
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AVCHD=0
REMOVE_WORKFILES=0
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
[Paths]
SOURCE_PATH=C:\BD\1-BD\CARS_USA\
WORKING_PATH=C:\BD\BD REBUILDER TEMP\

[PurpleMan]

Originally Posted by jdobbs

I'll see if I can find "Pan's Labyrinth" and run it.

Thanks. In further efforts to get to the bottom of this, I opened VID_00033.avs (BD-RB generated) in VirtualDub (which points to the original m2ts file, VC1).

I have also copied this AVS to another one, and changed the source file inside to point to the encoded BD-RB file (h264).

I then began going frame-by-frame to see where things get bad. I've found out that on the encoded file there are certain frames (very little, for instance - the first one is #3640) that appear TWICE one after another (Shifting the rest of the movie).

The extremely weird thing is that on the AVS that bd-rb used (the one pointing to the original m2ts) - the frames appeared correctly in VirtualDub - no doubles!

So if the source AVS opens correctly, how the hell did the encoded file get all f***ed up? It actually makes sense that the decoding wasn't the problem - after all, internal x264 decoding caused a similar result.

A penny for your thoughts, jdobbs?

I want to continue investigating this. Got a direction?

Update: Thanks to a friend's vc1 dgindex, I can confirm that there is absolutely nothing special about the stream, it's completely progressive 1920:1088 w/ crop flag (to 1920x1080) - which is very much standard to VC1 streams. :/

[picrade]

I used BDRB to do a movie only BD-25 backup of Charade (Criterion), and the encoded BD was over sized.
Way over sized. It was about 800 MB over BD-25 limit.

After some digging I traced it to the audio track. It is LPCM 1 channel.
I chose to keep the LPCM track.
The problem is the demuxed wav file is about 900 MB, but scanning the BD with BDInfo shows that the audio track
takes twice as much space (about 1.8 Gig) in the m2ts stream.

Also on the main screen of BDInfo it shows the LPCM has a bit rate of 1152 kbs.
But after doing a bit rate scan it shows a bit rate of 2304 (double) in the report.
It is the same with the original disc.

The problem is BDRB calculates the video bit rate (and size of the output BD) based on the size of the wav file.
But after muxing it takes twice the size in the m2ts stream.

I never had problem going over size when keeping other lossless audio formats, Dolby or DTS.
This was my first try with LPCM.

Is there something peculiar about the LPCM audio that requires twice as much space when muxing?
Or is this an unusual case?

P.S. I solved the problem by setting the custom size to 1 Gig less than usual and re-encoded again.
This time the result was within the BD-25 limit.

[jdobbs]

Originally Posted by picrade

I used BDRB to do a movie only BD-25 backup of Charade (Criterion), and the encoded BD was over sized.
Way over sized. It was about 800 MB over BD-25 limit.

After some digging I traced it to the audio track. It is LPCM 1 channel.
I chose to keep the LPCM track.
The problem is the demuxed wav file is about 900 MB, but scanning the BD with BDInfo shows that the audio track
takes twice as much space (about 1.8 Gig) in the m2ts stream.

Also on the main screen of BDInfo it shows the LPCM has a bit rate of 1152 kbs.
But after doing a bit rate scan it shows a bit rate of 2304 (double) in the report.
It is the same with the original disc.

The problem is BDRB calculates the video bit rate (and size of the output BD) based on the size of the wav file.
But after muxing it takes twice the size in the m2ts stream.

I never had problem going over size when keeping other lossless audio formats, Dolby or DTS.
This was my first try with LPCM.

Is there something peculiar about the LPCM audio that requires twice as much space when muxing?
Or is this an unusual case?

P.S. I solved the problem by setting the custom size to 1 Gig less than usual and re-encoded again.
This time the result was within the BD-25 limit.

I've never heard of anything like that. I did a lot of testing during development to see what the M2TS overhead was for all the audio/video types. For LPCM is was typically a little less than 15%. It has worked well on every LPCM encode I've done. I can't imagine a 100% overhead for any kind of audio track.

[setarip_old]

@jdobbs

Regarding the post by "picrade" - Is it possible that the LPCM one channel audiostream is being converted to two channel stereo?

[jdobbs]

Originally Posted by setarip_old

@jdobbs

Regarding the post by "picrade" - Is it possible that the LPCM one channel audiostream is being converted to two channel stereo?

Definitely not if it is being kept intact. The size allocation is based upon the actual WAV file that is to be muxed. In his case he is saying that file doubles as a part of the mux. I'll look around to see if I can find a mono LPCM disc to test -- I think "Stagecoach" may be.

[PurpleMan]

@jdobbs:

I am pleased to announce that I got to the bottom of the problem with Pan's Labyrinth - and I've found the bug in BD-Rebuilder!

Apparently, the video was not the problem, it was flawless. What led me to the wrong conclusions I posted here is the poor performance of virtualdub and avisynth directshow decoding/seeking.

Anyway - the problem is that the DTS track on the original disc is muxed with a 1010ms delay. Inspecing BD-RB's meta file revealed that even though the audio file remained untouched, BD-RB did not copy the delay, and just muxed it as-is.

I remuxed it manually with the original-disc delay of 1010ms - and viola - perfect sync.

[jdobbs]

Originally Posted by PurpleMan

@jdobbs:

I am pleased to announce that I got to the bottom of the problem with Pan's Labyrinth - and I've found the bug in BD-Rebuilder!

Apparently, the video was not the problem, it was flawless. What led me to the wrong conclusions I posted here is the poor performance of virtualdub and avisynth directshow decoding/seeking.

Anyway - the problem is that the DTS track on the original disc is muxed with a 1010ms delay. Inspecing BD-RB's meta file revealed that even though the audio file remained untouched, BD-RB did not copy the delay, and just muxed it as-is.

I remuxed it manually with the original-disc delay of 1010ms - and viola - perfect sync.

I'll try "Pan's Labyrinth" to see what happens -- but BD Rebuilder very definitely finds and adjusts for delays. That was added in v0.29.04.

[PurpleMan]

Originally Posted by jdobbs

I'll try "Pan's Labyrinth" to see what happens -- but BD Rebuilder very definitely finds and adjusts for delays. That was added in v0.29.04.

I know you added it on v0.29.04 (If I recall correctly, I had something to do with it). Which makes me think that there's some reason that on this specific disc it didn't work. So what's different?

The only thing I can think of is that when I loaded the disc in BD-RB, it automatically unchecked the Spanish DTS track (original language, this is a Spanish movie) audio and checked only the English commentary track. I had to manually uncheck the English track and recheck the Spanish DTS track before I started processing. Could this be why it 'forgot' the audio delay?

I am, however, a 100% positive about this (ran this thru bd-rb 4 times, in 4 different work folders, resulted in 4 identical meta files - without the delay flag in it).

Also, just to be triple sure - When I open the original file in tsmuxer (GUI), it auto detects the delay and writes it in its generated meta-file, as well as DGIndex mentioning the delay on the filename of the demuxed audio. MUX_00033.meta, however, does not include it.

If all this information still isn't useful and you end up getting the disc - make sure you get the UK edition.

Hope this helped!

[jdobbs]

Originally Posted by PurpleMan

I know you added it on v0.29.04 (If I recall correctly, I had something to do with it). Which makes me think that there's some reason that on this specific disc it didn't work. So what's different?

The only thing I can think of is that when I loaded the disc in BD-RB, it automatically unchecked the Spanish DTS track (original language, this is a Spanish movie) audio and checked only the English commentary track. I had to manually uncheck the English track and recheck the Spanish DTS track before I started processing. Could this be why it 'forgot' the audio delay?

I am, however, a 100% positive about this (ran this thru bd-rb 4 times, in 4 different work folders, resulted in 4 identical meta files - without the delay flag in it).

Also, just to be triple sure - When I open the original file in tsmuxer (GUI), it auto detects the delay and writes it in its generated meta-file, as well as DGIndex mentioning the delay on the filename of the demuxed audio. MUX_00033.meta, however, does not include it.

If all this information still isn't useful and you end up getting the disc - make sure you get the UK edition.

Hope this helped!

Hmmm... don't remember if I adjust for that. I'll check the code and see.

[Edit] Yep. That's it. It is only scanning the selected audio streams, and the scan isn't redone when you check/uncheck. That was silly...

Thanks for the report and analysis. Much appreciated. It'll be fixed in the next release.

[PurpleMan]

Originally Posted by jdobbs

Hmmm... don't remember if I adjust for that. I'll check the code and see.

[Edit] Yep. That's it. It is only scanning the selected audio streams, and the scan isn't redone when you check/uncheck. That was silly...

Thanks for the report and analysis. Much appreciated. It'll be fixed in the next release.

Happy to help, as always!

[jdobbs]

Originally Posted by diver90

I have removed them and will try again with LAVF on and then off. Any other ideas in the interim?

Anything different on later run(s)?

[diver90]

Originally Posted by jdobbs

Anything different on later run(s)?

Thanks for asking. Still no luck. Same failure. No problem with other titles.

[buerste3]

Originally Posted by jdobbs

To avoid problems you have to follow the directions in the first post of this thread or in the README files that is included in the BD Rebuilder zip file.

The first time you run BD-RB you have to "Run as Administrator" and BD Rebuilder will update those settings in the registry.

Okay i did everything like the first post. Now this problems:

- Windows Version: 6.1 [7600]
- AVISYNTH Version: 2.5.7.0, Ok
- HAALI Splitter: Isn't recommended version
- FFDSHOW: 3326, Ok
- FFDSHOW_RAW_AUDIO: Set to "All Supported", Ok
- WIN7 preferred AVC CODEC: Not Set correctly
- WIN7 preferred VC-1 CODEC: Not Set correctly
- WIN7 preferred MPEG2 CODEC: Not Set correctly
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- BD Rebuilder v0.36.0.2, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok

Also i must everytime "Run as Administrator" because BD Rebuilder will not update those settings in the registry.

Whats the problem??