BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Thanks kindly, but I don't understand how that helps me utilize that function in any way. Those are the settings that have been giving me trouble to re-encode anyway (as I've mentioned exhaustively already, using a 1-pass CRF encode with DirectShow ALWAYS gives me an AnyDVD error regardless of source. Or, if I set it for FRIM frame server I THINK that will run)

But, that doesn't tell me how to use this new function though. HOW, do I use it or use it to tell me what the CRF will be at a certain size, etc...?You can't use FRIM with CRF when prediction is needed because FRIM doesn't support frame-accurate seeking.

[DoctorM]

You can import half or full SBS -- and it will create a 3DBD (after reencoding). You can also use ALTERNATE output to convert it to half SBS. Right now BD-RB only supports SBS, but I guess over-under wouldn't be that hard to add.

3840x4320?

I doubt it would be important enough to add if it doesn't already exist.

Yup, that resolution is insane. I don't know what they think anyone would play it on. It's not like there is such thing as 4k 3D as any sort of standard. Let alone at 60fps.

[Lathe]

You can't use FRIM with CRF when prediction is needed because FRIM doesn't support frame-accurate seeking.

Okidoke, thanks...

[KaraokeAmerica]

Right now BD-RB only supports SBS, but I guess over-under wouldn't be that hard to add.
For us folks with passive 3D where TAB is potentially better, that would be great!

[jdobbs]

For us folks with passive 3D where TAB is potentially better, that would be great!I can't imagine how it could be better or worse. It's pretty much exactly the same (at least for full resolution).

[gonca]

I can't imagine how it could be better or worse. It's pretty much exactly the same (at least for full resolution).

To paraphrase someone
Opinions are like ... Everybody has one
Better/worse is opinion

No offense meant to anyone

[jdobbs]

To paraphrase someone
Opinions are like ... Everybody has one
Better/worse is opinion

No offense meant to anyoneYou miss the point. There is no "opinion" involved. A 3840x1080 SBS picture will give you exactly the same quality as a 1920x2160 over-under picture.

[gonca]

I realize that, but some will feel that one is better than the other based on what light goes on their receiver
Much like which sounds better, DTS-HD, True HD or AC3 at 640
Like I said, no offense meant
Sorry for the OT

[DoctorM]

Maybe he is referring to half-SBS and half-OU? I don't see how that makes a difference though.

Some claim SBS is better, but you're still halving the total pixels either way. It just determines the direction of the artifacts.

[jdobbs]

Maybe he is referring to half-SBS and half-OU? I don't see how that makes a difference though.

Some claim SBS is better, but you're still halving the total pixels either way. It just determines the direction of the artifacts.Could be. For those who are encoding to a passive system that displays alternate lines (for each view), cutting the horizontal resolution via half-SBS might make it look worse (since it's also halving the vertical resolution in playback). I'm not positive that's what happens exactly, but that's what it looked like when I tested passive 3D in a store.

[soneca]

jdobbs, the import mode should not accept files with higher resolution than standard bluray?

https://s20.postimg.org/ybgvqjclp/BDREBUILDER.png

Edit: I think it's hard because BDRebuilder depends on the creation of pseudo structure, which is also non-standard. :o

[jdobbs]

jdobbs, the import mode should not accept files with higher resolution than standard bluray?

https://s20.postimg.org/ybgvqjclp/BDREBUILDER.pngNo. It currently doesn't. Is this a UHD source? That's something I need to update.

[soneca]

No. It currently doesn't. Is this a UHD source? That's something I need to update.

That's right, UHD source.

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=8
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 8mn 46s
Bit rate mode : Variable
Bit rate : 60.0 Mbps
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.241
Stream size : 3.68 GiB (100%)
Title : DJI.AVC
Language : English
Encoded date : UTC 2015-11-29 18:35:26
Tagged date : UTC 2015-11-29 18:35:26
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

[KaraokeAmerica]

Could be. For those who are encoding to a passive system that displays alternate lines (for each view), cutting the horizontal resolution via half-SBS might make it look worse (since it's also halving the vertical resolution in playback). I'm not positive that's what happens exactly, but that's what it looked like when I tested passive 3D in a store.

This is along the lines of what I have heard, although I admit I am not an engineer.

The format exists for a reason though. I don't think there was a coder out there sitting around thinking "what can I do to make my life more difficult while gaining nothing...."

.....;)

[jdobbs]

This is along the lines of what I have heard, although I admit I am not an engineer.

The format exists for a reason though. I don't think there was a coder out there sitting around thinking "what can I do to make my life more difficult while gaining nothing...."

.....;)But SBS is much more common, and as long as you stay with full-SBS there would be no loss. The only time you would use half-SBS for playback on a standalone player would be if you had created and were using an MKV or MP4 file and was forcing 3D during playback.

[gg72]

I have a question about the different decoding/frame serving options in the setup menu: With the option "FRIMSource" is for me (Intel i7-3770) the decoding is more quickly/powerful, than with the option "X264/LAVF" (70 FPS vs. 45 FPS; CPU usage 100% vs. 40%), but I'm not sure, is the Intel Quick Sync in my system enabled?

BD-Rebuilder v0.50.17
- Windows Version: 6.2 [9200]
- Working Path Free Space: 866,32GB
- AVISYNTH Version: 2.6.0.6, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok

Which decoding/frame serving option should I use?

[jdobbs]

If one is faster than the other -- use the faster one. It only effects decoding, and two properly decoded frames should be identical.

Something you can also try is DirectshowSource with LAV installed. Then go into the LAV Filters Video Configuration properties dialog and try each of the "Hardware Acceleration" options. You'll see that "Intel Quick-Sync" is one of the choices.

[gg72]

Something you can also try is DirectshowSource with LAV installed. Then go into the LAV Filters Video Configuration properties dialog and try each of the "Hardware Acceleration" options. You'll see that "Intel Quick-Sync" is one of the choices.

Thanks.
I tried, but somehow it did not work with DirectshowSource with LAV... I decode only 2D sources, so I think this is not a problem, when I stay with these 2 options:
- X264's internal LAVF
or
- FRIMSource

[Lathe]

Just a quick comment about how WILDLY different the file sizes are coming out for me in compressing Blu-rays at a CRF of 18. I was just REALLY surprised at the differences.

For example, I did 'LEPRECHAUN 3' (of all films) and the original movie file size was about 17 Gigs and only compressed to about 9 Gigs, which was larger than most of the ones I've done. Then, I did a newer Blu-ray with the movie file size about about 19 Gigs and it came out to 2.3 Gigs! WOW, what a difference. Granted the Leprechaun film has a lot of visuals and action and the other film is more sedate visually, but still...

So, if all my settings are the same and I am re-encoding using a CRF of 18, the 'perceived' quality should still be roughly about the same, right? Even with the extreme disparity in file sizes?

[ascottj]

I have made numerous encoding attempts on IP Man 3 Blu-ray, but the subtitles simply will not sync ... first time I have come across this issue. The subtitles are in sync when playing the AnyDVD HD rip. What elements should I address in BD-RD to attempt to correct the subtitle syncing?

[Lathe]

I have made numerous encoding attempts on IP Man 3 Blu-ray, but the subtitles simply will not sync ... first time I have come across this issue. The subtitles are in sync when playing the AnyDVD HD rip. What elements should I address in BD-RD to attempt to correct the subtitle syncing?

I don't know why the subs are off in BDRB, but any easy fix would be that you could use a free subtitle program like Subtitle Workshop or Subtitle Edit and if you can extract the subtitle track from your m2ts file and drop it in one of these, then simply adjust the delay / advance timing, save it, and remux it back in.

[DoctorM]

I have made numerous encoding attempts on IP Man 3 Blu-ray, but the subtitles simply will not sync ... first time I have come across this issue. The subtitles are in sync when playing the AnyDVD HD rip. What elements should I address in BD-RD to attempt to correct the subtitle syncing?

Ran into this problem with Underworld Awakening. Here's what I did: http://forum.doom9.org/showthread.php?p=1734647#post1734647

[KaraokeAmerica]

But SBS is much more common, and as long as you stay with full-SBS there would be no loss. The only time you would use half-SBS for playback on a standalone player would be if you had created and were using an MKV or MP4 file and was forcing 3D during playback.

"Standalone player"? Do you mean a physical disk player or standalone software player? I generally use Plex to serve my media. I create 3D, TAB MKV's for this purpose as a rule, but I am open to other options if they are superior.

[ascottj]

Thank you for the advice, Lathe and DoctorM. I will give your suggestions a try to find out which one I can actually grasp. :) The solution(s) have to be less frustrating than trying to keep up with the out-of-sync subtitles.

[DoctorM]

Thank you for the advice, Lathe and DoctorM. I will give your suggestions a try to find out which one I can actually grasp. :) The solution(s) have to be less frustrating than trying to keep up with the out-of-sync subtitles.

Good luck. I'm pretty sure it's a tsMuxeR bug, not BD Rebuilder.

[Lathe]

Good luck. I'm pretty sure it's a tsMuxeR bug, not BD Rebuilder.

Speaking of which... I'm not sure that TSMuxer will allow you to adjust the delay / advance of subtitles (you CAN adjust the advance / delay of audio) So, if you can, it will be SUPER easy because then you just drop the movie m2ts file that BDRB just created (in the BDMV folder / STREAM folder) into TSMuxer and highlight the subtitle and adjust the timing and then re-render the m2ts file (or BDMV folder if all you have is the movie) :)

[MrVideo]

"Standalone player"? Do you mean a physical disk player or standalone software player? I generally use Plex to serve my media. I create 3D, TAB MKV's for this purpose as a rule, but I am open to other options if they are superior.

Standalone player normally means a physical Blu-ray player, as it is standalone. No other hardware or software needed in order to play Blu-ray discs. Requiring a display of some sort, not included. :D

Software players are not standalone as they require other hardware/OS in order to be able to work.

[geheim]

Hi,
I've got a Problem with the Blu-ray Disc of "Maze Runner". BD Rebuilder always crashes while encoding 3D sources.

Here is the log:

----------------------
[08.15.16] BD Rebuilder v0.50.17
[19:15:09] Source: MAZE_RUNNER
- Input BD size: 42,02 GB
- Approximate total content: [04:30:29.794]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[19:15:11] PHASE ONE, Encoding
- [19:15:11] Processing: VID_00232 (33 of 41)
- [19:15:11] Reencoding video [VID_00232]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 11.780 frames
- Bitrate: 15.981 Kbs
- Using FRIMEncoder for MVC encoding
- [19:15:11] Reencoding: VID_00232, Pass 1 of 1
[19:16:12] - Failed video encode, aborted



And my ini file:


[Options]
MODE=0
TARGET_SIZE=23500
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=18000
PRIORITY_CLASS=0
ENCODE_QUALITY=2
QUICK_EXTRAS=0
VERSION=0.50.0.17
ONEPASS_ENCODING=0
AUTO_QUALITY=0
OPEN_GOP=0
DEINTERLACE=0
SD_TO_1080=0
CONVERT_WIDE=0
AC3_192=0
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
RESIZE_1440=0
RESIZE_720=0
IGNORE_3D=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
FRIMSOURCE=0
OVERRIDE_AVCHD_AUDIO_LIMIT=1
ENCODER=0
DECODER=2
SUPPRESS_FF_WARNING=1
OUTPUT_3D_ISO=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=1
AUDIO_DRC=0
PGSTOSRT=0


If anyone could help me figuring out what is going wrong, I'd really appreciate it!
Thanks!!

[jdobbs]

Just a quick comment about how WILDLY different the file sizes are coming out for me in compressing Blu-rays at a CRF of 18. I was just REALLY surprised at the differences.

For example, I did 'LEPRECHAUN 3' (of all films) and the original movie file size was about 17 Gigs and only compressed to about 9 Gigs, which was larger than most of the ones I've done. Then, I did a newer Blu-ray with the movie file size about about 19 Gigs and it came out to 2.3 Gigs! WOW, what a difference. Granted the Leprechaun film has a lot of visuals and action and the other film is more sedate visually, but still...

So, if all my settings are the same and I am re-encoding using a CRF of 18, the 'perceived' quality should still be roughly about the same, right? Even with the extreme disparity in file sizes?Yes they should be.

[DoctorM]

Since FRIM is inferior in speed and quality to X264, would it be possible for 3D sources to use x264 for encoding the AVC portion and FRIM for the MVC portion, or in fact encode the AVC with x264 while leaving the MVC untouched?

The latter sounds silly, but MVC seems to be fairly efficient already come in around a third of the bitrate, while using a more efficient encoder on the AVC portion would allow you to steal more space from that.

If AVC and MVC can be kept on separate .M2TS files I would THINK it might be possible, or are their data is too tightly integrated to allow this sort of thing?

[jdobbs]

Since FRIM is inferior in speed and quality to X264, would it be possible for 3D sources to use x264 for encoding the AVC portion and FRIM for the MVC portion, or in fact encode the AVC with x264 while leaving the MVC untouched?

The latter sounds silly, but MVC seems to be fairly efficient already come in around a third of the bitrate, while using a more efficient encoder on the AVC portion would allow you to steal more space from that.

If AVC and MVC can be kept on separate .M2TS files I would THINK it might be possible, or are their data is too tightly integrated to allow this sort of thing?The two are linked too closely. I don't see how it would be possible.

[DoctorM]

The two are linked too closely. I don't see how it would be possible.

Just a thought. Kind of surprised x264 never took on 3D.

[Sharc]

Just a thought. Kind of surprised x264 never took on 3D.

It did some time ago, but the mvc fork hasn't been followed up since.

[Lathe]

Yes they should be.

Amazing how that works!

I think that I read that when doing a 2 pass encode set for a certain size (say BD-25 for example) that basically x264 is analyzing and determining what CRF to use for the entire encode, right? So, it's the same as if you already KNEW the precise CRF to use in order to render that size, right?

So, when BDRB is set to do a 2 pass for a BD-25, is there any way to know what CRF value it ultimate chooses (or will choose) in order to create the resulting size? Seems like you told me recently that you somehow figured out that doing a full BD-25 encode of a film would use a CRF of 12.5. How did you determine that?

And conversely, when BDRB tells us this after extracting the A/V files:

- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 202,033 frames
- Bitrate: 19,277 Kbs

Does that mean that that will be the RESULTING AVERAGE bit rate after the encode, or what? Because if it is determining what CRF to use in the 2nd pass, then that number cannot be a CONSTANT bit rate for the resulting encode, right?

[Sharc]

@Lathe
How to find out the "ultimate" CRF for a given target size:
Run BDRB in 1-pass CRF prediction mode, i.e. remove the FIXED_CRF= in your .ini, and select 1-pass CRF encode and select a target size.
BDRB then runs a number of short CRF prediction steps (kind of trial and error learning) to find out the "final" CRF which will produce the target file size. This "final" CRF is then used in the subsequent 1-pass CRF encoding.
During the CRF prediction phase you will see in the log how CRF develops towards the "final" CRF.

[kufo]

[QUOTE=geheim;1777145]Hi,
I've got a Problem with the Blu-ray Disc of "Maze Runner". BD Rebuilder always crashes while encoding 3D sources.

First of all: Maze Runner isn´t a 3D source. You´ll have to set your settings correctly for encoding such sources.
Why do you use a custom size of 18000? It´s to big for DVD and to small for Blu-Ray:confused:
There many settings that make not really sense for me:sly:
On the other hand there are settings missing:(
Take a look on the HIDDENOPTS folder...
I did this film in Code B without issues.

[geheim]

First of all: Maze Runner isn´t a 3D source. You´ll have to set your settings correctly for encoding such sources.
Why do you use a custom size of 18000? It´s to big for DVD and to small for Blu-Ray:confused:
There many settings that make not really sense for me:sly:
On the other hand there are settings missing:(
Take a look on the HIDDENOPTS folder...
I did this film in Code B without issues.

Thanks for your answer @kufo!

Maze Runner has some extras on it that are in 3D! The main movie is not, that's right, but the extras are and I'd like to keep them in 3D for my BD25 backup. That's why FRIM is used for the backup process.

The custom size is wrong in deed, I'll change that, but as I did not use the custom size for Maze Runner this should have no influence on this issue...

What Settings are missing that could have any influence on 3D backups?? I did not find any...

Did you do a full backup on your disc (and keeping 3D extras in 3D) or a movie-only??

Thanks and I'd appreciate any further tips!!

[jdobbs]

Amazing how that works!

I think that I read that when doing a 2 pass encode set for a certain size (say BD-25 for example) that basically x264 is analyzing and determining what CRF to use for the entire encode, right? So, it's the same as if you already KNEW the precise CRF to use in order to render that size, right?

So, when BDRB is set to do a 2 pass for a BD-25, is there any way to know what CRF value it ultimate chooses (or will choose) in order to create the resulting size? Seems like you told me recently that you somehow figured out that doing a full BD-25 encode of a film would use a CRF of 12.5. How did you determine that?

And conversely, when BDRB tells us this after extracting the A/V files:

- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 202,033 frames
- Bitrate: 19,277 Kbs

Does that mean that that will be the RESULTING AVERAGE bit rate after the encode, or what? Because if it is determining what CRF to use in the 2nd pass, then that number cannot be a CONSTANT bit rate for the resulting encode, right?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)

[MrVideo]

Maze Runner has some extras on it that are in 3D!

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?

[DoctorM]

I personally let BD Rebuilder determine the CRF for my target disc size, and then strip more/less stuff (and adjust the encode speed) until I like the CRF #.
I then let BD RB do a 2-pass encoding.

I figure that gives me better quality than 1-pass, but an idea of the expected quality because of the calculated CRF number guides how I tweak things.

For example, today I'm encoding a BD that is a movie with no extras but 35gb.
I was able to determine that keeping the DTS HD MA audio track untouched the CRF would be 17.3.
That's more than enough. If I didn't do the CRF test first I would have unnecessarily stripped the lossless audio track.

[geheim]

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]

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]

- 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_kYcBALPkwEY01FXzF5aThwbmM/view?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 :D 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.