This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

not working nvenc ffmpeg
#1
I solve my problem that was typed here before. I just delete Cover.jpg in attached in mkv.
For now, not working nvenc ffmpeg,


-> Creating jobs for source 1,...
-> Generating calls for: C:\work\test (1)-002_new_new.mkv
Current Output: C:\work\test (1)-002_new_new.mkv
 adding NVEnc (FFmpeg) calls for source: 1
 createJobs for C:\work\test (1)-002_new_new.mkv
  creating attachment extraction subjobs
  creating video subjobs
  creating muxing subjobs
  optimizing the subJobs
-> finished creating subjobs for current source
 added new job with id 18_19_16_7210
-> should be there after processing: C:\Users\vvulpes\AppData\Local\Temp\test (1)-002_new_new_18_19_16_7210_01.mkv
starting 18_19_16_7210_01_video@18:19:16.814 - C:\work\test (1)-002_new_new.mkv
finished after 00:00:01.330
-> 18_19_16_7210_01_video crashed: ERROR: C:\Users\vvulpes\AppData\Local\Temp\test (1)-002_new_new_18_19_16_7210_01.mkv is too small! (byteSize: 0byte)
Aborting '18_19_16_7210_01_video' due to: ERROR: C:\Users\vvulpes\AppData\Local\Temp\test (1)-002_new_new_18_19_16_7210_01.mkv is too small! (byteSize: 0byte)
Job 18_19_16_7210 finished!


And i have question, how to keep or improve grain on videos? What parametres i should take ?
Reply
#2
The data you provided doesn't help at all, read sticky.
Also note that nvenc ffmpeg is marked experimental, Hybrid does not check any settings there. So if you use a feature combination that isn't supported by your hardware ffmpeg will crash.
-> On Windows better use NVEncC.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
Thumbs Up 
Okay, i get it. Thanks.

I found nvencC in program folder also in config-tools. How i need activate this to encode?
Reply
#4
Hybrid allows to use it in case:
NVEncC.exe --check-features
reports that your card can be used.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
Maybe im dummy, where to text it?
Reply
#6
Hybrid comes with NCEncC.exe in it's 64bit folder.
So if you want to see the same as Hybrid you would need to call something like
c:\Programs\Hybrid\64bit\NVEncC.exe --check-features
inside a 'Windows Command Prompt'.
My guess is that there is a problem with your driver<>hardware combination.

NVEncC has a bunch of 'Information Options':
Information Options:
-h,-? --help                    print help
-v,--version                    print version info
   --check-device               show DeviceId for GPUs available on system
   --check-hw [<int>]           check NVEnc codecs for specified DeviceId
                                  if unset, will check DeviceId #0
   --check-features [<int>]     check for NVEnc Features for specified DeviceId
                                  if unset, will check DeviceId #0
   --check-environment          check for Environment Info
   --check-avversion            show dll version
   --check-codecs               show codecs available
   --check-encoders             show audio encoders available
   --check-decoders             show audio decoders available
   --check-formats              show in/out formats available
   --check-protocols            show in/out protocols available
   --check-filters              show filters available
source: part of the output of 'NVEncC.exe --help'

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#7
Er... Yes I did it right. But problem is window open and...  closes i cannot read or do anything.  Undecided Angry
Reply
#8
You didn't open a command prompt and executed the command.
Your just executed the command.
There is a difference.
-> https://www.lifewire.com/how-to-open-com...pt-2618089
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)