BD Rebuilder Beta - Bug Reports Only

[geheim]

Originally Posted by MrVideo

I've never heard of anyone releasing a 2D disc with 3D extras. The case would have to indicate that 3D material exists.

Does the disc have a STREAMS/SSIF directory?

Yes it has a SSIF directory! On the disc there is a short movie extra which you can choose to play in 2D or 3D!

It's the only disc I know where a 2D movie has 3D extras on it...

[MrVideo]

Wow, that is different.

[worknstiff]

@ MrVideo RE: Wow, that is different.

Maybe that's like the latest 4K releases where the only way to get the 3D is if you buy a 4K, lol. Wow, what will they try next to fleece more money from us?

[Ch3vr0n]

i've seen a couple like that too with 3D trailers or something on a 2D release

[MrVideo]

Originally Posted by worknstiff

Maybe that's like the latest 4K releases where the only way to get the 3D is if you buy a 4K, lol. Wow, what will they try next to fleece more money from us?

4K UHD 3D does not exist. Or do you mean a multipack release with 4K, 3D Blu-ray and DVD?

[jdobbs]

I have updated the first post of this thread with a link to the latest update to BD-RB (v0.50.18). Changes for this release:

- Added a new hidden option MENU_ITEMS_PAGE.
  It is used for identifying specific item
  counts for each menu page when importing 
  multiple sources.  It's particularly useful
  for creating discs comprised of multiple
  episodic seasons.  See HIDDENOPTS.TXT for 
  details.
- Added to the list of supported DIVX Codec 
  IDs supported during import of video files.
- Made changes to the import algorithm for
  import resizing (to meet standards). This
  should assure better retention of original
  aspect ratio in oddly formatted sources.
- Fixed an issue in which conversions from
  PAL to FILM during import was not making
  necessary timing corrections in subtitles.
- Added hidden option ALTERNATE_KEEP_SRT, it
  allows you to reintegrate extracted SRT
  files from an import when outputting to
  ALTERNATE formats (rather than the PGC
  that was created from the SRT during the
  import) See HIDDENOPTS.TXT for details.
- Made changes to prevent a rare XVID import
  problem that could result in audio that is 
  out of sync.
- Replaced the SPLIT.EXE tool which was
  mistakenly regressed in the last release. 
- Other minor corrections and cosmetic fixes.

[Ch3vr0n]

- Replaced the SPLIT.EXE tool which was mistakenly regressed in the last release.

curious if that one will fix my issue

[jdobbs]

Originally Posted by Ch3vr0n

- Replaced the SPLIT.EXE tool which was mistakenly regressed in the last release.

curious if that one will fix my issue

It just might. Someone reported that an AV program was flagging the one from v0.50.17. I tested it with a couple of AV packages, and it was a false positive. But he also reported that an earlier one worked. That made me wonder how it was possible since I haven't modified that program in years -- so I looked at it. It turns out the one included in v0.50.17 wasn't the correct one.

I'm not sure how it happened. I had a hard drive fail last month and had to restore some of the files to a new drive. Apparently the version of SPLIT.EXE must have been the wrong one. At least that's my best guess.

[Ch3vr0n]

i'll let you know. I'll remove it from the AV deep scan exclusion list to see what happens. Hey shit happens.

** edit ** @jdobbs SUCCES!! 4 way split active on "The Revenant" each process consuming about 20-25% of CPU @ 0.7-1.3MB/sec doing +-104-150fps

i did notice something strange GUI wise when it was doing the splitting itself. The progress bar should normally go from 0-100, well in my case it went something like 0-25-63-42-89-12-0-75-92... and after about 10-20 seconds or so bdrb didn't care that happened and started the 4-way conversion. I'll report later if the split is in sync. When it reached the splitting fase for the main title it went like 0-6-18-28-53-75-98-0-12-22-47... quite a few times but in the end chugged along nicely

below you'll find a link to a small avi file displaying the progress bar issue

https://drive.google.com/file/d/0B_k...ew?usp=sharing

Merging went fine too. Turning it into an iso with bdrb=>imgburn right now

----------------------
[08/18/16] BD Rebuilder v0.50.18
[20:06:10] Source:  THE_REVENANT
  - Input BD size: 42,70 GB
  - Approximate total content: [03:43:55.962]
  - Target BD size: 22,95 GB
  - Windows Version: 6.2 [9200]
  - Auto Quality: Good (Very Fast), ABR
  - Output folder: D:\Blu-ray\Rebuilds\BDRB\
  - Decoding/Frame serving: DirectShow [4-way]
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[20:06:10] PHASE ONE, Encoding
 - [20:06:10] Processing: VID_00191 (1 of 3)
 - [20:06:10] Extracting A/V streams [VID_00191]
 - [20:06:17] Reencoding video [VID_00191]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 1*432 frames
   - Bitrate: 9*694 Kbs
 - [20:06:17] Reencoding: VID_00191, Pass 1 of 1
 - [20:06:29] Video Encode complete
 - [20:06:29] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [20:06:29] Multiplexing M2TS
 - [20:06:34] Processing: VID_00200 (2 of 3)
 - [20:06:34] Extracting A/V streams [VID_00200]
 - [20:07:33] Reencoding video [VID_00200]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 63*408 frames
   - Bitrate: 7*452 Kbs
 - [20:07:33] Reencoding: VID_00200, Pass 1 of 1
 - [20:16:29] Video Encode complete
 - [20:16:29] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [20:16:29] Multiplexing M2TS
 - [20:17:11] Processing: VID_00800 (3 of 3)
 - [20:17:11] Extracting A/V streams [VID_00800]
 - [20:24:40] Reencoding video [VID_00800]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 224*928 frames
   - Bitrate: 11*500 Kbs
 - [20:24:40] Reencoding: VID_00800, Pass 1 of 1
 - [21:02:14] Video Encode complete
 - [21:02:14] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [21:02:14] Multiplexing M2TS
[21:11:08]PHASE ONE complete
[21:11:08]PHASE TWO - Rebuild Started
 - [21:11:08] Rebuilding BD file Structure
[21:16:05] - Encode and Rebuild complete
[21:16:05] Writing BD structure to ISO file
 - ImgBurn completed successfully
 - THE_REVENANT folder removed.
 - WORKFILES folder removed.
[21:23:44] JOB: THE_REVENANT finished.

Just over an hour to finish the encoding part itself to cut disc size in half and another 15min to rebuild the structure and create the ISO Not too bad Would have been a lot longer on my old system Oh and i'm wondering is there perhaps a chance you could increase the max number of instances to match the variable NUMBER_OF_PROCESSORS? As mentioned in a previous post the 6700k flags that as 8, and i'm curious what an 8-way split would do ^^

[soneca]

jdobbs, thanks!
Multi-process(3-way) running again via DirectShow.

[m.rup]

Hi, is there meanwhile a solution for the donation issue?

[Ch3vr0n]

The only really available method i could see is bitcoin or something.

[Ch3vr0n]

Hah, first 3D rebuild on this new rig just finished. Damn thing used almost every bit available on a BD50. 43.73GB > 22.95 => 3h15m. Old rig: 13+ hours, 25% or less of the time it would have taken on that one ^^

[jdobbs]

@Ch3vr0n

You should be able to test it by setting MULTIPROCESS=8.

[Ch3vr0n]

great. Just got a couple new discs to try it on. Test disc: Jungle Book ^^. I'll let you know. Oh and if you've seen the video file above (nothing visible but BDRB ), let me know. Then i'll pull it off gdrive, or you can edit the post and remove the link

** edit ** rebuild of that 3D disc didn't go too well. Succesful log, yet the ISO is only 15GB in size and the video locks up at chapter 12 while audio continues playing and so does the playtime counter (40+min left)

[08/19/16] BD Rebuilder v0.50.18
[20:24:05] Source:  BATMAN_V_SUPERMAN_DAWN_JUSTICE
  - Input BD size: 43,73 GB
  - Approximate total content: [02:38:47.851]
  - Target BD size: 22,95 GB
  - Windows Version: 6.2 [9200]
  - Quality: Good (Very Fast), ABR
  - Output folder: D:\Blu-ray\Rebuilds\BDRB\
  - MVC 3D Output Mode enabled
  - Decoding/Frame serving: FRIMDecode
  - Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[20:24:09] PHASE ONE, Encoding
 - [20:24:09] Processing: VID_00052 (1 of 2)
 - [20:24:09] Extracting A/V streams [VID_00052]
 - [20:35:37] Reencoding video [VID_00052]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 218*209 frames
   - Bitrate: 18*147 Kbs
   - Using FRIMEncoder for MVC encoding
 - [20:35:37] Reencoding: VID_00052, Pass 1 of 1
 - [23:13:59] Video Encode complete
 - [23:13:59] Processing audio tracks
   - Track 4352 (eng): Keeping original audio
 - [23:13:59] Multiplexing M2TS
 - [23:22:28] Scanning for 3D CLPI info...
 - [23:25:41] Processing: VID_00103 (2 of 2)
 - [23:25:41] Extracting A/V streams [VID_00103]
 - [23:25:49] Reencoding video [VID_00103]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 8*159 frames
   - Bitrate: 4*805 Kbs
   - Using FRIMEncoder for MVC encoding
 - [23:25:49] Reencoding: VID_00103, Pass 1 of 1
 - [23:30:16] Video Encode complete
 - [23:30:16] Processing audio tracks
 - [23:30:16] Multiplexing M2TS
 - [23:30:20] Scanning for 3D CLPI info...
[23:30:22]PHASE ONE complete
[23:30:22]PHASE TWO - Rebuild Started
 - [23:30:22] Converting SSIF file references
 - [23:30:55] Rebuilding BD-3D file Structure
[23:33:48] - Encode and Rebuild complete
[23:33:48] Writing BD structure to ISO file
 - ImgBurn completed successfully
 - BATMAN_V_SUPERMAN_DAWN_JUSTICE folder removed.
 - WORKFILES folder removed.
[23:40:59] JOB: BATMAN_V_SUPERMAN_DAWN_JUSTICE finished.

gonna try again later. First 8-way jungle book

[DoctorM]

Does MULTIPROCESS work on 3D content? The help page specifically says multiple instances of x264. Multiple instances of FRIM are launched as well? That should make a huge difference.

[Ch3vr0n]

not that i know off, or the log would have indicated x-Way. Anyway 8-way split: bad idea. encoding auto-aborts after about 10-15 seconds. auto-split (4-way), happily chugs along.

[jdobbs]

Originally Posted by Ch3vr0n

not that i know off, or the log would have indicated x-Way. Anyway 8-way split: bad idea. encoding auto-aborts after about 10-15 seconds. auto-split (4-way), happily chugs along.

Interesting. I can't imagine why. I've done it on my system... but it's slower than 4 way for me (I hit 100% processor utilization on all eight processors with MULTIPROCESS at 4).

Also, I can't test the file. I'm on the road with nothing but my iPad for a couple days.

[Ch3vr0n]

Oh i load all 8 cores too at 100% with auto-split. Though i'm not going to cry about 8-way manual split not working. The conversion times i have now compared to my old rig are like 4x less, i'm happy with that. About the file, no worries. Just send me a pm or tag me or something when you've had the chance to take a look. I'll leave it up until then.

[Lathe]

Originally Posted by jdobbs

Two pass is actually the reverse of CRF. In CRF you are setting a desired quality level -- and the bitrate is the result of the need to keep that level. In two pass you have a fixed bitrate (computed by the requirement to hit the output target size selected). In the first pass, the encoder is determining how to distribute that bitrate across all scenes/picture elements in order to get the best quality -- with the bitrate available. In the second pass it is applying what it learned to an actual encode.

BD-RB's prediction phase tries to perform a hybrid of the two. It encodes a subset of the scenes/picture elements in the source and tries to find what CRF will result in the required target size. It then encodes using that CRF. The price for that is accuracy. Two pass is always very, very close to the desired output size. Predicted CRF will often undersize or oversize by some small amount. Not much -- but not perfect.

You are right. It is an AVERAGE bitrate. The first pass (of a two pass encode) determines where it is necessary to use higher rates (difficult scenes) and where bitrate can be lowered (simpler scenes). There is also a specified maximum bitrate (set by the fastest transfer rate a BD disc's spin speed can accommodate, for example)

Hmmm, that's good that you explain that. It seems to me then, that the 2 pass, since it does NOT set a desired CRF rate to match the size, but I guess if I understand correctly, merely is concerned with what AVERAGE bit rate it takes to fill the desired size, then to me it seems quite clear that CRF would always be preferable then (if a precise size is not necessary) because if I understand right, CRF will always try to keep a constant 'perceived quality' no matter WHAT bit rate is needed within the Blu-ray limits of course.

Seems like CRF for backup is almost always the way to go then.

Thanks JD!