BDRebuilder - after 7 hrs. an error

[ricoman]

First time I encountered this, successfully encoded Fast Five earlier this week, but now I get this:
----------------------
[10:04:42] BD Rebuilder v0.39.01 (beta)
- Source: TRANSFORMERS_3_AC
- Input BD size: 42.48 GB
- Approximate total content: [02:34:23.295]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=1 DTS=0 HD=0 Kbs=640
[10:04:43] PHASE ONE, Encoding
- [10:04:43] Processing: VID_00800 (1 of 1)
- [10:04:43] Extracting A/V streams [VID_00800]
- [10:23:22] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 222,097 frames
- Bitrate: 18,979 Kbs
- [10:23:22] Reencoding: VID_00800, Pass 1 of 2
- [12:28:07] Reencoding: VID_00800, Pass 2 of 2
- [17:28:31] Video Encode complete
- [17:28:31] Reencoding audio tracks (if req'd)
- [17:30:34] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00800.meta
- Not enought buffer for parse video stream. Current frame num 175495
[17:50:01] - Failed to build structure, aborted

I have an i7 system with 8gb of ram, so I'm surprised that there seems to be a buffer overun problem.

What do you think?

[HWK]

What are you telling usually indicate bad source rip. What program you used. Also this does not happen always make sure you use good ripper.

[ricoman]

Ripped with AnyDVDHD as I always do. I've ripped and encoded dozens before. As I said, I did Fast Five this week with the same latest beta of both AnyDVD & BDRebuilder.

[HWK]

Possibly maybe bad disc.

[jdobbs]

As HWK said, that error (it comes from TSMUXER) is pretty much always associated with a bad rip. One of the streams (PGS maybe?) is likely corrupt.

[ricoman]

I'll clean the disc and try another rip & report back with the results. Thanks.

[jdobbs]

Let me know what you find.

[Rich86]

I processed the Transformers3 title down to the default 25gb setting (ripped with DVDFabHD) without a problem.
I did movie only since there are no extras on this title, kept HD audio & english subs, with BD-RB settings for very best quality.
It ran long - but worked fine - and subsequently burned with imgburn fine.
The source movie only is around 42gb, as I recall, so a fair amount of crunching was necessary.
The output BD looks & plays fine.

[setarip_old]

I successfully made a BD-9 Full Disc backup of Transformers 3 (initially ripped with MakeMKV) excluding, of course, the HD audio and retaining all subpic streams.

Viewing quality is excellent, thanks to the tremendous percentage of CGI versus "real". As with other primarily CGI discs, it seems that you can compress them tremendously (Remember the HD-DVD release of "King Kong"?) without any loss of quality.

I've got to believe that "Ricoman's" source material is/was problematic...

[ricoman]

I cleaned the disc and ripped it again with AnyDVDHD with no problems, but when I tried to process it movie only to BD25, BDRB asked if I wanted to continue with the previous process. Since I was 7 hrs. into it I said yes. Unfortunately, after about 1/2 hr. it aborted with the same message. For Jollies, I thought I'd try DVDFABHDDecryptor and after 6 1/2 hrs. I had a successfully burned BD25 disc that seems to work fine (I haven't watched it thru completely, but I skipped around and it seemes fine). DVDFAB however, does not copy the DTS HD files, but converts to AC3 5.1, so maybe the problem is with the DTS audio file. I will try one more time when I go to bed to process the new rip in its entirety with BDRB. I'll let you know how that works tomorrow evening when I get back from work.

Hey Rich86, I can't help but to notice your Uconn Husky avatar. Are you from CT, I live in the Farmington Valley?

[Rich86]

Hey Rich86, I can't help but to notice your Uconn Husky avatar. Are you from CT, I live in the Farmington Valley?

I am from Conn - and a UConn graduate, but live in California now (a job transfer many years ago). Naturally I still root for my Huskies in sports . . . regardless of what conference they end up in or who is left in the Big East with them . .
My wife and I still talk about moving back "home" . . maybe someday . . :cool:

[Rich86]

DVDFAB however, does not copy the DTS HD files, but converts to AC3 5.1, so maybe the problem is with the DTS audio file. I will try one more time when I go to bed to process the new rip in its entirety with BDRB. I'll let you know how that works tomorrow evening when I get back from work.

You need to doublecheck your settings in DVDFab, because it handles DTS HD codecs just fine. Make sure "Remove HD Audio" is NOT checked.

Update . . wait . . now that I think about it, I do not believe there is a DTS-HD track on the Transformers 3 title - isn't this Dolby TrueHD 7.1?
When I played around with this title, DVDFabHDDecryptor kept the TrueHD 7.1 track just fine and BD-RB processed it just fine.

However you still need to make sure "Remove HD Audio" is not checked if you want to preserve the HD audio in full disc copy mode.

[ricoman]

You all were right. It must have been a spec on the disc or maybe a power surge at night when I ripped the first time. I started from scratch with an AnyDVDHD rip an processed movie only with BDRB and when I got up this morning it was burning a BD25 with Imgburn. I just checked out a few scenes and it seems fine. Sorry for all the hassle, my bad. Thanks for all your help.
And Rich... GO HUSKIES!

[mbcd]

Come on Guys, cant you read the log?

The original disc was OK, the video ist still ready encoded. There was a problem building the structure, maybee there was too less space on harddrive left for it. Thats what I read. But maybee :stupid:

[ricoman]

Come on Guys, cant you read the log?

The original disc was OK, the video ist still ready encoded. There was a problem building the structure, maybee there was too less space on harddrive left for it. Thats what I read. But maybee :stupid:
Yeah, that buffer message threw me, that's why I never thought of a defective disk or bad rip. Plenty of HD space, more than half of a 1TB drive. Anyway, it's done now, though I am curious what the issue was.