![]() ![]() Sure in a scenario with SW decoder + NV encoder I get far more speed. Tho, when decoder is nvdec, quality for lower profiles, from let's 480p and under is really really bad compared to those that are being decoded via SW and encoded via NVENC. ![]() Also i added -y as usual in automation in order to avoid potentially forever hanging ffmpeg, waiting for me to confirm overwrite of the output file.ĭid you manage to get nvenc and qsv running on the same machine at the same time?Īlso, yes, I'm running nvdec, nvenc and qsv on the same machine. You don't need a custom build just for utilizing QSV or NVENC, it is contained in every standard build these days. Note that i removed also -loglevel debug just in order to remove noise and also i change the ffmpeg path to the one that comes with ffastrans. was instrumental with getting the QSV version working, as I was having all kinds of headaches trying to use only VAAPI.Code: Select all %comspec% /C ""%s_ffmpeg%" -c:v h264_qsv -i "%s_source%" -c:v h264_qsv -f mp4 -y "C:\temp\%s_original_name%_1.mp4"" The only requirement on the host is that the /dev/dri device be available. The repo is here: and I have images already built if you don't want to build your own available both from my personal repository and Docker Hub.Īs an example, this is what I would run on one of my NUCs assuming that the source files are in a sub directory named src that is in my current working directory:ĭocker run -rm -device /dev/dri:/dev/dri -v $(pwd):$(pwd) -w $(pwd) /img/other-transcode:qsv-0.7.0 -eac3 -pass-dts -add-subtitle auto -burn-subtitle auto -decode all -qsv-decoder -preset veryslow src/*.mkv The advantage is you don't have to mess around with system dependencies. I didn't think of it until just now, but since you're on a Linux box, you might find the Docker containers that I make for other-transcode useful. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |