Feature Request: NVENC
- Thread starter HowardD
- Start date
The windows error you were seeing is probably due to a bug in their CNVEncoderH264
If you look in the constructor you'll find some code like this
If you add this:
You'll get a better idea of what the problem is. Likely you are getting a 'your driver does not support this version' or something like that. NV_ENCODE_API_FUNCTION_LIST_VER is the macro that gets the version.
If you look in the constructor you'll find some code like this
Code:
nvStatus = nvEncodeAPICreateInstance(m_pEncodeAPI);If you add this:
Code:
if (NV_ENC_SUCCESS != nvStatus) {
PRINTERR("CNvEncoder::CNvEncoder() failed to load specific version of interface");
m_bEncodeAPIFound = false;
checkNVENCErrors(nvStatus);
}You'll get a better idea of what the problem is. Likely you are getting a 'your driver does not support this version' or something like that. NV_ENCODE_API_FUNCTION_LIST_VER is the macro that gets the version.
I tried build it from sample with August release and launch on my gtx 670 and now with latest drivers i have same GUID error:Geoning said:
Code:
D:\nvenc_3.0_sdk_windows\Samples\nvEncodeApp>nvEncoder -configFile=HeavyHand_1080p.txt -outfile=HeavyHandIdiot.3sec.264
>> GetNumberEncoders() has detected 1 CUDA capable GPU device(s) <<
[ GPU #0 - < GeForce GTX 670 > has Compute SM 3.0, NVENC Available ]
>> InitCUDA() has detected 1 CUDA capable GPU device(s)<<
[ GPU #0 - < GeForce GTX 670 > has Compute SM 3.0, Available NVENC ]
>> Select GPU #0 - < GeForce GTX 670 > supports SM 3.0 and NVENC
File: src\CNVEncoder.cpp, Line: 1750, nvEncOpenEncodeSessionEx() returned with error 21
Note: GUID key may be invalid or incorrect. Recommend to upgrade your drivers and obtain a new key NVENC error at src\CNVEncoder.cpp:1752 code=21(NVENC Feature not available for current license key type) "nvStatus"You can try it by your own, just download nvenc sdk from nvidia site, you can simple google it, but it seems we have to wait further updates...
gdlk said:
I am so blind... I didnt see "Samples".
I got this same error, but yes.
>> Select GPU #0 - < GeForce GTX 660M > supports SM 3.0 and NVENC
I still do not understand why ShadowPlay dont support mobile kepler o,O
Good news is that, if Jim or other coder will add nvenc to OBS, mobile GPUs will use it.
Anyway, I streamed LoL with QuickSync + GameCapture Yes! It have been fixed, and we can use GameCapture (game on nvidia) + Intel QuickSync
http://www.twitch.tv/geoning/c/3156596
Quality is really good.
720p 60fps
i5-3210m + Intel 4000 + GTX 660m
60% (50% for game) cpu or less
There was a great post at guru3d forum by the RivaTuner developer Unwinder:
http://forums.guru3d.com/showpost.php?p ... stcount=61
Maybe this could be used on OBS too?
http://forums.guru3d.com/showpost.php?p ... stcount=61
Unwinder said:
Maybe this could be used on OBS too?
Just curious for some sort of update from the devs. Are you guys looking into possibly working with it, working with it currently or are passing it aside to work on other things? I just read an article about nvidia and the encoder they have and thought of OBS so I decided to swing by to see.
LeperMessiah
New Member
Ok well shadowplay quality is awesome. The cpu usage is awesome. The hit to my framerate in game is so low its awesome as well.
I hate to sound like a prick but I find it hard to believe no one has gotten it to work yet. The guys at bandicam figured out how to implement cuda encoding before shadowplay was even released.
So when is this going to be implemented into OBS?
I hate to sound like a prick but I find it hard to believe no one has gotten it to work yet. The guys at bandicam figured out how to implement cuda encoding before shadowplay was even released.
So when is this going to be implemented into OBS?
That's not to say it will never be added. OBS Studio will have the ability to support different encoders, and if NVENC comes around to being more open and easier to use, then anybody could add it, really. It's something we're keeping our eye on but as far as I know, no one has stepped up to work on it.
LeperMessiah
New Member
WIsh I had the programming knowledge to do it lol.
The quality is incredibly good. I dont know what the percentage of users that have 600 series or higher nvidia cards is but we all have a hardware encoder sitting on our video card capable of offloading all the work to, its a shame not to use it.
Also, i thought the licensing restriction was lifted. I remember reading about that somewhere.
The quality is incredibly good. I dont know what the percentage of users that have 600 series or higher nvidia cards is but we all have a hardware encoder sitting on our video card capable of offloading all the work to, its a shame not to use it.
Also, i thought the licensing restriction was lifted. I remember reading about that somewhere.
hello.
here is a post from Unwinder, the RivaTuner's creater.
http://forums.guru3d.com/showpost.php?p ... stcount=61
It said that the main reason for ShadowPlay's low cpu usage is not the NVENC's encoder but NvFBC frame buffer capture.
It can skip the very costly DirectX frame grabber process that cost more CPU than encoder itself.
「So ShadowPlay’s success is built on two key hardware technologies: NVFBC for very effective frame capture and NVENC for very effective frame compression. BTW, NVFBC is a direct reason why ShadowPlay is not capturing video in windowed mode, if you follow the link above, you’ll see that NVFBC is able to grab whole frame buffer only.」
And NvFBC itself is free to use, so OBS can use it for another video source for free, OBS should support NvFBC at first, NVENC is only for resolution, and it is not so important for online video broadcast.
NvFBC has one main drawback that it must be used on full screen gaming, if we need windows mode grab, It well need NVIFR.
Those are only for NVIDIA's GPU.
here is a post from Unwinder, the RivaTuner's creater.
http://forums.guru3d.com/showpost.php?p ... stcount=61
It said that the main reason for ShadowPlay's low cpu usage is not the NVENC's encoder but NvFBC frame buffer capture.
It can skip the very costly DirectX frame grabber process that cost more CPU than encoder itself.
「So ShadowPlay’s success is built on two key hardware technologies: NVFBC for very effective frame capture and NVENC for very effective frame compression. BTW, NVFBC is a direct reason why ShadowPlay is not capturing video in windowed mode, if you follow the link above, you’ll see that NVFBC is able to grab whole frame buffer only.」
And NvFBC itself is free to use, so OBS can use it for another video source for free, OBS should support NvFBC at first, NVENC is only for resolution, and it is not so important for online video broadcast.
NvFBC has one main drawback that it must be used on full screen gaming, if we need windows mode grab, It well need NVIFR.
Those are only for NVIDIA's GPU.
Someone posted that exact same thing on page 3 of this same thread. He didn't say NVENC not what causes the low CPU usage, he said that NVFBC is being underappreciated as a part of the process that reduces load. But with OBS, the big CPU hog is still the encoder...OBS's game capture is really good already (maybe not as good as NVFBC but still really great) and it can capture windowed games, so the OBS load is still on the encoder.
Presumably people want to encode their whole stream with NVENC, not just their fullscreen game, so NVENC is still the thing that would be useful to add. NVFBC could be cool as a capture source, though, I suppose.
Presumably people want to encode their whole stream with NVENC, not just their fullscreen game, so NVENC is still the thing that would be useful to add. NVFBC could be cool as a capture source, though, I suppose.