BD Rebuilder Beta - Bug Reports Only

[jdobbs]

A question to jdoobs:

I read in the Frequently Asked Questions thread about AUTO_BIAS=n the following:

"You replace the "n" with one of 3 values: 0, 1, or 2. "0" tells the quality selection to have a bias toward speed, "1" (the default) balances speed and quality, and "2" tells the quality selection algorithim to have a bias toward higher quality."

But in the HIDDENOPTS file it says: n = 0-3 - Def=1, Auto Qual bias, 0=high speed, 1=normal, 2=high quality, 3=highest qual

Can I use 3? What is the difference between 2 and 3 (quality and speed)? Those values change the thresholds in which BD-RB makes decisions within "Automatic" quality settings. It doesn't change any settings specifically, only the points at which BD-RB decides it needs to increase quality settings. "3" is a legal value, I'll update the docs.

[jdobbs]

I have updated the first post of this thread with a link to an updated release of BD-RB (v0.40.10). Changes for this release:- Corrected an issue related to unusual MPLS files
that could result in "SourceCheck() 00006 2501" at
program startup or during scanning.
- Corrected an error in which under very unusual and
rare circumstances the bitrate can be calculated
as a negative number. This could result in encode
failure.
- Made several improvements to increase speed and
provide greater resilience.
- Added a new hidden option "OVERWRITE_PROMPT". If
set to "0", BD-RB will not prompt for overwrite
when the output folder already exists. Instead it
will rename the output folder.
- Updated the included version of X264.EXE to the
latest release (r2200).
- Updated the included version of X264-64.EXE to
the latest release (r2200).
- Other minor corrections and cosmetic fixes.

[Sharc]

Hmmm... not sure how that could happen. It looks like it gets close to the target size with the first CRF, and does one more tweak before encoding -- which for some reason swings it way off-kilter. I'll take a look at it.

Did you have a chance to look into this?

[jdobbs]

Did you have a chance to look into this? Not yet. I'm still constrained by other work. I looked at it quickly and didn't find anything. I'll work on it for the next release.

[omegaman7]

You're awesome Jdobbs. Thanks a lot! :)

[worknstiff]

@ jdobbs: RE: BD-RB (v0.40.10). - Corrected an issue related to unusual MPLS files
that could result in "SourceCheck() 00006 2501" at program startup or during scanning.

I just tried the Hannibal Rising BD (Momentum Import All Region A-B-C title) that previously had the Source Check Error. It now throws up a Source Check () 00006 2503, Selected source is not BD Format. This disk is weird enough that it has a 25MB 11 second m2ts thats added in front of the 2:10:00 minute m2ts. If I try to create a BD folder with Clown it plays ok except that the runtime shows up as 13:10:00 and has a hard time changing chapters, it completely crashes TMT5 when FF or chapter skip but it does play. The resulting Clown BD that is created throws up the same not BD format error that the original Hannibal folder does. I finally had to extrract the streams and create a new BD of this disk to run through BD_RB. thanks again for the hard work you do on this great program. worknstiff

[jdobbs]

@ jdobbs: RE: BD-RB (v0.40.10). - Corrected an issue related to unusual MPLS files
that could result in "SourceCheck() 00006 2501" at program startup or during scanning.

I just tried the Hannibal Rising BD (Momentum Import All Region A-B-C title) that previously had the Source Check Error. It now throws up a Source Check () 00006 2503, Selected source is not BD Format. This disk is weird enough that it has a 25MB 11 second m2ts thats added in front of the 2:10:00 minute m2ts. If I try to create a BD folder with Clown it plays ok except that the runtime shows up as 13:10:00 and has a hard time changing chapters, it completely crashes TMT5 when FF or chapter skip but it does play. The resulting Clown BD that is created throws up the same not BD format error that the original Hannibal folder does. I finally had to extrract the streams and create a new BD of this disk to run through BD_RB. thanks again for the hard work you do on this great program. worknstiff

Hmmm... I tried to find that disc online... I only see Region A/1 and B/2 versions available at Amazon. Can you point me to a place where I can get the problem disc?

[worknstiff]

Sorry about that, It is just listed as region B/2 on Amazon but on the back of the case it's listed as ABC. Here is the product listed on Amazon Hannibal Rising (Uncut Edition) . (http://www.amazon.com/gp/product/B001AS7VQM/ref=oh_details_o03_s00_i00)
Hope this helps, worknstiff

[Scorpio1]

I have attached below the specs of the BD-R disks I am using and I have 2 questions.

1) I have set BD Rebuilder to a custom output size of 23866mb (23.32gb), and imgburn is set to make an ISO at the end of the conversion process, I frequently get images that are too big to fit on one of the disks though, so I have tried to complete the process by manually burning to disk, IMGburn still tells me the filesize is too big for the disk. What is the actual CUSTOM SIZE I should be using with BDRebuilder (23866 is obviously too big)?

2) The disks are obviously capable of burning at 8x according to imgburn but the packaging says they are rated at 4x - which is correct?

Disk specs follow obtained via DVDinfo pro

HL-DT-ST BD-RE BH10LS30 1.01 (ATA)
Current Profile: BD-R

Disc Information:
Status: Empty
State of Last Session: Empty
Erasable: No
Free Sectors: 12,219,392
Free Space: 25,025,314,816 bytes
Free Time: 2715:27:17 (MM:SS:FF)
Next Writable Address: 0
MID: PHILIP-R04-000
Supported Write Speeds: 2x, 4x, 6x, 8x

Disc Definition Structure:
Certified: No
Scanned: No
Manufacturers Name: HL-DT-ST
Additional ID: BD-RE BH10LS30
Serial Number: K9GA28B2634

BD Disc Information:
Disc ID: PHILIP-R04-000
Disc Type: BD-R
Disc Size: 120mm
Disc Class: 0
Disc Version: 1
Number of Layers: 1
Layer Type: Writable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50nm (25GB Per Layer)
Push-Pull Polarity: Positive
Recorded Mark Polarity: HTL
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 131,072
Last PAA of Data Zone: 1,658,494

Format Capacities:
DT: 0x01 - NB: 12219392 (0x00BA7400) - TDP: 151552
FT: 0x00 - NB: 11826176 (0x00B47400) - TDP: 12288
FT: 0x32 - NB: 11826176 (0x00B47400) - TDP: 12288
FT: 0x32 - NB: 7369728 (0x00707400) - TDP: 151552
FT: 0x32 - NB: 12088320 (0x00B87400) - TDP: 4096

Performance (Write Speed):
Descriptor 1...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 12219391 (0x00BA73FF)
-> RS: 44,879 KB/s (10x) - WS: 8,991 KB/s (2x)
Descriptor 2...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 12219391 (0x00BA73FF)
-> RS: 44,879 KB/s (10x) - WS: 17,982 KB/s (4x)
Descriptor 3...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 12219391 (0x00BA73FF)
-> RS: 44,879 KB/s (10x) - WS: 26,973 KB/s (6x)
Descriptor 4...
-> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00
-> EL: 12219391 (0x00BA73FF)
-> RS: 44,879 KB/s (10x) - WS: 35,964 KB/s (8x)


Anyway my questions are :-

1) What size should I be putting in the Custom size option to make sure that BDRebuilder doesn't make the rip too big, but still uses as much of the available space as possible?

2) What write speed should I use, I have used 8x and everything seems to be OK, but normally for peace of mind I have been burning at 4x.:thanks:

[jdobbs]

The best option for a BD-R disc (25GB) is to use the default for BD-25. It has been sized to: 1.) Assure inaccuracies in sizing don't cause issues. 2.) Avoid the outer edges of the disc (that are prone to error). Trying to squeeze that little extra out of the disc doesn't give you any measurable improvement in quality -- and just causes headaches.

I'd recommend you use 1/2 the rated write speed on discs that are rated more than 4x. So for an 8x, I'd suggest burning at 4x. I've been doing that for a long time, and I've had very good luck with disc reliability and longevity.

[colinhunt]

My aim is to always get as close to 25,000,000,000 bytes as possible. I've learned through trial and error that a custom size of 24150 - 24400, depending on the amount of titles on disc, results in output very close to the target. That worked for 0.40.09, at least. We'll see what happens with the new version.

I haven't had any problems with writing to edge of disc but that's mostly because I use a good burner and excellent media from a quality manufacturer. The media is rated 6x but the burner supports 12x for this particular media. I've done successful writes at 10x that pass both verify run and Opti Drive Control's write quality test. However, I do most writes at 6x.

[colinhunt]

I thought this one had been squashed already but bumped into it on 04009 and 04010 last night:

BD Rebuilder experienced an error 1801 [07:23:02] ReencodeAudio()
00075 1801

As before, prompted by a short title (493 frames in this case) which has two apparently identical PCM tracks.

[jdobbs]

I thought this one had been squashed already but bumped into it on 04009 and 04010 last night:

BD Rebuilder experienced an error 1801 [07:23:02] ReencodeAudio()
00075 1801

As before, prompted by a short title (493 frames in this case) which has two apparently identical PCM tracks. That means that a path doesn't exist. It could be the path to the audio encoder, the AVS file, or the working/source paths. In any event -- the error is passed to BD-RB from the operating system.

Please note that without the logs being posted, many of these reports become meaningless. For instance, in this one I have no idea whether it is a full backup, a movie-only, or output to MKV/MP4. That makes a huge difference. I'm happy to find and fix errors... but I can't do that when I'm groping around in the dark.

[colinhunt]

That means that a path doesn't exist. It could be the path to the audio encoder, the AVS file, or the working/source paths. In any event -- the error is passed to BD-RB from the operating system.
That's quite mysterious! In the case of this backup, I managed to manually fix the problem by making a copy of the 4352.AC3 file BD-RB had created (first of the two PCM files always gets converted to AC3 without problems, then the second one fails), renaming the copy as the missing 4353.AC3, then asking BD-RB to resume. BD-RB sees that the previously missing 4353.AC3 file now exists and resumes happily to muxing, then rebuilds the backup without further errors.

On this disc the audio error took place right at the end of the process, so once I had copied and renamed the AC3 file, it took only a few seconds from Resume to finished backup.

Please note that without the logs being posted, many of these reports become meaningless. For instance, in this one I have no idea whether it is a full backup, a movie-only, or output to MKV/MP4. That makes a huge difference. I'm happy to find and fix errors... but I can't do that when I'm groping around in the dark.
Ah, sorry. It was a full backup, no blanking. Here's the log:

[06.07.12] BD Rebuilder v0.40.10 (beta)
[23:41:47] Source: GANJA_AND_HESS
- Input BD size: 36,56 GB
- Approximate total content: [02:26:53.846]
- Target BD size: 23,58 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[23:41:49] PHASE ONE, Encoding
- [23:41:49] Processing: VID_00003 (1 of 6)
- [23:41:49] Extracting A/V streams [VID_00003]
- [23:44:06] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29,970fps, 53*330 frames
- Bitrate: 16*397 Kbs
- [23:44:06] Reencoding: VID_00003, Pass 1 of 2
- [00:01:40] Reencoding: VID_00003, Pass 2 of 2
- [01:07:55] Video Encode complete
- [01:07:55] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [01:08:01] Multiplexing M2TS
- [01:09:25] Processing: VID_00004 (2 of 6)
- [01:09:25] Extracting A/V streams [VID_00004]
- [01:09:32] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 256 frames
- Bitrate: 4*437 Kbs
- [01:09:32] Reencoding: VID_00004, Pass 1 of 2
- [01:09:38] Reencoding: VID_00004, Pass 2 of 2
- [01:09:45] Video Encode complete
- [01:09:45] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Reencoding audio to AC3...
- [01:09:46] Multiplexing M2TS
- [01:09:49] Processing: VID_00005 (3 of 6)
- [01:09:49] Extracting A/V streams [VID_00005]
- [01:09:56] Reencoding video [VID_00005]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 240 frames
- Bitrate: 2*740 Kbs
- [01:09:56] Reencoding: VID_00005, Pass 1 of 2
- [01:10:01] Reencoding: VID_00005, Pass 2 of 2
- [01:10:06] Video Encode complete
- [01:10:06] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Reencoding audio to AC3...
- [01:10:07] Multiplexing M2TS
- [01:10:10] Processing: VID_00006 (4 of 6)
- [01:10:10] Extracting A/V streams [VID_00006]
- [01:20:32] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 161*970 frames
- Bitrate: 22*277 Kbs
- [01:20:32] Reencoding: VID_00006, Pass 1 of 2
- [02:22:41] Reencoding: VID_00006, Pass 2 of 2
- [07:11:27] Video Encode complete
- [07:11:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Reencoding audio to AC3...
- [07:12:46] Multiplexing M2TS
- [07:22:22] Processing: VID_00007 (5 of 6)
- [07:22:22] Extracting A/V streams [VID_00007]
- [07:22:26] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29,970fps, 30 frames
- Bitrate: 500 Kbs
- [07:22:26] Reencoding: VID_00007, Pass 1 of 2
- [07:22:28] Reencoding: VID_00007, Pass 2 of 2
- [07:22:30] Video Encode complete
- [07:22:30] Processing audio tracks
- [07:22:30] Multiplexing M2TS
- [07:22:33] Processing: VID_00043 (6 of 6)
- [07:22:33] Extracting A/V streams [VID_00043]
- [07:22:42] Reencoding video [VID_00043]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 493 frames
- Bitrate: 3*306 Kbs
- [07:22:42] Reencoding: VID_00043, Pass 1 of 2
- [07:22:52] Reencoding: VID_00043, Pass 2 of 2
- [07:23:02] Video Encode complete
- [07:23:02] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Reencoding audio to AC3...
- [07:23:02] ReencodeAudio() 00075 1801
[10:25:18] - Failed to reencode audio, aborted
---------------------- <-- COPIED & RENAMED AC3 FILE, THEN RESUMED.
[06.08.12] BD Rebuilder v0.40.10 (beta)
[10:26:20] Source: GANJA_AND_HESS
- Input BD size: 36,56 GB
- Approximate total content: [02:26:53.846]
- Target BD size: 23,58 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[10:26:21] PHASE ONE, Encoding
- [10:26:21] Processing: VID_00043 (6 of 6)
- [10:26:21] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Reencoding audio to AC3...
- [10:26:22] Multiplexing M2TS
[10:26:26]PHASE ONE complete
[10:26:26]PHASE TWO - Rebuild Started
- [10:26:26] Rebuilding BD file Structure
[10:26:47] - Encode and Rebuild complete
[10:26:47] JOB: GANJA_AND_HESS finished.

[jdobbs]

So it appears that track 4353 was never extracted. Are you sure it actually exists in the source? Sometimes preprocessing can remove tracks but leave the references, any chance you ran it through some other software for any reason first?

[colinhunt]

So it appears that track 4353 was never extracted. Are you sure it actually exists in the source?
Absolutely. MediaInfo of the source file:

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : PCM
Format settings, Endianness : Big
Format settings, Sign : Signed
Muxing mode : Blu-ray
Codec ID : 128
Duration : 20s 555ms
Bit rate mode : Constant
Bit rate : 2 304 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 24 bits
Stream size : 5.65 MiB (36%)

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : PCM
Format settings, Endianness : Big
Format settings, Sign : Signed
Muxing mode : Blu-ray
Codec ID : 128
Duration : 20s 555ms
Bit rate mode : Constant
Bit rate : 2 304 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 24 bits
Stream size : 5.65 MiB (36%)

I can also extract both tracks from the file using MeGUI's HD Stream Extractor and eac3to.

Sometimes preprocessing can remove tracks but leave the references, any chance you ran it through some other software for any reason first?
Nope, this was a very normal AnyDVD rip from disc to hard drive.

Every time this error occurs, the culprit is a small file which has two or more (one had 5!) identical PCM tracks. On this disc, 00043.m2ts is white static text block on black background and the audio tracks appear to be empty.

It looks to me like some authoring shops try to minimize problems by including the same number of audio tracks on all files. In other words, if the main feature contains 3 dubs (for example english, french and spanish), all extra features and even menus have three audio tracks - even though those tracks are identical in content.

[jdobbs]

It probably is a part of a playlist with another M2TS that has that audio stream present. Streams that share a playlist should have the same number of audio streams. In most circumstances if it is not needed it should be a stream that contains some type of audio (even if it is silence). If the file doesn't exist at the time of reencoding, I have to suspect it isn't really there. It might just be referenced in the PAT/PMT headers of the M2TS (which might fool MediaInfo).

TSMUXER does the demuxing and should have created that file, open that M2TS with TSMUXER and see what it says about track 4353. I'd suggest you also try demuxing it and see what happens.

[colinhunt]

TSMUXER does the demuxing and should have created that file, open that M2TS with TSMUXER and see what it says about track 4353. I'd suggest you also try demuxing it and see what happens.
TSMUXER shows two PCM audio tracks (2304Kbps, 48Khz, 24-bit) and demuxes both nicely. (I mentioned in my previous post I can extract both tracks.)

[jdobbs]

TSMUXER shows two PCM audio tracks (2304Kbps, 48Khz, 24-bit) and demuxes both nicely. (I mentioned in my previous post I can extract both tracks.) Ok then, I'm confused. I thought the extracted track was missing -- and you corrected it by copying/renaming the first track for the encode. I guess that apparently isn't the case. So I have no idea what is happening.

[dfsooner]

It's a bad rip.

Never confuse "playing" with "decoding and reencoding" -- playing can ignore errors, decoding/reencoding can't.

The error comes from TSMUXER. The AV buffer isn't really the issue. That's just where the corrupt source showed itself. You'd probably get it no matter how big you made the buffer.

I re-ripped the disc and still got the same error. I'm trying to get hold of another copy of the disc. I'll rip it using a different drive (& manufacturer) and see if I get the same problem.

In the meantime I've pulled out the offending LPCM audio track, run BDRB and muxed the audio back in and it seems to work ok.

[jdobbs]

I re-ripped the disc and still got the same error. I'm trying to get hold of another copy of the disc. I'll rip it using a different drive (& manufacturer) and see if I get the same problem.

In the meantime I've pulled out the offending LPCM audio track, run BDRB and muxed the audio back in and it seems to work ok. What did you use to pull the audio?

[dfsooner]

What did you use to pull the audio?

I used tsmuxer and deselected the audio stream. However, it created a .wav file during the process that I plugged back into the compressed version of the m2ts, also using tsmuxer. That was on a version compressed to 21000.

Interestingly, when I did the same thing to a version compressed to 6500, tsmuxer failed when trying to insert the LPCM stream. I expected either both to succeed or both to fail. Not sure what is going on.

Still trying to get another copy of the disc, however to try a distinctly different rip. I'm hoping to pin it down to either a bad disc or a problem with my original drive.

[colinhunt]

Ok then, I'm confused.
Sorry, my bad, I'm sure.

I thought the extracted track was missing -- and you corrected it by copying/renaming the first track for the encode. I guess that apparently isn't the case. So I have no idea what is happening.
Yes, the extracted track was missing and that caused the ReencodeAudio() error. In other words, tsmuxer was unable to extract the track during BD-RB processing.
I corrected the problem by making a copy of 4352.ac3 (which BD-RB had successfully created) and renaming it 4353.ac3, then resuming BD-RB.

Everything I did and posted about after that was to test & prove that 00043.m2ts does in fact contain two PCM tracks. I ran TSMUXER, dropped 00043.m2ts into it, selected both PCM tracks, chose Demux as output and tsmuxer extracted two PCM tracks.

In other words, tsmuxer failed to extract one of the two PCM tracks during BD-RB operation -- but extracted both fine when I operated tsmuxer as a stand-alone app.

[asiafan]

Hi i am poiting this question to Jdobbs i got 1st time ever problem with lastest Rebuilder. Since this version my reencoding is finishing @ 25,5 GB (27 451 559 936)
doesnt matter if i choose target 25GB or manuall it ends @27GB. Even after removing LPCM audio still same. Best way its to use 2 previous versions but as usuall expired :(

[Yordan5]

With this version my encodings seem to finish between 0.5 and 1.5Gb smaller (depending on the size of the original movie - the larger it is the bigger the difference is between target size and actual size BDRebuilder produces) than what I specify in the Custom Target Size option. This was not the case with previous versions. If a log is needed I'll do another back up and will provide it. I did Transformers 3 (original size just over 38Gb) and set the Custom target size to 20Gb. The eventual back up was 18.5Gb. Next I did Planet Earth disk 1 (original size just over 22Gb) and set the Custom target size to 16.1Gb the eventual back up ended up 15.6Gb. The settings were Two Pass, High Quality, keeping original HD Audio.

[jdobbs]

@asiafan
@Yordan5

Nothing has changed in this version that affects sizing in any way (except possibly the new version of X264 -- but that is very, very unlikely). I would suggest you uninstall/reinstall FFDSHOW, HAALI, and AVISYNTH.

[dfsooner]

I used tsmuxer and deselected the audio stream. However, it created a .wav file during the process that I plugged back into the compressed version of the m2ts, also using tsmuxer. That was on a version compressed to 21000.

Interestingly, when I did the same thing to a version compressed to 6500, tsmuxer failed when trying to insert the LPCM stream. I expected either both to succeed or both to fail. Not sure what is going on.

Still trying to get another copy of the disc, however to try a distinctly different rip. I'm hoping to pin it down to either a bad disc or a problem with my original drive.

OK. Here's an update:

I have now ripped this 5 times with two different original discs on three different blu-ray drives from two different manufacturers. I get exactly the same error in every case.

Because the error is generated from tsmuxer, I have to assume that either there is a bug in tsmuxer or an authoring anomaly in the title itself. Not sure there is any way around it at this point. I even tried converting the LPCM track to AC3 using Audacity but had some sound gaps that made it unusable. Ideas anyone?

[asiafan]

@asiafan
@Yordan5

Nothing has changed in this version that affects sizing in any way (except possibly the new version of X264 -- but that is very, very unlikely). I would suggest you uninstall/reinstall FFDSHOW, HAALI, and AVISYNTH.


i will be reencoding few others BDs so i will inform you if this is just matter or single BD or matter of x264 version


this last BD was 27GB so i done quickly BD25 fast two pass
mode + DTS HD => ac3 .





PS can i put x264 files older to new version or its pointless? :D

[laserfan]

I have now ripped this 5 times with two different original discs on three different blu-ray drives from two different manufacturers. I get exactly the same error in every case.

Because the error is generated from tsmuxer, I have to assume that either there is a bug in tsmuxer or an authoring anomaly in the title itself...Ideas anyone?
Only time I've seen txmuxer fail is with a "bad" subtitle track, so (long shot) try muxing w/o a sub and see if that works.

[jdobbs]

i will be reencoding few others BDs so i will inform you if this is just matter or single BD or matter of x264 version


this last BD was 27GB so i done quickly BD25 fast two pass
mode + DTS HD => ac3 .





PS can i put x264 files older to new version or its pointless? :D

Please follow the advice about reinstalling the helper apps before trying other things (as I recommended). It is the likely source of your error.

[colinhunt]

Bumped into a peculiar disc: Thin Ice (http://www.amazon.com/Thin-Ice-Blu-ray-Greg-Kinnear/dp/B007RKFY0W). It's 46GB in total and contains two large .m2ts files. 00000.m2ts is 18.9GB and 00034.m2ts is 21GB. The latter, when played in MPC-HC, has a running time of 109 minutes. 00000.m2ts, while a smaller file, has a running time of more than 200 minutes -- but when one tries to skip ahead, MPC-HC crashes.

I tried to create a full backup of the disc while blanking 00034.m2ts (and trailers):

[06.12.12] BD Rebuilder v0.40.10 (beta)
[19:23:51] Source: THIN_ICE
- Input BD size: 23,35 GB
- Approximate total content: [04:15:08.634]
- Target BD size: 23,78 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[19:23:53] PHASE ONE, Encoding
- [19:23:53] Processing: VID_00000 (1 of 28)
- [19:23:53] Extracting A/V streams [VID_00000]
- [19:29:32] Reencoding video [VID_00000]
- [19:29:32] Keeping original video (no reencode)
- [19:29:32] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:29:32] Multiplexing M2TS
- [19:29:38] Processing: VID_00024 (2 of 28)
- [19:29:38] Extracting A/V streams [VID_00024]
- [19:29:49] Reencoding video [VID_00024]
- [19:29:49] Keeping original video (no reencode)
- [19:29:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:29:49] Multiplexing M2TS
- [19:29:54] Processing: VID_00025 (3 of 28)
- [19:29:54] Extracting A/V streams [VID_00025]
- [19:30:02] Reencoding video [VID_00025]
- [19:30:02] Keeping original video (no reencode)
- [19:30:02] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:30:02] Multiplexing M2TS
- [19:30:06] Blanking: VID_00026 (4 of 28)
- [19:30:06] Blanking: VID_00034 (5 of 28)
- [19:30:06] Processing: VID_00035 (6 of 28)
- [19:30:06] Extracting A/V streams [VID_00035]
- [19:30:15] Reencoding video [VID_00035]
- [19:30:15] Keeping original video (no reencode)
- [19:30:15] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:30:15] Multiplexing M2TS
- [19:30:19] Processing: VID_00101 (7 of 28)
- [19:30:19] Extracting A/V streams [VID_00101]
- [19:32:53] Reencoding video [VID_00101]
- [19:32:53] Keeping original video (no reencode)
- [19:32:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:32:53] Multiplexing M2TS
- [19:34:20] Processing: VID_00102 (8 of 28)
- [19:34:20] Extracting A/V streams [VID_00102]
- [19:35:42] Reencoding video [VID_00102]
- [19:35:42] Keeping original video (no reencode)
- [19:35:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:35:42] Multiplexing M2TS
- [19:35:56] Processing: VID_00104 (9 of 28)
- [19:35:56] Extracting A/V streams [VID_00104]
- [19:36:16] Reencoding video [VID_00104]
- [19:36:16] Keeping original video (no reencode)
- [19:36:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:36:16] Multiplexing M2TS
- [19:36:27] Processing: VID_00105 (10 of 28)
- [19:36:27] Extracting A/V streams [VID_00105]
- [19:36:39] Reencoding video [VID_00105]
- [19:36:39] Keeping original video (no reencode)
- [19:36:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:36:39] Multiplexing M2TS
- [19:36:44] Processing: VID_00106 (11 of 28)
- [19:36:44] Extracting A/V streams [VID_00106]
- [19:36:58] Reencoding video [VID_00106]
- [19:36:58] Keeping original video (no reencode)
- [19:36:58] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:36:58] Multiplexing M2TS
- [19:37:03] Processing: VID_00107 (12 of 28)
- [19:37:03] Extracting A/V streams [VID_00107]
- [19:37:15] Reencoding video [VID_00107]
- [19:37:15] Keeping original video (no reencode)
- [19:37:15] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:37:15] Multiplexing M2TS
- [19:37:20] Processing: VID_00108 (13 of 28)
- [19:37:20] Extracting A/V streams [VID_00108]
- [19:37:32] Reencoding video [VID_00108]
- [19:37:32] Keeping original video (no reencode)
- [19:37:32] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:37:32] Multiplexing M2TS
- [19:37:38] Processing: VID_00109 (14 of 28)
- [19:37:38] Extracting A/V streams [VID_00109]
- [19:37:49] Reencoding video [VID_00109]
- [19:37:49] Keeping original video (no reencode)
- [19:37:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:37:49] Multiplexing M2TS
- [19:37:54] Processing: VID_00110 (15 of 28)
- [19:37:54] Extracting A/V streams [VID_00110]
- [19:38:05] Reencoding video [VID_00110]
- [19:38:05] Keeping original video (no reencode)
- [19:38:05] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:38:05] Multiplexing M2TS
- [19:38:11] Processing: VID_00111 (16 of 28)
- [19:38:11] Extracting A/V streams [VID_00111]
- [19:38:24] Reencoding video [VID_00111]
- [19:38:24] Keeping original video (no reencode)
- [19:38:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:38:24] Multiplexing M2TS
- [19:38:31] Processing: VID_00112 (17 of 28)
- [19:38:31] Extracting A/V streams [VID_00112]
- [19:38:43] Reencoding video [VID_00112]
- [19:38:43] Keeping original video (no reencode)
- [19:38:43] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:38:43] Multiplexing M2TS
- [19:38:48] Processing: VID_00113 (18 of 28)
- [19:38:48] Extracting A/V streams [VID_00113]
- [19:39:00] Reencoding video [VID_00113]
- [19:39:00] Keeping original video (no reencode)
- [19:39:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:39:00] Multiplexing M2TS
- [19:39:05] Processing: VID_00114 (19 of 28)
- [19:39:05] Extracting A/V streams [VID_00114]
- [19:39:19] Reencoding video [VID_00114]
- [19:39:19] Keeping original video (no reencode)
- [19:39:19] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:39:19] Multiplexing M2TS
- [19:39:24] Processing: VID_00115 (20 of 28)
- [19:39:24] Extracting A/V streams [VID_00115]
- [19:39:37] Reencoding video [VID_00115]
- [19:39:37] Keeping original video (no reencode)
- [19:39:38] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:39:38] Multiplexing M2TS
- [19:39:43] Processing: VID_00116 (21 of 28)
- [19:39:43] Extracting A/V streams [VID_00116]
- [19:40:01] Reencoding video [VID_00116]
- [19:40:01] Keeping original video (no reencode)
- [19:40:01] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:40:01] Multiplexing M2TS
- [19:40:10] Processing: VID_00318 (22 of 28)
- [19:40:10] Extracting A/V streams [VID_00318]
- [19:40:23] Reencoding video [VID_00318]
- [19:40:23] Keeping original video (no reencode)
- [19:40:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:40:23] Multiplexing M2TS
- [19:40:29] Blanking: VID_00325 (23 of 28)
- [19:40:29] Blanking: VID_00326 (24 of 28)
- [19:40:29] Blanking: VID_00327 (25 of 28)
- [19:40:29] Blanking: VID_00328 (26 of 28)
- [19:40:29] Processing: VID_00340 (27 of 28)
- [19:40:29] Extracting A/V streams [VID_00340]
- [19:40:41] Reencoding video [VID_00340]
- [19:40:41] Keeping original video (no reencode)
- [19:40:41] Processing audio tracks
- [19:40:41] Multiplexing M2TS
- [19:40:46] Processing: VID_00343 (28 of 28)
- [19:40:46] Extracting A/V streams [VID_00343]
- [19:40:57] Reencoding video [VID_00343]
- [19:40:57] Keeping original video (no reencode)
- [19:40:57] Processing audio tracks
- [19:40:57] Multiplexing M2TS
[19:41:02]PHASE ONE complete
[19:41:02]PHASE TWO - Rebuild Started
- [19:41:02] Rebuilding BD file Structure
[19:41:37] - Encode and Rebuild complete
[19:41:37] JOB: THIN_ICE finished.

At some point during the process, BD-RB popped up a dialog window to report that an audio type is different from reported, asked me to choose which audio type to use. (Can't remember the exact wording of the dialog window, but I'm sure jdobbs knows which one I mean.)

Here's where things go weird: 00000.m2ts and 00034.m2ts are not in the same playlist, so BD-RB lets me blank 00034.m2ts -- and you can see from the log BD-RB processes 00000.m2ts by keeping original video and audio -- but the final output is less than 5GB in size.

Yes, I'm using custom size but I don't think this is related to that. Just a guess, mind you :)

[dfsooner]

Only time I've seen txmuxer fail is with a "bad" subtitle track, so (long shot) try muxing w/o a sub and see if that works.

Tried to remux with only the video and the primary LPCM audio - no other audio and no subtitles. Tsmuxer failed. Thanks for the suggestion though.

[jdobbs]

Bumped into a peculiar disc: Thin Ice (http://www.amazon.com/Thin-Ice-Blu-ray-Greg-Kinnear/dp/B007RKFY0W). It's 46GB in total and contains two large .m2ts files. 00000.m2ts is 18.9GB and 00034.m2ts is 21GB. The latter, when played in MPC-HC, has a running time of 109 minutes. 00000.m2ts, while a smaller file, has a running time of more than 200 minutes -- but when one tries to skip ahead, MPC-HC crashes.

I tried to create a full backup of the disc while blanking 00034.m2ts (and trailers):

[06.12.12] BD Rebuilder v0.40.10 (beta)
[19:23:51] Source: THIN_ICE
- Input BD size: 23,35 GB
- Approximate total content: [04:15:08.634]
- Target BD size: 23,78 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
...
[19:41:02]PHASE ONE complete
[19:41:02]PHASE TWO - Rebuild Started
- [19:41:02] Rebuilding BD file Structure
[19:41:37] - Encode and Rebuild complete
[19:41:37] JOB: THIN_ICE finished.

At some point during the process, BD-RB popped up a dialog window to report that an audio type is different from reported, asked me to choose which audio type to use. (Can't remember the exact wording of the dialog window, but I'm sure jdobbs knows which one I mean.)

Here's where things go weird: 00000.m2ts and 00034.m2ts are not in the same playlist, so BD-RB lets me blank 00034.m2ts -- and you can see from the log BD-RB processes 00000.m2ts by keeping original video and audio -- but the final output is less than 5GB in size.

Yes, I'm using custom size but I don't think this is related to that. Just a guess, mind you :)

The message you mentioned is actually coming from DGDecNV. I think it is telling you that the PAT/PMT of the M2TS doesn't match the MPLS & CLPI files.

[colinhunt]

The message you mentioned is actually coming from DGDecNV. I think it is telling you that the PAT/PMT of the M2TS doesn't match the MPLS & CLPI files.
I'm pretty sure that's the one, yes. Does that have any bearing on the very small output size?

[colinhunt]

Thin Ice is an interesting specimen for another reason: the Director's Cut playlist includes an additional bit shown before the movie.. which messes up audio sync if one tries to do a movie-only backup.

[jdobbs]

I'm pretty sure that's the one, yes. Does that have any bearing on the very small output size? Actually it's more likely that it is telling you the PAT/PMT tables don't match the actual stream. I doubt that the DGDecNV driver looks at the MPLS/CLPI.

[colinhunt]

Actually it's more likely that it is telling you the PAT/PMT tables don't match the actual stream. I doubt that the DGDecNV driver looks at the MPLS/CLPI.
OK. When I have a moment, I'll run the backup again the same way to see what it's actually telling me.

[ttringle]

I have a motherboard with Virtu support, is there a way to enable virtu support in FFDShow to speed up the re-encoding process, or enable CUDA on my main video card for the same purpose?

Thanks

TimT

[jdobbs]

I have a motherboard with Virtu support, is there a way to enable virtu support in FFDShow to speed up the re-encoding process, or enable CUDA on my main video card for the same purpose?

Thanks

TimT

I'm not that familiar wiht Virtu, but CUDA is supported through DGDecNV decoding, assuming you have it installed (see the SETUP dialog). As some point in the future it might also be available through support of LAV filters.

[ttringle]

jdobbs,

Quick question, can I use DVD Rebuilder Pro to upscale a 480p DVD to 720p or 1080p? I know there wouldn't be any improvement in video quality other than bypassing my televisions scaler but I'm just curious.

[jdobbs]

jdobbs,

Quick question, can I use DVD Rebuilder Pro to upscale a 480p DVD to 720p or 1080p? I know there wouldn't be any improvement in video quality other than bypassing my televisions scaler but I'm just curious. DVD Rebuilder doesn't output to anything but legal DVD resolutions.

In BD Rebuilder (the subject of this thread) it's pretty easy. Just select "Convert SD to 720p" or "Convert SD to 1080p" in the SETUP dialog.

You can use multiAVCHD to convert a DVD to BD pretty easily -- and use that as the source for BD-RB. There are several other ways to do it also.

[xterminater]

jdobbs, I have tried to research on why bd-rb blank out dts-express mono audio but have no luck finding on how to not have it delete that audio. Is there a way to force BD-RB to keep the dts-express mono audio?

[Audiophile1178]

jdobbs, I have tried to research on why bd-rb blank out dts-express mono audio but have no luck finding on how to not have it delete that audio. Is there a way to force BD-RB to keep the dts-express mono audio?

This used to be in the hiddenopts.txt but for some reason it's no longer there. Just put DTSX_ENABLE=1 in your bdrebuilder.ini (you can put it right underneath [Options])and it'll keep dts express for you. Remember to save the bdrebuilder.ini after you insert the line.

Note, even though it'll keep the dts express the dts express sound might still not work. I have this issue myself and jdobbs is aware that certain players will read the encode and other ones won't. He'll eventually figure it out! He's a smart fella!


Jdobbs, I have some questions for you. I'm doing a complete disc encode of an episode disc of a tv series and the original disc is 43.2GB with a bdrebuilder output of 22.4GB. Taking a look at one episode using bdinfo and MPC the original bitrate is ~14,000 Kb/s and the bdrebuilder bitrate is ~4,500 Kb/s. From my reading it seems like this bitrate is far too low for 1080p? Would it be best to convert it to 720p?

Also, I don't want to do this with these discs but for future reference could I blank half the episodes and putting them on one bluray disc with the other half on another bluray? I thought about doing this but it would take too many bluray discs and cost too much.

Thank you for your continued support on a great program!

[jdobbs]

This used to be in the hiddenopts.txt but for some reason it's no longer there. Just put DTSX_ENABLE=1 in your bdrebuilder.ini (you can put it right underneath [Options])and it'll keep dts express for you. Remember to save the bdrebuilder.ini after you insert the line.

Note, even though it'll keep the dts express the dts express sound might still not work. I have this issue myself and jdobbs is aware that certain players will read the encode and other ones won't. He'll eventually figure it out! He's a smart fella!


Jdobbs, I have some questions for you. I'm doing a complete disc encode of an episode disc of a tv series and the original disc is 43.2GB with a bdrebuilder output of 22.4GB. Taking a look at one episode using bdinfo and MPC the original bitrate is ~14,000 Kb/s and the bdrebuilder bitrate is ~4,500 Kb/s. From my reading it seems like this bitrate is far too low for 1080p? Would it be best to convert it to 720p?

Also, I don't want to do this with these discs but for future reference could I blank half the episodes and putting them on one bluray disc with the other half on another bluray? I thought about doing this but it would take too many bluray discs and cost too much.

Thank you for your continued support on a great program! Whether 4,500Kbs is too little is dependent upon the source. If it is less than other episodes, it would mean that the original also uses less for that one. I'd watch it and see if it is noticable before I'd worrry about it. It's really odd to see a bitrate that low on a BD-25 backup, though... how many hours does it show in the log?

Yes, you could make a backup in the way you describe. You could, for instance on a disc that had 8 episodes, blank the second 4 on the first backup and blank the first 4 on the second.

[Audiophile1178]

First of all, does blanking a title just produce a blank (black?) video of low bitrate to save space or eliminate the title from the disc? I've never used blanking before so I don't know.


I didn't expect such a quick response... I just read that if your bitrate is around 4,000Kb/s it's better to go for 720p as they'll be more information per frame since it's a lower resolution. I did a bdrebuilder encode of 1080p and 720p. I'm currently deciding which one to burn. Whichever one I go with I'll do the rest that way. I even looked at only keeping the DTS core and not the full DTS-HD.MA but that'll only gain me 1GB per eposide so I didn't think that i'll gain that much in picture quality so I kept the high def audio.

The discs are Star Trek The Original Series and each episode is 50 mins long. I've only touched one disc so far and it has four episodes on it. I'm pretty sure that the rest of the discs will have 4 episodes as well. Each episode has an original unmastered video and a digitally mastered one so that the viewer can switch between the two and see how it originally aired. Some episodes also have pip of commentary and stuff but I don't think that i'm going to be able to hear the audio since it's DTS Express.


It took me 10 hours to encode this bad boy at the settings below!!!


[22:46:22] Source: STAR_TREK_SEASON_2__DISC_1
- Input BD size: 43.28 GB
- Approximate total content: [04:49:35.632]
- Target BD size: 23.54 GB
- Windows Version: 6.1 [7601]
- SHUTDOWN at completion enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640


BTW, I just scanned all episodes with BDinfo and the originals were all around 14,000 Kb/s and the encode were around 4,900 Kb/s.

[jdobbs]

You can't use bitrate as a finite "if then else" decision parameter. It isn't something that functions on its own, it depends on other factors as well (like source complexity and encoding bells-and-whistles used). I've done a lot of encoding at lower bitrates with much success. You'll also find a lot of high quality MKV & MP4 files floating around that look good with a lot less...

Blanking replaces the original video with a short (~.5 second) blank video.

Not sure how halving the size of the disc cuts the bitrate by that much? There must be a huge portion that is kept intact?

[Audiophile1178]

Not sure how halving the size of the disc cuts the bitrate by that much? There must be a huge portion that is kept intact?

Thanks for the blanking info... I too was a bit surprised at the final bitrate result. I figured that cutting the disc in half would result in half the bitrate (~7,000Kb/s) and not a third of the original. It's very hard to tell if anything is kept in tact as the titles seems to be using seemless branching (forgive me if that's the incorrect term). There are 121 .m2ts files which seem like most of those files make up all four episodes except for one files that's a bonus video of 12 minutes (which is 1.5GB in size) about them making the shows.


Out of all the files that make up the four episodes there are: (2x) 4.5GB, (2x) 3.5GB, (2x) 2.5GB, (2x) 1.5GB, and the rest are below 1GB. Bdrebuilders log shows that it encoded 91 files. A majority of the files for the episodes are below 1GB. I know some of the files are menus and other things so it looks like it encoded everything correctly.


As you can see from the beginning of the log in the previous post that there was almost 5 hours of 1080p video on this one disc! That pretty much explains why the original is only 14,000Kb/s. Any higher and they'd have to put less episodes on each disc. If you think about it though it's 1960's Star Trek! Even if you had a higher bitrate it wouldn't make the video quality any better. :D


BTW, what would I look for in the 1080p encode to see if it's bad? Pixelization? Every encode that i've done with x264 no matter how low the bitrate gets looks fine to me but then again my tv is a 60" 720p so that could explain why i've never seen bad video since it's not full 1080p.

[jdobbs]

Thanks for the blanking info... I too was a bit surprised at the final bitrate result. I figured that cutting the disc in half would result in half the bitrate (~7,000Kb/s) and not a third of the original. It's very hard to tell if anything is kept in tact as the titles seems to be using seemless branching (forgive me if that's the incorrect term). There are 121 .m2ts files which seem like most of those files make up all four episodes except for one files that's a bonus video of 12 minutes (which is 1.5GB in size) about them making the shows.


Out of all the files that make up the four episodes there are: (2x) 4.5GB, (2x) 3.5GB, (2x) 2.5GB, (2x) 1.5GB, and the rest are below 1GB. Bdrebuilders log shows that it encoded 91 files. A majority of the files for the episodes are below 1GB. I know some of the files are menus and other things so it looks like it encoded everything correctly.


As you can see from the beginning of the log in the previous post that there was almost 5 hours of 1080p video on this one disc! That pretty much explains why the original is only 14,000Kb/s. Any higher and they'd have to put less episodes on each disc. If you think about it though it's 1960's Star Trek! Even if you had a higher bitrate it wouldn't make the video quality any better. :D


BTW, what would I look for in the 1080p encode to see if it's bad? Pixelization? Every encode that i've done with x264 no matter how low the bitrate gets looks fine to me but then again my tv is a 60" 720p so that could explain why i've never seen bad video since it's not full 1080p. If you don't see pixelation in darkest scenes, you're usually good to go.

I know I have the first season of Star Trek (TOS), but can't remember if I have all the seasons. If I do, I'll test that disc.

They did a really good job with those discs. They went back to the original film prints and created HD from them. They also give you the option of using newer (more up-to-date) graphics (on the space scenes and the bridge's "big screen"). It is really impressive.

They'll be coming out with TNG in HD using the same concepts this year (season one in July)... can't wait. I got the preview disc w/three episodes on it -- looks pretty good. It's a little disconcerting, though, to think that after I paid for all 7 seasons on DVD, I may have to do the same on BD...

[ihmcjacky]

I have followed strictly the instruction on the first page, but still got error on converting my adele concert blu-ray disc to 25gb discs, the following is the log

[06/15/12] BD Rebuilder v0.40.10 (beta)
[10:57:54] Source: ADELE
- Input BD size: 26.40 GB
- Approximate total content: [02:00:05.331]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[10:57:54] PHASE ONE, Encoding
- [10:57:54] Processing: VID_00000 (1 of 3)
- [10:57:54] Extracting A/V streams [VID_00000]
- [11:15:48] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 178,602 frames
- Bitrate: 23,493 Kbs
- [11:15:48] Reencoding: VID_00000, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.40.10 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[11:15:49] - Failed video encode, aborted

My computer configuration:
Intel Core i7 2600
8gb ram
win7 64 bit ultimate

Will it be the bug of the software?

[jdobbs]

Is this the first time you've run it, or has it worked for you before? Sometimes other software changes the settings without telling you. Try uninstalling and reinstalling AVISYNTH, FFDSHOW, and HAALI.