BD Rebuilder Beta - Bug Reports Only

[jdobbs]

I experienced exactly this ERROR some time ago repeatedly. I could fix it by using this version of wavi.exe. (http://forum.doom9.org/showthread.php?p=1508525#post1508525)
Maybe you give it a try and report back if it solves the 'aften' issue.Thought I mention... the link reference is for WAVI.EXE 1.06m -- that's the same one that is distributed with BD-RB.

[Sharc]

Thought I mention... the link reference is for WAVI.EXE 1.06m -- that's the same one that is distributed with BD-RB.
Ah good, thanks. It has been quite a while ago since I found that the former version should probably be replaced by this one - at least for my system.

[jdobbs]

Ah good, thanks. It has been quite a while ago since I found that the former version should probably be replaced by this one - at least for my system.Your post back then was probably why I replaced it. ;)

[dfsooner]

Trying to create 3D mkv from the movie Dredd and got the following mkvmerge error at the end. Looks like the problem seen by AmigaFuture because there is a zero-length AC3 file in the workfiles (AUD_00201_4353.AC3).

Log file:
[05/20/13] BD Rebuilder v0.44.06 (beta)
[07:41:12] Source: DREDD_00800
- Input BD size: 23.61 GB
- Approximate total content: [01:35:51.787]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- 3D conversion mode enabled
- Decoding/Frame serving: DirectShowMVC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[07:41:12] PHASE ONE, Encoding
- [07:41:12] Processing: VID_00201_3D (1 of 1)
- [07:41:12] Combining multiple 3D segments.
- [07:57:48] Extracting A/V streams [VID_00201]
- [08:10:16] Reencoding video [VID_00201]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 137,905 frames
- Converting output to Side-By-Side 3D Format
- [08:10:16] Reencoding: VID_00201, Pass 1 of 1
- [09:50:42] Video Encode complete
- [09:50:42] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
[09:52:35]PHASE ONE complete
[09:52:35]PHASE TWO - Rebuild Started
- [09:52:35] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MKVMERGE)
[09:55:01] - Failed to REBUILD

INF file:
[Status]
LABEL=DREDD
VERSION=v0.44.06 (beta)
SOURCE_SIZE=25346598912
SOURCE_VIDEO_SIZE=25346598912
TARGET_SIZE=8422162432
REDUCTION=.33227978480429
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;fra;ger;spa;
BACKUP_MODE=1
MOVIEONLY_TYPE=10
USE_LAVF=0
INSTANCES=4
DGDECNV=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=0
[00201]
AUDIO=110
PGS=101
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=3540969373
SPLITS=1
NSIZE=0
FLINK=-1
MLINK=0

[jdobbs]

I've been trying for about a week now -- and I can't create any 0 length files no matter how hard I try.

[AmigaFuture]

I've been trying for about a week now -- and I can't create any 0 length files no matter how hard I try.

I know, and I'm attempting to find the "show" so BD-RB does reproduce it for you. I'm really...hoping...your order of "Paul" will do it. :-D


@AmegaFuture

Please check your PM.

Is that what happens when eyes become code-crossed?? Haw, haw!

[thegame]

I am really sorry if this has been asked before I went back quite a few pages and even tried the forum search and found nothing, but I do remember a long time ago this being talked about, but does BD-RB have a problem with PIP audio? I ran it on a title and everything on the BD works but the PIP audio, and I see that when I load the BD into BD-RB and I click on full some audio files are still "x" out, so I click on them to un "x" them but one file stays "x" is this the audio for the PIP? which I think it read DTS Express, and again sorry for bringing this up now because like I said I do remember quite some time ago this being discussed but I cannot find it now, but it would be nice to have audio with the PIP lol.

Thanks

*EDIT, never mind, I googled some more and found my answer at the Slysoft forums lol, I read that I needed to enable a hidden setting in my ini file, DTSX_ENABLE=1, so I am trying it out now.

Thanks and sorry to bring up and old subject.

[Ch3vr0n]

you need to enable the hidden options for them to be processed. Enter the following into the bdrebuilder.ini file in it's installation folder "ENABLE_TEST=1" and "DTSX_ENABLE=1". That will allow them to be processed. Remember though, not all standalone players like the way how BDRB does it's magic. Some play the audio, some don't (even if your player is setup properly to allow for mixed audio). More often then not software players like powerdvd don't play the pip stream at all, if they do. Usually without audio aswell.

dts-e or pip audio streams in general can easily be identified.

they'll be labelled something like "AUD_008 (2nd) DTS-Express, Stereo, English". note that the "DTS-Express" part can also be AC3. There will also be an entry under the main video title for "Secundairy Video". That's the pip stream video.

[dfsooner]

I've been trying for about a week now -- and I can't create any 0 length files no matter how hard I try.

Re-ripped Dredd - different original disc, different system, different drive - same error.

[jdobbs]

Trying to create 3D mkv from the movie Dredd and got the following mkvmerge error at the end. Looks like the problem seen by AmigaFuture because there is a zero-length AC3 file in the workfiles (AUD_00201_4353.AC3).

Log file:
...

INF file:
...Just thought I'd let you know. With the help of AmigaFuture I was able to reproduce the error and I have fixed it for the next release -- which you should see later today.

[jdobbs]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.44.09). Changes for this version:- Updated the IMPORT FILE function so that PGS
subtitles (.SUP) are imported from MKV files
when they are present.
- Corrected an issue in which multipart sources
consisting of a very large number of segments
could cause a failed demux.
- Fixed an error introduced in v0.44.6 that may
cause "ERROR in attempt to mux (MKVMERGE)"
during rebuild to ALTERNATE output.
- Corrected an error that could result in audio
reencode errors or a failed rebuild (due to
zero length AC3 files).
- Corrected an error in which backup MPLS files
were not being properly renamed when performing
a QUICK_PLAY backup.
- Fixed a problem in Quick-Play rebuild that may
result in "DoEncoding() 00058 2408" error.
- Updated the included version of X264.EXE to the
latest release (r2334).
- Updated the included version of X264-64.EXE to
the latest release (r2334).
- Other minor corrections and cosmetic fixes.

[soneca]

:) :thanks:

- Updated the IMPORT FILE function so that PGS
subtitles (.SUP) are imported from MKV files
when they are present.

Very useful for me.;)

[jdobbs]

:) :thanks:



Very useful for me.;)I aim to please... :)

[AmigaFuture]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.44.09). Changes for this version:- Updated the IMPORT FILE function so that PGS
subtitles (.SUP) are imported from MKV files
when they are present.
- Corrected an issue in which multipart sources
consisting of a very large number of segments
could cause a failed demux.
- Fixed an error introduced in v0.44.6 that may
cause "ERROR in attempt to mux (MKVMERGE)"
during rebuild to ALTERNATE output.
- Corrected an error that could result in audio
reencode errors or a failed rebuild (due to
zero length AC3 files).
- Corrected an error in which backup MPLS files
were not being properly renamed when performing
a QUICK_PLAY backup.
- Fixed a problem in Quick-Play rebuild that may
result in "DoEncoding() 00058 2408" error.
- Updated the included version of X264.EXE to the
latest release (r2334).
- Updated the included version of X264-64.EXE to
the latest release (r2334).
- Other minor corrections and cosmetic fixes.

Ahh, cool, I'll test that first underline soon...been hoping for that. For now, though, it was awesome to watch "Keeping original audio.." as it also copied the AC3 files for "Paul". Whoohoo!! No 0 byte files where created or harmed in this test. (Laughing as I'm make fun of those disclaimers about animals in movies.)

Paul completed...Video, audio tracks, subs, chapters...all are doing well as I seek through. I'll watch/listen tonight but I have 0 doubt. High 5, JDobbs!! Toy Story 3 hasn't finished yet, no doubt there either as I watched the same happen.

Sweeet! :D

Edit: There's a video reencode happening with Toy Story 3..I'll post when it's finished.

Edit 2:

The Log:


[05/21/13] BD Rebuilder v0.44.09 (beta)
[16:14:05] Source: TOY_STORY_3_DISC_1_00800
- Input BD size: 27.37 GB
- Approximate total content: [01:42:33.355]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV, Intact Video, DTStoAC3 or Keep AC3
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[16:14:08] PHASE ONE, Encoding
- [16:14:08] Processing: VID_00296 (1 of 47)
- [16:14:08] Extracting A/V streams [VID_00296]
- Extracting A/V to M2TS [VID_00296]
- Extracting A/V from M2TS [VID_00296]
- [16:19:12] Reencoding video [VID_00296]
- [16:19:12] Keeping original video (no reencode)
- [16:19:12] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4354 (eng): Keeping original audio
- [16:21:39] Processing: VID_00320 (2 of 47)
- [16:21:40] Extracting A/V streams [VID_00320]
- [16:21:45] Reencoding video [VID_00320]
- [16:21:45] Keeping original video (no reencode)
- [16:21:45] Processing: VID_00297 (3 of 47)
- [16:21:45] Extracting A/V streams [VID_00297]
- [16:21:55] Reencoding video [VID_00297]
- [16:21:55] Keeping original video (no reencode)
- [16:21:55] Processing: VID_00321 (4 of 47)
- [16:21:55] Extracting A/V streams [VID_00321]
- [16:22:00] Reencoding video [VID_00321]
- [16:22:00] Keeping original video (no reencode)
- [16:22:01] Processing: VID_00298 (5 of 47)
- [16:22:01] Extracting A/V streams [VID_00298]
- [16:22:06] Reencoding video [VID_00298]
- [16:22:06] Keeping original video (no reencode)
- [16:22:06] Processing: VID_00322 (6 of 47)
- [16:22:06] Extracting A/V streams [VID_00322]
- [16:22:11] Reencoding video [VID_00322]
- [16:22:11] Keeping original video (no reencode)
- [16:22:11] Processing: VID_00299 (7 of 47)
- [16:22:11] Extracting A/V streams [VID_00299]
- [16:22:35] Reencoding video [VID_00299]
- [16:22:35] Keeping original video (no reencode)
- [16:22:35] Processing: VID_00323 (8 of 47)
- [16:22:35] Extracting A/V streams [VID_00323]
- [16:22:43] Reencoding video [VID_00323]
- [16:22:43] Keeping original video (no reencode)
- [16:22:43] Processing: VID_00301 (9 of 47)
- [16:22:43] Extracting A/V streams [VID_00301]
- [16:22:48] Reencoding video [VID_00301]
- [16:22:48] Keeping original video (no reencode)
- [16:22:48] Processing: VID_00324 (10 of 47)
- [16:22:48] Extracting A/V streams [VID_00324]
- [16:22:55] Reencoding video [VID_00324]
- [16:22:55] Keeping original video (no reencode)
- [16:22:55] Processing: VID_00302 (11 of 47)
- [16:22:55] Extracting A/V streams [VID_00302]
- [16:23:02] Reencoding video [VID_00302]
- [16:23:02] Keeping original video (no reencode)
- [16:23:02] Processing: VID_00325 (12 of 47)
- [16:23:02] Extracting A/V streams [VID_00325]
- [16:23:07] Reencoding video [VID_00325]
- [16:23:07] Keeping original video (no reencode)
- [16:23:07] Processing: VID_00303 (13 of 47)
- [16:23:07] Extracting A/V streams [VID_00303]
- [16:23:13] Reencoding video [VID_00303]
- [16:23:13] Keeping original video (no reencode)
- [16:23:13] Processing: VID_00326 (14 of 47)
- [16:23:13] Extracting A/V streams [VID_00326]
- [16:23:21] Reencoding video [VID_00326]
- [16:23:21] Keeping original video (no reencode)
- [16:23:21] Processing: VID_00304 (15 of 47)
- [16:23:21] Extracting A/V streams [VID_00304]
- [16:23:29] Reencoding video [VID_00304]
- [16:23:29] Keeping original video (no reencode)
- [16:23:29] Processing: VID_00327 (16 of 47)
- [16:23:29] Extracting A/V streams [VID_00327]
- [16:23:34] Reencoding video [VID_00327]
- [16:23:34] Keeping original video (no reencode)
- [16:23:34] Processing: VID_00305 (17 of 47)
- [16:23:34] Extracting A/V streams [VID_00305]
- [16:23:39] Reencoding video [VID_00305]
- [16:23:39] Keeping original video (no reencode)
- [16:23:39] Processing: VID_00328 (18 of 47)
- [16:23:39] Extracting A/V streams [VID_00328]
- [16:23:46] Reencoding video [VID_00328]
- [16:23:46] Keeping original video (no reencode)
- [16:23:46] Processing: VID_00306 (19 of 47)
- [16:23:46] Extracting A/V streams [VID_00306]
- [16:24:49] Reencoding video [VID_00306]
- [16:24:49] Keeping original video (no reencode)
- [16:24:49] Processing: VID_00329 (20 of 47)
- [16:24:49] Extracting A/V streams [VID_00329]
- [16:24:57] Reencoding video [VID_00329]
- [16:24:57] Keeping original video (no reencode)
- [16:24:57] Processing: VID_00307 (21 of 47)
- [16:24:57] Extracting A/V streams [VID_00307]
- [16:25:12] Reencoding video [VID_00307]
- [16:25:12] Keeping original video (no reencode)
- [16:25:12] Processing: VID_00330 (22 of 47)
- [16:25:12] Extracting A/V streams [VID_00330]
- [16:25:17] Reencoding video [VID_00330]
- [16:25:17] Keeping original video (no reencode)
- [16:25:17] Processing: VID_00308 (23 of 47)
- [16:25:17] Extracting A/V streams [VID_00308]
- [16:25:25] Reencoding video [VID_00308]
- [16:25:25] Keeping original video (no reencode)
- [16:25:25] Processing: VID_00331 (24 of 47)
- [16:25:25] Extracting A/V streams [VID_00331]
- [16:25:35] Reencoding video [VID_00331]
- [16:25:35] Keeping original video (no reencode)
- [16:25:35] Processing: VID_00309 (25 of 47)
- [16:25:35] Extracting A/V streams [VID_00309]
- [16:26:13] Reencoding video [VID_00309]
- [16:26:13] Keeping original video (no reencode)
- [16:26:13] Processing: VID_00341 (26 of 47)
- [16:26:13] Extracting A/V streams [VID_00341]
- [16:26:18] Reencoding video [VID_00341]
- [16:26:18] Keeping original video (no reencode)
- [16:26:18] Processing: VID_00310 (27 of 47)
- [16:26:18] Extracting A/V streams [VID_00310]
- [16:26:25] Reencoding video [VID_00310]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,583 frames
- [16:26:25] Reencoding: VID_00310, Pass 1 of 1
- [16:27:34] Video Encode complete
- [16:27:34] Processing: VID_00332 (28 of 47)
- [16:27:34] Extracting A/V streams [VID_00332]
- [16:27:42] Reencoding video [VID_00332]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,346 frames
- [16:27:42] Reencoding: VID_00332, Pass 1 of 1
- [16:30:00] Video Encode complete
- [16:30:00] Processing: VID_00311 (29 of 47)
- [16:30:00] Extracting A/V streams [VID_00311]
- [16:30:09] Reencoding video [VID_00311]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,882 frames
- [16:30:09] Reencoding: VID_00311, Pass 1 of 1
- [16:33:12] Video Encode complete
- [16:33:12] Processing: VID_00333 (30 of 47)
- [16:33:12] Extracting A/V streams [VID_00333]
- [16:33:20] Reencoding video [VID_00333]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,147 frames
- [16:33:20] Reencoding: VID_00333, Pass 1 of 1
- [16:35:43] Video Encode complete
- [16:35:43] Processing: VID_00312 (31 of 47)
- [16:35:43] Extracting A/V streams [VID_00312]
- [16:35:53] Reencoding video [VID_00312]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,184 frames
- [16:35:53] Reencoding: VID_00312, Pass 1 of 1
- [16:39:11] Video Encode complete
- [16:39:11] Processing: VID_00334 (32 of 47)
- [16:39:11] Extracting A/V streams [VID_00334]
- [16:39:16] Reencoding video [VID_00334]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 547 frames
- [16:39:16] Reencoding: VID_00334, Pass 1 of 1
- [16:39:51] Video Encode complete
- [16:39:51] Processing: VID_00313 (33 of 47)
- [16:39:51] Extracting A/V streams [VID_00313]
- [16:39:57] Reencoding video [VID_00313]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 939 frames
- [16:39:57] Reencoding: VID_00313, Pass 1 of 1
- [16:40:55] Video Encode complete
- [16:40:55] Processing: VID_00335 (34 of 47)
- [16:40:55] Extracting A/V streams [VID_00335]
- [16:41:02] Reencoding video [VID_00335]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,363 frames
- [16:41:02] Reencoding: VID_00335, Pass 1 of 1
- [16:42:46] Video Encode complete
- [16:42:46] Processing: VID_00314 (35 of 47)
- [16:42:46] Extracting A/V streams [VID_00314]
- [16:42:53] Reencoding video [VID_00314]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,776 frames
- [16:42:53] Reencoding: VID_00314, Pass 1 of 1
- [16:45:10] Video Encode complete
- [16:45:10] Processing: VID_00336 (36 of 47)
- [16:45:10] Extracting A/V streams [VID_00336]
- [16:45:17] Reencoding video [VID_00336]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,371 frames
- [16:45:17] Reencoding: VID_00336, Pass 1 of 1
- [16:47:06] Video Encode complete
- [16:47:06] Processing: VID_00315 (37 of 47)
- [16:47:06] Extracting A/V streams [VID_00315]
- [16:47:15] Reencoding video [VID_00315]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,705 frames
- [16:47:15] Reencoding: VID_00315, Pass 1 of 1
- [16:51:29] Video Encode complete
- [16:51:29] Processing: VID_00337 (38 of 47)
- [16:51:29] Extracting A/V streams [VID_00337]
- [16:51:34] Reencoding video [VID_00337]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 510 frames
- [16:51:34] Reencoding: VID_00337, Pass 1 of 1
- [16:52:26] Video Encode complete
- [16:52:26] Processing: VID_00316 (39 of 47)
- [16:52:26] Extracting A/V streams [VID_00316]
- [16:52:42] Reencoding video [VID_00316]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,054 frames
- [16:52:42] Reencoding: VID_00316, Pass 1 of 1
- [17:01:52] Video Encode complete
- [17:01:52] Processing: VID_00338 (40 of 47)
- [17:01:52] Extracting A/V streams [VID_00338]
- [17:02:13] Reencoding video [VID_00338]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,337 frames
- [17:02:13] Reencoding: VID_00338, Pass 1 of 1
- [17:09:58] Video Encode complete
- [17:09:58] Processing: VID_00317 (41 of 47)
- [17:09:58] Extracting A/V streams [VID_00317]
- [17:10:15] Reencoding video [VID_00317]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 7,058 frames
- [17:10:15] Reencoding: VID_00317, Pass 1 of 1
- [17:18:48] Video Encode complete
- [17:18:48] Processing: VID_00339 (42 of 47)
- [17:18:48] Extracting A/V streams [VID_00339]
- [17:18:58] Reencoding video [VID_00339]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,295 frames
- [17:18:58] Reencoding: VID_00339, Pass 1 of 1
- [17:20:52] Video Encode complete
- [17:20:52] Processing: VID_00318 (43 of 47)
- [17:20:52] Extracting A/V streams [VID_00318]
- [17:20:58] Reencoding video [VID_00318]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 583 frames
- [17:20:58] Reencoding: VID_00318, Pass 1 of 1
- [17:21:30] Video Encode complete
- [17:21:30] Processing: VID_00340 (44 of 47)
- [17:21:30] Extracting A/V streams [VID_00340]
- [17:21:35] Reencoding video [VID_00340]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 570 frames
- [17:21:35] Reencoding: VID_00340, Pass 1 of 1
- [17:22:06] Video Encode complete
- [17:22:06] Processing: VID_00319 (45 of 47)
- [17:22:06] Extracting A/V streams [VID_00319]
- [17:22:16] Reencoding video [VID_00319]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,804 frames
- [17:22:16] Reencoding: VID_00319, Pass 1 of 1
- [17:24:59] Video Encode complete
- [17:24:59] Processing: VID_00477 (46 of 47)
- [17:24:59] Extracting A/V streams [VID_00477]
- [17:25:12] Reencoding video [VID_00477]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,959 frames
- [17:25:12] Reencoding: VID_00477, Pass 1 of 1
- [17:28:26] Video Encode complete
- [17:28:26] Processing: VID_00342 (47 of 47)
- [17:28:26] Extracting A/V streams [VID_00342]
- [17:28:31] Reencoding video [VID_00342]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 659 frames
- [17:28:31] Reencoding: VID_00342, Pass 1 of 1
- [17:28:59] Video Encode complete
[17:28:59]PHASE ONE complete
[17:28:59]PHASE TWO - Rebuild Started
- [17:28:59] Building ALTERNATE OUTPUT Structure
[17:52:48] - Encode and Rebuild complete
[17:52:48] JOB: TOY_STORY_3_DISC_1 finished.


I selected Toy Story 3 after Paul without any changes made and clicked "Backup".

The video looks like it's all in sequence.

[AmigaFuture]

I found it! Disabled "Quicker" Encode for Extras and ran it again. This time, no reencode of video for Toy Story 3. It's rebuilding now.

[jdobbs]

I found it! Disabled "Quicker" Encode for Extras and ran it again. This time, no reencode of video for Toy Story 3. It's rebuilding now.I'll take a look at that.

[Capsbackup]

I aim to please... :)

And you are quite the marksman!! ;) :D
:thanks:

[AmigaFuture]

It's building with MKVMERGE now, so...it's complete. ;) If that were to fail...I'll update This message. Hence, don't expect it. Haha! Woo! Wicked Cool, JDobbs! I Knew my Desktop is doing well. Haha! That was fun, and a bit learned.

[dfsooner]

Just rebuilt Dredd with 44.09. Completed without error and output looks good. Subtitles work great too.

[sojourner353]

Hi all,

Is there a way to work on MKV sources directly in BDRB I have some I want to re-encode using alternate profiles?

BDRB does such a great job and what I do at the moment is rebuild the MKV into a BR structure using tsMuxer then feed it into BDRB to work on it that way but if BDRB could accept MKV source that would be great, thanks, have a good one.

[AmigaFuture]

@ sojourner353

Is there a way to work on MKV sources directly in BDRB I have some I want to re-encode using alternate profiles?


Are you unsure you want to?

Use BD-RB's import feature. File then Import.. In the Alternative Output, Put a Check on "Output BD or AVCHD Compliant Structure."

[sojourner353]

@ sojourner353



Are you unsure you want to?

Use BD-RB's import feature. File then Import.. In the Alternative Output, Put a Check on "Output BD or AVCHD Compliant Structure."

Thanks for that tried everything but click on the file menu, was using the browse function, cheers.

[Winenut]

First, per suggestion, I merely removed and reinstalled (using the existing versions I had). And that didn't work.

I tried that first, as your suggestion it was a problem with my system...and if were corruption, just reinstalling should (at least in theory) should have fixed it.

I then checked the current versions on your site. Of the three supporting applications, only AviSynth has not changed. Even though AviSynth was the exact (bit for bit) same version I had, I downloaded it along with the other two...and installed them. I then downloaded a fresh copy of BD Rebuilder 44.06 and unzipped that...effectively installing it. And just in case, gave it Admin Authority.

FFdshow is now at 1.2.4422.0
MatroskaSplitter is now at 1.4.92.1
AviSynth is still at 2.5.8.5

That worked for the AVC titles I was doing that day, but did not work for the VC-1 title...which I thought at the time might be bad.

Today I worked on a different AVC title, and like before...it failed.

[05/22/13] BD Rebuilder v0.44.06 (beta)
[13:47:41] Source: PARKER_00800
- Input BD size: 34.17 GB
- Approximate total content: [01:58:40.154]
- Target BD size: 4.36 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow [3-way]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[13:47:43] PHASE ONE, Encoding
- [13:47:43] Processing: VID_00800 (1 of 1)
- [13:47:43] Extracting A/V streams [VID_00800]
- [13:56:34] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 170,713 frames
- Bitrate: 4,027 Kbs
- [13:56:34] Reencoding: VID_00800, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.44.06 (beta)
- Windows Version: 6.1 [7600]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4422, 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
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[14:07:12] - Failed video encode, aborted

Note that this time I was re-encoding down to a BD5.

I'm the current (version 11) of DirectX, and as far as I know on the correct version of DirectShow. Since MS does not generally include updates (as fixes), but instead releases whole new versions. I couldn't find that any of the updates (that I've not applied) had anything to do with DirectX or DirectShow.

Now it's possible this disc is bad or involves something that makes it more difficult to handle. I don't know. Some work and some don't. And prior to installing 44.06, I never had any problems remotely like this. At least not related to the initial install of BD Rebuilder.

And lastly here's a copy of the INI file..

[Options]
VERSION=0.44.0.6
MODE=3
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=0
TARGET_SIZE=4469
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AVCHD=1
REMOVE_WORKFILES=1
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=1
COMPLETION_BEEP=1
DGDECNV=0
OUTPUT_3D=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24500
MULTIPROCESS=3
ENABLE_TEST=1
[Paths]
WORKING_PATH=E:\BD WORK\Z-TEMP\
SOURCE_PATH=K:\BD STAGE\PARKER\

Steve

[gonca]

@Winenut
What are you using, and what version, to decrypt the movie?

Try using the latest version of BD_RB

[AmigaFuture]

@ sojourner353

You're welcome. I'm glad to help.

@ Winenut

Looks like a possible bad rip. Are you using AnyDVD (HD)?

[jdobbs]

@Winenut

I'm ripping "PARKER" now to see if it might be a ripping issue. I'll let you know how it comes out.

Just as an observation, though, you're going to have a hard time getting decent quality by encoding using the fastest setting and ABR when you have a BD-5 selected for output.

[Edit] I'm currently running "PARKER" after ripping with AnyDVD 7.2.0.0 and it seems to be encoding fine. I'll post the log when it completes.

If your installation worked for a while and then stopped... there is a VERY GOOD CHANCE that some other software package is meddling with the settings of intercepting. Reinstall FFDSHOW again and re-run the job. If it works -- then something else is definitely screwing with your setup. If you have any "Codec Packs" installed -- remove them.

[Winenut]

It was done as a test...because it's faster to encode a BD5. And as you can see, all the tools are up to date and I was using 44.06.

In any case, switching back to 44.03, I had no problem. Encoded just fine. So it's not the disk.

Busy at work, so further testing and research will have to wait for the weekend. But I thought of something last night and I post this as soon as I do it. But I figure I'll save the LAST.CMD from the good encode and compare it with the LAST.CMD from the bad encode...to see if there a difference...as I'm expecting there will be.

Steve

[Winenut]

Here's the two LAST.CMD files...and they are appear identical.

Bad Encode...

"J:\SMB DATA\SMB2 Data\SMB Downloads\BD Rebuilder\BD_Rebuilder\tools\x264.exe" "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.3.AVS" --preset superfast --bluray-compat --b-pyramid none --weightp 1 --qpmin=0 --bitrate 4027 --level 4.0 --qpfile "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.3.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 13000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --output "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.AVS.3.264"

Good Encode...

"J:\SMB DATA\SMB2 Data\SMB Downloads\BD Rebuilder\BD_Rebuilder\tools\x264.exe" "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.3.AVS" --preset superfast --bluray-compat --b-pyramid none --weightp 1 --qpmin=0 --bitrate 4027 --level 4.0 --qpfile "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.3.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 13000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --output "E:\BD WORK\Z-TEMP\WORKFILES\VID_00800.AVS.3.264"

So since the 3rd party tools are the same, I though it might be X264. But they are same version between two releases.

Interestingly enough, I can take the failed encode...the WORKFILES and continue the encode with 44.03...and it works. So it's nothing to do with the work that precedes that point.

Steve

[jdobbs]

It was done as a test...because it's faster to encode a BD5. And as you can see, all the tools are up to date and I was using 44.06.

In any case, switching back to 44.03, I had no problem. Encoded just fine. So it's not the disk.

Busy at work, so further testing and research will have to wait for the weekend. But I thought of something last night and I post this as soon as I do it. But I figure I'll save the LAST.CMD from the good encode and compare it with the LAST.CMD from the bad encode...to see if there a difference...as I'm expecting there will be.

SteveWell... I had no problem either -- using v0.44.9:[05/23/13] BD Rebuilder v0.44.09 (beta)
[09:27:50] Source: PARKER_00800
- Input BD size: 34.17 GB
- Approximate total content: [01:58:40.154]
- Target BD size: 4.36 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow [3-way]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[09:27:52] PHASE ONE, Encoding
- [09:27:52] Processing: VID_00800 (1 of 1)
- [09:27:52] Extracting A/V streams [VID_00800]
- [09:37:13] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 170,713 frames
- Bitrate: 4,108 Kbs
- [09:37:13] Reencoding: VID_00800, Pass 1 of 1
- [10:13:46] Video Encode complete
- [10:13:46] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
[10:17:54]PHASE ONE complete
[10:17:54]PHASE TWO - Rebuild Started
- [10:17:54] Rebuilding AVCHD file Structure
[10:20:00] - Encode and Rebuild complete
[10:20:00] JOB: PARKER finished.

[jdobbs]

It was done as a test...because it's faster to encode a BD5. And as you can see, all the tools are up to date and I was using 44.06.

In any case, switching back to 44.03, I had no problem. Encoded just fine. So it's not the disk.

Busy at work, so further testing and research will have to wait for the weekend. But I thought of something last night and I post this as soon as I do it. But I figure I'll save the LAST.CMD from the good encode and compare it with the LAST.CMD from the bad encode...to see if there a difference...as I'm expecting there will be.

SteveTry moving the x264.exe from 44.03 to 44.06 and see if it completes.

Have you tried it with the latest release (v0.44.09)? There is a newer version of X264 in that one -- and there were a lot of fixes made in the last three minor releases.

[soneca]

Jdobbs, i do not usually use an alternative mode in mkv(MKV Container, 1920x1080p, 640Kbps DD5.1) but the second time(below) I get no subtitles, maybe I'm missing something.:confused:
Can check?

LABEL=MISTERIOS_DO_NILO
VERSION=v0.44.09 (beta)
SOURCE_SIZE=11256176640
SOURCE_VIDEO_SIZE=11256176640
TARGET_SIZE=4686086144
REDUCTION=.41631242062669
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=por;
BACKUP_MODE=1
MOVIEONLY_TYPE=10
USE_LAVF=0
INSTANCES=2
DGDECNV=-1
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=100
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4686086144
SPLITS=2
NSIZE=0
FLINK=0
MLINK=0

[jdobbs]

Jdobbs, i do not usually use an alternative mode in mkv(MKV Container, 1920x1080p, 640Kbps DD5.1) but the second time(below) I get no subtitles, maybe I'm missing something.:confused:Writing SUPs to MKV is not the default (although it will be on the next release). So, if you created the MKV with BD-RB it would not (by default) include the subtitles.

Look in HIDDENOPTS.TXT -- and add this hidden option:

MKV_MUXSUPS=1

If the subtitles exist in the MKV, BDRB will import them automatically.

[soneca]

Writing SUPs to MKV is not the default (although it will be on the next release).
Thanks!
Rarely use this option so I had not paid attention to the hidden option...:(
Glad that option is no longer hidden in the next version!;)
If the subtitles exist in the MKV, BDRB will import them automatically.
I've been doing some tests with mkv(sup embedded), and it has worked very well!!!

[omegaman7]

I've been doing some tests with mkv(sup embedded), and it has worked very well!!!

So have I. And it is good. Oddly, I swear I've outputted MKV with Sups embedded, without forcing any setting :S I could be mistaken.

[soneca]

May have activated configuration and forgotten that.:D

[omegaman7]

Nope, it's not activated. I probably am mistaken about it outputting with SUP. I greatly look forward to the auto embed feature. But the hidden option could due for now ;)

90% of the time (Lately), I output to AVCHD BD-9 movie only. The 'Great' movies though, I backup to BD-25.

[AmigaFuture]

I've been testing the Alternate Output (MKV) pretty extensively with AC3 because of recent events.. Thus far, I'm very pleased. Most of my Blu-ray originals I've used the 25GB Backup with. For when Friends and Family come over. Massive thumbs Up to Digistor for their quality BD25 disks (or Euro...disc), too! However, (Huuuuge) thanks to JDobbs and recent events, I've been able to make backups for my TV and LG player via USB. My originals are even now ..more... closely protected than before...as well as "Here, connect this Hard Drive.." I'll never replace the portable HDD, for my disks (discs), and thanks to the JDobbs, BD-RB fits many desires. Everyone should donate...it's Brilliant software by a passionate programmer!

Another note, once I moved OUTPUT_FOLDER from being after [Paths] in the config............Whooo!! Very nice option. I haven't really tried it until tonight. Good speed difference to a completely different partition as I knew!!


JDobbs... Watch "Paul" (or don't)..No Matter --> Thanks............Man!!

[omegaman7]

Mmmm, I have some digistor BD-25 discs. They seem agreeable.
It's a CMCMAG-BA5 dye.

[Yannes]

A few days back I did a batch queue of 3 blu-rays to BD25 format (I use custom size: 24000 for that), it turned out that the first blu-ray was perfect in size like usual, but the 2 other blu-rays turned out to be about 25.500.00.000 in size, about a GB larger than I indicated. After changing the output setting to the default BD25 mode, this problem still occurred, the size didn't even change. I checked the .inf files for the settings and it looks just like previous BD25 back-ups I did. This problem occurred with version 0.44.04 as well as 0.44.09.

The source blu-ray was a stripped criterion blu-ray with only two 400MB menu files and 1 video .m2ts of about 33GB. The output size is always between 24.000.000.000 and 24.500.000.000 just like I want it to be. The output size in this case was 25,556,638,909 bytes.

[Status]
LABEL=
VERSION=v0.44.09 (beta)
SOURCE_SIZE=36859881741
SOURCE_VIDEO_SIZE=36016257024
TARGET_SIZE=25165824000
REDUCTION=.675311686797229
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00274]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24322199283
RATE=22904
SPLITS=1
NSTART=27000000
NEND=362947275
NSIZE=24713017344
FLINK=0
MLINK=0


[05/23/13] BD Rebuilder v0.44.09 (beta)
[10:32:28] Source:
- Input BD size: 34.33 GB
- Approximate total content: [02:07:52.289]
- Target BD size: 23.44 GB
- Windows Version: 5.1 [2600]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[10:32:28] PHASE ONE, Encoding
- [10:32:28] Processing: VID_00274 (1 of 1)
- [10:32:28] Extracting A/V streams [VID_00274]
- [10:49:31] Reencoding video [VID_00274]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 178,993 frames
- Bitrate: 22,904 Kbs
- [10:49:32] Reencoding: VID_00274, Pass 1 of 2
- [12:45:40] Reencoding: VID_00274, Pass 2 of 2
- [21:15:04] Video Encode complete
- [21:15:06] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:15:06] Multiplexing M2TS
[21:23:13]PHASE ONE complete
[21:23:13]PHASE TWO - Rebuild Started
- [21:23:13] Rebuilding BD file Structure
[21:23:26] - Encode and Rebuild complete
- WORKFILES folder removed.
[21:23:27] JOB: finished.


This was the result:

http://img402.imageshack.us/img402/35/resultl.png

My settings:

http://img254.imageshack.us/img254/384/settingsrt.png

I use the LAVF decoding method because that is apparently the only one that works on Linux.

Config file:

[Options]
VERSION=0.44.0.9
MODE=0
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
OUTPUT_3D=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24000
TARGET_SIZE=24000
[Paths]
SOURCE_PATH=Y:\
WORKING_PATH=Y:\WORKING\


.inf file of a previous backup that did succeed:

[Status]
LABEL=AMELIE
VERSION=v0.43.04 (beta)
SOURCE_SIZE=37716099931
SOURCE_VIDEO_SIZE=37246629888
TARGET_SIZE=25165824000
REDUCTION=.663049355908482
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00800]
AUDIO=11
PGS=111
APULLDOWN=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24696353957
RATE=21074
SPLITS=1
NSTART=27000000
NEND=356496480
NSIZE=23924809728
FLINK=0
MLINK=0

[jdobbs]

A few days back I did a batch queue of 3 blu-rays to BD25 format (I use custom size: 24000 for that), it turned out that the first blu-ray was perfect in size like usual, but the 2 other blu-rays turned out to be about 25.500.00.000 in size, about a GB larger than I indicated. After changing the output setting to the default BD25 mode, this problem still occurred, the size didn't even change. I checked the .inf files for the settings and it looks just like previous BD25 back-ups I did. This problem occurred with version 0.44.04 as well as 0.44.09. That setting is measured in megabytes. One megabyte is 1048576 bytes. 24000 * 1048576 = 25,165,824,000. The 1% difference is simply rounding due to encoding and muxing accuracy.

What can I say? If you tell BD-RB to output to a size that won't fit on a BD -- you'll get a size that won't fit on a BD. I'd suggest you use the default BD-25 setting.

[RobertM]

(I use custom size: 24000 for that), it turned out that the first blu-ray was perfect in size like usual, but the 2 other blu-rays turned out to be about 25.500.00.000 in size

24000 MB will certainly fit within the capacity of a 25GB BD-R. The problem is that true final size won't be known until the encode has been completed. The bit-size of each frame of film will vary depending upon the content, and BD-RB cannot predict that with 100% accuracy ahead of time. So your 24000 setting is just a target, and BD-RB tries to hit it as best it can.

If you do as JDobbs suggests, and use the default setting (23500 MB), then there will be a little more elbow room for an undersized estimate to still fit on a BD-25 disc.

I use a custom setting of 24200 MB and this almost always gives a burn size of 98% according to ImgBurn. I always use good quality media, so that edge problems (burning close to the max capacity of the disc) should be minimized. I've never detected a problem. I do occasionally get an over-sized rebuild, of course, but probably less than 10% of the time. I just reduce the target and run the process again for that title.

Hope this helps.

[Capsbackup]

I always use good quality media, so that edge problems (burning close to the max capacity of the disc) should be minimized. I've never detected a problem.

Maybe not a problem right away from the initial burn/verify, but after playing the disc a few times, in and out of the disc tray and case, touching with our fingers, etc... makes the disc more susceptible to premature failure. :(

[jdobbs]

Maybe not a problem right away from the initial burn/verify, but after playing the disc a few times, in and out of the disc tray and case, touching with our fingers, etc... makes the disc more susceptible to premature failure. :(Agreed. I would never trust the outer edges -- even on the most expensive high-quality disc. Is it really worth losing your valuable data to get that last 1% of the disc (which will not noticably affect quality)?
24000 MB will certainly fit within the capacity of a 25GB BD-R
If it fits it is pure luck because of undersizing. A BD+R will hold 25,025,314,816 bytes. So I would never recommend a setting of 24000 - as if it sized perfectly it would be 25,165,824,000 and would not fit.

[omegaman7]

I've had Taiyo Yuden discs age at the outer edge. Thankfully, the credits ended up at the edge of the disc ;) I don't even mind undersizing by 1Gb. The difference is negligible, in my opinion. Though I have ran into a few discs, where some material could benefit from that 1Gb, if prioritizing bitrate were possible. Not really hinting here, just an observation.

Though one defect, can compromise a complete backup ;) I no longer use those Disc booklets. Notorious for scratching discs over time. I prefer envelopes, and hard drive backups now.

[RobertM]

If it fits it is pure luck because of undersizing. A BD+R will hold 25,025,314,816 bytes. So I would never recommend a setting of 24000 - as if it sized perfectly it would be 25,165,824,000 and would not fit.

I can't argue with your math: it's spot on.

But...

BD-RB under-sizes my re-encodes all the time. With the default settings I was regularly getting disc image sizes of 94% to 96% (and one 92% IIRC), which I thought was a bit small. Since I switched to 24200 MB (23.63 GB) I regularly get 98%. In fact, for the last 10 rebuilds which required re-encoding none were oversized and none were over 98.5%. Here's the list:


Image size Disc fill %
24,633,278,464 98.4%
24,632,688,640 98.4%
24,549,098,440 98.1%
24,640,028,672 98.5%
24,624,824,320 98.4%
24,629,018,624 98.4%
24,472,190,976 97.8%
24,626,135,040 98.4%
24,639,075,496 98.5%
24,603,376,672 98.3%



By way of comparison, I ran a couple of encodes recently after d/l the latest version of BD-RB, and I forgot to set my custom size, so the target was the default of 22.95 GB. Here's what I got:


Image size Disc fill %
23,923,326,976 95.6%
23,883,546,624 95.4%


I do get the occasional over-size, and anything that comes in at >99% I re-run with default settings.

All I'm saying is if you use a custom setting of 24000 MB in BD-RB it will fit virtually all the time. This isn't the right thing for everybody, but I feel it works well for me.

And it's not a bug anyway, so I won't belabour the point any more.

And I should say that ALL of my backups are High-Quality, 2-pass, Movie-Only. So it's possible that my results might not apply when doing a Full-Backup, for instance.

[jdobbs]

Yep. Too each his/her own. The undersizing is purposeful. Whenever there is variability (especially in estimating muxing overhead, and it is truly an educated guess) I always make sure to err on the side of caution. People get mean when they spend a few hours encoding only to have the output not fit on their target (even when they use a custom size and cause the oversize themselves ;)).

[jdobbs]

I've had Taiyo Yuden discs age at the outer edge. Thankfully, the credits ended up at the edge of the disc ;) I don't even mind undersizing by 1Gb. The difference is negligible, in my opinion. Though I have ran into a few discs, where some material could benefit from that 1Gb, if prioritizing bitrate were possible. Not really hinting here, just an observation.

Though one defect, can compromise a complete backup ;) I no longer use those Disc booklets. Notorious for scratching discs over time. I prefer envelopes, and hard drive backups now. The ones that really tick me off are the dual-layer backups that start screwing up right in the middle of the movie (at the layer change). These days, though, you can get inexpensive BD-25's for about a nickle more than a Dual Layer DVD+R blank, so I only see it on the occasional test backup.

[omegaman7]

Yeah, I haven't used a Dual layer dvd since I got my first BD burner :D The BD-9 size, just seems to be agreeable. I plan to play around more though, in an attempt to save hard drive space. I have seen Excellent results under 3Gb. Typically the CGI movies.

[soneca]

The ones that really tick me off are the dual-layer backups that start screwing up right in the middle of the movie (at the layer change). These days, though, you can get inexpensive BD-25's for about a nickle more than a Dual Layer DVD+R blank, so I only see it on the occasional test backup.

I agree, it is difficult to get reliable medias, I have had many problems and 95% of them just at the point of changing layers.
Here, "the country of high taxes", this type of media is still a bit expensive.:mad:

[Yannes]

That setting is measured in megabytes. One megabyte is 1048576 bytes. 24000 * 1048576 = 25,165,824,000. The 1% difference is simply rounding due to encoding and muxing accuracy.

What can I say? If you tell BD-RB to output to a size that won't fit on a BD -- you'll get a size that won't fit on a BD. I'd suggest you use the default BD-25 setting.

The thing is that i've used 24000MB a few dozen times before and the output size was always between 24 and 24.5m bytes. And if you read my post you'd see that I did use the BD25 mode and the result was the same as the custom 24000 size, the movie file turned out to be a GB too large for no apparent reason.

There is bug somewhere in there, there is no denying that. The same problem occurred with another blu-ray I tried to shrink down as well, which had an end result of 25.5m bytes.

But sure, i'll do it again with BD25 mode and give some more in-depth details.