BD Rebuilder Beta - Bug Reports Only

[MrVideo]

I'm trying to convert an HEVC MKV file into an x264 archive file (AVC/AC3)
Please code wrap included text.

That said, I'm confused as to why you would want to convert a smaller video file into a larger video file. Is the wrapper for the new file going to be MKV? If not, what?

If it is going to be a MKV file, then don't use BDRB, instead use the standalone encoder. That is assuming you have a compatible nVidia or Intel GPU. The whole process will then be quick and easy.

[Lathe]

@Lathe
Try using LAV as frame server and disable your "tweaks" temporarily.

Will do, thanks!

I went ahead and used CleverFFMpeg which works great, but you don't have as much control over the parameters.

[Lathe]

Please code wrap included text.

That said, I'm confused as to why you would want to convert a smaller video file into a larger video file. Is the wrapper for the new file going to be MKV? If not, what?

If it is going to be a MKV file, then don't use BDRB, instead use the standalone encoder. That is assuming you have a compatible nVidia or Intel GPU. The whole process will then be quick and easy.

Yeah, sorry about that, I don't know how to 'code wrap', I know that's a nuisance, my apologies...

No, I don't want to create a larger file, but my OPPO will not play HEVC files, so since I archive everything to playable disc I need to convert to x264 with the correct parameters.

It's so funny how I can never tell how big a file is going to come out (unless I do a sample and extrapolate on that of course) But, sometimes I can take a full on UHD file at like 50+ Gigs and use a fairly high CRF value (high as in low) and I'll be surprised at how small the resulting playable Blu-ray is. Then, I can take a small file like this and use basically the same CRF, and the file goes from around 3 Gigs to like 15! :) But, at least I can do it, I just wish I could figure out why BDRB is not doing it.

[MrVideo]

Yeah, sorry about that, I don't know how to 'code wrap', I know that's a nuisance, my apologies...
It is easy. Here is an example.
Do a Reply w/ Quote to this posting and you will see how it is done.
No, I don't want to create a larger file, but my OPPO will not play HEVC files, so since I archive everything to playable disc I need to convert to x264 with the correct parameters.
I'm going to assume that you are creating BD-ROM discs containing MKV files. If not, you should be, as the Oppo will play those.

Use the standalone program that comes with the BDRB release to recode the H265 videos to H264. Of coursse the use of this program requires a compatible nVidia or Intel GPU. If so, you can select H.264 and the quality or bitrate. It is a one-stop shop for re-encoding videos.

If you don't have a compatible GPU, then I'm afraid that I can't be of help, as I do not use BDRB for any kind of archiving, other than building UHD discs w/ menus.

[Lathe]

It is easy. Here is an example.
Do a Reply w/ Quote to this posting and you will see how it is done.

I'm going to assume that you are creating BD-ROM discs containing MKV files. If not, you should be, as the Oppo will play those.

Use the standalone program that comes with the BDRB release to recode the H265 videos to H264. Of coursse the use of this program requires a compatible nVidia or Intel GPU. If so, you can select H.264 and the quality or bitrate. It is a one-stop shop for re-encoding videos.

If you don't have a compatible GPU, then I'm afraid that I can't be of help, as I do not use BDRB for any kind of archiving, other than building UHD discs w/ menus.

Thank you! :)

[Blurayhd]

Hello, I dont know what to do, I try encoding a movie and with procesor take almost 8 hours and with my nvidia take no more than 17 minutes, I ask because the final quality?

[jdobbs]

Hello, I dont know what to do, I try encoding a movie and with procesor take almost 8 hours and with my nvidia take no more than 17 minutes, I ask because the final quality?My experience has been that they are of equivalent quality at a given bitrate. I can't say for sure if that holds true when you are forced to use low bitrates, as I haven't tested that. But definitely when using constant quality encodes you see similar quality at similar output sizes.

[Blurayhd]

My experience has been that they are of equivalent quality at a given bitrate. I can't say for sure if that holds true when you are forced to use low bitrates, as I haven't tested that. But definitely when using constant quality encodes you see similar quality at similar output sizes.

And another thing is the size, I dont know what but with procesor the final size is few gb less than Nvidia

[MrVideo]

And another thing is the size, I dont know what but with procesor the final size is few gb less than Nvidia
If you have the software encode set for two-pass, that will help reduce the size.

[Lathe]

that will help reduce the size.

WHAT?!! Reduce the size...??!

I've always heard that size matters... https://lh3.googleusercontent.com/pw/AP1GczNuSHXicvIvdYEl-wb99oyNaE1gavkEGTT7HSnVqz5pGPEXLyXQvQ8LiOllw7D6hYjqX6y71aZ09-magBjY5mcW2zU5pSdDprOC1jGadqQHhzSQ_RRGV4lBT_9ydGbj80uWSk895V-CwIUn5x2BXCXrtg=w15-h15-s-no-gm?authuser=0

[gonca]

WHAT?!! Reduce the size...??!

I've always heard that size matters... https://lh3.googleusercontent.com/pw/AP1GczNuSHXicvIvdYEl-wb99oyNaE1gavkEGTT7HSnVqz5pGPEXLyXQvQ8LiOllw7D6hYjqX6y71aZ09-magBjY5mcW2zU5pSdDprOC1jGadqQHhzSQ_RRGV4lBT_9ydGbj80uWSk895V-CwIUn5x2BXCXrtg=w15-h15-s-no-gm?authuser=0

Well said, PEEWEE.

[Blurayhd]

If you have the software encode set for two-pass, that will help reduce the size.

Two pass but which biltrate to use? which one will I put?

[gonca]

Two pass but which biltrate to use? which one will I put?

Maybe use file size?

[coopervid]

From my experience rewritable discs do not play well on BD Players.
Did you try a one-time writable disc for comparison?

Generally most standalone player will only recognize BD-R 50. Some 66GB (2 layers) on BD-R XL but not 100GB. Only one player is known to read 100GB from BD-Rs or be it BD-RE.

[Intel Iris the Great]

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. Also, everything looks fine here:

[08/02/24] Checking System Settings
- BD-Rebuilder v0.62.06
- Windows Version: 6.2 [9200]
- Working Path Free Space: 857.07GB
- 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
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[08/02/24] Systems Settings Check complete

Hoping someone can help. Thanks in advance.

[jdobbs]

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. Also, everything looks fine here:

[08/02/24] Checking System Settings
- BD-Rebuilder v0.62.06
- Windows Version: 6.2 [9200]
- Working Path Free Space: 857.07GB
- 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
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[08/02/24] Systems Settings Check complete

Hoping someone can help. Thanks in advance.Hmm... Haven't tested that. I'll take a look at it.

[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

[Lathe]

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

Well, it's really personal choice, but for me if I am backing up say a normal Blu-ray (HD) if you have plenty of room and your main objective is not in shrinking it as small as it can go (like gonca does, for example...) then if you can get away with '16' that is pretty much transparent. If that is producing a file size too big for what you want (you can always run the encode and about 10% the way through check the 'Properties' of the resulting file in the 'Workfiles' to project roughly the final size) then '18' should be perfectly fine.

But, if you need smaller file sizes then many use 20-22 or so. Personally, I wouldn't go higher than that.

I hope that helps!

[Blurayhd]

Well, it's really personal choice, but for me if I am backing up say a normal Blu-ray (HD) if you have plenty of room and your main objective is not in shrinking it as small as it can go (like gonca does, for example...) then if you can get away with '16' that is pretty much transparent. If that is producing a file size too big for what you want (you can always run the encode and about 10% the way through check the 'Properties' of the resulting file in the 'Workfiles' to project roughly the final size) then '18' should be perfectly fine.

But, if you need smaller file sizes then many use 20-22 or so. Personally, I wouldn't go higher than that.

I hope that helps!

Thank You, always in Veryslow right?

[jdobbs]

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 advanceIt changes depending upon which encoder you are using (x264, x265, NVIDIA, INTEL). The same number delivers different quality for each.

[Lathe]

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...' :rolleyes: 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]

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]

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...' :rolleyes: 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]

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...' :rolleyes: 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]

Loosey Goosey?

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

:D

Sorry Boss, couldn't resist...

[Lathe]

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]

No, no, not exactly, sorry...Sigh... of course not. Typical...

By this:
('Sure, MP3 is just fine, you can't hear the difference anyway...' :rolleyes: 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]

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]

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]

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... :D

[jdobbs]

I see what you did there... :DGood 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]

Just a little thing. The title on the first post still says 62.06 not 62.10Whoops. 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.php?p=2005030#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]

@dietachi

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

Yes, "--avsw" works.

[jdobbs]

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.

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.62.11). Changes for this release:- Corrected an issue in which encoding can
fail while using the QSVENC (Intel) GPU
encoder if encoding 720x480 interlaced
sources and deinterlacing is enabled.
- Fixed an error in which VC-1 sources were
failing to encode while using the QSVENC
(Intel) GPU encoder.
- Other minor corrections and cosmetic fixes.

[Blurayhd]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.62.11). Changes for this release:- Corrected an issue in which encoding can
fail while using the QSVENC (Intel) GPU
encoder if encoding 720x480 interlaced
sources and deinterlacing is enabled.
- Fixed an error in which VC-1 sources were
failing to encode while using the QSVENC
(Intel) GPU encoder.
- Other minor corrections and cosmetic fixes.

Executable cant modify, cant run

[jdobbs]

Executable cant modify, cant runHuh? It works here.

Anybody else having issues?

[zinoswink]

Executes just fine, no issue.

[dietachi]

Huh? It works here.

Anybody else having issues?

There are no issues here.

VC1 and 480i work fine in the latest version as well for QSVEnc.

[jdobbs]

Executes just fine, no issue.There are no issues here.

VC1 and 480i work fine in the latest version as well for QSVEnc.Thanks.

[Intel Iris the Great]

Works very well, thanks for the quick fix.

[jdobbs]

Works very well, thanks for the quick fix.Cool :)

[dietachi]

@jdobbs

VC1 and 480i have problems with VCEEnc.

For VC1:


"G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avhw --fps 23.976 -i "K:\BTTF_BD\BDMV\STREAM\00300.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 9624 --sar 1:1 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00300.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00300.AVS.264
--------------------------------------------------------------------------------
avvce: codec vc1(yuv420p) unable to decode by vce.
failed to initialize file reader(s).
Finished with error in VCEEncC.



I switched to "--avsw" and it works


"G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avsw --fps 23.976 -i "K:\BTTF_BD\BDMV\STREAM\00300.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 9624 --sar 1:1 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00300.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00300.AVS.264
--------------------------------------------------------------------------------
storage->SetProperty(BPicturesDeltaQP)=6 failed: invalid param..
storage->SetProperty(ReferenceBPicturesDeltaQP)=4 failed: invalid param..
VCEEnc (x86) 8.23 (r1710) by rigaya, Jul 18 2024 12:57:30 (VC 1940/Win)
OS: Windows 11 x64 (22631) [UTF-8]
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.99GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]
AMF: Runtime 1.4.34 / SDK 1.4.34
Input Info: avsw: vc1(yv12)->nv12 [AVX2], 1920x1080, 24000/1001 fps



For the 480i the option "--vpp-deinterlace" does not exist in VCEEnc, only the following:


--vpp-afs
--vpp-nnedi
--vpp-yadif
--vpp-decomb


I tested it with "--vpp-decomb" and it works


G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avhw --fps 29.97 --interlace tff --vpp-decomb -i "K:\BTTF_BD\BDMV\STREAM\00314.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 2021 --sar 40:33 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 30 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264
--------------------------------------------------------------------------------
storage->SetProperty(BPicturesDeltaQP)=6 failed: invalid param..
storage->SetProperty(ReferenceBPicturesDeltaQP)=4 failed: invalid param..
VCEEnc (x86) 8.23 (r1710) by rigaya, Jul 18 2024 12:57:30 (VC 1940/Win)
OS: Windows 11 x64 (22631) [UTF-8]
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.96GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]
AMF: Runtime 1.4.34 / SDK 1.4.34
Input Info: avvce: H.264/AVC, 720x480, 30000/1001 fps
VPP cspconv(nv12 -> yv12)
decomb: full on, threshold 20, dthreshold 7, blend off
cspconv(yv12 -> nv12)



Works with "--vpp-nnedi"


"G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avhw --fps 29.97 --interlace tff --vpp-nnedi -i "K:\BTTF_BD\BDMV\STREAM\00314.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 2021 --sar 40:33 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 30 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264
--------------------------------------------------------------------------------
storage->SetProperty(BPicturesDeltaQP)=6 failed: invalid param..
storage->SetProperty(ReferenceBPicturesDeltaQP)=4 failed: invalid param..
VCEEnc (x86) 8.23 (r1710) by rigaya, Jul 18 2024 12:57:30 (VC 1940/Win)
OS: Windows 11 x64 (22631) [UTF-8]
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.92GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]
AMF: Runtime 1.4.34 / SDK 1.4.34
Input Info: avvce: H.264/AVC, 720x480, 30000/1001 fps
VPP cspconv(nv12 -> yv12)
nnedi: field auto, nns 32, nsize 32x4, quality fast, prec fp32
pre_screen new_block, errortype abs, weight "internal"


It works for "--vpp-yadif mode=auto"


"G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avhw --fps 29.97 --interlace tff --vpp-yadif mode=auto -i "K:\BTTF_BD\BDMV\STREAM\00314.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 2021 --sar 40:33 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 30 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264
--------------------------------------------------------------------------------
storage->SetProperty(BPicturesDeltaQP)=6 failed: invalid param..
storage->SetProperty(ReferenceBPicturesDeltaQP)=4 failed: invalid param..
VCEEnc (x86) 8.23 (r1710) by rigaya, Jul 18 2024 12:57:30 (VC 1940/Win)
OS: Windows 11 x64 (22631) [UTF-8]
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.74GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]
AMF: Runtime 1.4.34 / SDK 1.4.34
Input Info: avvce: H.264/AVC, 720x480, 30000/1001 fps
VPP cspconv(nv12 -> yv12)
yadif: mode auto



It works with "--vpp-afs preset=default"


"G:\BD_Rebuilder\tools\vceenc\vceencc.exe" --avhw --fps 29.97 --interlace tff --vpp-afs preset=default -i "K:\BTTF_BD\BDMV\STREAM\00314.m2ts" --codec h264 --preset fast --qp-min 0 --vbr 2021 --sar 40:33 --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 30 --bframes 3 -o "G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264"
--------------------------------------------------------------------------------
G:\BD_REBUILDER\WORK\WORKFILES\VID_00314.AVS.264
--------------------------------------------------------------------------------
storage->SetProperty(BPicturesDeltaQP)=6 failed: invalid param..
storage->SetProperty(ReferenceBPicturesDeltaQP)=4 failed: invalid param..
VCEEnc (x86) 8.23 (r1710) by rigaya, Jul 18 2024 12:57:30 (VC 1940/Win)
OS: Windows 11 x64 (22631) [UTF-8]
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.83GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]
AMF: Runtime 1.4.34 / SDK 1.4.34
Input Info: avvce: H.264/AVC, 720x480, 30000/1001 fps
VPP cspconv(nv12 -> yv12)
afs: clip(T 16, B 16, L 32, R 32), switch 0, coeff_shift 192
thre(shift 128, deint 48, Ymotion 112, Cmotion 224)
level 3, shift on, drop off, smooth off, force24 off
tune off, tb_order 1(tff), rff on, timecode off, log off
cspconv(yv12 -> nv12)


For "--vpp-afs preset=XYZ" I did not check all the modes.

My apologies. I didn't had enough time to test this at the same time as the QSVenc.
Let me know if you need more info.

[jdobbs]

@dietachi

I'll work on it. As you know, I don't have a VCEEnc GPU for testing. Of the options available to replace "--vpp-deinterlace", which do you think generates the best looking output?

I'm inclined to go with "-vpp-decomb" since the others appear to throw away one field and regenerate it from the kept field. But I have seen instances where that actually looks better...