BD Rebuilder Beta - Bug Reports Only

[Dr.Tom]

Hi2All! How I can use x264-x64 in BD Rebuilder correctly? Do something in config?

[jdobbs]

Hi2All! How I can use x264-x64 in BD Rebuilder correctly? Do something in config? In the future please use the "search" function -- this has been answers many, many times.

If you select "Use X264's internal LAVF for decoding" in the SETUP menu the 64 bit version will be used whenever possible. Note, though, that some things like resizing, filters, etc. will for 32 bit mode.

[DKdude]

X264.exe crashes for no reason in the newest build :( (Running on i7 - 6gb ram - Windows 7 Ultimate 64bit)

Its trying 2 times and failes - worked perfect in 39.04

---------------------
[11:04:23] BD Rebuilder v0.39.07 (beta)
- Source: DIRCH
- Input BD size: 32,41 GB
- Approximate total content: [03:04:18.360]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:04:23] PHASE ONE, Encoding
- [11:04:23] Processing: VID_00001 (1 of 18)
- [11:04:23] Extracting A/V streams [VID_00001]
- [11:04:26] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 357 frames
- Bitrate: 2.074 Kbs
- [11:04:26] Reencoding: VID_00001, Pass 1 of 2
- [11:04:33] Reencoding: VID_00001, Pass 2 of 2
- [11:04:51] Video Encode complete
- [11:04:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:04:52] Multiplexing M2TS
- [11:04:55] Processing: VID_00005 (2 of 18)
- [11:04:55] Extracting A/V streams [VID_00005]
- [11:05:00] Reencoding video [VID_00005]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.835 frames
- Bitrate: 6.049 Kbs
- [11:05:00] Reencoding: VID_00005, Pass 1 of 2
- [11:05:40] Reencoding: VID_00005, Pass 2 of 2
- [11:06:25] Video Encode complete
- [11:06:25] Processing audio tracks
- Track 4352 (dan): Keeping original audio
- [11:06:25] Multiplexing M2TS
- [11:06:29] Processing: VID_00006 (3 of 18)
- [11:06:29] Extracting A/V streams [VID_00006]
- [11:06:34] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 1.605 frames
- Bitrate: 6.053 Kbs
- [11:06:34] Reencoding: VID_00006, Pass 1 of 2
- [11:07:10] Reencoding: VID_00006, Pass 2 of 2
- [11:08:10] Video Encode complete
- [11:08:10] Processing audio tracks
- Track 4352 (dan): Keeping original audio
- [11:08:10] Multiplexing M2TS
- [11:08:14] Processing: VID_00007 (4 of 18)
- [11:08:14] Extracting A/V streams [VID_00007]
- [11:08:20] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.935 frames
- Bitrate: 6.745 Kbs
- [11:08:20] Reencoding: VID_00007, Pass 1 of 2
- [11:09:37] Reencoding: VID_00007, Pass 2 of 2
- [11:11:30] Video Encode complete
- [11:11:30] Processing audio tracks
- Track 4352 (dan): Keeping original audio
- [11:11:30] Multiplexing M2TS
- [11:11:35] Processing: VID_00009 (5 of 18)
- [11:11:35] Extracting A/V streams [VID_00009]
- [11:11:46] Reencoding video [VID_00009]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 3.176 frames
- Bitrate: 6.729 Kbs
- [11:11:46] Reencoding: VID_00009, Pass 1 of 2
- [11:13:16] Reencoding: VID_00009, Pass 2 of 2
- [11:16:06] Video Encode complete
- [11:16:06] Processing audio tracks
- Track 4352 (dan): Keeping original audio
- [11:16:06] Multiplexing M2TS
- [11:16:12] Processing: VID_00010 (6 of 18)
- [11:16:12] Extracting A/V streams [VID_00010]
- [11:16:16] Reencoding video [VID_00010]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 25 frames
- Bitrate: 27.537 Kbs
- [11:16:16] Reencoding: VID_00010, Pass 1 of 2
- [11:16:17] Reencoding: VID_00010, Pass 2 of 2
- [11:16:17] Video Encode complete
- [11:16:17] Processing audio tracks
- [11:16:17] Multiplexing M2TS
- [11:16:21] Processing: VID_00015 (7 of 18)
- [11:16:21] Extracting A/V streams [VID_00015]
- [11:32:20] Reencoding video [VID_00015]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 165.903 frames
- Bitrate: 19.640 Kbs
- [11:32:21] Reencoding: VID_00015, Pass 1 of 2
- Encode failed. Retrying.

[jdobbs]

There's always a reason. Usually overclocking or a corrupt source. The version of X264 didn't change in the latest release, but it did in v0.39.05.

It's possible there may be a glitch in the r2120, but I haven't seen any other reports of issues.

[DKdude]

i dont OC at all - no reason.

it seems it might be a bug in the 2 newest AnyDVD - only diff. since last BD rebuilder tyhat worked - tested .04 - same error now :(

(tested with 2 diff. BD)

latest test on another BD in .04 now (tried 3 now):

- [16:53:53] Reencoding: VID_00800, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.39.04 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, 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 "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[17:06:01] - Failed video encode, aborted

[Ch3vr0n]

@DKdude: to exclude the bug, try using 39.07 but replace the x264.exe and x264-64.exe files with the one from the 39.04 build. If it processes the disc as normal, then its not a bug in BDRB itself but something in x264 that's making it crash.

[DKdude]

@DKdude: to exclude the bug, try using 39.07 but replace the x264.exe and x264-64.exe files with the one from the 39.04 build. If it processes the disc as normal, then its not a bug in BDRB itself but something in x264 that's making it crash.


No joy .. since new anydvd (last two) - it crashes - also in .04

[jdobbs]

I got a similar report via e-mail from someone who was using AnyDVD v6.8.9.2. He went back to 6.8.9.0 and his problem went away. Have you tried the version of AnyDVD that came out today (v6.9.1.0)?

I usually don't upgrade on the interim test versions, only the ones for which you get notified from within the app.

[Ch3vr0n]

there have been a few minor bugs yes in the previous 2 beta's from anydvd. Those should all be fixed with the latest release

[DKdude]

I got a similar report via e-mail from someone who was using AnyDVD v6.8.9.2. He went back to 6.8.9.0 and his problem went away. Have you tried the version of AnyDVD that came out today (v6.9.1.0)?

I usually don't upgrade on the interim test versions, only the ones for which you get notified from within the app.

Yes, same error (sadly) (only running alpha builds of anydvd - not beta)

and THANKS for a great program! - forgot that before!

UPDATE: i tried out the new beta from anydvd - same problem - wrote them on their forum - and as expected "AnyDVD cant cause that problem" - well, funny, since it works perfect if you go back a few versions! - why cant ppl just test instead of saying no! - learn from jdobbs - full respect for your bug report handling!

[SuperFist]

-----------------------
[06:00:07] BD Rebuilder v0.39.07 (beta)
- Source: PIRATES2
- Input BD size: 31.33 GB
- Approximate total content: [02:30:40.031]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[06:00:07] PHASE ONE, Encoding
- [06:00:07] Processing: VID_00001 (1 of 2)
- [06:00:07] Extracting A/V streams [VID_00001]
- Error in attempt to extract audio/subs.
- AV frame too large (65497 bytes). Increase AV buffer.
[06:01:31] - Failed to retrieve audio, aborted
-----------------------

As you can see from the log above, it fails to encode my BD-25 sized movies anymore. Just a few weeks ago an older version of BD Rebuilder was working - v0.39.0.2. This latest one isn't. I didn't even install anything new on my Win 7 64-bit computer so nothing has changed on my end.

Is there a way you can leave older versions alone to work separately and independently of the latest versions? Something like how DVDFab does their software?

This disc is Pirates of the Caribbean: Dead Man's Chest, by the way. It has the entire movie in a single m2ts file.

[jdobbs]

-----------------------
[06:00:07] BD Rebuilder v0.39.07 (beta)
- Source: PIRATES2
- Input BD size: 31.33 GB
- Approximate total content: [02:30:40.031]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[06:00:07] PHASE ONE, Encoding
- [06:00:07] Processing: VID_00001 (1 of 2)
- [06:00:07] Extracting A/V streams [VID_00001]
- Error in attempt to extract audio/subs.
- AV frame too large (65497 bytes). Increase AV buffer.
[06:01:31] - Failed to retrieve audio, aborted
-----------------------

As you can see from the log above, it fails to encode my BD-25 sized movies anymore. Just a few weeks ago an older version of BD Rebuilder was working - v0.39.0.2. This latest one isn't. I didn't even install anything new on my Win 7 64-bit computer so nothing has changed on my end.

Is there a way you can leave older versions alone to work separately and independently of the latest versions? Something like how DVDFab does their software?

This disc is Pirates of the Caribbean: Dead Man's Chest, by the way. It has the entire movie in a single m2ts file. What version of AnyDVD are you using? Read the previous few posts.

No, there isn't a way to "leave previous versions alone" -- if that happened I'd be continuously responding to bug reports for problems that were fixed a year ago. Versions will continue to expire until I at least get the software out of beta. I also have to say that you are making an unsubstantiated (and highly probably incorrect) assumption in saying that somehow an older version would work -- lots of other things have changed since the last time you did the disc (like AnyDVD, for example).

Please post your BDREBUILDER.INI file so I can see what settings you are using.

[Peer van Heuen]

well, funny, since it works perfect if you go back a few versions! - why cant ppl just test instead of saying no! - learn from jdobbs - full respect for your bug report handling!

Please be aware that the reply you got there, was from a plain user, not from SlySoft.
If you had contacted our support, you certainly would have gotten our "full respect" ;)

But in defense of that user - it is hard to think of how AnyDVD could mess up a stream.

What version of AnyDVD are you using? Read the previous few posts.


I can think of one single thing:

if the disc in question has PMTs that don't fit into a single packet AND the stream is not read entirely in its "natural sector order", it can happen, that individual PMTs get corrupted.

This normally is no issue, because PMTs are repeated every 100ms and come with a checksum that would identify broken PMTs.
When you read using the file system, the Windows file caching does usually mess up the sector read order.

Ripping with the AnyDVD ripper first ensures correct PMTs, but of course it's an additional step no one wants.

So, jdobbs, if you read the PMTs and neglect to check the checksum, that MAY be an issue, though it doesn't sound to me like something that would cause that specific error.
The broken PMTs are still identifiable as such (PID 0x100) and are structurally ok.

If you can think of anything a simple decrypting process could mess up, let me know.

In the meantime, I'll see if I can reproduce the effect.

[DKdude]

Please be aware that the reply you got there, was from a plain user, not from SlySoft.
If you had contacted our support, you certainly would have gotten our "full respect" ;)

But in defense of that user - it is hard to think of how AnyDVD could mess up a stream.



I can think of one single thing:

if the disc in question has PMTs that don't fit into a single packet AND the stream is not read entirely in its "natural sector order", it can happen, that individual PMTs get corrupted.

This normally is no issue, because PMTs are repeated every 100ms and come with a checksum that would identify broken PMTs.
When you read using the file system, the Windows file caching does usually mess up the sector read order.

Ripping with the AnyDVD ripper first ensures correct PMTs, but of course it's an additional step no one wants.

So, jdobbs, if you read the PMTs and neglect to check the checksum, that MAY be an issue, though it doesn't sound to me like something that would cause that specific error.
The broken PMTs are still identifiable as such (PID 0x100) and are structurally ok.

If you can think of anything a simple decrypting process could mess up, let me know.

In the meantime, I'll see if I can reproduce the effect.

sorry about that - looked like a sly team member for me - hence i dident understand the dismissing reply from him.

thanks.

still trying everything to find the bug - where ever it may be - but it startede after det last 2 alpha builds of anydvd - sadly.

BUT i will keep looking!

[Ch3vr0n]

It's probably me you 2 are talking about :) I don't work for slysoft, i just translate the products into dutch for them, and try to help out on the forums where and when i can. Nothing more.

[jdobbs]

Please be aware that the reply you got there, was from a plain user, not from SlySoft.
If you had contacted our support, you certainly would have gotten our "full respect" ;)

But in defense of that user - it is hard to think of how AnyDVD could mess up a stream.



I can think of one single thing:

if the disc in question has PMTs that don't fit into a single packet AND the stream is not read entirely in its "natural sector order", it can happen, that individual PMTs get corrupted.

This normally is no issue, because PMTs are repeated every 100ms and come with a checksum that would identify broken PMTs.
When you read using the file system, the Windows file caching does usually mess up the sector read order.

Ripping with the AnyDVD ripper first ensures correct PMTs, but of course it's an additional step no one wants.

So, jdobbs, if you read the PMTs and neglect to check the checksum, that MAY be an issue, though it doesn't sound to me like something that would cause that specific error.
The broken PMTs are still identifiable as such (PID 0x100) and are structurally ok.

If you can think of anything a simple decrypting process could mess up, let me know.

In the meantime, I'll see if I can reproduce the effect. I'm not reading the source at all at that point. All I'm doing is passing the settings to X264 for reencoding. It is X264 attempting to encode that is experiencing the error. The deconstructing of the stream is done by HAALI unless the user has chosen to use X264's internal LAVF decoding.

I can think of many, many ways a "simple decrypting process" could cause pretty much any kind of error if it glitches in the process -- so I guess I don't understand that comment at all??? But that's your area, not mine.

The bottom line is that the reports say that simply changing versions of AnyDVD made the error go away. So how else am I supposed to read that? But since I've never actually experienced it myself I can't say definitively what does or doesn't cause it. There are a lot of variables involved in the process including AnyDVD, HAALI, FFDSHOW, AVISYNTH, and X264. Assuming, though, that none of those changed and switching AnyDVD versions fixes the problem one would certainly suspect it.

[Note: I've edited this post. My previous response was related to a different (wrong) error report.]

[jdobbs]

@DKdude

Go into the SETUP dialog and select "Use X264's internal LAVF..." and try your encode again. If that fails, then we know the error wasn't caused by HAALI, FFDSHOW, or AVISYNTH. If it works, then remove/reinstall HAALI, FFDSHOW, and AVISYNTH. Sometimes other programs or installations can change settings that might cause issues. Reinstalling will often corrects that.

[Peer van Heuen]

I can think of many, many ways a "simple decrypting process" could cause pretty much any kind of error if it glitches in the process -- so I guess I don't understand that comment at all??? But that's your area, not mine.

Oh, then, sorry, I neglected to write down a couple of thoughts that ran through my head at the time:

"....given that there has never ever been any trace of video playback on blu-rays by any BD player, that wasn't 100% immaculate" (except for actual BD+ issues, but that's not the point here).

AnyDVD is known to absoluty 100% reliably remove AACS at all times.
When you remove AACS, it is pretty much impossible to "partly mess up". Either it's ok or it's not. If it's not, no part of the movie will be ok.
As soon as the keys are available, decryption is such a simple straight forward operation, that you just can't do anything wrong.

Question: is it a BD+ disc (or discs) causing the problem? (would open up a few additional possibilities)

[jdobbs]

Oh, then, sorry, I neglected to write down a couple of thoughts that ran through my head at the time:

"....given that there has never ever been any trace of video playback on blu-rays by any BD player, that wasn't 100% immaculate" (except for actual BD+ issues, but that's not the point here).

AnyDVD is known to absoluty 100% reliably remove AACS at all times.
When you remove AACS, it is pretty much impossible to "partly mess up". Either it's ok or it's not. If it's not, no part of the movie will be ok.
As soon as the keys are available, decryption is such a simple straight forward operation, that you just can't do anything wrong.

Question: is it a BD+ disc (or discs) causing the problem? (would open up a few additional possibilities) Don't know. I haven't personally even seen the error. I'm not even sure what disc "DIRCH" is, as sometimes the volume label is just an acronym. Let's see what DKdude finds by switching the frame-serving before we jump to any conclusions. Sometimes other things can change and people aren't aware of the changes.

Good product, by the way. I recommend it to everyone.

[Ch3vr0n]

Dirch = perhaps http://www.imdb.com/title/tt1706596/ ? couldn't find out anything about the protection used though

[Adbear]

What version of AnyDVD are you using? Read the previous few posts.

No, there isn't a way to "leave previous versions alone" -- if that happened I'd be continuously responding to bug reports for problems that were fixed a year ago. Versions will continue to expire until I at least get the software out of beta. I also have to say that you are making an unsubstantiated (and highly probably incorrect) assumption in saying that somehow an older version would work -- lots of other things have changed since the last time you did the disc (like AnyDVD, for example).

Please post your BDREBUILDER.INI file so I can see what settings you are using.Not sure if it helps, but I tested my original of Pirates2 with the latest build of AnyDVDHD and the latest build of BD Rebuilder and it encodes to a movie only just fine. My BD input size appears to be the same so I hope I'm using the same region disc.

[jdobbs]

Not sure if it helps, but I tested my original of Pirates2 with the latest build of AnyDVDHD and the latest build of BD Rebuilder and it encodes to a movie only just fine. My BD input size appears to be the same so I hope I'm using the same region disc. Does that disc have an HD LPCM audio track? I noticed that the report showed settings that were keeping HD audio.

[Adbear]

Yes it does, mines the US release

[SqUaDrApHoNiC]

Hi jdobbs, firstly I just want say thankyou for such a quality program. Could you please look at my log for Ladder 49 this is the very first error I have ever had with your software. Thanks.

-----------------------
[12:34:10] BD Rebuilder v0.39.04 (beta)
- Source: LAD1NNE1
- Input BD size: 21.75 GB
- Approximate total content: [01:55:04.731]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, 1920x1080, Auto-AAC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=448
[12:34:11] PHASE ONE, Encoding
- [12:34:11] Processing: VID_00001 (1 of 2)
- [12:34:11] Extracting A/V streams [VID_00001]
- [12:45:03] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 165,524 frames
- Bitrate: 4,521 Kbs
- [12:45:03] Reencoding: VID_00001, Pass 1 of 2
- [14:15:57] Reencoding: VID_00001, Pass 2 of 2
- [16:36:39] Video Encode complete
- [16:36:39] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
- [16:47:07] Multiplexing M2TS
- [16:47:07] Processing: VID_00004 (2 of 2)
- [16:47:07] Extracting A/V streams [VID_00004]
- [16:47:10] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 24 frames
- Bitrate: 1,299 Kbs
- [16:47:10] Reencoding: VID_00004, Pass 1 of 2
- [16:47:11] Reencoding: VID_00004, Pass 2 of 2
- [16:47:12] Video Encode complete
- [16:47:12] Multiplexing M2TS
[16:47:12]PHASE ONE complete
[16:47:12]PHASE TWO - Rebuild Started
- [16:47:12] Rebuilding stream 00001 [1 of 2]
- [16:47:12] Rebuilding stream 00004 [2 of 2]
- [16:47:12] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[05:52:58] - Failed to REBUILD
-----------------------
[05:53:03] BD Rebuilder v0.39.04 (beta)
- Source: LAD1NNE1
- Input BD size: 21.75 GB
- Approximate total content: [01:55:04.731]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, 1920x1080, Auto-AAC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=448
- Resuming from previously started job.
[05:53:06] PHASE ONE, Encoding
[05:53:06]PHASE ONE complete
[05:53:06]PHASE TWO - Rebuild Started
- [05:53:06] Rebuilding stream 00001 [1 of 2]
- [05:53:06] Rebuilding stream 00004 [2 of 2]
- [05:53:06] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[05:58:48] - Failed to REBUILD

[jdobbs]

@SqUaDrApHoNiC

Not sure. Could you post your BDREBUILDER.INI file? If so, I'll try picking up that disc and giving it a run with your settings.

[SqUaDrApHoNiC]

@SqUaDrApHoNiC

Not sure. Could you post your BDREBUILDER.INI file? If so, I'll try picking up that disc and giving it a run with your settings.

Yeah sure, here it is. Thanks in advance.

VERSION=0.39.0.4
MODE=2
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
PRIORITY_CLASS=2
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=0
AVCHD=1
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
UNMASK_CHAPTER=0
COMPLETION_BEEP=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=4350
TARGET_SIZE=4190
MOVIEONLY_TYPE=18
ALTCRF=20
ALT_TARGET=4350
ALTMETHOD=2
ALTAUTOCROP=0
QUICK_EXTRAS=0

[SuperFist]

What version of AnyDVD are you using? Read the previous few posts.

No, there isn't a way to "leave previous versions alone" -- if that happened I'd be continuously responding to bug reports for problems that were fixed a year ago. Versions will continue to expire until I at least get the software out of beta. I also have to say that you are making an unsubstantiated (and highly probably incorrect) assumption in saying that somehow an older version would work -- lots of other things have changed since the last time you did the disc (like AnyDVD, for example).

Please post your BDREBUILDER.INI file so I can see what settings you are using.

I'm sorry, I didn't mean to anger you for stating what was on my mind. To my knowledge I haven't installed any other software on my computer since I've used that older version of BD Rebuilder. Heck, I don't even actually have AnyDVD installed on my computer nor do I have Windows Updates on automatic.

Here is my INI file:


[Options]
VERSION=0.39.0.7
MODE=2
ENCODE_QUALITY=5
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=0
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
TARGET_SIZE=23500
PRIORITY_CLASS=2
[Paths]
SOURCE_PATH=F:\MOVIES\FULLDISC\PIRATES2\
WORKING_PATH=F:\MOVIES\



Thanks for all the hard work you put into making such a wonderful program, jdobbs. You da man! :D :thanks:

[AmigaFuture]

BD Rebuilder 39.07 (and 39.06) for the movie Inception the "Extraction Mode" is selected rather than the regular movie and I don't see a way to choose between. Which means extras are included in the render. Perhaps a prompt or the ability to choose when this happens? A Bug? Thanks.

[sytyguy]

BD Rebuilder 39.07 (and 39.06) for the movie Inception the "Extraction Mode" is selected rather than the regular movie and I don't see a way to choose between. Which means extras are included in the render. Perhaps a prompt or the ability to choose when this happens? A Bug? Thanks.

I have the exact same problem. I started with movie only, and I got the extraction, then tried full back up and still only got the extraction.

[jdobbs]

I have the exact same problem. I started with movie only, and I got the extraction, then tried full back up and still only got the extraction. Not sure I'm understanding correctly.

Extraction is automatic. It is done when it isn't necessary to reencode to meet the target size -- keeping the original quality intact. Most of the time that is preferable, but if you want to always reencode you can use the "FORCE_ENCODE=1" hidden option (see HIDDENOPTS.TXT in the BD Rebuilder folder).

If, however, you aren't talking about that and there actually is a playlist called "Extraction" -- then just go to Alternate Playlist and select the other one. There actually is no way to determine definitively what playlist is the movie, so BD Rebuilder simply looks at several factors and makes a "guess". 99.9% of the time it is correct, but occasionally an "Extra" might be longer and appear to be the feature. When that happens, just look at the alternate playlists and pick the one that actualy is the movie.

[AmigaFuture]

Hi Jdobbs,

sytyguy didn't quote the way I did about "Extraction Mode". I will try your suggestion for the Playlist and let you know the results. :-)

I had a feeling to check that setting before posting but I ignored it. I thought it was more of a Batch method hence Playlist. First test looks and sounds great with Inception.

I have been noticing something interesting...when TSMUXER is active programs becomes less responsive. When I set Affinity to 1 CPU the Muxing is the same speed, but programs are a bit more responsive. Have you noticed such activity? I already have Encoding set to Idle and since it's not an encoder it shouldn't be effected.

[jdobbs]

@SqUaDrApHoNiC

Thanks for posting the INI, but unforunately it can't be the one you used when you did Ladder 49. It's set for Full Backup, and your log shows an encode attempt to "MOVIE-ONLY/ALTERNATE OUTPUT mode enabled".

I'll try just setting up for MP4 output and see what happens when I run it. Hopefully using your INI with just that change will give similar results.

[omegaman7]

Rebuilt "KICK-ASS" last night. Quite a bit of content on the disc (6+ hours). In order to maximize quality, I blanked the main titles commentary track(same length of the main title). The output size came out almost perfectly. Looks like the blanking feature is nearly working perfectly. Thanks a bunch :)

[Dr.Tom]

In the future please use the "search" function -- this has been answers many, many times.

If you select "Use X264's internal LAVF for decoding" in the SETUP menu the 64 bit version will be used whenever possible. Note, though, that some things like resizing, filters, etc. will for 32 bit mode.

Inordinately grateful. I know and use that. But I thought that it allows to use 64bit-operating system resource "at all" and would like to use an additional 64-bit mode for x264-codec. :thanks:

[jdobbs]

Inordinately grateful. I know and use that. But I thought that it allows to use 64bit-operating system resource "at all" and would like to use an additional 64-bit mode for x264-codec. :thanks: If you are using that setting you are using a 64 bit codec. :confused: When it is selected, the 64 bit version of X264 is executed and it decodes using the LAVF library that was also compiled for 64 bit.

[SqUaDrApHoNiC]

@SqUaDrApHoNiC

Thanks for posting the INI, but unforunately it can't be the one you used when you did Ladder 49. It's set for Full Backup, and your log shows an encode attempt to "MOVIE-ONLY/ALTERNATE OUTPUT mode enabled".

I'll try just setting up for MP4 output and see what happens when I run it. Hopefully using your INI with just that change will give similar results.

Cheers jdobbs, let me know how ya go...in the meantime ive updated to 39.07

[jdobbs]

Cheers jdobbs, let me know how ya go...in the meantime ive updated to 39.07Unfortunately I ran "LADDER 49" using your INI (with changes to select the proper output) and other than the fact that the job took an exceptionally long time to encode, everything worked as it should (see below). I'd recommend you remove everything (BD-RB, FFDSHOW, HAALI, and AVISYNTH) and reinstall from scratch.

[17:24:27] BD Rebuilder v0.40.01 (beta)
- Source: LADDER_49
- Input BD size: 21.75 GB
- Approximate total content: [01:55:04.731]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, 1920x1080, Auto-AAC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:24:29] PHASE ONE, Encoding
- [17:24:29] Processing: VID_00001 (1 of 2)
- [17:24:29] Extracting A/V streams [VID_00001]
- [17:31:15] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 165,524 frames
- [17:31:15] Reencoding: VID_00001, Pass 1 of 1
- [21:18:01] Video Encode complete
- [21:18:01] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
- [21:28:39] Multiplexing M2TS
- [21:28:39] Processing: VID_00004 (2 of 2)
- [21:28:39] Extracting A/V streams [VID_00004]
- [21:28:42] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 24 frames
- [21:28:42] Reencoding: VID_00004, Pass 1 of 1
- [21:28:45] Video Encode complete
- [21:28:45] Multiplexing M2TS
[21:28:45]PHASE ONE complete
[21:28:45]PHASE TWO - Rebuild Started
- [21:28:45] Rebuilding stream 00001 [1 of 2]
- [21:28:45] Rebuilding stream 00004 [2 of 2]
- [21:28:45] Building ALTERNATE OUTPUT Structure
[21:41:16] - Encode and Rebuild complete
[21:41:16]JOB: LADDER_49 finished.

[Ch3vr0n]

Version 40.01. I smell a new version coming soon. Wonder what's gonna be fixed/new.

[ggtop]

[21:41:16]JOB: LADDER_49 finished.

Severe bug found: There's a space missing between timestamp and "JOB:" :D

[jdobbs]

Version 40.01. I smell a new version coming soon. Wonder what's gonna be fixed/new.

I always backup the code with each version as it is released and then immediately change to the version number on of the next release on my computer... so don't count on too much. :)

[jdobbs]

Severe bug found: There's a space missing between timestamp and "JOB:" :D

Good catch... there's one of those "Other minor corrections and cosmetic fixes" I always list in the change logs.

[jfcarbel]

Ran into issues with Boyz in the Hood R1. I was doing a backup of just the bonus features (full backup, blank main movie, target BD-25).
Final size was 5.07 GB. Went to play with TMT5 and it asked to resume movie, then blank screen with TMT5 hanging.

I went thru streams and found that 98 and 99 are the motion backgrounds for main menu. Also this is a Java enabled menu since I see the JAR folder.
I replaced the 00098.m2ts and 00099.m2ts with originals and the associated CLIPINF and then the backup played fine with TMT5

So whats odd is that it recodes all the video streams even though the materials selected add up to easily less then 25GB. I never understood this. I know there is a NO_RECODE option but why even reencode if the target size is big enough. Also perhaps BD-Rebuilder should avoid recoding any of the main menu elements.

[DKdude]

Now i spent many hours trying everything - i still have the same problem - x264 crashes after a long time "pounding" the harddisk. :(

-----------------------
[23:24:41] BD Rebuilder v0.39.07 (beta)
- Source: DIRCH
- Input BD size: 32,41 GB
- Approximate total content: [03:04:18.360]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
- Resuming from previously started job.
[23:24:43] PHASE ONE, Encoding
- [23:24:43] Processing: VID_00015 (7 of 18)
- [23:24:43] Reencoding video [VID_00015]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 165.903 frames
- Bitrate: 19.640 Kbs
- [23:24:43] Reencoding: VID_00015, Pass 1 of 2
- Encode failed. Retrying.

[jdobbs]

Now i spent many hours trying everything - i still have the same problem - x264 crashes after a long time "pounding" the harddisk. :(

-----------------------
[23:24:41] BD Rebuilder v0.39.07 (beta)
- Source: DIRCH
- Input BD size: 32,41 GB
- Approximate total content: [03:04:18.360]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
- Resuming from previously started job.
[23:24:43] PHASE ONE, Encoding
- [23:24:43] Processing: VID_00015 (7 of 18)
- [23:24:43] Reencoding video [VID_00015]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 165.903 frames
- Bitrate: 19.640 Kbs
- [23:24:43] Reencoding: VID_00015, Pass 1 of 2
- Encode failed. Retrying.
I'm sorry -- but it is pretty almost 100% assured that the problem is your computer itself or the source is corrupted. If it failed immediately, it might be any of a host of problems. But if it runs for a long time and then fails -- it is most likely the system itself. Most of the time it is due to overheating or overclocking. I know you've said you don't overclock -- so I'd guess your processor's heatsink might be filled with dust, or possibly your memory might need reseating. If the program is working on other discs but fails only on this one -- there's also a chance that the source is corrupted.

Either way -- X264 isn't dying on any of the other several thousand computers running it -- and that narrows it down pretty well.

Just for the sake of trying, you might try using the "High Quality" mode instead of "Highest". That setting is almost never needed...

[omegaman7]

I found with an overclock one time, that the fastest setting (Good), actually discovered an overclock bug, where medium settings did not. (Good) seems to stress the CPU/Ram more so than the other settings(realtime priority)? Makes sense I guess. I prefer a stable clock though these days :p I only use the highest quality settings once in a blue moon(Depends on multiple factors). I have noticed a minor difference.

[RobertM]

DKDude could also be experiencing a hard drive failure. Faced with the same problem I would make a fresh rip, leaving the original in place, and see it the problem still happens.

[SqUaDrApHoNiC]

I'm sorry -- but it is pretty almost 100% assured that the problem is your computer itself or the source is corrupted. If it failed immediately, it might be any of a host of problems. But if it runs for a long time and then fails -- it is most likely the system itself. Most of the time it is due to overheating or overclocking. I know you've said you don't overclock -- so I'd guess your processor's heatsink might be filled with dust, or possibly your memory might need reseating. If the program is working on other discs but fails only on this one -- there's also a chance that the source is corrupted.

Either way -- X264 isn't dying on any of the other several thousand computers running it -- and that narrows it down pretty well.

Just for the sake of trying, you might try using the "High Quality" mode instead of "Highest". That setting is almost never needed...

Hi sorry if i'm out of my league here, but I had that same error several times last night and realised it was the simple fact I had no HDD space left on my destination drive. It was used up from pre-ripping disk to the HDD prior to encoding. I hope it is that simple for you.

[omegaman7]

I would think if people are ripping Blu ray discs, they are aware of the size requirements? I guess since the flooding in Thailand though, prices are rather ridiculous :(

[SqUaDrApHoNiC]

Unfortunately I ran "LADDER 49" using your INI (with changes to select the proper output) and other than the fact that the job took an exceptionally long time to encode, everything worked as it should (see below). I'd recommend you remove everything (BD-RB, FFDSHOW, HAALI, and AVISYNTH) and reinstall from scratch.

[17:24:27] BD Rebuilder v0.40.01 (beta)
- Source: LADDER_49
- Input BD size: 21.75 GB
- Approximate total content: [01:55:04.731]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, 1920x1080, Auto-AAC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:24:29] PHASE ONE, Encoding
- [17:24:29] Processing: VID_00001 (1 of 2)
- [17:24:29] Extracting A/V streams [VID_00001]
- [17:31:15] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 165,524 frames
- [17:31:15] Reencoding: VID_00001, Pass 1 of 1
- [21:18:01] Video Encode complete
- [21:18:01] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
- [21:28:39] Multiplexing M2TS
- [21:28:39] Processing: VID_00004 (2 of 2)
- [21:28:39] Extracting A/V streams [VID_00004]
- [21:28:42] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 24 frames
- [21:28:42] Reencoding: VID_00004, Pass 1 of 1
- [21:28:45] Video Encode complete
- [21:28:45] Multiplexing M2TS
[21:28:45]PHASE ONE complete
[21:28:45]PHASE TWO - Rebuild Started
- [21:28:45] Rebuilding stream 00001 [1 of 2]
- [21:28:45] Rebuilding stream 00004 [2 of 2]
- [21:28:45] Building ALTERNATE OUTPUT Structure
[21:41:16] - Encode and Rebuild complete
[21:41:16]JOB: LADDER_49 finished.

Hi jdobbs, Thanks again for confirming it for me. I re-installed to the latest version and re-installed all packages and I successfully encoded "Ladder 49". Thanks again. Is it just me or since I installed latest 39.07 my CPU speed only goes to 50% now instead of maxing continually on 100%. But the funny thing is it has been encoding them between 2/12 to 3/12 hours now instead of 3 1/2 to 4 1/2 hours. I don't understand why but am very happy with the outcome/quality and will not be changing anything in my settings.

Cheers,

Squad

[[SLiM]D12]

@jdobbs

Sorry if i'm bringing something up that's been addressed (read thru the thread, didn't see an answer)

Is there any progress with the "blanking" of titles?



Also, trying to backup Men In Black II and just getting all sorts of weird results.

Movie-Only works fine, when i do full backup, it comes out to 16GB but the main movie gets "stuck". It'll play for a few mins, then wherever you FF to, you're still stuck at the same frame. Real weird. I figured it was a source problem, but like i said, movie-only works, just not full backup.

I've tried that 'other' solution, just to see what would happen, and it chokes too, so i'm starting to think perhaps it's something with the way the disc is authored maybe?

thx
[SLiM]