StaxRip

[NikosD]

The Nvidia GT630 v2 is a Kepler card and NVEncC should work for you.

Your driver is ancient...

Install the latest and it will do the job.

[JohnLai]

Maybe he choose NVIDIA H.265 preset instead of Nvidia H.264 preset.
Remember, Nvidia Kepler only supports NVENC H264 encoding.
HEVC encoding is only supported on Maxwell V2 (Too bad for Maxwell V1).

[Dust Signs]

The new support for more then two audio tracks had a bad bug so I've uploaded a new build:

https://github.com/stax76/staxrip/wiki/Test-Build

Nice, thank you. Is there any automatic cropping available yet when using VapourSynth?

Best regards
Dust Signs

[Pengaban]

Thanks!

For the driver version I was incorrect it's actually a newer 347.52 from 2015 installed on that sys.

For the GPU error I suspect that maybe the GPU memory type is the cause for the error?
This GT 630 has only cheap DDR3 with 14.4GB/s bandwith(according to GPU-Z). I will try another GK208 GPU laying around a "GT 640" with GDDR5 memory on the system and 40.1GB/s bandwith. Maybe that will do the trick.

Buying a new second gen maxwell eg. GTX950 for about 150,- € only for transcoding isn't worth it for me. Pascal is around the corner. Hopefully there will be some low end Pascal GPUs for NVENC usage.


I double checked that I use "NVIDIA H.264" at encoder settings. I'm using StaxRip v1.3.1.7 and I read this article for a first orientation and setup:
http://www.techspot.com/article/1131-hevc-h256-enconding-playback/page5.html

[NikosD]

Thanks!

For the driver version I was incorrect it's actually a newer 347.52 from 2015 installed on that sys.

For the GPU error I suspect that maybe the GPU memory type is the cause for the error?


Still, too old driver.

I suggest you to download and install latest driver for your system.

GPU memory type and performance has nothing to do with such compatibility errors.

[NikosD]

Tried latest StaxRip x64 test-build

1)I have asked this previously.

For the file below in "Single file" mode I can mux subtitles.
In "file batch" mode, I can't.

Sample:
http://www.filedropper.com/00063

Bug or limitation ?


2) More than 2 audio streams muxing looks good.


3) VCEEnc has a newer version 1.03v2 here:

https://onedrive.live.com/?id=6BDD4375AC8933C6%21516&cid=6BDD4375AC8933C6


4) I think going to Help -> Support forum should point here and not in videohelp.com forum :)

[luigizaninoni]

Is it possible to use x265.exe (for example 8-bit or 10-bit) instead of the multilibrary x265_ml.exe ?

I'm asking this because there are several builds available on the web, updated daily, based of various compilers, while as far as I know x265_ml.exe is only available in Ligh's builds, which are updated less frequently and built with a single compiler.

So using single libraries might be, occasionally, more flexible.

[burfadel]

--psy-rd in Staxrip is only adjustable down from the default value of 2.00. The value in x265 can be up to 5.00.

[NikosD]

Has anyone succeeded in using HW encoding (QSV, NVEnc, VCEEnc) on a laptop with GPU switching technology ?

Like Nvidia Optimus or AMD Enduro.

[Havokdan]

Has anyone succeeded in using HW encoding (QSV, NVEnc, VCEEnc) on a laptop with GPU switching technology ?

Like Nvidia Optimus or AMD Enduro.

Me with Nividia Optimus (Intel 4000 and GTX 675MX) in Clevo P151.

[NikosD]

How ?
Can you describe it a little ?

Which program worked ?

QSVEncC, NVEncC or both ?

[Havokdan]

Both worked, used the H264 version. I've never used these encoders before, I was surprised by their speed. Just to make sure I'm not mistaking, you refer to these encoders that I highlighted in the image below?

https://i.imgur.com/KLjPCC3.png

As were the ones I used.

* I can understand a little English, but to talk I use google translator, so if something sounds incomprehensible, i am sorry.

[stax76]

--psy-rd in Staxrip is only adjustable down from the default value of 2.00. The value in x265 can be up to 5.00.

Will be fixed in the next build.

Is it possible to use x265.exe (for example 8-bit or 10-bit) instead of the multilibrary x265_ml.exe ?

It should work if you use x265_ml.exe as name and don't use incompatible switches. StaxRip will notice that it has a unknown build date but you can change the date and version with F12.


For the file below in "Single file" mode I can mux subtitles.
In "file batch" mode, I can't.

Bug or limitation ?


it's a limitation, please create issue/ticket for it

I think going to Help -> Support forum should point here and not in videohelp.com forum

I'll show both and add some other things to the help menu.

Is there any automatic cropping available yet when using VapourSynth?

unfortunately no, please create issue/ticket for it

[NikosD]

@Stax76

It seems that you have some interesting options for decoder using NVEncC, like ffmpeg DXVA2 and QuickSync.

Is it possible to add those to VCEEncC too ?

[Pengaban]

Hi guys,

just wanted to give a quick feedback on the NVENC error. My educated guess was right about the GPU RAM Type. I just swapped the GT630(DDR3) with the GT640(GDDR5) without changing anything on the software side and it worked like a charm with the 347.52 driver. Remember the GPU cores are the same on the two cards both GK208. Maybe this is something worth to mention anywhere in the documentation?

Done some quick&dirty test on a FullHD.ts(variable bitrate ~9MBit/s) file recorded from SAT TV. I got ~33 fps with NVENC H.264(Mode:CQP standard) compared to 3,x fps with x264 on the same old system(Athlon64 x2 DualCore 2GHz). OK x264 at "medium" settings managed to get a 50% smaller file compared to the original .ts as NVENC only managed a ~20% reduction. But I think room to improve on that.

Looking forward to Nvidia Pascal and some lowend GPUs with enhanced NVENC support.

[NikosD]

My educated guess was right about the GPU RAM Type. I just swapped the GT630(DDR3) with the GT640(GDDR5) without changing anything on the software side and it worked like a charm with the 347.52 driver.


That is really strange.

Are you 100% sure your GT630 is not a Fermi card ?


Done some quick&dirty test on a FullHD.ts(variable bitrate ~9MBit/s) file recorded from SAT TV. I got ~33 fps with NVENC(Mode:CQP standard) compared to 3,x fps with x264 on the same old system(Athlon64 x2 DualCore 2GHz).


That is really slow!

Did you try to choose as decoder the CUVID decoder of latest StaxRip versions ?

It should be a lot faster than your CPU (SW) decoder.

[Pengaban]

That is really strange.

Are you 100% sure your GT630 is not a Fermi card ?

.

I'm pretty sure, I checked it with GPU-Z(still got both screenshots on my tablet). As far as I know GPU-Z only reads out the BIOS information so there might be small chance for disinformation here. I never changed the BIOS on those cards myself. But on the other hand I remember exactly when I bought this very GT630 / 640 GPUs because at that time I wanted a power efficient replacement for some stone aged onboard GPUs. I got information about a newer generation of low end GPUs from NV at that time that used small & efficient mobile Chips(GK208).
So finally the power draw of the whole system was about equal with the GT630 in place compared to the old onboard GPU.


....
That is really slow!

Did you try to choose as decoder the CUVID decoder of latest StaxRip versions ?

It should be a lot faster than your CPU (SW) decoder.

Ok I will have a look on that, so there might already be a much faster encoding in place also for the older first gen. NVENC H.264 cards?

Is this "CUVID" an new ecoding "Mode" from the NCENC encoder?

[NikosD]

Ok I will have a look on that, so there might already be a much faster encoding in place also for the older first gen. NVENC H.264 cards?

Is this "CUVID" an new ecoding "Mode" from the NCENC encoder?

No.
CUVID has nothing to do with encoding.

CUVID is a fast HW decoder in order to accelerate the transcoding process (decoding+encoding)

Because you decode the clip with your very slow CPU which is slowing down the whole process and your NVENC (HW) encoder, which is faster than your CPU.

[Pengaban]

No.
CUVID has nothing to do with encoding.

CUVID is a fast HW decoder in order to accelerate the transcoding process (decoding+encoding)

Because you decode the clip with your very slow CPU which is slowing down the whole process and your NVENC (HW) encoder, which is faster than your CPU.

Is that decoding switch at the advanced tab of the NVENC encoder, I think I tried that yesterday and it got me an error that it didn't found QuickSync on my sys. Obviously cause its a stone aged AMD athlon 64 and no newer Intel CPU with QuickSync support.

[NikosD]

Yes, that switch.
You have to select the NVEnc cuvid decoder.

Tell us your results on the same clip and settings.

[Pengaban]

I tried "NVEnc cuvid" decoder with StaxRip x64 : 1.3.1.7(testbuild -> StaxRip_x64_2016-02-07_test.7z) and got that error.

------------------------------------------------------------
Error Encoding using NVEncC
------------------------------------------------------------

Encoding using NVEncC failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code....



Maybe a newer Geforce driver needed?


Edit: The same error code with AviSynth/VapourSynth used as decoder instead of "NVEncC cuvid".

[NikosD]

Your StaxRip test build is not the latest, find the link from the first page of this thread.

I have told you at least 2 times to upgrade your driver, but you preferred to upgrade your HW in order to avoid updating your SW!

That's a very rare behavior and sorry I can't help you more than this.

I can't do the update for you.

[luigizaninoni]

It should work if you use x265_ml.exe as name and don't use incompatible switches. StaxRip will notice that it has a unknown build date but you can change the date and version with F12.


Works fine, thanks

[Magik Mark]

Stax

Is it possible to incorporate audio channels greater than 6?

[stax76]

Is it possible to incorporate audio channels greater than 6?

It depends on if there are tools which support it.

It seems that you have some interesting options for decoder using NVEncC, like ffmpeg DXVA2 and QuickSync.

Is it possible to add those to VCEEncC too ?

I hope it's just a little bit copy and paste, next build allows m2ts files as subtitle source file for mkv muxing.

[NikosD]

I hope it's just a little bit copy and paste



Then you could put the ffmpeg DXVA2 option to QSVEncC too.

It would be interesting to test the performance and the compatibility of the different decoders on Intel hardware.


Next build allows m2ts files as subtitle source file for mkv muxing.

Thanks, I'll try it.

[NikosD]

Two suggestions for the first page of this thread:

The phrase "AMD/Intel/NVIDIA GPU encoding" could be rephrased as "AMD/Intel/NVIDIA HW encoding" because GPUs do so little or nothing these days for the encoding, so HW encoding is more accurate, I think.

The phrase "Intel Quick Sync H.264 encoding" should be "Intel Quick Sync H.264/H.265 encoding" because you have already added H.265 GUI for QSVEncC.

[Yups]

Two suggestions for the first page of this thread:

The phrase "AMD/Intel/NVIDIA GPU encoding" could be rephrased as "AMD/Intel/NVIDIA HW encoding" because GPUs do so little or nothing these days for the encoding, so HW encoding is more accurate, I think.



On Intel its GPU is a big factor for encoding, in quality and performance as well.

[NikosD]

Yes, but even on Intel there is a mode for Skylake to completely isolate GPU from encoding.

For Nvidia and AMD, GPU has zero impact on both performance and quality.

[Yups]

Yes, but even on Intel there is a mode for Skylake to completely isolate GPU from encoding.



This mode doesn't make sense because the quality is very poor and performance can be slower as well. The GPU has a big impact for the quality of Intels Hybrid encoding. It's just a power saving mode which is useless for most people.

[NikosD]

OK...But StaxRip is an app that leverages HW encoding for all brands AMD/Nvidia/Intel.

And HW encoding includes even GPU without explicitly referring to it.

It's a more accurate term in my opinion.

[legend]

Using 1st time I got this message

http://s24.postimg.org/fyuzcgvn9/staxrip.png

My log File

http://pastebin.com/g4yvcZWN


How can I solve this problem.

[stax76]

@legend

Looks like AviSynth+ x64 isn't working, to verify this you can try to open the avs file generated by StaxRip with VirtualDub x64.

I see this error very often, any idea what could have damaged the setup?

[Lupissimo]

After downloading Staxrip 64 ( or 32bit ) I just copied the downloaded files to C:\ . After creating a link to desktop I started the program and assinged the default directory. When trying to drop a file to encode into Staxrip, this is no longer possible.
Could someone please post the correct "installation" procedure ( any security settings, administrator rights etc.).

[stax76]

After downloading Staxrip 64 ( or 32bit ) I just copied the downloaded files to C:\ . After creating a link to desktop I started the program and assinged the default directory. When trying to drop a file to encode into Staxrip, this is no longer possible.
Could someone please post the correct "installation" procedure ( any security settings, administrator rights etc.).

better use a folder with full write access, there are like +100 exe and dll files included, who knows if all of them work correctly in a folder without full write access.

[stax76]

new test build (1.3.3.1 - 2016-03-14) with lot's of changes...

Download

https://drive.google.com/folderview?id=0B-gPKiJYuKuIRGUxckdyQU5DUkE&usp=sharing

http://1drv.ms/1OqPDOe

New Features


support for 3 or more audio tracks added to the muxing dialog
code preview added to filters menu and script preview renamed to code preview in script editor
added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments
yadifmod2 plugin for AviSynth added
TComb AviSynth plugin added
auto crop plugin replaced with new internal routine supporting both AviSynth and VapourSynth
better subtitle support for m2ts container
decoding options added for AMD encoder
larger x265 custom command line TextBox
x265 new switch added --rc-grain
the encoding options dialogs for x265, AMD, Intel and NVIDIA have now an option to display the full command line


Fixed Bugs


fixed window freeze in eac3to dialog happening when eac3to fails on the input.
fixed showing filter selection dialog even if the source is vpy or avs
fixed StaxRip trying to auto correct the script even if the source is avs
fixed StaxRip recalculating the video bitrate even when the fixed bitrate option is used
avi muxer supports two audio tracks now
in some cases the two audio output file paths were identical
moving subtitles up and down wasn't working correctly
the new mp4box update should fix a bug many people reported
fixed editing dates in apps dialog not working with Persian calendar
fixed crash using ' character in file paths using VapourSynth
fixed inaccurate right and bottom magnifiers in crop dialog
removed one x265 switch that was accidentally added twice :-)


Tweaks


better error handling when the source is vpy or avs
when loading an audio file without language info the language of the audio profile/stream stays instead of being changed to undetermined
improved changelog
cutting with VapourSynth is now possible without AviSynth being installed (the audio cutting code was using AviSynth)
The info in the preview looks better and is readable regardless of the current background
source filter preferences in the settings dialog under Source Filter to configure which source filter should be used for a given file in case the source filter in the project is called Automatic is now also available for VapourSynth, with this VapourSynth support in StaxRip should be on par with AviSynth support making both scripting engines first class citizens
x265 tune grain defaults updated
improved bitrate calculation
The media info dialog shows the file size now also in mega byte instead of giga byte only
removed ffmpeg writing long build info to the log file


Updated Tools


mp4box 0.6.0
QSVEncC 2.37
x264 2665
AVSMeter 2.1.6
fmtconv 18
ffmpeg 2016-03-10
x265 1.9+88

[JohnLai]

If I am not mistaken, in order to use ffmpeg DXVA, one must adds -threads 1 in front of -input;

ffmpeg -hwaccel dxva2 -threads 1 -i INPUT

No idea when this -threads 1 was implemented......every compiled ffmpeg after december 2015 seems to require it.
Stax~~~~, did you add -threads 1 accordingly?

[stax76]

the dialog has a feature to show and copy the command line, as example a generated command line looks like this:

D:\Projekte\GitHub\staxrip\bin\Apps\ffmpeg\ffmpeg.exe -threads 1 -hwaccel dxva2 -i D:\Temp\Video\Clips\twk.mkv -f yuv4mpegpipe -pix_fmt yuv420p -loglevel error - | D:\Projekte\GitHub\staxrip\bin\Apps\QSVEncC\QSVEncC64.exe --cqp 24:26:27 --input-file D:\Temp\Video\Clips\twk.mkv --output-file D:\Temp\Video\Clips\twk_temp\twk_new_out.h264

what the latest build also does it encloses quotes in paths only if necessary

it encodes a while but then shows an error:

av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe

[NikosD]

Haven't tested yet your new build, but you could try latest QSVEncC v2.39 which has fixed many stability issues.

[NikosD]

added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments


Tried it with QSVEncC but I didn't see any new dialog showing up.

Can you give an example of a dialog hidden so far ?

Also, why not put it by default to show all dialogues ?


better subtitle support for m2ts container


Fixed for my m2ts files - Thanks!


decoding options added for AMD encoder


...and Intel encoder too


the encoding options dialogs for x265, AMD, Intel and NVIDIA have now an option to display the full command line


You have also added a "Search" field in Intel encoders GUI for easily find some switches in the GUI.



it encodes a while but then shows an error:

av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe



That error is visible even with latest QSVEncC v2.39, I've sent an email to rigaya


NEW BUG:


When QSVEncC decoder is selected in Intel encoders GUI, the "Execute Command Line" no longer works due to incomplete command sent (missing QSVEncC path)


QUESTIONS:


1) What is the "iv" subtitle language abbreviation automatically added in Options -> Subtitles -> Auto load subtitles ?

2) Have you put by default the --avqsv switch to QSVEncC app when using NVEncC and VCEEncC decoders ?

Because it doesn't show up when "Show command line" is pressed, but from the transcoding process it is clear that --avqsv is used (very low CPU usage) even in my system which has no Nvidia/ AMD card.


SUGGESTIONS:


1) VCEEncC as a decoder can't be used by Intel encoder or even AMD encoder because VCEEncC has no HW decoder implemented.
AMD has no API for decoding yet.

You could remove them from decoder option of Intel H.264/H.265 and AMD H.264 encoders GUI without harm.


2) In Tools -> Apps -> QSVEncC description you could add H.265 and MPEG2 encoding


3) You could add Intel MPEG2 encoding in first page description of this thread, too.


4) The "search" field in Intel encoders GUI is useful and I suggest to highlight the options selected in red color.

Grey is not easily distinguished from black.

Also, -profile and -level switches seem to not be highlighted when selected.

The -scenechange switch is not highlighted and missing completely from the GUI.


5) The "MPEG2" encoding GUI for Intel encoder is missing from the templates.

Also, the encoding mode "ICQ" is not valid for MPEG2 encoding.

I have asked rigaya to send me the list of valid encoding modes for Intel MPEG2 encoding and put them in help.txt, too.

BTW, there is a very useful command in latest QSVEncC versions called --fallback-rc

When an encoding option is selected that is not supported by the platform (like ICQ for MPEG2 or LA-ICQ for H.264 on older CPUs like Sandybridge/ Ivybridge) then the app instead of stopping, it automatically falls back to a compatible encoding mode.

I tried it for ICQ in MPEG2 GUI and it works. It falls back to CQP.

Maybe you could add it somewhere as an option probably enabled by default.


6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

[NikosD]

Regarding the error using ffmpeg dxva2, rigaya replied that it's not his app message.

So, it should be ffmpeg's.

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

[TalasNetrag]

When opening the muxing dialog for the audiotracks, the window has the wrong size when the audio tab was already selected.

http://www.mediafire.com/download/7f5sw0b76pi2sgw/StaxrRip_resize_issue.mp4

[stax76]

When opening the muxing dialog for the audiotracks, the window has the wrong size when the audio tab was already selected.

http://www.mediafire.com/download/7f5sw0b76pi2sgw/StaxrRip_resize_issue.mp4

I don't see it due to different DPI scaling, please try the build I've just uploaded.

added a command line switch -show-dialogs:bool and project option 'Show all dialogs when invoked from CLI', by default dialogs are not shown when StaxRip receives CLI arguments

Tried it with QSVEncC but I didn't see any new dialog showing up.

At the moment it affects the demuxing and filter selection dialog I believe, those should be hidden by default when StaxRip is started with CLI parameters.

Also, why not put it by default to show all dialogues ?

I'm not sure what is more important.

You have also added a "Search" field in Intel encoders GUI for easily find some switches in the GUI.

I think it was hidden in case < 20 switches (it's the same dialog for all more recent encoders)

When QSVEncC decoder is selected in Intel encoders GUI, the "Execute Command Line" no longer works due to incomplete command sent (missing QSVEncC path)

fixed

1) What is the "iv" subtitle language abbreviation automatically added in Options -> Subtitles -> Auto load subtitles ?

it's in the help ;) (right click label to show tooltip as message (task) dialog or press F1)

I use the languages defined in the .NET framework added with some mapping, iv is .NET's invariant culture for which I mapped 'und' as three letter code.

Have you put by default the --avqsv switch to QSVEncC app when using NVEncC and VCEEncC decoders ?

Because it doesn't show up when "Show command line" is pressed, but from the transcoding process it is clear that --avqsv is used (very low CPU usage) even in my system which has no Nvidia/ AMD card.

When it's not shown than it's not used for encoding because it's the same routine, maybe it's not needed and HW decoding is used automatically, in this case I will remove it.

1) VCEEncC as a decoder can't be used by Intel encoder or even AMD encoder because VCEEncC has no HW decoder implemented.
AMD has no API for decoding yet.

You could remove them from decoder option of Intel H.264/H.265 and AMD H.264 encoders GUI without harm.

removed

2) In Tools -> Apps -> QSVEncC description you could add H.265 and MPEG2 encoding

added

3) You could add Intel MPEG2 encoding in first page description of this thread, too.

I added it to the local md (markdown) file so with the next source code commit it will show on github, as for the first page it's based on the markdown file but only updated from time to time using a markdown to bbcode converter.

4) The "search" field in Intel encoders GUI is useful and I suggest to highlight the options selected in red color.

It uses the color of your windows os customization, here it's green atm, this color is used in StaxRip often

Also, -profile and -level switches seem to not be highlighted when selected.

I've fixed it but controls currently hidden are still in the list, it would be some work to change, maybe not worth it, I've added a message for this case: 'Option is hidden by other option.'

The -scenechange switch is not highlighted and missing completely from the GUI.

it's only visible for avs/vs decoder

5) The "MPEG2" encoding GUI for Intel encoder is missing from the templates.

It's maybe not important enough to add a profile but users can make their own profile.

Also, the encoding mode "ICQ" is not valid for MPEG2 encoding.

fixed

BTW, there is a very useful command in latest QSVEncC versions called --fallback-rc

When an encoding option is selected that is not supported by the platform (like ICQ for MPEG2 or LA-ICQ for H.264 on older CPUs like Sandybridge/ Ivybridge) then the app instead of stopping, it automatically falls back to a compatible encoding mode.

I tried it for ICQ in MPEG2 GUI and it works. It falls back to CQP.

Maybe you could add it somewhere as an option probably enabled by default.

but then users might not notice incompatible settings, it would also clutter the command line, the GUI already hides incompatible options.

6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

added

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

I've updated it now for all three codecs.

New build is online.

[JohnLai]

Regarding the error using ffmpeg dxva2, rigaya replied that it's not his app message.

So, it should be ffmpeg's.

Now, about MPEG2 encoding modes, we can run --check-features in order to see which encoding are available.

T_T.....nobody read my post on ffmpeg dxva requiring "-threads 1" after december 2015?

[NikosD]

I think you didn't read Stax76's reply :)

He has already said that the app uses the -thread 1 switch as you can see above in his reply, which I can confirm too.

[TalasNetrag]

I don't see it due to different DPI scaling, please try the build I've just uploaded.
The new build works fine.

[NikosD]

I downloaded your latest beta from the same link.

Here they are my comments:


I've fixed it but controls currently hidden are still in the list, it would be some work to change, maybe not worth it, I've added a message for this case: 'Option is hidden by other option.'


The issue here is that -profile and -level are always available for all three codecs and for all four decoders (avisynth, qsv, nvencc and ffmpeg dxva2), because decoders have nothing to do with profiles and levels.

Somehow the app thinks that only for avisynth those switches should be available, which is not true.



but then users might not notice incompatible settings, it would also clutter the command line, the GUI already hides incompatible options.



OK, it seems that you did the job and GUI truly hides the incompatible options, but it doesn't work for all cases.

For example, if you own a SandyBridge or IvyBridge the H.264 GUI options are the same like Haswell, but in reality they are less than Haswell or newer CPU.

How are you going to hide dynamically the GUI options based on CPU/ GPU architecture ?
It's not possible, you have to use MediaSDK programming.

Also, don't be afraid of users not noticing incompatible settings because the CLI message of QSVEncC is in yellow and warns clearly the user that the encoding mode he selected is not compatible and that it has to fall back to another one, mentioning that too.

You have to test it for yourself in order to understand the message better, but I can assure you it is clear.



6) In Tools -> Launch, I think it would be useful to automatically add as an argument the source file already loaded for mkvinfo GUI

added


For me it tries to open the app but it crashes immediately.


Quote:
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe


Do you have any idea how that could be fixed ?


SUGGESTION:

The decoders should have the same names for all HW GUIs.

NVEncC decoder -> NVEncC CUVID

QSVEncC decoder -> QSVEncC QSV

[NikosD]

One last think I forgot:

QSVEncC has a newer version than the one included, v2.39

[stax76]

The issue here is that -profile and -level are always available for all three codecs and for all four decoders (avisynth, qsv, nvencc and ffmpeg dxva2), because decoders have nothing to do with profiles and levels.

Somehow the app thinks that only for avisynth those switches should be available, which is not true.

There was a bug, I rewrote half of the list/search code, should be perfect or close now!


OK, it seems that you did the job and GUI truly hides the incompatible options, but it doesn't work for all cases.

For example, if you own a SandyBridge or IvyBridge the H.264 GUI options are the same like Haswell, but in reality they are less than Haswell or newer CPU.

How are you going to hide dynamically the GUI options based on CPU/ GPU architecture ?
It's not possible, you have to use MediaSDK programming.

Also, don't be afraid of users not noticing incompatible settings because the CLI message of QSVEncC is in yellow and warns clearly the user that the encoding mode he selected is not compatible and that it has to fall back to another one, mentioning that too.

You have to test it for yourself in order to understand the message better, but I can assure you it is clear.


you are right, I've added it and enabled it by default

For me it tries to open the app but it crashes immediately.

what crashes and how?


av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe
Do you have any idea how that could be fixed ?


it comes from ffmpeg, the code is on github so it's easy to search in the code:

https://github.com/FFmpeg/FFmpeg/search?utf8=%E2%9C%93&q=av_interleaved_write_frame

you could try to contact the ffmpeg people, maybe wait until I add hw decoding support for x264 and x265 encoding

The decoders should have the same names for all HW GUIs.

changed to:

NVEncC (NVIDIA CUVID)
QSVEncC (Intel Quick Sync)
ffmpeg (DXVA2)

QSVEncC has a newer version than the one included, v2.39

done

new build is online, I think for today it's enough. :)

[NikosD]

Excellent release!


what crashes and how?


When I select a .mkv file as source and then go to Tools -> Launch -> mkvinfo GUI then StaxRip tries to open mkvinfo GUI but closes instantly, it crashes.

The same procedure with no source selected or other container selected (like .m2ts or .mp4) it opens mkvinfo GUI without problem.

So, the bug has something to do with the .mkv file as argument in mkvinfo GUI app.



it comes from ffmpeg, the code is on github so it's easy to search in the code:

https://github.com/FFmpeg/FFmpeg/search?utf8=%E2%9C%93&q=av_interleaved_write_frame

you could try to contact the ffmpeg people



I wish I could debug that code, but I can't.

My question is this:

Is it a problem for Intel encoder only or Nvidia/ AMD has the same problem too, using ffmpeg dxva2 as a decoder ?



maybe wait until I add hw decoding support for x264 and x265 encoding



That could be interesting, but putting a very fast HW decoder to pipe the output to a very slow SW encoder like x264 or even worse x265, I'm not sure it will be that effective.

Probably only "ultrafast" setting of those SW encoders could benefit from a HW decoder.

Unless you mean H.264 & H.265 HW encoders.



changed to:

NVEncC (NVIDIA CUVID)
QSVEncC (Intel Quick Sync)
ffmpeg (DXVA2)



According to Intel, Quick Sync is one word QuickSync :p


new build is online, I think for today it's enough. :)

It's more than enough!
Thanks again!