#11271: How to choose the best hwaccel?
-------------------------------------+-------------------------------------
Reporter: Mads | Owner: (none)
Johansen |
Type: enhancement | Status: closed
Priority: normal | Component:
| undetermined
Version: git-master | Resolution: fixed
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by MasterQuestionable):
͏ Interesting finding. But I don't use Windows. (though test at times)
͏ Which Windows version did you test on?
͏ What about writing the "null" output to certain actual file?
͏ (would it differ?)
͏ Also maybe it's better to time the whole transcoding task:
͏ Rather than reading speed stats. (lest potential wrong display)
\\
\\
͏ On Nvidia GPU P (Performance/Power) states:
͏
https://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/group__gpupstate.html#details
͏ .
͏ The 2 commands:
͏ `ffmpeg -hwaccel cuda -i "example.h264" -an -c:v rawvideo -f null -`
͏ `ffmpeg -hwaccel cuda -i "example.h264" -an -c:v rawvideo -f null
NUL`
͏ ; are basically identical.
͏ So probably not the real cause for the P-state switch.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11271#comment:11>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
