[FFmpeg-user] ddagrab

Michael Koch astroelectronic at t-online.de
Mon Feb 20 17:12:23 EET 2023


Am 20.02.2023 um 15:50 schrieb Michael Koch:
> Am 20.02.2023 um 15:46 schrieb Gyan Doshi:
>>
>>
>> On 2023-02-20 07:58 pm, Michael Koch wrote:
>>> Am 20.02.2023 um 15:18 schrieb Gyan Doshi:
>>>>
>>>> On 2023-02-20 07:33 pm, Michael Koch wrote:
>>>>> Am 20.02.2023 um 14:54 schrieb Gyan Doshi:
>>>>>>
>>>>>>
>>>>>> On 2023-02-20 07:15 pm, Michael Koch wrote:
>>>>>>> Am 20.02.2023 um 14:29 schrieb Gyan Doshi:
>>>>>>>>
>>>>>>>>
>>>>>>>> On 2023-02-20 06:27 pm, Michael Koch wrote:
>>>>>>>>> Am 20.02.2023 um 13:50 schrieb Gyan Doshi:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 2023-02-20 06:03 pm, Michael Koch wrote:
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> I'm testing the ddagrab filter with the example from the 
>>>>>>>>>>> documentation. I did only add -t 10 -y, but that can't be 
>>>>>>>>>>> the problem.
>>>>>>>>>>>
>>>>>>>>>>> ffmpeg -f lavfi -i ddagrab -c:v h264_nvenc -cq 18 -t 10 -y 
>>>>>>>>>>> out.mp4
>>>>>>>>>>>
>>>>>>>>>>> What does this error message mean?
>>>>>>>>>>> [h264_nvenc @ 000001f5f7bbf980] OpenEncodeSessionEx failed: 
>>>>>>>>>>> no encode device (1): (no details)
>>>>>>>>>>
>>>>>>>>>> Works here. Could be a driver issue - try reverting.
>>>>>>>>>
>>>>>>>>> It did not work woth the older driver either. That's why I 
>>>>>>>>> updated the driver today.
>>>>>>>>
>>>>>>>> 1) Try older builds, say, a month or two older.
>>>>>>>
>>>>>>> Do you mean older builds of FFmpeg, or older Nvidia driver?
>>>>>>
>>>>>> Older ffmpeg builds.
>>>>>
>>>>> I will do that later.
>>>>
>>>> From System Information, what is the OS version?
>>>
>>> Windows 10 Home
>>> Version 22H2
>>> OS build 19045.2604
>>>
>>>
>>>> From dxdiag, what is the DirectX version?
>>>>
>>>
>>> DirectX 12
>>
>> Ok, don't see any obvious issues.
>>
>> One last try: run the cmd with -cq removed.
>
> same problem.

I opened ticket 10205.

Michael



More information about the ffmpeg-user mailing list