BD Rebuilder Beta - Bug Reports Only

[mparade]

When do you recommend using EXTENDED_GOP=1? Is it just to improve compression efficiency for BD-5/9 output at the cost of seeking precision?

Any help is appreciated.

[musiclover]

On the first page of this thread is given to ensure that Uncompressed audio is set to "All Supported" in ffdshow. In the readme in the bd_rebuilder archive however this step is omitted. Is this step still valid?

[AmigaFuture]

Ah, good to have the forum back.

MKV output from multiple files is functioning well here. I didn't realize it wasn't since with the previous version I hadn't really used that feature. I've tested with several movies, and...Nice! I think I found a different kind of bug.

When I edited Total Recall (Original not remake), and Iron Main 3 I edited both with BD-50 active with main machine. Noreencode happened except for audio.. As per normal. Then played both, and all looked/sounded good. Transfered them to my other machine for encoding in Batch BD25.
I checked them each, unchecking the extras I had kept before and making sure the (banked) were set the same as with my machine. I repeated this for the other movie. Later, I check to find with Iron Man 3 some Extras weren't kept, and for Total Recall
the same. Anyone else doing this and notice it? Using 0.46.05, Thanks.

[Sharc]

Originally Posted by mparade

When do you recommend using EXTENDED_GOP=1? Is it just to improve compression efficiency for BD-5/9 output at the cost of seeking precision?

Any help is appreciated.

Yes. Longer GOPs improve compression efficiency because there will be less I frames. On BD5/9 this makes sense, as high efficiency is most crucial for low bitrate encoding.

[pididdi]

I had pulsating dtc-blocks in bd-dvd output from a certain Bluray-source with BD-RBV04605, so i have taken a short 10 min. clip from the certain Bluray-source for a test-run and encoded it with v0.45.03 with the latest x264.exe from v0.46.05. the result was quite better, there were no dtc-blocks anywhere to find. Here is the avs-script i have used everytime.

LoadPlugin("C:\video\dgdecnv2045\DGDecodeNV.dll")
DGSource("C:\VIDEO\FILM\WORKFILES\VID_00001.DGI", fieldop=0)
BicubicResize(1440,1080)
ConvertToYV12().AssumeFPS(24000,1000)

Now i will encode the whole bluray-source with v0.45.03!

[jdobbs]

Originally Posted by pididdi

I had pulsating dtc-blocks in bd-dvd output from a certain Bluray-source with BD-RBV04605, so i have taken a short 10 min. clip from the certain Bluray-source for a test-run and encoded it with v0.45.03 with the latest x264.exe from v0.46.05. the result was quite better, there were no dtc-blocks anywhere to find. Here is the avs-script i have used everytime.

LoadPlugin("C:\video\dgdecnv2045\DGDecodeNV.dll")
DGSource("C:\VIDEO\FILM\WORKFILES\VID_00001.DGI", fieldop=0)
BicubicResize(1440,1080)
ConvertToYV12().AssumeFPS(24000,1000)

Now i will encode the whole bluray-source with v0.45.03!

I'm sorry, but I don't see how that is logically possible. The two versions should use identical settings in the encode.

The encode command line is stored in LASTCMD.TXT in the BD-RB folder. If you see a difference, please report it. The same version of X264, with the same source and the same command line cannot create different output. In fact I suspect they will have bit-for-bit identical .264 files.

[jdobbs]

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

- Added a new type of IMPORT function. BD-RB
  will now import video files in 3D side-by-
  side (SBS) format, and when reencoding the
  created pseudo source to BD-5/9/25/50 they 
  will be converted back to standard MVC for 
  3D playback in 3D-capable BD players.
- Corrected an error the could result in a
  failed encode when outputting to ALTERNATE
  formats from a 3D source without having the
  "Enable SBS 3D Movie-Only output" selected.
- Fixed a problem with some non-multipart 
  sources using multiprocessing settings that 
  could result in a "ERROR in attempt to mux 
  (MKVMERGE)" error when ALTERNATE output has
  been selected.
- Fixed an issue in which an ALTERNATE choice
  from a 3D source that has been selected for
  intact video output without SBS mode chosen
  might sometimes incorrectly reencode.
- Other minor corrections and cosmetic fixes.

[omegaman7]

Originally Posted by jdobbs

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

- Added a new type of IMPORT function. BD-RB
  will now import video files in 3D side-by-
  side (SBS) format, and when reencoding the
  created pseudo source to BD-5/9/25/50 they 
  will be converted back to standard MVC for 
  3D playback in 3D-capable BD players.
- Corrected an error the could result in a
  failed encode when outputting to ALTERNATE
  formats from a 3D source without having the
  "Enable SBS 3D Movie-Only output" selected.
- Fixed a problem with some non-multipart 
  sources using multiprocessing settings that 
  could result in a "ERROR in attempt to mux 
  (MKVMERGE)" error when ALTERNATE output has
  been selected.
- Fixed an issue in which an ALTERNATE choice
  from a 3D source that has been selected for
  intact video output without SBS mode chosen
  might sometimes incorrectly reencode.
- Other minor corrections and cosmetic fixes.

You're amazing JD! Donation when I get my return!

Here's a good question. When outputting to 3DBD(25/50), does it automatically create an .iso, or is user intervention required? We need to manually tell it to create the .iso?

[jdobbs]

Originally Posted by omegaman7

You're amazing JD! Donation when I get my return!

Here's a good question. When outputting to 3DBD(25/50), does it automatically create an .iso, or is user intervention required? We need to manually tell it to create the .iso?

It follows the same rules as backing up a 3D disc. By default it creates an ISO, but it can be changed with a hidden setting. I highly recommend ISO output, however, as currently (because of the way BD3D works) you will reduce quality when outputting to a folder.

[omegaman7]

Originally Posted by jdobbs

It follows the same rules as backing up a 3D disc. By default it creates an ISO, but it can be changed with a hidden setting. I highly recommend ISO output, however, as currently (because of the way BD3D works) you will reduce quality when outputting to a folder.

Very logical, as I thought. Thanks

[pididdi]

Originally Posted by pididdi

I had pulsating dtc-blocks in bd-dvd output from a certain Bluray-source with BD-RBV04605, so i have taken a short 10 min. clip from the certain Bluray-source for a test-run and encoded it with v0.45.03 with the latest x264.exe from v0.46.05. the result was quite better, there were no dtc-blocks anywhere to find. Here is the avs-script i have used everytime.

LoadPlugin("C:\video\dgdecnv2045\DGDecodeNV.dll")
DGSource("C:\VIDEO\FILM\WORKFILES\VID_00001.DGI", fieldop=0)
BicubicResize(1440,1080)
ConvertToYV12().AssumeFPS(24000,1000)

Now i will encode the whole bluray-source with v0.45.03!

here is the inf of the main-movie "odd thomas" in question (if this will help):

[Status]
LABEL=ODD_THOMAS
VERSION=v0.46.05 (beta)
SOURCE_SIZE=29937389568
SOURCE_VIDEO_SIZE=29937389568
TARGET_SIZE=4771020800
REDUCTION=.15936662711233
RESIZE_1080=0
RESIZE_1440=-1
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
SSIF_MODE=0
QUICK=0
ENCODE_STEP=3
[00003]
AUDIO=11
PGS=11
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=707924
SPLITS=1

i have used LAVF and DgdecoderNV - no change! and with older versions of bd-rebuilder i have the same problem. would it help to increase the target size?

oh man, i'm sorry for this! but i have to run some tests! the problem in question appeares by rebuilding the main movie. Now i have tried strict avchd option.

"C:\video\BD_Rebuilder\tools\x264.exe" "C:\VIDEO\FILM\WORKFILES\VID_00001.AVS" --preset medium --bluray-compat --b-pyramid none --weightp 1 --qpmin=0 --bitrate 4650 --level 4.0 --qpfile "C:\VIDEO\FILM\WORKFILES\VID_00001.CHP" --sar 4:3 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 13000 --keyint 48 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --stats "C:\VIDEO\FILM\WORKFILES\VID_00001.AVS.264.stats" --pass 2 --output "C:\VIDEO\FILM\WORKFILES\VID_00001.AVS.264"

i go to sleep now!

[jdobbs]

@pididdi

Please read my response to your first post.

[HWK]

Jdobbs, for SBS option. Does program accept full and half option or is it limited to one type.

[jdobbs]

Originally Posted by HWK

Jdobbs, for SBS option. Does program accept full and half option or is it limited to one type.

I'll have to look at it. I aimed at half-SBS at 1080 or less and didn't give much thought to full. If it doesn't work at full, I'll add it for the next release, it shouldn't be a big deal. The only other limitation is that it must be 23.976fps, as the output will be 1080p. I may add the ability to import 50/60fps at some point in the future for 720p backup, but I think those types of files will be pretty rare.

[HWK]

Originally Posted by jdobbs

I'll have to look at it. I aimed at half-SBS at 1080 or less and didn't give much thought to full. If it doesn't work at full, I'll add it for the next release, it shouldn't be a big deal. The only other limitation is that it must be 23.976fps, as the output will be 1080p. I may add the ability to import 50/60fps at some point in the future for 720p backup, but I think those types of files will be pretty rare.

Thinking about it I realize FRIM want full SBS with resolution 3840*1080, so the way I see is use avisynth resize filter to make correct size for half SBS.

Aldo did you notice or aware of frimsource.dll increase frame rate by 2.

[mparade]

Originally Posted by Sharc

Yes. Longer GOPs improve compression efficiency because there will be less I frames. On BD5/9 this makes sense, as high efficiency is most crucial for low bitrate encoding.

Thanks.

[jdobbs]

Originally Posted by HWK

Thinking about it I realize FRIM want full SBS with resolution 3840*1080, so the way I see is use avisynth resize filter to make correct size for half SBS.

Aldo did you notice or aware of frimsource.dll increase frame rate by 2.

Yes. I currently upsize to 3840x1080 via AVISYNTH when I feed it to FRIMEncode.

I'm not having any issues with output from frimsource() in my testing, so I don't think it has an impact.

[mparade]

Sorry for my neither bug nor 3D related questions....

From changes.txt: "any bitrate you use for secondaries is stolen directly from the primary video." If I used FIXED_CRF for primary video encoding would this statement be still remained? So, will the primary video's quality "suffer" some in this case as well?

Thank you for the help.

[jdobbs]

Originally Posted by mparade

Sorry for my neither bug nor 3D related questions....

From changes.txt: "any bitrate you use for secondaries is stolen directly from the primary video." If I used FIXED_CRF for primary video encoding would this statement be still remained? So, will the primary video's quality "suffer" some in this case as well?

Thank you for the help.

No... but the output size would be unpredictable. It may or may not be small enough to fit on your selected target.

[jdobbs]

Originally Posted by HWK

Jdobbs, for SBS option. Does program accept full and half option or is it limited to one type.

I had to make one small change to enable full SBS support. I'm doing a test now, and will post an update (assuming it works ok).