StaxRip

[NikosD]

No problem.

I covered my needs using two apps (a GUI of eac3to from tebasuna51 and Mkvmerge GUI) in batch processing mode and two steps process, that was a matter of a few minutes to set up.

[impei]

Any chance of including VP8 encoding? It's still pretty commonly used for web based video.

[JohnLai]

Hi! StaxRip uses fixed size instead of fixed bitrate by default, for fixed bitrate there is a option: Options > Misc > Use fixed bitrate

Summoning [@stax76], rigaya just added new NvencC functionality.
Those are "Adaptive Quantization" and "Two Pass VBR".
http://rigaya34589.blog135.fc2.com/blog-entry-702.html
Hoping stax76 can update staxrip gui ASAP........


<s>--vbr-2pass (Rigaya typed wrong, it is not --vbr2, but --vbr-2pass)</s> Well......his/her 1.13v2 Nvencc64 changed it back to --vbr2
--aq

[Magik Mark]

Does anybody know what the "Level" is for in Nvidia x265 encoding? Encoder options -> Basic. What does it do? Why do we even have B frames option when actually this is not supported. Every time it encodes this is set to 0 anyway

I think the 2 pass vbr will even improve the quality of the encodes. I hope staxrip is updated soon. Can't wait to test it

[JohnLai]

Does anybody know what the "Level" is for in Nvidia x265 encoding? Encoder options -> Basic. What does it do? Why do we even have B frames option when actually this is not supported. Every time it encodes this is set to 0 anyway

I think the 2 pass vbr will even improve the quality of the encodes. I hope staxrip is updated soon. Can't wait to test it

Level?
-.- Well......In this case, level is set for warning you if there are some parameters that violated the level.
https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels
Let say if you set reference frame to 14 on 1920x1080 video, but you want your video to be Level 4.1 compliant, the moment you set the level 4.1, the encoder will warn you the parameter reference number isn't level 4.1 compliant because the maximum reference frame for L4.1 is 6 (Most likely it will be 5 due to other parameter factors)

Cause in the future.....updated nvenc black box chip will support B frames. Might as well leaving the option there.....

Next....the VBR 2 pass isn't exactly the multipass encoding you normally find on x264,xvid and x265 sofware. Nvenc VBR 2 Pass is actually single frame two pass (the first pass analysis without lookahead on single frame)

Example;
x264 two pass = run first pass with lookahead from beginning until end of video, then starts actual bitrate allocation encoding based on data from first pass.

Nvenc VBR 2 Pass = run first pass on SINGLE frame without lookahead, then immediately starts bitrate allocation encoding. (Mostly aimed for reducing banding)


So, the most important addition is actually 'adaptive quantization'.

[Magik Mark]

Level?
-.- Well......In this case, level is set for warning you if there are some parameters that violated the level.
https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels
Let say if you set reference frame to 14 on 1920x1080 video, but you want your video to be Level 4.1 compliant, the moment you set the level 4.1, the encoder will warn you the parameter reference number isn't level 4.1 compliant because the maximum reference frame for L4.1 is 6 (Most likely it will be 5 due to other parameter factors)

Cause in the future.....updated nvenc black box chip will support B frames. Might as well leaving the option there.....

Next....the VBR 2 pass isn't exactly the multipass encoding you normally find on x264,xvid and x265 sofware. Nvenc VBR 2 Pass is actually single frame two pass (the first pass analysis without lookahead on single frame)

Example;
x264 two pass = run first pass with lookahead from beginning until end of video, then starts actual bitrate allocation encoding based on data from first pass.

Nvenc VBR 2 Pass = run first pass on SINGLE frame without lookahead, then immediately starts bitrate allocation encoding. (Mostly aimed for reducing banding)


So, the most important addition is actually 'adaptive quantization'.

Thanks for the reply.

Can you elaborate nvenc black box. Is this a hardware or software?
What is adaptive quantization? Is this different from VBR CQP or CBR?
Can you also recommend a good level?
Can you also recommend which is better? VBR CQP or CBR. Emphasizing quality

[JohnLai]

Thanks for the reply.

1. Can you elaborate nvenc black box. Is this a hardware or software?
2. What is adaptive quantization? Is this different from VBR CQP or CBR?
3. Can you also recommend a good level?
4. Can you also recommend which is better? VBR CQP or CBR. Emphasizing quality

1 : It is both hardware (predominantly hardware) and software if you take a look on Nvenc SDK code provided at nvidia website. https://developer.nvidia.com/nvidia-video-codec-sdk

2 : Adaptive Quantization, if we follow x264 definition.......it should follow something like this https://forums.animesuki.com/showthread.php?p=1500517#post1500517
But, the name "adaptive" quantization means it isn't suppose to work in CQP mode ("constant" quantization point), but who knows how nvidia designs and programs its nvenc. I am not even sure if AQ works in CQP for nvenc. In theory, Adaptive Quantization option supposely works for VBR, VBR 2 Pass and CBR only.

From NVENC 4.0 SDK, Adaptive quantization = This is a SW feature that defines which quantization parameters to be used and changed within a row. The regular NVENC rate control is row-based. This feature helps in situations where there is a change in textures within a row.

Meanwhile, NVENC 4.0 and 5.0 SDK manual states "2-pass rate control modes help the encoder to gather statistics of the frame to be encoded before actually encoding it in the second pass, thereby resulting in optimal bit-utilization within the frame and consequently, higher encoding quality."

3 : If we take a look on industry standard, the level used by Blu-ray and maximum supported level by media player, tv decoder & etc is Level 4.1, might as well as follow it.

4 : Quality? Stick with CQP. Nvenc has issue encoding black and dark background no matter what parameters and hardware. Nothing can be done.


EDIT: I will teach you how to use DXVA decode acceleration in conjunction with NVenc encode later. (Hardware decode and hardware encode, if you have need for speed)

[Magik Mark]

Yes, Pls Teach me the best way to encode using Nvidia. Thanks a lot!

[JohnLai]

Yes, Pls Teach me the best way to encode using Nvidia. Thanks a lot!

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle

Transcode means the media must be decoded before it can be encoded to smaller size video or other video format.

I assume these are your system information.
Now, let start with the bad news;
1 : Core I7-5820 has no IGPU, thus depriving you from using IGPU for hardware decoding and pre/post processing purposes (Intel QuickSync / QSV is the fastest hardware decoder/encoder available for codec it can support, faster than AMD and Nvidia)

Hmm, better elaborate the marketing name;

Intel decoder = QuickSync Decoder (QSV Decoder to avoid confusion)
AMD decoder = Unified Video Decoder (UVD)
Nvidia decoder = PureVideo

Intel encoder = QuickSync Encoder (QSV Encoder)
AMD encoder = Video Coding Engine (VCE)
Nvidia encoder = Nvidia Encoder (NVENC)

2: If you often resize video, let say from 1080p to 720p or 480p, you are forced to use CPU based resizer.

Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).

If you have Intel QSV though ;
Decode (QSV Decode) --> (Pre processing) Intel VPP resize, yes, this is part of QSV hardware based resizer --> Encode (GTX 960)

CPU based resizing = slowing down the transcode a lot....
Too bad you don't have IGPU.
I was planning to teach you how to use Intel QSV to speed up decoding and resizing. Well, not much you can do now......we shall stick with PureVideo decode and NVENC encode.


3: Let begin ;

First picture = http://imgur.com/u3NZyyo
Second picture = http://imgur.com/12ijxKI

Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)
--aq stands for adaptive quantization
--cu-min and --cu-max is self explanatory.
--ref (you know it)
--bframe (no bframe support for nvenc hevc/h265, maximum 3 for h264)

Note:
We are lucky because stax76's ffmpeg has dxva2 support compiled........generally, the other ffmpeg you find around the internet doesn't enable -hwaccel functionality at all.
In case if you wanna try the adaptive quantization and vbr2pass, you need to download and extract NVEnc 1.13v2 from http://rigaya34589.blog135.fc2.com/blog-entry-702.html to replace NVEncC and NVEncC64 at Staxrip\Apps\NVEncC folder.

[Magik Mark]

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle

Transcode means the media must be decoded before it can be encoded to smaller size video or other video format.

I assume these are your system information.
Now, let start with the bad news;
1 : Core I7-5820 has no IGPU, thus depriving you from using IGPU for hardware decoding and pre/post processing purposes (Intel QuickSync / QSV is the fastest hardware decoder/encoder available for codec it can support, faster than AMD and Nvidia)

Hmm, better elaborate the marketing name;

Intel decoder = QuickSync Decoder (QSV Decoder to avoid confusion)
AMD decoder = Unified Video Decoder (UVD)
Nvidia decoder = PureVideo

Intel encoder = QuickSync Encoder (QSV Encoder)
AMD encoder = Video Coding Engine (VCE)
Nvidia encoder = Nvidia Encoder (NVENC)

2: If you often resize video, let say from 1080p to 720p or 480p, you are forced to use CPU based resizer.

Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).

If you have Intel QSV though ;
Decode (QSV Decode) --> (Pre processing) Intel VPP resize, yes, this is part of QSV hardware based resizer --> Encode (GTX 960)

CPU based resizing = slowing down the transcode a lot....
Too bad you don't have IGPU.
I was planning to teach you how to use Intel QSV to speed up decoding and resizing. Well, not much you can do now......we shall stick with PureVideo decode and NVENC encode.


3: Let begin ;

First picture = http://imgur.com/u3NZyyo
Second picture = http://imgur.com/12ijxKI

Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)
--aq stands for adaptive quantization
--cu-min and --cu-max is self explanatory.
--ref (you know it)
--bframe (no bframe support for nvenc hevc/h265, maximum 3 for h264)

Note:
We are lucky because stax76's ffmpeg has dxva2 support compiled........generally, the other ffmpeg you find around the internet doesn't enable -hwaccel functionality at all.
In case if you wanna try the adaptive quantization and vbr2pass, you need to download and extract NVEnc 1.13v2 from http://rigaya34589.blog135.fc2.com/blog-entry-702.html to replace NVEncC and NVEncC64 at Staxrip\Apps\NVEncC folder.

Thanks. This is very informative. What I do most of the time is try to tranascode x264 to x265 in order to decrease the file size. I would like to have a quality similar or better from the original but smallest possible file size using nvidia. CPU transcoding is taking so much time and it it taking a toll on my CPU. That's why I want to maximize the potential of GPU transcoding. I work with 1080p & 720p videos predominantly

You are very helpful. Thanks a lot!

[Magik Mark]

CQP has good quality. But the file size is not significantly reduced.

VBR2 4500 is unsuccessfull. I get this error:

Error Encoding video command line encoder: Command Line | NVIDIA H.265

Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument



StaxRip.ErrorAbortException: Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument


at StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:line 233
at StaxRip.BatchEncoder.Encode() in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:line 430

[JohnLai]

CQP has good quality. But the file size is not significantly reduced.

VBR2 4500 is unsuccessfull. I get this error:

Error Encoding video command line encoder: Command Line | NVIDIA H.265

Encoding video command line encoder: Command Line | NVIDIA H.265 failed with error code 1

C:\Users\Magik Mark\Desktop\StaxRip>"C:\Users\Magik Mark\Desktop\StaxRip\Apps\ffmpeg\ffmpeg.exe" -hwaccel dxva2 -i "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01.avs" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "C:\Users\Magik Mark\Desktop\StaxRip\Apps\NVEncC\NVEncC64.exe" --sar 1:1 --codec h265 --y4m --VBR2 4500 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "C:\Users\Magik Mark\Desktop\Bones S11E01 temp files\Bones S11E01_out.h265"
Unknown Option : 4500av_interleaved_write_frame(): Invalid argument

Strange. Let begin the troubleshooting;

1 : Did you update to latest NVEnc_1.13v2? You are supposed to replace the NVEncC64.exe inside Staxrip\Apps\NVEncC folder.

2 : Make sure your nvidia driver is up to date.

3 : https://github.com/stax76/staxrip/releases Are you using StaxRip_x64_1.3.1.7_beta? Cause I think older ffmpeg included by stax76 doesn't have dxva2 acceleration. Note: Not all video format can be hardware decoded, in this case, it will automatically fall back to software decoding.

4 : Some recommendation on video bitrate in case you plan to use nvenc VBR2Pass + AQ for 23 - 30fps video.

1080p = 4500
720p = 2500
480p = 1000
360p = 750
240p = 400

[Magik Mark]

Found this in rigaya's blog:

"2015.11.08 6:27 NVEncC x64 executable file is not up-to-date version, - Fixed vbr2 of did not work. x86 Edition is no problem. "

Rough translation of google. The way i understand it, x64 version is not working well

[JohnLai]

Found this in rigaya's blog:

"2015.11.08 6:27 NVEncC x64 executable file is not up-to-date version, - Fixed vbr2 of did not work. x86 Edition is no problem. "

Rough translation of google. The way i understand it, x64 version is not working well


Duh.....he said he fixed it, that why he released V2.
-.- You better update staxrip nvencc.

[Magik Mark]

Duh.....he said he fixed it, that why he released V2.
-.- You better update staxrip nvencc.

How do I do this?

[JohnLai]

How do I do this?

Are you serious?
http://i.imgur.com/WF5Okqa.png

[Magik Mark]

Thank you very much JohnLai for your patience and understanding. I'm really new to this. Continue on giving us advise. Thanks A Lot!

[Yups]

http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=1901&lang=en


Media SDK 1.17 has been released with this driver. No documentation or changelog available yet. Intel says soon, whatever it means.

[NikosD]

@Stax76

Hello.

Is it possible to add Unicode support to StaxRip ?

I mean in filenames and path.

I have no idea how difficult/painful is this.

[NikosD]

Hi.

Just a few more questions...

1) Is it possible to somehow configure the "File Batch" mode ?
For example, I have some files with embedded subtitles which in "File Batch" mode, the subtitles disappeared after transcoding. (No subs included)

I think, that "File Batch" mode follows your current project user preferences regarding video (video encoder profile, selected container) and audio (audio encoder profile)

But what about subs ?
Shouldn't be included by default ?
How can I select what to include in "File Batch" mode ?

2) What is the use and gain of using "Demux and Index before creating jobs" option in "File Batch" mode ?

3) Is it possible to avoid "indexing" when in video encoders profiles "Just Mux" is selected for both single file processing and "file batch" processing ?

I don't know if indexing is used for anything else besides video processing.

[Yups]

http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=fileinfo&id=1901&lang=en


Media SDK 1.17 has been released with this driver. No documentation or changelog available yet. Intel says soon, whatever it means.


New documentation has been released for API 1.17.

https://software.intel.com/sites/default/files/mediasdk_release_notes.pdf
https://software.intel.com/sites/default/files/managed/47/49/mediasdk-man.pdf

[NikosD]

The release notes are for API v1.16, but the reference manual is for v1.17.

Stax76 and StaxRip has nothing to do with this, because he doesn't write code for MediaSDK.

The developer of QSVEncC which is based on MediaSDK is rigaya, you could send him an email.

Here in Doom9 there is no thread for MediaSDK.

A few years ago, the thread of QSV decoder (a decoder based on MediaSDK) by egur (Eric Gur) - an Intel employee - was very active, but now he doesn't seem interested in development any more.

[Yups]

Release notes should be for 1.17 because there wasn't Skylake support in 1.16, now it is. And there are specific 1.17 notes. Rigaya told this might be interesting for QSVEncC.

[NikosD]

API v1.17 added for the first time rotation of 90,180 and 270 degrees.

I've already asked rigaya for implementing it.

Hope he adds it and Stax76 too in StaxRip's GUI.

[NikosD]

QSVEncC v2.22 is out adding support of API v1.17 using latest unofficial drivers v4312.

It adds vpp-rotation <angle>.

[stax76]

I'll catch up on missed posts in the next days. :)

Regarding test builds I made a separate wiki page, changes not yet uploaded will be stated in the future.

https://github.com/stax76/staxrip/wiki/Development-Changelog

[dejong12]

I'll catch up on missed posts in the next days. :)

Regarding test builds I made a separate wiki page, changes not yet uploaded will be stated in the future.

https://github.com/stax76/staxrip/wiki/Development-Changelog
Thanks! NVEncC 1.13 is out by the way. :)

[JohnLai]

Indeed.....VBR2pass and adaptive quantization option gui for staxrip?

[stax76]

Indeed.....VBR2pass and adaptive quantization option gui for staxrip?

please let me know if it works

https://github.com/stax76/staxrip/wiki/Development-Changelog

[JohnLai]

please let me know if it works

https://github.com/stax76/staxrip/wiki/Development-Changelog

Will test it later.

Stax76, I got few questions.....

1)Why is your ffmpeg version has dxva decode support, but lack of ffmpeg QSV Decode + VPP? Oh,plus NVENC support as well?

2)On 9 November 2015 or so....nvidia include GPU Resize and GPU Zero-copy for ffmpeg. https://developer.nvidia.com/ffmpeg . Scroll down the site and click the green "Download" to get nvidia pdf reference.

Reason = rigaya qsv decode + vpp resize often crash for my win10 hd4000 intel igpu. I wonder if ffmpeg is more error resilience at it?

*I actually need hardware based resizer......T_T...Although your ffmpeg has DXVA support (it actually faster in decoding than DSS2 LAVfilter copyback), the cpu based resizing really take a hit on transcoding fps.

*One ffmpeg to rule them all?

[stax76]

@JohnLai

sounds promising, I'll investigate it.

[Magik Mark]

@JohnLai

vbr2 is awesome! Good Quality & small file size. It can encode in 10 minutes for a typical 1 hour tv show

[NikosD]

1)Why is your ffmpeg version has dxva decode support, but lack of ffmpeg QSV Decode + VPP? Oh,plus NVENC support as well?

Reason = rigaya qsv decode + vpp resize often crash for my win10 hd4000 intel igpu. I wonder if ffmpeg is more error resilience at it?

...Although your ffmpeg has DXVA support (it actually faster in decoding than DSS2 LAVfilter copyback), the cpu based resizing really take a hit on transcoding fps.


I remember checking FFMpeg a while ago and for Intel, it had all HW features supported - decoding, encoding and VPP.

BUT IIRC, encoding and VPP were loosely supported, meaning very low API version support, capable for SandyBridge.

SandyBridge can support up to API v1.4 only (I think), so all the advanced rate controls and VPP functions shouldn't be supported by FFMPEG QSV encoding and VPP.

Do you know if the latest version of FFMPEG QSV has changed that ?
Is it updated ?

Now, regarding FFMpeg QSV decoding haven't seen or tested yet.

Have you done any tests regarding speed and video stream compatibility of FFMPEG QSV decoding compared to DXVA LAV and MediaSDK QSVEncC by Rigaya ?

Would be interesting to know...

P.S

I forgot to say that your problems with qsvencc decode + vpp could probably occur due to your Ivybridge setup.
I don't think Haswell or better have such problems.

What is the latest API version support of Ivy ?

[JohnLai]

@JohnLai

sounds promising, I'll investigate it.

Thanks for your hardwork. ^.^b
Oh ya, the VBR2 and AQ GUI option works without issue.

@JohnLai

vbr2 is awesome! Good Quality & small file size. It can encode in 10 minutes for a typical 1 hour tv show

Remember to use adaptive quantization too.

I remember checking FFMpeg a while ago and for Intel, it had all HW features supported - decoding, encoding and VPP.

BUT IIRC, encoding and VPP were loosely supported, meaning very low API version support, capable for SandyBridge.

SandyBridge can support up to API v1.4 only (I think), so all the advanced rate controls and VPP functions shouldn't be supported by FFMPEG QSV encoding and VPP.

Do you know if the latest version of FFMPEG QSV has changed that ?
Is it updated ?

Now, regarding FFMpeg QSV decoding haven't seen or tested yet.

Have you done any tests regarding speed and video stream compatibility of FFMPEG QSV decoding compared to DXVA LAV and MediaSDK QSVEncC by Rigaya ?

Would be interesting to know...

P.S

I forgot to say that your problems with qsvencc decode + vpp could probably occur due to your Ivybridge setup.
I don't think Haswell or better have such problems.

What is the latest API version support of Ivy ?

Even without VPP usage, rigaya QSVencC decode still crash for my system.
From rigaya qsvencc, the API version 1.11 is reported for HD4000.


FFMPEG QSV 2.8 supposes to change that......but so far....I cant find any ffmpeg cli that has full QSV decode + vpp + encode around the internet. Compiling one is too troublesome. Headache.
There is one ffmpeg with qsv_h264 decoder. ffmpeg-20150610-git-913685f-win64-static from zeronoa. The problem, it doesnt work. You will encounter exactly error as mentioned here http://ffmpeg.org/pipermail/ffmpeg-devel/2015-August/176843.html
Based on the mailing list, seems like the latest ffmpeg fixed it, but there isnt anyone compiling and making it available online.


EDIT: -.-......I just found one binary.....https://github.com/illuspas/ffmpeg-hw-win32 .........click 'Download Zip'.....

Extract out anywhere..... Benchmark time? Start command prompt.......

ffmpeg -vcodec h264_qsv -i test_track1_und.h264 -f null -

Should work? GPUZ report the HD4000 has utilization of 70 - 76% for bitrate 3072Kbps 1080p test file.

The log:

ffmpeg version 2.8 Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --prefix=/home/aliang/Library/mingw --cross-prefix=i686-w64-mingw32- --cc='ccache i686-w64-mingw32-gcc' --enable-cross-compile --target-os=mingw32 --arch=i686 --enable-small --disable-doc --disable-debug --enable-nvenc --enable-libmfx --enable-libfdk-aac --enable-libspeex --enable-libx264 --enable-libx265 --enable-libopenh264 --enable-libopus --enable-libmp3lame --enable-nonfree --enable-gpl
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100
Input #0, h264, from 'test_track1_und.h264':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264, nv12, 1920x1080, 12.50 fps, 25 tbr, 1200k tbn, 25 tbc
Output #0, null, to 'pipe:':
Metadata:
encoder : Lavf56.40.101
Stream #0:0: Video: rawvideo (NV12 / 0x3231564E), nv12, 1920x1080, q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc
Metadata:
encoder : Lavc56.60.100 rawvideo
Stream mapping:
Stream #0:0 -> #0:0 (h264 (h264_qsv) -> rawvideo (native))
Press [q] to stop, [?] for help
[h264_qsv @ 027bebe0] A decode call did not consume any data=N/A
Last message repeated 10 times
frame=34410 fps=179 q=-0.0 Lsize=N/A time=00:45:53.12 bitrate=N/A
video:2151kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown


Note:someone is adding qsv vpp as ffmpeg -vf support to ffmpeg on 12 Nov 16:46 2015......
http://search.gmane.org/?author=Sven+Dueking&sort=date
*deleted*

Hmm...just noticed ffmpeg -benchmark argument, might as well as testing using the command below;

ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -


Update:
-.- Darn it.....seem like ffmpeg QSV above is really slow in decoding. When I use "ffmpeg -an -benchmark -hwaccel dxva2 -i test.mkv -f null -" in order to benchmark the same video using my discrete gpu gtx 970....i got this result :

Input stream #0:0 frame changed from size:1920x1080 fmt:yuv420p to size:1920x1080 fmt:nv12
[null @ 04707300] Encoder did not produce proper pts, making some up.
frame=34410 fps=402 q=-0.0 Lsize=N/A time=00:23:55.31 bitrate=N/A
video:2151kB audio:247256kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
bench: utime=32.672s
bench: maxrss=236900kB

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?

ffmpeg -vcodec h264_qsv -i test.mkv -an -vcodec h264_qsv -q 20 test.h264
frame= 4795 fps=130 q=-0.0 Lsize= 141545kB time=00:03:19.78 bitrate=5804.0kbits/s

Hmm.....i wonder if one must use "-hwaccel qsv" instead of using h264_qsv decoder?
From ffmpeg documentation;
-hwaccel[:stream_specifier] hwaccel (input,per-stream)
Use hardware acceleration to decode the matching stream(s). The allowed values of hwaccel are:
qsv
Use the Intel QuickSync Video acceleration for video transcoding.
Unlike most other values, this option does not enable accelerated decoding (that is used automatically whenever a qsv decoder is selected), but accelerated transcoding, without copying the frames into the system memory.
For it to work, both the decoder and the encoder must support QSV acceleration and no filters must be used.

-.- too bad when i run "ffmpeg -hwaccels" to list out any hardware acceleration, only "dxva2" is shown.

Update2: On the bright side of the news....
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-October/181843.html
Thu Oct 22 17:56:10 CEST 2015

He said 2.5 times faster? Maybe like 179fps X 2.5 = 358fps? (This figure seems to be realistic)
Oh well...let see how ffmpeg developers re-design session control and internal allocation.......(copy pasted)

[NikosD]

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?

ffmpeg -vcodec h264_qsv -i test.mkv -an -vcodec h264_qsv -q 20 test.h264
frame= 4795 fps=130 q=-0.0 Lsize= 141545kB time=00:03:19.78 bitrate=5804.0kbits/s

Hmm.....i wonder if one must use "-hwaccel qsv" instead of using h264_qsv decoder?
From ffmpeg documentation;
-hwaccel[:stream_specifier] hwaccel (input,per-stream)
Use hardware acceleration to decode the matching stream(s). The allowed values of hwaccel are:
qsv
Use the Intel QuickSync Video acceleration for video transcoding.
Unlike most other values, this option does not enable accelerated decoding (that is used automatically whenever a qsv decoder is selected), but accelerated transcoding, without copying the frames into the system memory.
For it to work, both the decoder and the encoder must support QSV acceleration and no filters must be used.

-.- too bad when i run "ffmpeg -hwaccels" to list out any hardware acceleration, only "dxva2" is shown.


Maybe I could try that version , although I have to say that I'm very pleased of QSVEncC by Rigaya in terms of both speed and features (+stream compatibility)

It uses ffmpeg for demuxing and muxing only and the transcoding (decoding/encoding) is processed by MediaSDK code of Rigaya and not ffmpeg's.

He has added mpeg2/vc1/hevc HW decoding and mpeg2 HW encoding that ffmpeg qsv doesn't support (I think)

Also, rigaya has implemented his transcoding pipeline without using system memory (memory copy) and that is the reason that is very fast with very low CPU utilisation.


Update2: On the bright side of the news....
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-October/181843.html
Thu Oct 22 17:56:10 CEST 2015

He said 2.5 times faster? Maybe like 179fps X 2.5 = 358fps? (This figure seems to be realistic)
Oh well...let see how ffmpeg developers re-design session control and internal allocation.......(copy pasted)

Hendrik Leppkes is nevcairiel, here in Doom9 the developer of LAV filters.
You could ask him directly here without using ffmpeg forum.

[NikosD]

According to rigaya his app has a lot of differences with ffmpeg version.
I asked him and this is his reply:

ffmpeg and QSVEncC is rather different program, although it uses libavformat for demuxing and muxing.

ffmpeg does not have many encoding options for QSV which is there in QSVEncC.
They only have options below API 1.10, and they don’t have options for bluray, and many other options.

ffmpeg don’t have ability to check QSV features on runtime like QSVEncC has.

Frame rate detection algorithm is completely different, I don’t know which is better.

Also, it does not have vpp feature or full GPU transcoding currently.
But I think ffmpeg will have it soon, because I’ve heard that libav has that feature now.

Currently ffmpeg cannot decode HEVC in QSV.

On the other hand, when using QSV in ffmpeg, you can use many features which ffmpeg has,
such as various audio & video filters which are not there in QSVEncC.


I also said to him to open a thread here in doom9, supporting all his apps for hardware transcoding using AMD/Intel/Nvidia GPUs, in order to help us users and to help him too.

I think it's a good idea.

[JohnLai]

Maybe I could try that version , although I have to say that I'm very pleased of QSVEncC by Rigaya in terms of both speed and features (+stream compatibility)

He has added mpeg2/vc1/hevc HW decoding and mpeg2 HW encoding that ffmpeg qsv doesn't support (I think)

Also, rigaya has implemented his transcoding pipeline without using system memory (memory copy) and that is the reason that is very fast with very low CPU utilisation.

Hendrik Leppkes is nevcairiel, here in Doom9 the developer of LAV filters.
You could ask him directly here without using ffmpeg forum.

Oh? I never know that H.L. is nevcairiel......Maybe I will ask him later.

Latest ffmpeg from github supports qsv hardware decode; (using ffmpeg -decoders>decoder.txt to list out)

V....D h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264)
V....D hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec hevc)
V....D mpeg2_qsv MPEG-2 video (Intel Quick Sync Video acceleration) (codec mpeg2video)
V..... vc1_qsv VC-1 video (Intel Quick Sync Video acceleration) (codec vc1)


Meanwhile, the ffmpeg hardware based encoders support ; (using ffmpeg -encoders>encoders.txt to list out)

V..... h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264)
V..... hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec hevc)
V..... mpeg2_qsv MPEG-2 video (Intel Quick Sync Video acceleration) (codec mpeg2video)

V..... nvenc NVIDIA NVENC h264 encoder (codec h264)
V..... nvenc_h264 NVIDIA NVENC h264 encoder (codec h264)
V..... nvenc_hevc NVIDIA NVENC hevc encoder (codec hevc)

Impressively, ffmpeg latest git even has nvenc hevc encode support. I dont understand what is the difference between "nvenc" and "nvenc_h264", should be the same?


According to rigaya his app has a lot of differences with ffmpeg version.
I asked him and this is his reply:


I also said to him to open a thread here in doom9, supporting all his apps for hardware transcoding using AMD/Intel/Nvidia GPUs, in order to help us users and to help him too.

I think it's a good idea.

True, ffmpeg still doesnt support QSV VPP yet......I am hopeful it can be added to official ffmpeg trunk, same with nvidia zero copy and gpu resize.

-.-.....the only thing missing....where is AMD VCE?

*Took me some time to compile full actual working ffmpeg using ffmpeg-windows-build-helpers.
*Will benchmark later. Right now, I just make sure everything works......

[NikosD]

*Took me some time to compile full actual working ffmpeg using ffmpeg-windows-build-helpers.
*Will benchmark later. Right now, I just make sure everything works......

Thank you for the link of the compiled version of full ffmpeg.exe.


ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

Update:
-.- Darn it.....seem like ffmpeg QSV above is really slow in decoding. When I use "ffmpeg -an -benchmark -hwaccel dxva2 -i test.mkv -f null -" in order to benchmark the same video using my discrete gpu gtx 970....i got this result :

179fps ffmpeg QSV decoder vs 402fps ffmpeg DXVA2 gtx 970 decoder.
I guess this ffmpeg slow qsv decode is the same issue encountered by rigaya not too long ago. Before any conclusion is done......NikosD~~, can you post your ffmpeg QSV decode fps here?


Using your command line:
ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

...it is clear to me, that the h264_qsv acceleration is using a copy-back mode for decoding and I also get slow results, with very low GPU clock and a CPU usage that demonstrates a copy-back method.

ffmpeg h264_qsv is faster than Eric's Gur Intel QSV decoder (which also uses copy-back mode) but slower than LAV DXVA copy-back.

I think that -hwaccel dxva2 could use a dxva2 native mode, but unfortunately it gives me the following error with my iGPU and falls back to software mode:

[h264 @ 000001ae43867f00] Hardware accelerated decoding with frame threading is not supported.

I'm afraid we are using a wrong thread for all these, because they have nothing or little to do with StaxRip.

Make another thread regarding ffmpeg HW acceleration (decoding/encoding) to go on there...

[JohnLai]

Thank you for the link of the compiled version of full ffmpeg.exe.

Using your command line:
ffmpeg -an -benchmark -vcodec h264_qsv -i test.mkv -f null -

...it is clear to me, that the h264_qsv acceleration is using a copy-back mode for decoding and I also get slow results, with very low GPU clock and a CPU usage that demonstrates a copy-back method.

ffmpeg h264_qsv is faster than Eric's Gur Intel QSV decoder (which also uses copy-back mode) but slower than LAV DXVA copy-back.

I think that -hwaccel dxva2 could use a dxva2 native mode, but unfortunately it gives me the following error with my iGPU and falls back to software mode:

[h264 @ 000001ae43867f00] Hardware accelerated decoding with frame threading is not supported.

I'm afraid we are using a wrong thread for all these, because they have nothing or little to do with StaxRip.

Make another thread regarding ffmpeg HW acceleration (decoding/encoding) to go on there...

Yeah, maybe I should create a new thread, btw, something isn't right with the build I compile.

When either -vcodec h264_qsv or -hwaccel qsv is used, seem like it doesnt make use of the IGPU at all. Darn it.....the compile seems to be successful without any issue....I wonder what went wrong. The h264_qsv also fall back to software.

*Hope stax76 can compile one that actually work without any issue.

[NikosD]

For me h264_qsv works fine, but hevc_qsv doesn't seem to work.

[JohnLai]

For me h264_qsv works fine, but hevc_qsv doesn't seem to work.

It isn't working for my discrete gpu + headless igpu setup, all my 4 cores jumped to max utilization with 0% utilization on HD4000.

As for "Hardware accelerated decoding with frame threading is not supported." solution, you must specify;

ffmpeg -threads 1 -benchmark -hwaccel dxva2 -i test.mkv -an -sn -f null -

But...ffmpeg nvenc_hevc sure leaves a lot to be desired. Nothing much to control except specifying preset, level and tier.

ffmpeg -threads 1 -hwaccel dxva2 -i test.mkv -an -sn -preset slow -tier high -level 4.1 -vcodec nvenc_hevc output.mkv

I was playing around with ffmpeg nvenc_hevc and using the best possible option I can find from https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/nvenc.c , the end encoded video quality is downright abysmal. Full of visible blocking artifacts. Preset 'slow' has two pass enabled judging from the nvenc.c code and it should be the best preset ;

slow, medium, fast, hq, hp, bd, ll, llhp, llhq, lossless, losslesshp and default

Lack of user configurable option? How to select rate control mode? Where to specify CQP value? MinQP and MaxQP? How to specify b-frame value for H264 and number of reference frame?

I prefer rigaya NVencC encoder in this case. His encoder has more functions and produce way better video quality than ffmpeg right now.

I am hoping for the h264_qsv decoder to be working so that stax76 can include it once ffmpeg developers got the VPP resize working as ffmpeg video filter. >.> But, h264_qsv decoder doesn't seem to work in my case. Back to zero again T_T

[NikosD]

As for "Hardware accelerated decoding with frame threading is not supported." solution, you must specify;

ffmpeg -threads 1 -benchmark -hwaccel dxva2 -i test.mkv -an -sn -f null -



No, it doesn't work for me. No HW acceleration, it falls back to SW.

[JohnLai]

No, it doesn't work for me. No HW acceleration, it falls back to SW.

Strange, it works on mine though (GTX970). Oh well, I surrender.....I shall leave the hard work figuring it out to stax76.....:cool:

[Magik Mark]

Asus X99 Sabertooth - i7 5820 - Asus Strix GTX 960 4G - DDR4 16GB Predator - Pioneer KRP 600M (isf calibrated) - Windows 10 x64 - Kodi with DSplayer - Lav - MadVR - XYsubtitle


Your system;
Decode(GTX 960)---->(post processing) CPU based resizer (I7-5820K)---->Encode(GTX 960).


Generally, in your case;

"%app:ffmpeg%" -hwaccel dxva2 -i "%script_file%" -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 20:23:25 --cu-min 8 --cu-max 32 --aq --ref 5 --level 4.1 --bframes 0 --input - --output "%encoder_out_file%"

Free free to use different rate control method, such as --cqp 20:23:25 to --VBR2 4500 (Note, nvenc VBR 2 pass encode is really slow, gtx 970 = 150fps for encoding HEVC 1080P)

John, --y4m does not work with vbr2. Needed to remove that

Are there any other settings, parameters, filters that we can use to enhance the image and improve quality using vbr2?

[JohnLai]

John, --y4m does not work with vbr2. Needed to remove that

Are there any other settings, parameters, filters that we can use to enhance the image and improve quality using vbr2?

@Magik Mark,
Download stax76 test build from here.
https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

Staxrip test build H265 Nvidia preset has the vbr2 and AQ option now.
To replace the ffmpeg dxva2, go Filters--->Source, right click and select FFVideoSource. Much more easier.

As bearer of bad news, there is nothing more we can do to enhance and improve the quality using nvenc vbr2......





@NikosD,
I can confirm the -threads 1 with -hwaccel dxva2 doesn't work on my Core I3-4330 with only IGPU HD4600 being connected to display. It falls back to software decode as you mentioned. Noteworthy, the h264_qsv decode + encode with -hwaccel qsv actually works with great speed. (GPUZ report 85-93% utilization with -hwaccel qsv enabled for complete QSV transcode)

However, on my gaming system with GTX970 (connected to display) with I5-3570K igpu HD4000(headless), h264_qsv totally fall back to software decode. But the -threads 1 -hwaccel dxva2 works for the GTX970.

Sigh.....oh well, rigaya did mention he might implement all in one fully accelerated nvencc transcode (decode + nvenc resize + zero copy + nvenc). I hope he can successfully implement it.

Although I do think future upcoming FFMPEG video filter for QSV VPP has better quality than Nvidia ffmpeg resize filter sample patch.

From ffmpeg patch note;
QSV VPP resize = VPP uses a separable 8-tap poly-phase scaling filter with adaptive filter ringing suppression.

Nvidia Nvenc resize = From the patch code, I only saw Subsample_Bilinear ? =.=""

[NikosD]

@NikosD,
Noteworthy, the h264_qsv decode + encode with -hwaccel qsv actually works with great speed. (GPUZ report 85-93% utilization with -hwaccel qsv enabled for complete QSV transcode)


Yes, -hwaccel qsv is exactly that.
Full speed transcoding without copy-back but without using any VPP filters.

When ffmpeg implements VPP, they have to keep using GPU memory only without copying to system ram, in order to be fast.


Although I do think future upcoming FFMPEG video filter for QSV VPP has better quality than Nvidia ffmpeg resize filter sample patch.

From ffmpeg patch note;
QSV VPP resize = VPP uses a separable 8-tap poly-phase scaling filter with adaptive filter ringing suppression.

Nvidia Nvenc resize = From the patch code, I only saw Subsample_Bilinear ? =.=""

It is true that even since SandyBridge at 2011, Intel had better HW implemented algorithms for everything regarding VPP (resizing, deinterlacing, scaling etc)

[Magik Mark]

@Magik Mark,
Download stax76 test build from here.
https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

Staxrip test build H265 Nvidia preset has the vbr2 and AQ option now.
To replace the ffmpeg dxva2, go Filters--->Source, right click and select FFVideoSource. Much more easier.

As bearer of bad news, there is nothing more we can do to enhance and improve the quality using nvenc vbr2......

Can any other graphics card do better in x265 encoding with video enhancements, filters or processing? Something similar to CPU based encoding? How about SLI based encoding? Is this even possible with results similar to CPU?

[JohnLai]

Can any other graphics card do better in x265 encoding with video enhancements, filters or processing? Something similar to CPU based encoding? How about SLI based encoding? Is this even possible with results similar to CPU?

-.- I think you are confused about something.

HEVC/H.265 is a video compression standard.
x265 = software to encode HEVC compliant video.

As for your question, the ONLY alternative in which there might be better in hardware HEVC encoding with all those video processing done in hardware style (deinterlacing,sharpening, high quality resizing, color conversion, bla bla bla bla.......) is Intel Quicksync available only for Skylake microarchitecture. Yet......no hardware can ever beat software based encoding in term of quality.

SLI based encoding? Nvenc SDK only designed for single gpu so far.

[deekey777]

I cannot use AMD VCE:
Error Encoding using VCEEncC

Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"



StaxRip.ErrorAbortException: Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"


bei StaxRip.Proc.Start() in D:\Projekte\GitHub\staxrip\General\Proc.vb:Zeile 233.
bei StaxRip.AMDEncoder.Encode(String args) in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:Zeile 1643.
bei StaxRip.AMDEncoder.Encode() in D:\Projekte\GitHub\staxrip\General\VideoEncoder.vb:Zeile 1633.
bei StaxRip.MainForm.Encode() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:Zeile 2292.
bei StaxRip.MainForm.RunJobRecursive() in D:\Projekte\GitHub\staxrip\Forms\MainForm.vb:Zeile 3587.

Here is the Log:
------------------------------------------------------------
Encoding using VCEEncC
------------------------------------------------------------

"C:\Users\Denis x64\Downloads\StaxRip_x64_1.3.1.7_beta\Apps\VCEEncC\VCEEncC64.exe" --quality slow --cqp 22:24:27 --input "E:\Videos\HDTV-1080p-H264_007-Casino-Royale_AC3 temp files\HDTV-1080p-H264_007-Casino-Royale_AC3_new.avs" --output "E:\Videos\HDTV-1080p-H264_007-Casino-Royale_AC3 temp files\HDTV-1080p-H264_007-Casino-Royale_AC3_new_out.h264"

Unknow Options: "--input"

------------------------------------------------------------
Error Encoding using VCEEncC
------------------------------------------------------------

Encoding using VCEEncC failed with error code 1

Unknow Options: "--input"


Start: 13:21:09
End: 13:21:09
Duration: 00:00:00

PC: Windows 10 Pro x64 1511, R7 260X with the Crimson driver.

Here is a build with VCEEncC support for AMD H.264 encoding, I could not test it so I hope it works.

The build also fixes the issue with dialogs showing in command line mode.

http://www.mediafire.com/download/si8hl09q6hzdda5/StaxRip_x64_2015-09-28.7z
Oh, missed this posting. Give me 10 minutes.

Doesn't work.

[Magik Mark]

-.- I think you are confused about something.

HEVC/H.265 is a video compression standard.
x265 = software to encode HEVC compliant video.

As for your question, the ONLY alternative in which there might be better in hardware HEVC encoding with all those video processing done in hardware style (deinterlacing,sharpening, high quality resizing, color conversion, bla bla bla bla.......) is Intel Quicksync available only for Skylake microarchitecture. Yet......no hardware can ever beat software based encoding in term of quality.

SLI based encoding? Nvenc SDK only designed for single gpu so far.

As always, Thanks a lot for the info!