Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NvencC64 NVLM #16

Closed
virvol opened this issue Oct 30, 2017 · 8 comments
Closed

NvencC64 NVLM #16

virvol opened this issue Oct 30, 2017 · 8 comments

Comments

@virvol
Copy link

virvol commented Oct 30, 2017

I have this
NVEncC64.exe --cqp 18:20:22 --codec h265 --preset quality -i M:\Video\DJI_0024.MP4 -o M:\Video\DJI_0024_temp\DJI_0024_out.h265

Error (clGetPlatformIDs): -1001
Failed to start NVML Monitoring.

NVEncC (x64) 3.22 (r663) by rigaya, Sep 23 2017 09:17:29 (VC 1900/Win/avx2)
OS Version Windows 7 x64 (7601)
CPU Intel Core2 Quad Q6600 @ 2.40GHz (4C/4T)
GPU #0: GeForce GTX 950 (6 EU) @ 1278 MHz (388.00)

How to start using this (NVML) feature?

@rigaya
Copy link
Owner

rigaya commented Nov 3, 2017

How to start using this (NVML) feature?

There is no option for this, this feature should by on by default for x64, so I'm not able to figure out why the error is caused.

NVML monitoring uses nvml.dll, which should be installed below, which should be installed with your NVIDIA Graphics driver.
"C:\Program Files\NVIDIA Corporation\nvsmi\nvml.dll"

Could you check if your system have the nvml.dll above?

Also, please check if the command line below works properly.
"C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe" -q

@virvol
Copy link
Author

virvol commented Nov 3, 2017

Here it is, all works good except nvlm feature
nvml.dll exist
1.txt

@rigaya
Copy link
Owner

rigaya commented Nov 14, 2017

NVEncC 3.24 will show the detail of the nvml initialization error, hope it helps...

@virvol
Copy link
Author

virvol commented Nov 15, 2017

NVEncC64.exe --cqp 18:20:22 --codec h265 --preset quality -i M:\Video\DJI_0024.MP4 -o M:\Video\DJI_0024_temp\DJI_0024_out.h265

Error (clGetPlatformIDs): -1001
Failed to start NVML Monitoring for "0000:01:00.0": A query to find an object was unsuccessful.

Hm... what object didnt find it? File was encoded successful...
M:\Video\DJI_0024_temp\DJI_0024_out.h265 exist and feels good)

@rigaya
Copy link
Owner

rigaya commented Nov 26, 2017

NVML Monitoring for "0000:01:00.0": A query to find an object was unsuccessful.
NVML seems to not being able to find your GPU, but I don't know why...might be environment specific.

NVML is only about monitoring GPU (getting GPU and Video Engine usage), and it does nothing with encoding itself, so you need not to worry about the output file. (it should be fine)

@pwacooijmans
Copy link

The graphic card should technically support a very very limited feature set of h265 since it's not even officially supported due to it being too old ONLY 10x0 cards support h265 encoding completely....now I do NOT know the commands to make it work for YOUR videocard but you NEED to disable HDR in the encoder.

@pwacooijmans
Copy link

now to give an example: you can ONLY reencode h264 to h265 with your card meaning 8 bits color depth and rec709 colors....so you could "try" something like:
--sar 1:1 --codec h265 --output-depth 8 --vbr 12000 --preset quality --max-bitrate 12000 --strict-gop --mv-precision Q-pel --vbv-bufsize 12000 --videoformat (the region you live in, check wiki if you want to know which is which) --colormatrix bt709 --colorprim bt709 --transfer bt709 --fullrange (only when the input video ISN'T limited in colorrange)
This is about the max you can get out of the gtx950 in video quality in h265 I think....if this doesn't work then I don't think it's even supported.

@rigaya
Copy link
Owner

rigaya commented May 24, 2019

I will close this issue, as NVML monitoring is not really critical to encoding.

"Failed to start NVML Monitoring" is only a warning message, that you may ignore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants