BD Rebuilder Beta - Bug Reports Only

[B737Driver]

For the notebook: if you only have the intel graphics and not some other discreet graphics card it should be pretty much automatic in being able to use the integrated graphics (ie, Quick Sync). I would suggest going to the intel drivers center and running their program that checks your system and tells you which drivers need updating. Their latest driver should work fine.

It gets more tricky if you have another discreet graphics card in your system as many of us do. I do know if you have and NVidia discreet card in your laptop (Nvidia Optimus setup), their drivers allow you to select a program and specify which graphics it runs with. (it's in the 3D settings)--their website has instructions.

On my desktop system with Win7 x64 I was running Lucid Virtu; this resident software allows you to choose an executable and specify it to run on integrated or discreet graphics. On my rig I set it to run bdrb.exe, frimencode.exe, and frimedecode.exe to run on integrated graphics (the intel). As for the bdrb ini file, I always copied these 4 lines into the newest version:

FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
ENCODER_MENU=1
ENCODER=1

Further, I found that using the DirectShowSource for frame serving worked faster than any of the other selections in the settings dialog box, including the FRIMSource.

As worknstiff eluded to, there is a way to setup an extended display to force the computer into "recognizing" the integrated intel graphics. Then, a program that can utilize Quick Sync will recognize the intel graphics being available. That tutorial for this is at https://mirillis.com/en/products/tut..._desktops.html
This is apparently set up to work with Win7/8 as Win10 does not have display dialog boxes like this. The latest intel integrated graphics driver for Win10, though, does actively tell the system that quick sync is available, thus, I have been able to select it in Handbrake.

For me, for some reason, the current FRIM routines try to but can't pick up the integrated intel graphics to run...and they cough up the error.

BTW, these random questions to post are killing me!!

[jdobbs]

I would suggest going to the intel drivers center and running their program that checks your system and tells you which drivers need updating.

I went to the intel driver center -- I couldn't find anything like this.

[worknstiff]

It's called the Intel Driver Update Utility (https://downloadcenter.intel.com/dow...Update-Utility)

[jdobbs]

Originally Posted by worknstiff

It's called the Intel Driver Update Utility (https://downloadcenter.intel.com/dow...Update-Utility)

It tells me my system has a custom driver and I have to update from the manufacturer. Oh well.

[DoctorM]

I haven't updated my version of BD-RB in awhile. Did so today and I'm seeing different behavior.

I'm running Win7 x64. It LOOKS like the first pass is now encoded using x264-64's internal frame server, and then for the second pass switches to DirectShow/LAV Filter and x264-32.
Is that by design or do I have something messed up on my system?

I do not have any x64 filters/splitters installed (and I didn't see any linked to in the first post as recommended). I also see no options for enabling/disabling 64-bits so I'm surprised to see what the first pass is doing.

[jdobbs]

I don't see how that could happen, since the determination to use X264's internal frame-serving is the same for each pass. When internal frame-serving is used -- the 64 bit version will always be used on a 64 bit system.

Normally internal frame-serving is only used when selected -- but there are rare circumstances that might default to it when there is no overriding need for using an AVS.

Nothing in that decision tree has changed, however, in many, many versions.

Can you post the command line used in each of the passes?

[DoctorM]

I'm unable to reproduce the two passes using different frame servers and x264 versions today (and I couldn't stop it from doing it yesterday). Maybe I just needed to reboot.

In general though, I'm definitely confused. I've selected 'Use DirectshowSource for frame serving' in Setup, and in the past that involved LAV Filters having their icons pop up in the system tray and the 32-bit x264.exe running.

Now even though the log shows " - Decoding/Frame serving: DirectShow", the Config.ini shows "Encoder=0", it is using the internal LAVF demuxer and 64-bit x264.

"C:\Multimedia Tools\BD_Rebuilder\tools\x264-64.exe" "I:\THE GUNS OF NAVARONE\BDMV\STREAM\00000.m2ts" --preset slow --bluray-compat --ref 4 --b-adapt 1 --demuxer lavf
 --fps 24000/1001 --b-pyramid none --weightp 1 --qpmin=0 --bitrate 18021 --level 4.1 --qpfile "D:\TEMP\WORKFILES\VID_00000.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct 
--vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats 
"D:\TEMP\WORKFILES\00000.m2ts.264.stats" --pass 1 --output NUL

"C:\Multimedia Tools\BD_Rebuilder\tools\x264-64.exe" "I:\THE GUNS OF NAVARONE\BDMV\STREAM\00000.m2ts" --preset slow --bluray-compat --ref 4 --b-adapt 1 --demuxer lavf 
--fps 24000/1001 --b-pyramid none --weightp 1 --qpmin=0 --bitrate 18021 --level 4.1 --qpfile "D:\TEMP\WORKFILES\VID_00000.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct 
--vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats 
"D:\TEMP\WORKFILES\00000.m2ts.264.stats" --pass 2 --output "D:\TEMP\WORKFILES\00000.m2ts.264"

I don't know if the 64-bit version improves performance or not. I had the 32bit LAV Filters set to decode in hardware for whatever performance improvement that brought, but it appears to be disregarding the frame server I selected.

[worknstiff]

When I was experimenting with the FRIM_SW_DECODE switches yesterday I ended up not being able to use DirectShow for frame serving like I had been using and had to use x264/LAVF instead. It was on a VC1 source if that makes any difference.

[worknstiff]

Here's my settings:

Options]
VERSION=0.50.0.11
ENCODER=0
MODE=0
ENABLE_TEST=1
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=24350
PRIORITY_CLASS=2
AUDIO_TO_KEEP=eng;spa;
SUBS_TO_KEEP=eng;spa;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=0
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=1
SUPTITLE=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24350
PGSTOSRT=1
ENABLE_BLANKING=1
[Paths]
WORKING_PATH=G:\WORKING\
SOURCE_PATH=H:\THE_FAST_&_FURIOUS_4_BD\FAST_AND_FURIOUS\
NeroAACPath=C:\BLURAY_STUFF\BD_REBUILDER_STUFF\NeroAACCodec-1.5.1\win32\neroAacEnc.exe
SupTitlePath=C:\Program Files (x86)\AviSynth 2.5\plugins\SupTitle.dll


Here's the log:

10/11/15] BD Rebuilder v0.50.11
[14:41:51] Source: FAST_AND_FURIOUS
- Input BD size: 45.33 GB
- Approximate total content: [04:32:24.444]
- Target BD size: 23.78 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:41:51] PHASE ONE, Encoding
- [14:41:51] Processing: VID_00010 (1 of 36)
- [14:41:51] Extracting A/V streams [VID_00010]
- [14:49:59] Reencoding video [VID_00010]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 153,744 frames
- Bitrate: 11,138 Kbs
- [14:49:59] Reencoding: VID_00010, Pass 1 of 2
[14:54:46]PHASE ONE aborted by user request


As soon as encoding starts I get a H.264 (MPEG-4 AVC) encoder has stopped working error message.

[jdobbs]

Originally Posted by DoctorM

I'm unable to reproduce the two passes using different frame servers and x264 versions today (and I couldn't stop it from doing it yesterday). Maybe I just needed to reboot.

In general though, I'm definitely confused. I've selected 'Use DirectshowSource for frame serving' in Setup, and in the past that involved LAV Filters having their icons pop up in the system tray and the 32-bit x264.exe running.

Now even though the log shows " - Decoding/Frame serving: DirectShow", the Config.ini shows "Encoder=0", it is using the internal LAVF demuxer and 64-bit x264.

"C:\Multimedia Tools\BD_Rebuilder\tools\x264-64.exe" "I:\THE GUNS OF NAVARONE\BDMV\STREAM\00000.m2ts" --preset slow --bluray-compat --ref 4 --b-adapt 1 --demuxer lavf
 --fps 24000/1001 --b-pyramid none --weightp 1 --qpmin=0 --bitrate 18021 --level 4.1 --qpfile "D:\TEMP\WORKFILES\VID_00000.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct 
--vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats 
"D:\TEMP\WORKFILES\00000.m2ts.264.stats" --pass 1 --output NUL

"C:\Multimedia Tools\BD_Rebuilder\tools\x264-64.exe" "I:\THE GUNS OF NAVARONE\BDMV\STREAM\00000.m2ts" --preset slow --bluray-compat --ref 4 --b-adapt 1 --demuxer lavf 
--fps 24000/1001 --b-pyramid none --weightp 1 --qpmin=0 --bitrate 18021 --level 4.1 --qpfile "D:\TEMP\WORKFILES\VID_00000.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct 
--vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats 
"D:\TEMP\WORKFILES\00000.m2ts.264.stats" --pass 2 --output "D:\TEMP\WORKFILES\00000.m2ts.264"

I don't know if the 64-bit version improves performance or not. I had the 32bit LAV Filters set to decode in hardware for whatever performance improvement that brought, but it appears to be disregarding the frame server I selected.

That just means it is likely a multipart source, and since there was no resizing etc. that required an AVS involved, BD-RB chose to use X264's internal frame-serving (mainly for better frame accuracy). It's really not a big deal, since its using the same decoder as LAV.

[DoctorM]

The movie is split into three .M2TS files and I'm doing a movie-only encoding.
I started the re-encoding again and it used the x64 version until it got to part 3 then shifted to 32-bit x264 and LAV directshow filter.

I'm still not seeing it change encoders between passes though... now I'm starting to think I was just being crazy.
You're right, it is the same decoder, but apparently there is no hardware decoder available in it. Not a big deal I suppose, it's just something unexpected based on the settings.

[jdobbs]

That's because the last segment wouldn't have the ATCDelta flag set. Trust me, it's better this way.

[DoctorM]

Originally Posted by jdobbs

That's because the last segment wouldn't have the ATCDelta flag set. Trust me, it's better this way.

Trusted.

[dirty211]

I have noticed that when an MKV containing an Atmos audio stream is imported into BD Rebuilder the Atmos stream is not available when you go to encode or burn it. It seems that it defaults to the core or second audio stream. Not sure if this is a bug or just designed that way. I couldn't find any info on this in the thread so I thought Id share it here.

[Ch3vr0n]

BDRB is standard compliant, atmos is NOT part of the official BD standard. It's an extension/add-on to it. It's neither a bug nor designed that way. Jdobbs may choose to add support but that's up to him. It you want to keep the audio or an atmos track you will need to keep HD audio intact for that specific movie.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[dirty211]

Understood. I know that BDRB handles Atmos well when encoding a full disc encode thru standard bluray structure folder and the end result is a compressed bd25 with Atmos intact. I just noticed it wasn't available when importing MKV and trying to convert to BD folder structure. Jdobbs does a fantastic job with BDRB and I will continue to support whether he adds it or not.

[jdobbs]

Originally Posted by dirty211

Understood. I know that BDRB handles Atmos well when encoding a full disc encode thru standard bluray structure folder and the end result is a compressed bd25 with Atmos intact. I just noticed it wasn't available when importing MKV and trying to convert to BD folder structure. Jdobbs does a fantastic job with BDRB and I will continue to support whether he adds it or not.

The problem is, that since it isn't a part of the standard -- there is no documentation as to how you would actually activate it in movie-only BD backup.

[bjones]

Originally Posted by jdobbs

It tells me my system has a custom driver and I have to update from the manufacturer. Oh well.

jdobbs, you should still be able to use the Intel driver, the custom ones by the mfg aren't usually kept up to date once they've moved on to the next model.. and they just sometimes have some extra options but definitely not worth staying behind rev for.

I did have problems updating to the intel driver when it added in Win 10 support in the Spring and had to revert back to the last one that was built for win 7/8.1. It may be fixed in the latest one. I haven't checked.

your processor has a HD4400 in it so you should be able to use the same one I do for my HD4600 on Win7sp1x64 - its the win64_153619 file version for driver ver 4170

link -
https://downloadcenter.intel.com/dow...-7-8-8-1-64bit

BJ

[Starfiresg1]

I recently did a movie only encode with the option to resize to 1440x1080. The output has a wrong aspect ratio of 4:3 instead of 16:9. The source was 1920x1080 MPEG-4.

What I noticed was that it used the x64-Version of x264 even through I've it set to use DirectShow instead of x264's internal LAV.

I took a look at last_cmd while trying to find the problem:

"G:\Program Files (x86)\BD-Rebuilder\tools\x264-64.exe" "H:\BDMV\STREAM\00005.m2ts" --preset medium --bluray-compat 
--demuxer lavf --fps 24000/1001 --no-interlaced --video-filter resize:width=1440,height=1080,sar=1:1,method=bilinear 
--b-pyramid none --weightp 1 --qpmin=0 --bitrate 3463 --level 4.0 --qpfile "K:\BR-TEMP\WORKFILES\VID_00005.CHP" --sar 4:3 
--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 --stats "K:\BR-TEMP\WORKFILES\00005.m2ts.264.stats" --pass 1 --output NUL

I think the "sar=1:1" in the resize-filter takes precedence over the "--sar 4:3" in the command line here and causes the wrong AR in the final output?

Log:

[10.18.15] BD Rebuilder v0.50.11
[14:10:32] Source:  VAMPIRE_00002
  - Input BD size: 21,13 GB
  - Approximate total content: [01:58:28.100]
  - Target BD size: 4,36 GB
  - Windows Version: 6.2 [9200]
  - MOVIE-ONLY mode enabled
  - Resize: 1920 to 1440 enabled
  - Auto Quality: High Quality (Default), Two Pass
  - Decoding/Frame serving: DirectShow
  - Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[14:10:35] PHASE ONE, Encoding
 - [14:10:35] Processing: VID_00005 (1 of 2)
 - [14:10:35] Extracting A/V streams [VID_00005]
 - [14:14:43] Reencoding video [VID_00005]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 170.112 frames
   - Convert: 1440x1080, 23,976fps, 170.112 frames
   - Bitrate: 3.463 Kbs
 - [14:14:43] Reencoding: VID_00005, Pass 1 of 2
 - [14:39:51] Reencoding: VID_00005, Pass 2 of 2
 - [16:38:48] Video Encode complete
 - [16:38:48] Processing audio tracks
   - Track 4352 (deu): Reencoding audio to AC3...
   - Track 4353 (eng): Reencoding audio to AC3...
 - [16:47:32] Processing: VID_00015 (2 of 2)
 - [16:47:32] Extracting A/V streams [VID_00015]
 - [16:47:38] Reencoding video [VID_00015]
   - Source Video: MPEG-4 (AVC), 1920x1080
   - Rate/Length: 23,976fps, 312 frames
   - Convert: 1440x1080, 23,976fps, 312 frames
 - [16:47:38] Reencoding: VID_00015, Pass 1 of 1
 - [16:47:43] Video Encode complete
[16:47:43]PHASE ONE complete
[16:47:43]PHASE TWO - Rebuild Started
 - [16:47:43] Rebuilding AVCHD file Structure
[16:49:22] - Encode and Rebuild complete
[16:49:22] JOB: VAMPIRE finished.

Settings:

[Options]
VERSION=0.50.0.11
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
AUDIO_TO_KEEP=deu;eng;ger;
SUBS_TO_KEEP=deu;eng;ger;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=1
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=1
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=21500
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=1
TARGET_SIZE=4469
SHOW_ENCODER=0
MOVIEONLY_TYPE=0
ALTCRF=23
ALT_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_PLAY_THRESHOLD=15
MENU_BACKGROUND=G:\Program Files (x86)\BD-Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=40
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=1
IMPORT_KEEP_PLAYALL=0
PGSTOSRT=0
[Paths]
SOURCE_PATH=H:\
WORKING_PATH=K:\BR-TEMP\

[jdobbs]

I think the "sar=1:1" in the resize-filter takes precedence over the "--sar 4:3" in the command line here and causes the wrong AR in the final output?

If the source is 1920x1080, then the SAR in the resize should be correct. I'll have to look and see when/how the --sar 4:3 gets inserted, it's been a while since I looked at that code.