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]

Originally Posted by stax76

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...ack/page5.html

[NikosD]

Originally Posted by 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?

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=6BDD43...DD4375AC8933C6


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]

Originally Posted by NikosD

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?



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]

Originally Posted by Pengaban

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 ?

Originally Posted by Pengaban

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]

Originally Posted by NikosD

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.

Originally Posted by NikosD

....
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]

Originally Posted by Pengaban

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]

Originally Posted by NikosD

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.