BD Rebuilder Beta - Bug Reports Only

[Wolfe999]

Wolfe, how about starting a new thread to discuss this further. I have a similar setup to you. We can try to dissect this one point at a time to see where the failure is coming from. According to the change list, there were really only moderate changes from v.0.21.01 to 0.22.01, except for new versions of x264.exe and tsMuxer, and only minor changes between 0.22.01 and 0.22.02. It shouldn't be that difficult to find where things went wrong after reviewing some logs and settings... I can take your settings and see if I come up with the same failure. :)

Sorry for the delay, wasn't lack of interest, but of time. Of course if you want to open another thread I will gladly report there and see what can be done. But, I thought I had it solved, though I discovered it was only 50% (but at least I now can replicate the "freezing" and the finishing also of the movie)

After what you said about being only minor changes in between BD-Rebuilder versions, I decided to copy the TsMuxer version I was using in BD 0.21.01 and paste it in 0.22.02 (which was using 1.10.6). Don't remember why I had changed the TsMuxer version of 0.22.01 to 1.9.9 (maybe it was a recommendation from Turbojet, I can't remember). Once done, I did some Star Trek movies on that version. The first one (I was awake till 4 A.M, till it finished), didn't stopped till the end. I was very happy. I left doing another one (with the PC always ready to hybernate after 5 hours). The next morning, I found it was complete, but the progress bar stuck at the 50% position. BUT at least the codec kept on encoding and the movie was finished. I put another one and it got stuck at 50% too (can't say why), but I followed its progress and saw the movie finished in it's usual 4/5 hours span.

Immediately I did another movie, but on v0.21.01 (with the same 1.9.9 TSMuxer version and without changing anything) and everything went smootly, wiithout any freezing. So, where's the problem? In TsMuxer?

JDobbs, I'm doing right now a movie in 0.21.01, but as soon as it finishes, I will try the new version to see if finally this (whatever it might be) disappears :)

Thanx again and regards
Wolfe

[jdobbs]

Thats OK then I thought you might have started doing the re encoding from the demuxed stream instead of the m2ts but couldnt see any details in the release notes.

So after the ReEncode process has started its safe to manually delete the demuxed video file the only reason im asking is because I have a dedicated partition for the workfiles directory to help save the system drive from fragmentation due to the constant changing of data and its not enough space assigned to store the additianal demuxed video track.

When its done I will increase the partition size to suit. Not necessarily. Probably, but there is still a chance that it might be used. the only "safe" time is after encoding of all parts are completed. If it is a large component, though, it is very, very unlikely that deleting it will have any impact at all after it has started encoding. Because there would have to be an extremely large segment remaining to reverse the decision.

[jdobbs]

@jdobbs: Sorry, haven't gotten your reply for this.

In addition, I can confirm that in the new version you released yesterday the files are still encoded as 23.975. It would have been nice to see it go away just for cosmetic reasons -- but it's a non-issue as explained further back in this thread.

[jdobbs]

that was with 1080i VC1

it crashed x264 two times before at about 70%

hope it's working now with the old version and other decoder.. I don't know what you are saying. It crashed before, or it crashed on the new version?

[GaPony]

Sorry for the delay, wasn't lack of interest, but of time. Of course if you want to open another thread I will gladly report there and see what can be done. But, I thought I had it solved, though I discovered it was only 50% (but at least I now can replicate the "freezing" and the finishing also of the movie)

After what you said about being only minor changes in between BD-Rebuilder versions, I decided to copy the TsMuxer version I was using in BD 0.21.01 and paste it in 0.22.02 (which was using 1.10.6). Don't remember why I had changed the TsMuxer version of 0.22.01 to 1.9.9 (maybe it was a recommendation from Turbojet, I can't remember). Once done, I did some Star Trek movies on that version. The first one (I was awake till 4 A.M, till it finished), didn't stopped till the end. I was very happy. I left doing another one (with the PC always ready to hybernate after 5 hours). The next morning, I found it was complete, but the progress bar stuck at the 50% position. BUT at least the codec kept on encoding and the movie was finished. I put another one and it got stuck at 50% too (can't say why), but I followed its progress and saw the movie finished in it's usual 4/5 hours span.

Immediately I did another movie, but on v0.21.01 (with the same 1.9.9 TSMuxer version and without changing anything) and everything went smootly, wiithout any freezing. So, where's the problem? In TsMuxer?

JDobbs, I'm doing right now a movie in 0.21.01, but as soon as it finishes, I will try the new version to see if finally this (whatever it might be) disappears :)

Thanx again and regards
Wolfe

Yea.... I think its fixed now. No freezing on the progress bar and everything appears to be working normal with v.0.23.01 after about copying 6 movies.

[user822]

I don't know what you are saying. It crashed before, or it crashed on the new version?

it crashed before and now it does not use the video(black movie as you see in hte avs i quoted)

is there any solution to the VC1 1080 interlaced Problem(i had 5 crashes now)? :confused:

greetings
user

[colinhunt]

Finished first test of the new "no video re-encode" feature.
Disc size: 25.5 GB (27 478 268 964 bytes)
Movie (00003.m2ts): 23.6 GB (25 365 479 424 bytes)

I selected "Movie only" mode and removed all non-English audio & subs (i.e. one of the two Dolby TrueHD tracks and two subtitle tracks). BD-RB decided video needed no re-encoding. Output came to 21.9 GB and worked perfectly when played with TMT 3.0. Fantastic work, JDobbs!

For 2nd test, I selected "Full backup" and removed all non-English audio and subtitles from all VIDs. BD-RB began re-encoding 00000.m2ts (800MB) almost immediately, then skipped 00001 and 00002 (both less than 10MB) and is currently processing 00003.m2ts, the movie itself. Rest of the files are 00004 (772MB), 00005 (440MB) and 00006 (4MB).

So, if "movie only" came to 21.9 GB with non-English audio & subs removed, there's ~1 GB of space left on the BD25 for extras that take ~2 GB on the original disc.

I guess the next logical step would be to implement a "force main movie no re-encode with re-encoded extras" mode, where BD-RB first takes into account all removed audio & subs, then calculates how much disc space is left for extras and re-encodes extras at a low enough bitrate for them to fit on a BD25 with original, untouched movie video stream. How's that sound?

[GaPony]

It sounds like a topic for the "requested features" thread. :)

[PurpleMan]

It would have been nice to see it go away just for cosmetic reasons -- but it's a non-issue as explained further back in this thread.

Well, you could probably solve it by adding a "AssumeFPS(23.976)" to the avs script. Maybe it's worth a shot.

[colinhunt]

It sounds like a topic for the "requested features" thread. :)
Yeah, you're right. I just didn't want to split the post into two separate threads, to be honest.

[jdobbs]

it crashed before and now it does not use the video(black movie as you see in hte avs i quoted)

is there any solution to the VC1 1080 interlaced Problem(i had 5 crashes now)? :confused:

greetings
user The problem is that there just aren't any codecs that support field based interlaced video. The choice is crash or blank.

What might do it is if someone developed some code that merged the two fields together and made the video frame based interlaced. But I'm not sure that is even possible without decoding and encoding...

[LowDead]

Just had a major undersize on benjamin button EUR.. Choosed BD25 output and it came out 10GB.. If there's anything in particilar you need to know JD just let me know.. I have been away from testing due to work for some time know so i'm not sure what I'm supposted to post about bugs ^^

[Options]
RESIZE=0
MODE=0
ENCODE_QUALITY=3
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;swe;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450

"C:\DVD-Rip\BD_Rebuilder\tools\x264.exe" "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS" --bitrate 2156 --level 4.1 --sar 1:1 --fps 24000/1001 --aud --vbv-bufsize 25000 --keyint 24 --min-keyint 1 --vbv-maxrate 35000 --filter 0,0 --subme 9 --me umh --ref 4 --bframes 3 --mixed-refs --8x8dct --direct auto --weightb --trellis 1 --psy-rd 1.0:0.2 --aq-strength 0.8 --threads auto --thread-input --progress --no-psnr --no-ssim --stats "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV.stats" --pass 2 --output "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV"

//LD

[user822]

The problem is that there just aren't any codecs that support field based interlaced video. The choice is crash or blank.

What might do it is if someone developed some code that merged the two fields together and made the video frame based interlaced. But I'm not sure that is even possible without decoding and encoding...

none of the workarounds worked here
perhaps future versions of ffdshow will fix that problem

[jdobbs]

none of the workarounds worked here
perhaps future versions of ffdshow will fix that problem I don't think there are any workarounds for this issue. There is just nothing on the PC that will play them.

[Furiousflea]

Just had a major undersize on benjamin button EUR.. Choosed BD25 output and it came out 10GB.. If there's anything in particilar you need to know JD just let me know.. I have been away from testing due to work for some time know so i'm not sure what I'm supposted to post about bugs ^^

[Options]
RESIZE=0
MODE=0
ENCODE_QUALITY=3
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;swe;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450

"C:\DVD-Rip\BD_Rebuilder\tools\x264.exe" "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS" --bitrate 2156 --level 4.1 --sar 1:1 --fps 24000/1001 --aud --vbv-bufsize 25000 --keyint 24 --min-keyint 1 --vbv-maxrate 35000 --filter 0,0 --subme 9 --me umh --ref 4 --bframes 3 --mixed-refs --8x8dct --direct auto --weightb --trellis 1 --psy-rd 1.0:0.2 --aq-strength 0.8 --threads auto --thread-input --progress --no-psnr --no-ssim --stats "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV.stats" --pass 2 --output "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV"

//LD

You must be doing something wrong, I did this disc (EU version) and it actually oversizes by about 200mb which is well in the reasonable margin of error.

[Furiousflea]

On a PC I have found them all to work perfectly whether to bd-9 or bd-25 in full disc mode (but obviously without anything happening if you try and switch on PIP). On my only standalone player (Sony 550) if I copy a bd-9 structure to a dvd-dl disc, although everything 'works', you can't select the audio for the main movie, although the stream can be played on a PS3 with the audio there. If I take the same bd-9 structure and copy it to a bd-re, it works perfectly!! There is therefore something slightly quirky about the Sony's firmware. For full disc copies to bd-r or bd-re all have played fine so far.

Cheers dude :)

[Category 5]

Finished first test of the new "no video re-encode" feature.
Disc size: 25.5 GB (27 478 268 964 bytes)
Movie (00003.m2ts): 23.6 GB (25 365 479 424 bytes)

I selected "Movie only" mode and removed all non-English audio & subs (i.e. one of the two Dolby TrueHD tracks and two subtitle tracks). BD-RB decided video needed no re-encoding. Output came to 21.9 GB and worked perfectly when played with TMT 3.0. Fantastic work, JDobbs!

For 2nd test, I selected "Full backup" and removed all non-English audio and subtitles from all VIDs. BD-RB began re-encoding 00000.m2ts (800MB) almost immediately, then skipped 00001 and 00002 (both less than 10MB) and is currently processing 00003.m2ts, the movie itself. Rest of the files are 00004 (772MB), 00005 (440MB) and 00006 (4MB).

So, if "movie only" came to 21.9 GB with non-English audio & subs removed, there's ~1 GB of space left on the BD25 for extras that take ~2 GB on the original disc.

I guess the next logical step would be to implement a "force main movie no re-encode with re-encoded extras" mode, where BD-RB first takes into account all removed audio & subs, then calculates how much disc space is left for extras and re-encodes extras at a low enough bitrate for them to fit on a BD25 with original, untouched movie video stream. How's that sound?

Stellar. I must have missed how to enable this. So I need to add a manual switch?

0.20.03 wsorking flawlessly for me thus far BTW. 3 done.

[colinhunt]

So I need to add a manual switch?
Nope, there's no switch; BD-RB decides on its own when video re-encoding is not necessary.

[aquanash]

Looks like there is an issue with Frost/Nixon (US) using the latest v0.23.01. I ran this movie in movie-only mode to BD-25 last night and the output m2ts was oversized (25.3 gb) in the final output. I dug around the workfiles and it looks like for some reason it muxed the original video instead of the re-compressed video in the final step, completely ignoring the MKV file that was created. Here is contents of the MUX_MOVIE_ONLY.meta file:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --avchd --vbr --custom-chapters=00:00:00.000;02:01:57.393 --vbv-len=500
V_MS/VFW/WVC1, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4113.vc1"+"D:\BR\DONE\FROSTNIXON\WORKFILES\00083.track_4113.vc1", fps=23.976, track=1, insertSEI, contSPS
A_DTS, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4352.DTS", lang=eng
S_HDMV/PGS, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4608.SUP",fps=23.976,lang=eng

It has something to do with the VID_00083 video stream, which is just a "This movie has been rated R" screen that is played after the movie finishes. I was NOT able to unselect this stream in the GUI (is there a reason I can't unselect this?). As you can see in the log, it skipped re-compressing this unneeded stream after re-compressing the main movie stream (VID_00010):

-----------------------
[23:31:27] BD Rebuilder v0.23.01 (beta)
- Source: FROSTNIXON
- Input BD size: 29.48 GB
- Approximate total content: [02:01:57.643]
- Target BD size: 22.90 GB
- MOVIE-ONLY mode enabled
[23:31:27] PHASE ONE, Encoding
- [23:31:27] Extracting A/V streams [VID_00010]
- [23:46:10] Reencoding: VID_00010 (1 of 2)
- [09:13:53] Extracting A/V streams [VID_00083]
- [09:13:53] Keeping original video (no reencode)
[09:13:54]PHASE ONE complete
[09:13:54]PHASE TWO - Rebuild Started
- [09:13:54] Rebuilding BD file Structure
[09:30:22] - Encode and Rebuild complete
[09:30:22]JOB: FROSTNIXON completed.

Looks like there might be a problem with the new logic for deciding when to keep original video.

I've attached a zip file with the log, inf and all meta and avs files in the workfiles directory. I also created a file called file_list.txt that shows all the files (you can see the mkv) and their sizes in the workfiles directory.

Please let me know if you need any further info to help debug this problem.

[cyberdoggy]

o.k. I am running windows 7 build 7201 although I have a feeling that has nothing to do with anything, when I try and encode a vc-1 file, BD-Rebuilder build 0.23.01 hangs nothing happens, it does not even begin a encode, no counters change from zero, matroska icon appears in tray but nothing happens, I am lost as I never had this problem before I have tried changing the settings in ffdshow to all the the codecs that vc-1 presents and no change. as you can see I have tried these files over and over. All other codecs are working beautiful just not vc-1

- Input BD size: 36.24 GB
- Approximate total content: [03:44:19.279]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
- Resuming from previously started job.
[16:30:15] PHASE ONE, Encoding
- [16:30:15] Reencoding: VID_00001 (1 of 1)
- Encode failed. Retrying.
- Encode failed. Retrying.

[jdobbs]

Looks like there is an issue with Frost/Nixon (US) using the latest v0.23.01. I ran this movie in movie-only mode to BD-25 last night and the output m2ts was oversized (25.3 gb) in the final output. I dug around the workfiles and it looks like for some reason it muxed the original video instead of the re-compressed video in the final step, completely ignoring the MKV file that was created. Here is contents of the MUX_MOVIE_ONLY.meta file:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --avchd --vbr --custom-chapters=00:00:00.000;02:01:57.393 --vbv-len=500
V_MS/VFW/WVC1, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4113.vc1"+"D:\BR\DONE\FROSTNIXON\WORKFILES\00083.track_4113.vc1", fps=23.976, track=1, insertSEI, contSPS
A_DTS, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4352.DTS", lang=eng
S_HDMV/PGS, "D:\BR\DONE\FROSTNIXON\WORKFILES\00010.track_4608.SUP",fps=23.976,lang=eng

It has something to do with the VID_00083 video stream, which is just a "This movie has been rated R" screen that is played after the movie finishes. I was NOT able to unselect this stream in the GUI (is there a reason I can't unselect this?). As you can see in the log, it skipped re-compressing this unneeded stream after re-compressing the main movie stream (VID_00010):

-----------------------
[23:31:27] BD Rebuilder v0.23.01 (beta)
- Source: FROSTNIXON
- Input BD size: 29.48 GB
- Approximate total content: [02:01:57.643]
- Target BD size: 22.90 GB
- MOVIE-ONLY mode enabled
[23:31:27] PHASE ONE, Encoding
- [23:31:27] Extracting A/V streams [VID_00010]
- [23:46:10] Reencoding: VID_00010 (1 of 2)
- [09:13:53] Extracting A/V streams [VID_00083]
- [09:13:53] Keeping original video (no reencode)
[09:13:54]PHASE ONE complete
[09:13:54]PHASE TWO - Rebuild Started
- [09:13:54] Rebuilding BD file Structure
[09:30:22] - Encode and Rebuild complete
[09:30:22]JOB: FROSTNIXON completed.

Looks like there might be a problem with the new logic for deciding when to keep original video.

I've attached a zip file with the log, inf and all meta and avs files in the workfiles directory. I also created a file called file_list.txt that shows all the files (you can see the mkv) and their sizes in the workfiles directory.

Please let me know if you need any further info to help debug this problem. Thanks for the input. I had to modify a lot of code for that "keep original" feature, so I'm not surprised something came up. I have Frost/Nixon Region A -- I'll run it and see what happens on my system.

By the way. You can edit the INF file and remove the lines that say "USE_ORIGINAL=1" and then run BD-RB on it again. When it resumes it will rebuild using the reencoded files (assuming they exist).

[jdobbs]

o.k. I am running windows 7 build 7201 although I have a feeling that has nothing to do with anything, when I try and encode a vc-1 file, BD-Rebuilder build 0.23.01 hangs nothing happens, it does not even begin a encode, no counters change from zero, matroska icon appears in tray but nothing happens, I am lost as I never had this problem before I have tried changing the settings in ffdshow to all the the codecs that vc-1 presents and no change. as you can see I have tried these files over and over. All other codecs are working beautiful just not vc-1

- Input BD size: 36.24 GB
- Approximate total content: [03:44:19.279]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
- Resuming from previously started job.
[16:30:15] PHASE ONE, Encoding
- [16:30:15] Reencoding: VID_00001 (1 of 1)
- Encode failed. Retrying.
- Encode failed. Retrying. Actually I think it does have something to do with it. Look at this thread (http://forum.doom9.org/showthread.php?p=1283290#post1283290) and this thread (http://forum.doom9.org/showthread.php?t=146924). Sometimes Microsoft just doesn't think before they do.

[jdobbs]

Looks like there might be a problem with the new logic for deciding when to keep original video.It was. I've corrected it for the next release.

[LowDead]

You must be doing something wrong, I did this disc (EU version) and it actually oversizes by about 200mb which is well in the reasonable margin of error.

Well.. I just noticed BD-RB set the bitrate a little low. It should be alot higher. Ofcourse I could have done something wrong but I can't think of anything ^^

"C:\DVD-Rip\BD_Rebuilder\tools\x264.exe" "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS" --bitrate 2156 --level 4.1 --sar 1:1 --fps 24000/1001 --aud --vbv-bufsize 25000 --keyint 24 --min-keyint 1 --vbv-maxrate 35000 --filter 0,0 --subme 9 --me umh --ref 4 --bframes 3 --mixed-refs --8x8dct --direct auto --weightb --trellis 1 --psy-rd 1.0:0.2 --aq-strength 0.8 --threads auto --thread-input --progress --no-psnr --no-ssim --stats "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV.stats" --pass 2 --output "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV"

//LD

[Category 5]

Nope, there's no switch; BD-RB decides on its own when video re-encoding is not necessary.

Bitchin! jDobbs just earned another donation!

[setarip_old]

@jdobbs

I used v.0.23.01 to successfully without incident process two BluRays as "movie-only".

I then tried using it to process "Night at the Museum" (that I'd previously done without incident back in February). The progress bar stopped at "2/", "100% Current Progress", and "50% Overall Progress".

Selecting "Abort" and the "backup" got thing going again.

From what I've read in this thread, other reports of this behavior, with earlier versions, appear to have been limited to VC-1 video. Be advised that the main movie of "Night at the Museum" contains MPEG-2 video...

Your thoughts please?

[jdobbs]

@jdobbs

I used v.0.23.01 to successfully without incident process two BluRays as "movie-only".

I then tried using it to process "Night at the Museum" (that I'd previously done without incident back in February). The progress bar stopped at "2/", "100% Current Progress", and "50% Overall Progress".

Selecting "Abort" and the "backup" got thing going again.

From what I've read in this thread, other reports of this behavior, with earlier versions, appear to have been limited to VC-1 video. Be advised that the main movie of "Night at the Museum" contains MPEG-2 video...

Your thoughts please? Please check it again -- and make sure you aren't using the last version by mistake. I GUARANTEE the GUI code for grabbing status is no different than it was in the earlier versions before this was first reported. Others are saying they aren't seeing it anymore. If it is still doing this, please try it with an earlier version of X264. It would be the only thing related to this that has changed.

Is this something that only happens on Windows 7, maybe? I'm using Vista and never once (with encodes running pretty much 24hrs a day) have I ever seen it happen.

By the way... what is "2/"? Did you mean "2/2"? Is it actually reporting it that way?

[jdobbs]

Just had a major undersize on benjamin button EUR.. Choosed BD25 output and it came out 10GB.. If there's anything in particilar you need to know JD just let me know.. I have been away from testing due to work for some time know so i'm not sure what I'm supposted to post about bugs ^^

[Options]
RESIZE=0
MODE=0
ENCODE_QUALITY=3
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;swe;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450

"C:\DVD-Rip\BD_Rebuilder\tools\x264.exe" "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS" --bitrate 2156 --level 4.1 --sar 1:1 --fps 24000/1001 --aud --vbv-bufsize 25000 --keyint 24 --min-keyint 1 --vbv-maxrate 35000 --filter 0,0 --subme 9 --me umh --ref 4 --bframes 3 --mixed-refs --8x8dct --direct auto --weightb --trellis 1 --psy-rd 1.0:0.2 --aq-strength 0.8 --threads auto --thread-input --progress --no-psnr --no-ssim --stats "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV.stats" --pass 2 --output "C:\TEMP\BENNY\WORKFILES\VID_00015.AVS.MKV"

//LD Could you post the INF file and the LOG?

[jdobbs]

Updated the first post of this thread with links to a new version (v0.23.02). The changes for this version are:

June 20th, 2009 - v0.23.02
- Corrected an error in which a file may incorrectly
be flagged as no reencode and cause oversizing.
- Updated X264.EXE to newer version (r1169)
- Other minor corrections and cosmetic fixes.

June 18th, 2009 - v0.23.01
- Added the --fps parameter to the X264 command line
to circumvent possible inconsistencies in source
frame serving.
- Added code to detect pulldown in VC-1 sources and
perform special handling (e.g. auto removal).
- Changed the method of updating the progress bar
back to that in v0.21.01. It seems the O/S isn't
consistent returning window handles.
- Corrected an error in which field deinterlacing
could fail when the output of the source codec was
not YUY2 or YV12.
- Corrected an issue related to sources with pulldown
that could result in audio synch errors.
- Changed the default value of the FIX_CLPI hidden INI
setting. The CLPI errors were fixed in TSMUXER and
this is typically no longer needed. If you are using
an older version of TSMUXER rather than the one that
is shipped with BD-RB, however, please add FIX_CLPI=1
to the "Options" area of your config (INI) file.
- Fixed some overall progress reporting errors when
resuming a movie-only encode.
- Added code to identify troublesome (field based)
VC-1 interlaced files. In BD-25 backups they are (if
not the main-feature) automatically copied intact to
prevent CODEC failures during encoding with X264.
NOTE: Setting the RESIZE option will disable this
feature.
- Added two flags to the streams list following the fps
indicator. "*" means the source is PULLDOWN. "**"
(BD5/9 only) means the source is FIELD BASED interlaced
VC-1 and will be BLANKED during reencoding. Audio
will playback correctly, but with a blank screen. This
is required in order to prevent CODEC failures on these
sources. If you see a lot of "**" flags, you may want
to consider movie-only mode.
- Added a hidden option called "DISABLE_VC1_FIX=1" this
will disable the the two changes above (intact copy and
blanking) -- just in case a CODEC is discovered that
properly handles these streams. Flags will still be
displayed.
- Added code to detect when a video source does not
require encoding to meet target size goals, and keep it
intact. Please note that the decision contains more
than meets the eye. For example, if an M2TS is a part
of more than one MPLS and a component portion of the
other cannot be kept intact -- it may not qualify and
requires encoding.
- Other minor corrections and cosmetic fixes.

[setarip_old]

@jdobbsPlease check it again -- and make sure you aren't using the last version by mistake. I GUARANTEE the GUI code for grabbing status is no different than it was in the earlier versions before this was first reported. Others are saying they aren't seeing it anymore. If it is still doing this, please try it with an earlier version of X264. It would be the only thing related to this that has changed.

Is this something that only happens on Windows 7, maybe? I'm using Vista and never once (with encodes running pretty much 24hrs a day) have I ever seen it happen.

By the way... what is "2/"? Did you mean "2/2"? Is it actually reporting it that way?

1) It is DEFINITELY v.0.23.01 - It's still running and is at 59.30% Current and 79.70% Overall Progress.

2) Yes, I meant "2/2" - And it also showed "Frames 156,240/156,240!

3) I'm using a machine with Vista Home Premium SP2

4) I never had this happen with ANY of the previous versions, up to and including 0.22.02 - and as I initially stated - I had two non-problematic conversions using v.0.23.01 before encountering this (Again, it's an MPEG-2 format movie in this BluRay).

5) When "Night at the Museum" is finished, I'll use the SAME setup to convert another, different BluRay. If I encounter the same progress bar problem, I'll then swap in an earlier version of x264 and re-try - and will then advise you of the results.

**EDIT** Since you've just released another version, 0.23.02, I'll try it first...

[LowDead]

Could you post the INF file and the LOG?

INF:

[Status]
LABEL=THE_CURIOUS_CASE_OF_BENJAMIN_BUTTON
VERSION=v0.23.01 (beta)
SOURCE_SIZE=43982327792
SOURCE_VIDEO_SIZE=43839043584
TARGET_SIZE=24117248000
REDUCTION=.546863294270175
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;swe;
BACKUP_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=2
REBUILD_COMPLETE=1
[00001]
AUDIO=1000000000
PGS=1000000000000000010000000
M2TS_TARGET=23874570400
RATE=15594
NSIZE=10635644928
FLINK=0
MLINK=0
[00015]
AUDIO=
PGS=
M2TS_TARGET=99393392
RATE=2156
NSIZE=88565760
FLINK=0
MLINK=0

LOG:
-----------------------
[16:47:19] BD Rebuilder v0.23.01 (beta)
- Source: THE_CURIOUS_CASE_OF_BENJAMIN_BUTTON
- Input BD size: 40,96 GB
- Approximate total content: [02:51:43.584]
- Target BD size: 22,46 GB
[16:47:20] PHASE ONE, Encoding
- [16:47:20] Extracting A/V streams [VID_00001]
- [17:02:53] Reencoding: VID_00001 (1 of 2)
- [23:54:21] Extracting A/V streams [VID_00015]
- [23:54:26] Reencoding: VID_00015 (2 of 2)
[00:02:07]PHASE ONE complete
[00:02:07]PHASE TWO - Rebuild Started
- [00:02:07] Rebuilding BD file Structure
[00:02:11] - Encode and Rebuild complete
[00:02:11]JOB: THE_CURIOUS_CASE_OF_BENJAMIN_BUTTON completed.

//LD

[Sharc]

Just had a major undersize on benjamin button EUR.. Choosed BD25 output and it came out 10GB.. If there's anything in particilar you need to know JD just let me know.. I have been away from testing due to work for some time know so i'm not sure what I'm supposted to post about bugs ^^

I noticed that Benjamin Button is extremely well compressible (very clean and noise-free, not much motion/action content).
I did a crf 21.5 encode for a 720p resize, and ended up with surprisingly low 2.35GB for the 2h46min video. So I wonder if you just might have run into encoder saturation in your case.

[LowDead]

I noticed that Benjamin Button is extremely well compressible (very clean and noise-free, not much motion/action content).
I did a crf 21.5 encode for a 720p resize, and ended up with surprisingly low 2.35GB for the 2h46min video. So I wonder if you just might have run into encoder saturation in your case.

That is a valid thought. I was suprised myself of how clean it looked even after encoding. Will now try the latest build to see if there was something introduced in 0.23.01. It is VC-1 so you never know.. :)

[jdobbs]

I noticed that Benjamin Button is extremely well compressible (very clean and noise-free, not much motion/action content).
I did a crf 21.5 encode for a 720p resize, and ended up with surprisingly low 2.35GB for the 2h46min video. So I wonder if you just might have run into encoder saturation in your case.If it were saturation, though, you'd expect to see a specified bitrate that was much higher than 2.15 Mbs...

[Edit] Whoops -- I stand corrected, the INF shows that not to be the case. The low bitrate posted earlier was for the small 99MB component (00015) -- the main feature was encoded at 15.5Mbs... One of only two things could have happened. Either there was saturation or the film didn't completely reencode. If it were the second, though it should have flagged the error. I think it was saturation also, which of course is a good thing, as it means that even though it is undersize -- it is high quality.

[jdobbs]

@jdobbs

1) It is DEFINITELY v.0.23.01 - It's still running and is at 59.30% Current and 79.70% Overall Progress.

2) Yes, I meant "2/2" - And it also showed "Frames 156,240/156,240!

3) I'm using a machine with Vista Home Premium SP2

4) I never had this happen with ANY of the previous versions, up to and including 0.22.02 - and as I initially stated - I had two non-problematic conversions using v.0.23.01 before encountering this (Again, it's an MPEG-2 format movie in this BluRay).

5) When "Night at the Museum" is finished, I'll use the SAME setup to convert another, different BluRay. If I encounter the same progress bar problem, I'll then swap in an earlier version of x264 and re-try - and will then advise you of the results.

**EDIT** Since you've just released another version, 0.23.02, I'll try it first... If you do -- please try it with X264 version r1153 or r1145. The only other change that might affect that was the X264 update. Another option would be to run with "SHOW_ENCODER=1". BD-RB is looking at the caption of the window to get it's status reporting... see if there is anything odd happening there.

You might also try one of the older version with the newer X264.

I am just baffled as to how this could start happening out of nowhere -- happen only to certain people, and never happen to me. In the next version I'm going to put a STATUS message if it never finds the window handle, just so I know if that is definitely it.

[MikeyBK]

Just FYI JD... the stuck at 50% has not showed up for me using versions 0.23.01 or 0.23.02....they've all shown the progress status properly so far.

[setarip_old]

@jdobbs

Just to let you know that v.0.23.02 (as is, with the version of x264 you included in this v.0.23.02 zip package) properly and completely processed the movie-only version of "Night at the Museum", using the identical settings I had previously used with v.0.23.01.

The progress bars (and related frame ifo, etc., below the progress bars) displayed and progressed properly throughout the process...

(This was started well before your most recent post)

[LowDead]

If it were saturation, though, you'd expect to see a specified bitrate that was much higher than 2.15 Mbs...

[Edit] Whoops -- I stand corrected, the INF shows that not to be the case. The low bitrate posted earlier was for the small 99MB component (00015) -- the main feature was encoded at 15.5Mbs... One of only two things could have happened. Either there was saturation or the film didn't completely reencode. If it were the second, though it should have flagged the error. I think it was saturation also, which of course is a good thing, as it means that even though it is undersize -- it is high quality.

hehe.. I missed that one too.. I thought it was the main movie that was encoded at 2.15mbs.. All I can say is that this one is strange.. Tried a manual encode to BD25 movie only which resulted in an 10GB oversize.. Although when I did a manual movie only DVD9, it went spot on. Great quality on all encodes I have tested though.

//LD

[Category 5]

If it were saturation, though, you'd expect to see a specified bitrate that was much higher than 2.15 Mbs...

[Edit] Whoops -- I stand corrected, the INF shows that not to be the case. The low bitrate posted earlier was for the small 99MB component (00015) -- the main feature was encoded at 15.5Mbs... One of only two things could have happened. Either there was saturation or the film didn't completely reencode. If it were the second, though it should have flagged the error. I think it was saturation also, which of course is a good thing, as it means that even though it is undersize -- it is high quality.

The Us version, movie only, re-encoded to fill 96% of a BD25, and it does look fantastic as a re-code. Why would VC-1 source from a different region behave so differently?

[jdobbs]

The Us version, movie only, re-encoded to fill 96% of a BD25, and it does look fantastic as a re-code. Why would VC-1 source from a different region behave so differently? No clue.

@LowDead

It plays through from end-to-end? Nothing missing? If so, it has to be saturation... otherwise the size would be a lot large with a 15.5Mbs bitrate set. It may be hitting qpmin (I'm believe it defaults to 10). You could look at the stats file and see what q you are getting. If it is predominately 10, then this is definitely the reason for the undersize.

[LowDead]

No clue.

@LowDead

It plays through from end-to-end? Nothing missing? If so, it has to be saturation... otherwise the size would be a lot large with a 15.5Mbs bitrate set. It may be hitting qpmin (I'm believe it defaults to 10). You could look at the stats file and see what q you are getting. If it is predominately 10, then this is definitely the reason for the undersize.

The q's are approx. around 20 and qpmin is set to 10. Cannot check right now if it plays through. The last encode seemed to be complete (full runtime in mpc). Now I'm doing a new encode with the same config but with latest build. Tomorrow I want to test what happens if I do COMPLETE FULL backup (with ALL audio and sub tracks) to see how BD-RB will behave. If it is saturation it should end up around 21gig as all the tracks are about 10gb. But what will happen with calculations? BD-RB will "see" that it needs to lower the bitrate and it will undersize even more? That test will be interesting :)

Also.. Can someone more do a new test with Benjamin Button (US and EUR). Full BD25 encodes with best quality. This could answer if something is different between the both versions and also it could rule out that I'm a complete idiot and/or my system is messed up ^^

Quick update: The encode just finished. Worked flawlessly with v0.23.02. Exact same config and setup as before. 24GB, 97% filled BD25 :)

//LD

[setarip_old]

@jdobbs

I just used v.0.23.02 (as is, with the "tools" included in the zip) to process a "movie-only" version of "Speed Racer" (2008 movie), a VC-1 format BluRay.

No anomalies were noted - The progress bars performed and displayed properly throughout the conversion and the VC-1 video was properly converted and compressed.

This is now the second movie I've processed with this version, with no problems noted...

[jdobbs]

Hehehe... I'm working on PiP (secondary audio/video) right now. I've also added some code to make target sizing more accurate (thanks to some good research I got from lithiumus).

Good to know 23.2 seems to be working out well.

[Capsbackup]

Hehehe... I'm working on PiP (secondary audio/video) right now. I've also added some code to make target sizing more accurate (thanks to some good research I got from lithiumus).

Good to know 23.2 seems to be working out well.

PIP ?? Well that would be awesome!! If you can complete this task, I'll place you up there with that prophet that parted the waters!! LOL :p
I have always been impressed with your software programing skills, and this would just be another great achievement. I appreciate your efforts. :)

[PurpleMan]

jdobbs,

I asked before (twice I think) and didn't get a reply.

I was wondering if there is a reason for not using the dgdecode tools (DGAVCDecode, DGVC1Decode) with BD-Rebuilder?

That would achieve consistency in the decoding process on various platforms and boxes.

Thanks again!

[spida_singh]

jdobbs

I tried a full backup of Kung Fu Panda UK Disc, encoding went through fine apart from actually building the structure. Is there anyway I can build the structure manually?

BD-Rebuilder Code:

-----------------------
[21:23:49] BD Rebuilder v0.23.02 (beta)
- Source: KUNG_FU_PANDA_EN
- Input BD size: 44.48 GB
- Approximate total content: [03:26:24.671]
- Target BD size: 8.94 GB
[21:23:49] PHASE ONE, Encoding
- [21:23:49] Extracting A/V streams [VID_00004]
- Audio/PGS sizing issue. Continued...
- [21:37:05] Reencoding: VID_00004 (1 of 52)
- [23:16:54] Extracting A/V streams [VID_00005]
- [23:18:07] Reencoding: VID_00005 (2 of 52)
- [23:57:56] Extracting A/V streams [VID_00006]
- [23:58:33] Reencoding: VID_00006 (3 of 52)
- [00:19:36] Extracting A/V streams [VID_00007]
- [00:19:46] Reencoding: VID_00007 (4 of 52)
- [00:24:19] Extracting A/V streams [VID_00008]
- [00:24:39] Reencoding: VID_00008 (5 of 52)
- [00:31:43] Extracting A/V streams [VID_00009]
- [00:32:08] Reencoding: VID_00009 (6 of 52)
- [00:41:02] Extracting A/V streams [VID_00010]
- [00:41:22] Reencoding: VID_00010 (7 of 52)
- [00:48:17] Extracting A/V streams [VID_00011]
- [00:49:00] Reencoding: VID_00011 (8 of 52)
- [01:07:33] Extracting A/V streams [VID_00012]
- [01:07:59] Reencoding: VID_00012 (9 of 52)
- [01:17:50] Extracting A/V streams [VID_00013]
- [01:18:16] Reencoding: VID_00013 (10 of 52)
- [01:27:41] Extracting A/V streams [VID_00014]
- [01:28:01] Reencoding: VID_00014 (11 of 52)
- [01:36:56] Extracting A/V streams [VID_00015]
- [01:37:09] Reencoding: VID_00015 (12 of 52)
- [01:43:27] Extracting A/V streams [VID_00016]
- [01:43:51] Reencoding: VID_00016 (13 of 52)
- [01:54:39] Extracting A/V streams [VID_00017]
- [01:54:47] Reencoding: VID_00017 (14 of 52)
- [01:57:50] Extracting A/V streams [VID_00018]
- [01:58:03] Reencoding: VID_00018 (15 of 52)
- [02:02:47] Extracting A/V streams [VID_00019]
- [02:02:56] Reencoding: VID_00019 (16 of 52)
- [02:06:43] Extracting A/V streams [VID_00020]
- [02:06:52] Reencoding: VID_00020 (17 of 52)
- [02:10:26] Extracting A/V streams [VID_00021]
- [02:10:32] Reencoding: VID_00021 (18 of 52)
- [02:12:39] Extracting A/V streams [VID_00022]
- [02:12:47] Reencoding: VID_00022 (19 of 52)
- [02:16:05] Extracting A/V streams [VID_00023]
- [02:16:30] Reencoding: VID_00023 (20 of 52)
- [02:27:36] Extracting A/V streams [VID_00024]
- [02:27:51] Reencoding: VID_00024 (21 of 52)
- [02:34:22] Extracting A/V streams [VID_00026]
- [02:34:55] Reencoding: VID_00026 (22 of 52)
- [02:49:55] Extracting A/V streams [VID_00104]
- [02:50:02] Reencoding: VID_00104 (23 of 52)
- [02:53:21] Extracting A/V streams [VID_00105]
- [02:53:28] Reencoding: VID_00105 (24 of 52)
- [02:57:01] Extracting A/V streams [VID_00107]
- [02:57:06] Reencoding: VID_00107 (25 of 52)
- [02:59:38] Extracting A/V streams [VID_00108]
- [02:59:48] Reencoding: VID_00108 (26 of 52)
- [03:04:11] Extracting A/V streams [VID_00109]
- [03:04:21] Reencoding: VID_00109 (27 of 52)
- [03:08:36] Extracting A/V streams [VID_00110]
- [03:08:44] Reencoding: VID_00110 (28 of 52)
- [03:12:39] Extracting A/V streams [VID_00111]
- [03:12:46] Reencoding: VID_00111 (29 of 52)
- [03:16:26] Extracting A/V streams [VID_00121]
- [03:16:30] Reencoding: VID_00121 (30 of 52)
- [03:19:23] Extracting A/V streams [VID_00122]
- [03:19:24] Reencoding: VID_00122 (31 of 52)
- [03:20:01] Extracting A/V streams [VID_00123]
- [03:20:13] Reencoding: VID_00123 (32 of 52)
- [03:26:23] Extracting A/V streams [VID_00142]
- [03:26:27] Reencoding: VID_00142 (33 of 52)
- [03:29:41] Extracting A/V streams [VID_00143]
- [03:29:41] Reencoding: VID_00143 (34 of 52)
- [03:29:56] Extracting A/V streams [VID_00146]
- [03:30:01] Reencoding: VID_00146 (35 of 52)
- [03:32:34] Extracting A/V streams [VID_00147]
- [03:32:35] Reencoding: VID_00147 (36 of 52)
- [03:33:04] Extracting A/V streams [VID_00148]
- [03:33:08] Reencoding: VID_00148 (37 of 52)
- [03:35:37] Extracting A/V streams [VID_00149]
- [03:35:38] Reencoding: VID_00149 (38 of 52)
- [03:36:27] Extracting A/V streams [VID_00150]
- [03:36:29] Reencoding: VID_00150 (39 of 52)
- [03:37:50] Extracting A/V streams [VID_00151]
- [03:37:52] Reencoding: VID_00151 (40 of 52)
- [03:38:45] Extracting A/V streams [VID_00152]
- [03:38:45] Reencoding: VID_00152 (41 of 52)
- [03:38:51] Extracting A/V streams [VID_00153]
- [03:38:55] Reencoding: VID_00153 (42 of 52)
- [03:40:49] Extracting A/V streams [VID_00154]
- [03:40:53] Reencoding: VID_00154 (43 of 52)
- [03:42:47] Extracting A/V streams [VID_00155]
- [03:42:51] Reencoding: VID_00155 (44 of 52)
- [03:44:44] Extracting A/V streams [VID_00156]
- [03:44:48] Reencoding: VID_00156 (45 of 52)
- [03:46:42] Extracting A/V streams [VID_00157]
- [03:46:46] Reencoding: VID_00157 (46 of 52)
- [03:48:39] Extracting A/V streams [VID_00158]
- [03:48:40] Reencoding: VID_00158 (47 of 52)
- [03:48:46] Extracting A/V streams [VID_00159]
- [03:48:46] Reencoding: VID_00159 (48 of 52)
- [03:48:52] Extracting A/V streams [VID_00160]
- [03:48:53] Reencoding: VID_00160 (49 of 52)
- [03:48:59] Extracting A/V streams [VID_00161]
- [03:48:59] Reencoding: VID_00161 (50 of 52)
- [03:49:05] Extracting A/V streams [VID_00162]
- [03:49:05] Reencoding: VID_00162 (51 of 52)
- [03:49:12] Extracting A/V streams [VID_00612]
- [03:49:12] Reencoding: VID_00612 (52 of 52)
- Error in attempt to multiplex: MUX_00612.meta
[03:49:14] - Failed to build structure, aborted

[Status]
LABEL=KUNG_FU_PANDA_EN
VERSION=v0.23.02 (beta)
SOURCE_SIZE=47758113690
SOURCE_VIDEO_SIZE=40742940672
TARGET_SIZE=9594470400
REDUCTION=6.33066081990637E-02
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
BACKUP_MODE=0
QUICK=0
ENCODE_STEP=4
COMPLETED=51
[00004]
AUDIO=1000000000
PGS=10000000000000000
M2TS_TARGET=1550574245
NSIZE=6541873152
FLINK=0
MLINK=0
[00005]
AUDIO=1
PGS=01000000
M2TS_TARGET=124170639
RATE=899
NSIZE=130873344
FLINK=0
MLINK=0
[00006]
AUDIO=1
PGS=01000000
M2TS_TARGET=66745593
RATE=891
NSIZE=70508544
FLINK=0
MLINK=0
[00007]
AUDIO=1
PGS=01000000
M2TS_TARGET=18046382
RATE=846
NSIZE=18991104
FLINK=0
MLINK=0
[00008]
AUDIO=1
PGS=01000000
M2TS_TARGET=34843828
RATE=914
NSIZE=36599808
FLINK=0
MLINK=0
[00009]
AUDIO=1
PGS=01000000
M2TS_TARGET=45099036
RATE=910
NSIZE=47407104
FLINK=0
MLINK=0
[00010]
AUDIO=1
PGS=01000000
M2TS_TARGET=35079924
RATE=913
NSIZE=36851712
FLINK=0
MLINK=0
[00011]
AUDIO=1
PGS=01000000
M2TS_TARGET=77381979
RATE=903
NSIZE=81186816
FLINK=0
MLINK=0
[00012]
AUDIO=1
PGS=01000000
M2TS_TARGET=50149238
RATE=913
NSIZE=52733952
FLINK=0
MLINK=0
[00013]
AUDIO=1
PGS=01000000
M2TS_TARGET=48198236
RATE=910
NSIZE=50743296
FLINK=0
MLINK=0
[00014]
AUDIO=1
PGS=01000000
M2TS_TARGET=36208673
RATE=904
NSIZE=37976064
FLINK=0
MLINK=0
[00015]
AUDIO=1
PGS=
M2TS_TARGET=22554769
RATE=928
NSIZE=23666688
FLINK=0
MLINK=0
[00016]
AUDIO=1
PGS=01000000
M2TS_TARGET=42197426
RATE=901
NSIZE=44249088
FLINK=0
MLINK=0
[00017]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=14331465
RATE=1027
NSIZE=15009792
FLINK=0
MLINK=0
[00018]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=21848814
RATE=983
NSIZE=22751232
FLINK=0
MLINK=0
[00019]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=16678036
RATE=994
NSIZE=17399808
FLINK=0
MLINK=0
[00020]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=15749209
RATE=976
NSIZE=16422912
FLINK=0
MLINK=0
[00021]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=9252870
RATE=982
NSIZE=9787392
FLINK=0
MLINK=0
[00022]
AUDIO=1000000
PGS=01000000000000
M2TS_TARGET=14643797
RATE=1006
NSIZE=15249408
FLINK=0
MLINK=0
[00023]
AUDIO=1
PGS=01000000
M2TS_TARGET=44057801
RATE=892
NSIZE=46239744
FLINK=0
MLINK=0
[00024]
AUDIO=1
PGS=01000000
M2TS_TARGET=27549350
RATE=892
NSIZE=28901376
FLINK=0
MLINK=0
[00026]
AUDIO=0100000
PGS=01000000
M2TS_TARGET=63355455
RATE=979
NSIZE=66232320
FLINK=0
MLINK=0
[00104]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=12223325
RATE=1012
NSIZE=12736512
FLINK=0
MLINK=0
[00105]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=13114812
RATE=1010
NSIZE=13688832
FLINK=0
MLINK=0
[00107]
AUDIO=0100000
PGS=01000000
M2TS_TARGET=9638714
RATE=1005
NSIZE=10033152
FLINK=0
MLINK=0
[00108]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=18584697
RATE=1011
NSIZE=19365888
FLINK=0
MLINK=0
[00109]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=19039386
RATE=1008
NSIZE=19783680
FLINK=0
MLINK=0
[00110]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=15315913
RATE=1011
NSIZE=15962112
FLINK=0
MLINK=0
[00111]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=13006682
RATE=1013
NSIZE=13584384
FLINK=0
MLINK=0
[00121]
AUDIO=1
PGS=01000000
M2TS_TARGET=6707932
RATE=504
NSIZE=9431040
FLINK=0
MLINK=0
[00122]
AUDIO=1
PGS=01000000
M2TS_TARGET=1738632
RATE=484
NSIZE=1898496
FLINK=0
MLINK=0
[00123]
AUDIO=1000000
PGS=01000000
M2TS_TARGET=23859327
RATE=998
NSIZE=24803328
FLINK=0
MLINK=0
[00142]
AUDIO=1
PGS=01000000
M2TS_TARGET=7385882
RATE=504
NSIZE=8828928
FLINK=0
MLINK=0
[00143]
AUDIO=1
PGS=01000000
M2TS_TARGET=558152
RATE=442
NSIZE=626688
FLINK=0
MLINK=0
[00146]
AUDIO=1
PGS=01000000
M2TS_TARGET=7205406
RATE=489
NSIZE=7944192
FLINK=0
MLINK=0
[00147]
AUDIO=1
PGS=01000000
M2TS_TARGET=1262162
RATE=472
NSIZE=1406976
FLINK=0
MLINK=0
[00148]
AUDIO=1
PGS=01000000
M2TS_TARGET=7768614
RATE=502
NSIZE=8558592
FLINK=0
MLINK=0
[00149]
AUDIO=1
PGS=01000000
M2TS_TARGET=2815262
RATE=504
NSIZE=3102720
FLINK=0
MLINK=0
[00150]
AUDIO=1
PGS=01000000
M2TS_TARGET=3774427
RATE=501
NSIZE=4141056
FLINK=0
MLINK=0
[00151]
AUDIO=1
PGS=01000000
M2TS_TARGET=2798926
RATE=500
NSIZE=3078144
FLINK=0
MLINK=0
[00152]
AUDIO=1
PGS=01000000
M2TS_TARGET=158694
RATE=568
NSIZE=178176
FLINK=0
MLINK=0
[00153]
AUDIO=1
PGS=01000000
M2TS_TARGET=6551183
RATE=488
NSIZE=7163904
FLINK=0
MLINK=0
[00154]
AUDIO=1
PGS=01000000
M2TS_TARGET=6570630
RATE=490
NSIZE=7225344
FLINK=0
MLINK=0
[00155]
AUDIO=1
PGS=01000000
M2TS_TARGET=6563629
RATE=490
NSIZE=7139328
FLINK=0
MLINK=0
[00156]
AUDIO=1
PGS=01000000
M2TS_TARGET=6547293
RATE=488
NSIZE=7206912
FLINK=0
MLINK=0
[00157]
AUDIO=1
PGS=01000000
M2TS_TARGET=6584633
RATE=492
NSIZE=7243776
FLINK=0
MLINK=0
[00158]
AUDIO=1
PGS=01000000
M2TS_TARGET=163361
RATE=590
NSIZE=178176
FLINK=0
MLINK=0
[00159]
AUDIO=1
PGS=01000000
M2TS_TARGET=159083
RATE=570
NSIZE=172032
FLINK=0
MLINK=0
[00160]
AUDIO=1
PGS=01000000
M2TS_TARGET=159472
RATE=572
NSIZE=172032
FLINK=0
MLINK=0
[00161]
AUDIO=1
PGS=01000000
M2TS_TARGET=160639
RATE=577
NSIZE=178176
FLINK=0
MLINK=0
[00162]
AUDIO=1
PGS=01000000
M2TS_TARGET=158694
RATE=568
NSIZE=178176
FLINK=0
MLINK=0
[00612]
AUDIO=0100000
PGS=01000000000000
M2TS_TARGET=5056


Meta file in question

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --auto-chapters=5 --vbv-len=500
V_MPEG4/ISO/AVC, "I:\VIDEOS\MOVIES\KUNG.FU.PANDA\WORKFILES\VID_00612.AVS.MKV", fps=23.976, track=1, insertSEI, contSPS
A_AC3, "I:\VIDEOS\MOVIES\KUNG.FU.PANDA\WORKFILES\00612.track_4353.AC3", lang=eng
S_HDMV/PGS, "I:\VIDEOS\MOVIES\KUNG.FU.PANDA\WORKFILES\00612.track_4609.sup", fps=23.976, lang=eng


regards

[jdobbs]

jdobbs,

I asked before (twice I think) and didn't get a reply.

I was wondering if there is a reason for not using the dgdecode tools (DGAVCDecode, DGVC1Decode) with BD-Rebuilder?

That would achieve consistency in the decoding process on various platforms and boxes.

Thanks again! Yes. It would require someone to buy/donate something before they can use BD-RB. If you have to buy something -- it is no longer freeware.

BTW, I fully support Neuron2's concept of a required donation. That's what I do for DVD Rebuilder Professional Edition as well. It has been my experience to date that if you don't require it you will be very disappointed. People just generally want a free ride.

[gizzin]

Yes. It would require someone to buy/donate something before they can use BD-RB. If you have to buy something -- it is no longer freeware.

BTW, I fully support Neuron2's concept of a required donation. That's what I do for DVD Rebuilder Professional Edition as well. It has been my experience to date that if you don't require it you will be very disappointed. People just generally want a free ride.

lol, keep up the good work jdobbs.

[tekmobile]

Just got a encoder fail on doing the second pass of a very small file that BD-RB says needs doing because its part of another playlist

a screengrab of x264 shows this error as its reason


avis [info]: 1920x1080 @ 23.98 fps (6 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Slow
x264 [error]: requested bitrate is too low. estimated minimum is 28 kbps
x264 [error]: x265_encoder_open failed


LASTCMD.txt

"F:\BD_Rebuilder\tools\x264.exe" "F:\OUTPUT\WORKFILES\VID_00057.AVS" --bitrate 5 --level 4.1 --sar 1:1 --fps 24000/1001 --aud --vbv-bufsize 25000 --keyint 24 --min-keyint 1 --vbv-maxrate 35000 --filter 0,0 --subme 7 --me umh --ref 3 --bframes 3 --direct auto --8x8dct --weightb --trellis 1 --psy-rd 1.0:0.2 --aq-strength 0.8 --threads auto --thread-input --progress --no-psnr --no-ssim --stats "F:\OUTPUT\WORKFILES\VID_00057.AVS.MKV.stats" --pass 2 --output "F:\OUTPUT\WORKFILES\VID_00057.AVS.MKV"


The M2TS ReEncoded before this one was pretty much identical just a black screen but this one encoded without problems

To sort it I copied and renamed the MKV encoded in the previous step since it was pretty much the same size/content to match the one that failed and changed the step in the BDREBUILDER.INF file so it would skip the encoding of the file and proceed to the multiplexing of the MKV I copied/renamed it then completed ok

[liquidskin76]

@jdobbs

Just curious (again!)... how does BD-RB handle forced subs in Movie Only encodes? By forced, i mean subs that automatically appear when a foreign language is spoken in an english language film?

Kill Bill 1 is an example.

Cheers