BD Rebuilder Beta - Bug Reports Only

[Lathe]

Originally Posted by Blurayhd

Thank You, always in Veryslow right?

Well, that is up to you... If you do not have to worry about playability or compliance, then sure if you wish to do that. But, if you want playability on certain devices, I think 'Medium' is as high as you can go, but you can add some higher x264 'Tweaks' if you want. Personally, although I don't have the Loosey Goosey approach as JD does ('Sure, MP3 is just fine, you can't hear the difference anyway...' J/K) and 'Fast' is sufficient, still, for me personally anything over 'Medium' with some higher 'Tweaks' is probably overkill.

But, if your software players will play the encode, then sure whatever you want to squeeze out of it...

[Lathe]

Originally Posted by Blurayhd

Hello, I so wish to know in Alternate movie what CRF number do you recomend to use? for amazing quality? what you use? thank you in advance

Oh, that's right... JD brings up a good point. I was thinking x264 because that is what I always use, but if you are using x265 or something else, than sorry I don't know about that.

[Blurayhd]

Originally Posted by Lathe

Well, that is up to you... If you do not have to worry about playability or compliance, then sure if you wish to do that. But, if you want playability on certain devices, I think 'Medium' is as high as you can go, but you can add some higher x264 'Tweaks' if you want. Personally, although I don't have the Loosey Goosey approach as JD does ('Sure, MP3 is just fine, you can't hear the difference anyway...' J/K) and 'Fast' is sufficient, still, for me personally anything over 'Medium' with some higher 'Tweaks' is probably overkill.

But, if your software players will play the encode, then sure whatever you want to squeeze out of it...

If I understand correctly, you mean that it depends on what you select, veryslow in this case, whether it plays on my TV or not? If that is the case, which one should I select for compatibility?

[jdobbs]

Originally Posted by Lathe

Well, that is up to you... If you do not have to worry about playability or compliance, then sure if you wish to do that. But, if you want playability on certain devices, I think 'Medium' is as high as you can go, but you can add some higher x264 'Tweaks' if you want. Personally, although I don't have the Loosey Goosey approach as JD does ('Sure, MP3 is just fine, you can't hear the difference anyway...' J/K) and 'Fast' is sufficient, still, for me personally anything over 'Medium' with some higher 'Tweaks' is probably overkill.

But, if your software players will play the encode, then sure whatever you want to squeeze out of it...

Loosey Goosey?

Sorry, but I just believe in math, science, and engineering.

[Lathe]

Originally Posted by jdobbs

Loosey Goosey?

Sorry, but I just believe in math, science, and engineering.

Sorry Boss, couldn't resist...

[Lathe]

Originally Posted by Blurayhd

If I understand correctly, you mean that it depends on what you select, veryslow in this case, whether it plays on my TV or not? If that is the case, which one should I select for compatibility?

No, no, not exactly, sorry...

If you are already using some kind of software player that plays whatever you already encode then you are fine. I was only referring to if you are going to use a Hardware player, like a Blu-ray player to play actual discs, then the settings have to be compliant. But, I kind of doubt you or many others are actually doing that.

So, if whatever you are using to play your encoded files plays them okay, then you can use the most severe settings you want But, like I was teasing about JD, he feels even with the standard 'Fast' setting, etc., is good enough due to the efficient x264 codec, which for most simple not-too-big stuff, that is perfectly fine.

Now, IF I am compressing say a Blu-ray that is fairly large AND it contains a lot of detailed visual information, then just for my neurotic peace of mind, I just set it to the BDRB setting of 'High' (default - which actually I believe is the standard x264 'Medium' setting) and then I'll throw in a few tweaks 'Just Because' like bumping up the Psychovisual a little, increasing the ME and SUBme settings a tad, adding Trellis 2, and a few little things like that that won't affect hardware playability, but you don't really need to mess with that.

For Blu-rays that are just a little bigger than a BD25 where you are only shrinking it a few Gigs, AND if the material isn't too demanding, I'll just leave it on 'Fast' 1 Pass, and use milder 'Tweaks', but that is just me...

I hope that helps!

[jdobbs]

Originally Posted by Lathe

No, no, not exactly, sorry...

Sigh... of course not. Typical...

By this:

('Sure, MP3 is just fine, you can't hear the difference anyway...' J/K)

I assume you mean my comments where I tell everyone that high definition audio is nonsense. Unfortunately it is, whether people want to believe it or not. The audio companies (who have signed on to selling it, and are making a mint doing so) performed their own extensive double blind tests that proved that 5.1 AC3 @ 640Kbs is indistinguishable to the human ear from the original source. High definition? The human ear can only hear from 20hz to 20Khz, which pretty much all standards support. So I wish someone would explain what makes it "high". You know what I've found? That the only thing you get from HD audio is a little more gain. They increase the volume so people think they hear more.

I just like to call a spade a spade, and HD audio is the modern equivalent of snake oil. But, just like magical medical wonders of the 1800s, facts mean nothing and people will continue to swear by it, and more importantly, spend their money on it. No sense trying to reason with them or give them sound advice.

Math, science, and engineering are the only truths. But, unfortunately, they have less and less influence in the modern world. Dark ages, anyone? Get used to the idea. It won't be the first time.

Getting off of my soapbox now...

[Blurayhd]

Originally Posted by Lathe

No, no, not exactly, sorry...

If you are already using some kind of software player that plays whatever you already encode then you are fine. I was only referring to if you are going to use a Hardware player, like a Blu-ray player to play actual discs, then the settings have to be compliant. But, I kind of doubt you or many others are actually doing that.

The idea is play the MKV movie in one pendrive put on a USB on my TV

[Lathe]

Originally Posted by Blurayhd

The idea is play the MKV movie in one pendrive put on a USB on my TV

There you go... So, if whatever you are doing plays properly you are set.

[spotswood]

Originally Posted by jdobbs

So I wish someone would explain what makes it "high". You know what I've found? That the only thing you get from HD audio is a little more gain. They increase the volume so people think they hear more. No sense trying to reason with them or give them sound advice...

I see what you did there...

[jdobbs]

Originally Posted by spotswood

I see what you did there...

Good eye.

[jdobbs]

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

- Added a "Encode after Import" option to 
  the FILE/IMPORT menu.  When checked BD-RB
  will automatically reencode the imported
  BD structure after importing it. Note:
  Clear the working folder before the import
  if you don't want BD-RB to pause and ask
  whether to clear it during the reencode.
- Fixed an issue in which X265 could fail to
  perform CRF prediction when set for output
  to UHD format.
- Added experimental code for support of AMD
  GPUs via VCEENCC.  Note that this s/w does
  not support an equivalent of CRF encoding
  (so it is disabled).  In order to test
  this new feature it must be enabled in the
  "[Options]" area of BDREBUILDER.INI by
  adding VCE_TEST=1.  If your GPU doesn't
  support B-Frames and you experience issues,
  they can be disabled by also including
  VCE_BFRAMES=0 in the "[Options]" area of
  BDREBUILDER.INI. You should also ensure you
  are using the most current video drivers. 
  A personal "thanks" to dietachi for initial
  testing of the VCE capability.
- Updated the included version of FFMPEG to
  v4.2.1.
- Other minor corrections and cosmetic fixes.

[jdobbs]

Just as a note, if anyone is using the latest version of BD Rebuilder for encoding with older gen AMD GPUs (around Polaris), it has been reported that b-frame usage might result in poor quality. If you experiencing this, you might want to add VCE_BFRAMES=0 to your BDREBUILDER.INI. B-Frames aren't required -- but they will typically make encoding more efficient.

[MajorEvent]

Just a little thing. The title on the first post still says 62.06 not 62.10

[jdobbs]

Originally Posted by MajorEvent

Just a little thing. The title on the first post still says 62.06 not 62.10

Whoops. Fixed. Thanks for the heads-up.

[dietachi]

@jdobbs

Reencoding of VC1 fails for Intel GPU, QSVEnc.

qsvencc.exe" --avhw  --fps 23.976 -i "I:\VIDEO\BTTF_BD\BDMV\STREAM\00300.m2ts" --codec h264 --quality fastest --qp-min 0 --icq 27 --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --no-b-adapt --gop-len 24 -o "H:\BD_REBUILDER_WORK\WORKFILES\VID_00300.AVS.264"

H:\BD_REBUILDER_WORK\WORKFILES\VID_00300.AVS.264
--------------------------------------------------------------------------------
avqsv: codec vc1(yuv420p) unable to decode by qsv.
failed to initialize file reader(s).


QSVEncC.exe finished with error!

According to Rigaya, the problem is that VC1 is not implemented as hardware decoding, as there have been issues in the past.
For the VC1 video, the decoding should be done via

--avsw

.

It is also not listed under the decode capabilities of the HW.

QSVEncC
Supports QSV(hw) decoding
MPEG2
H.264/AVC
HEVC
VP8
VP9
AV1
Supports various formats such as avs, vpy, y4m, and raw
Supports demux/muxing using libavformat
Supports decode using libavcodec

This is related to the issue here:
https://forum.doom9.org/showthread.p...30#post2005030

Hello everyone,

First time poster here, so I hope it’s okay to ask this right here.

I’m testing the newly available Decoding/Frame serving: QSVENCC option in BD Rebuilder v0.62.06 with my Intel Iris Plus Graphics GPU on my Intel Core i7 – 1065G7 system. It works really well and super-fast at reencoding MPEG-4 (AVC), 1920x1080 HD video source, but fails when encountering VC-1, 1920x1080 HD video source. It also fails when encountering MPEG-4 (AVC), 720x480 SD video source within the BD structure. Needless to say, the reencoding works fine for all SD or HD video sources when using Decoding/Frame serving: DirectShow.

I’m thinking there’s probably a setting(s) that needs to be changed so that Intel QuickSync can work properly on my system when using BD Rebuilder.

Thank you.

[dietachi]

@jdobbs

Additionally, regarding the 480i issue in the same issue here:

I’m testing the newly available Decoding/Frame serving: QSVENCC option in BD Rebuilder v0.62.06 with my Intel Iris Plus Graphics GPU on my Intel Core i7 – 1065G7 system. It works really well and super-fast at reencoding MPEG-4 (AVC), 1920x1080 HD video source, but fails when encountering VC-1, 1920x1080 HD video source. It also fails when encountering MPEG-4 (AVC), 720x480 SD video source within the BD structure. Needless to say, the reencoding works fine for all SD or HD video sources when using Decoding/Frame serving: DirectShow.

"D:\BdRebuilder\tools\qsvenc\qsvencc.exe" --avhw  --fps 29.97 --interlace tff --vpp-deinterlace adaptive -i "I:\VIDEO\BTTF_BD\BDMV\STREAM\00314.m2ts" --codec h264 --quality fastest --qp-min 0 --icq 18 --sar 40:33 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --no-b-adapt --gop-len 30 -o "H:\BD_REBUILDER_WORK\WORKFILES\VID_00314.AVS.264"
Error: Invalid value "adaptive" for "--vpp-deinterlace"
QSVEncC.exe finished with error!

According to the listed options,

adaptive

is unavailable in QSVEnc.

--vpp-deinterlace <string>
Activate GPU deinterlacer.

parameters
none ... no deinterlace (default)
normal ... standard 60i → 30p interleave cancellation.
it ... inverse telecine
bob ... 60i → 60p interleaved.

The encoding proceeds if I replace it with any of the other available options.

Thank you.

[jdobbs]

@dietachi

Thanks for the in-depth reporting. I'll correct for another release.

Have you tried replacing "--avhw" with "--avsw" in the command line to see if VC1 decoding works?

[dietachi]

Originally Posted by jdobbs

@dietachi

Have you tried replacing "--avhw" with "--avsw" in the command line to see if VC1 decoding works?

Yes, "--avsw" works.

[jdobbs]

Originally Posted by dietachi

Yes, "--avsw" works.

Thanks. I'm glad you mentioned those issues, I had it in on my bug list to look at them (from the previous post) - but forgot to actually do it.