latest ffmpeg has now the hardware amd amf encoder hevc_amf and h264_amf and there is a update to vp8/vp9 codec that includes alot of optimizations, am unsure which the current shotcut uses but newer versions of libvpx since 1.6.1 included multi-threading which is pointless not to include in a video editing application…
The latest release of Shotcut (18.01.02) uses FFMpeg version 3.2.0. We update it from time to time when there is a compelling reason do to so, but not with every release so that we can maintain some level of stability.
Shotcut has supported multi-threading encoding for years. On the “Export” panel, click on the “Codec” tab and set the “Codec threads” to whatever you like. The default is “0” which will cause Shotcut to automatically select the number of threads (usually equal to the number of processors).
also can you look into why “pix_fmt=yuv420p” does not apply when saving it in a export profile? everytime i have to manually do it, its soo annoying here is my workflow until shotcut gets a modern ffmpeg version
edit in shotcut
export via profile to 1080p y4m yuv4mpegpipe wrapped_avframe (pix_fmt=yuv420p)
Oh. I see what I was missing. I didn’t realize that a new parameter was required in FFMpeg. I assumed that the new feature you were looking for would be used automatically by libvpx regardless of what FFMpeg version was calling it. Sorry for the goose hunt.
A couple of suggestions for you:
Check that the change you are looking for is in FFMpeg 3.4 (That is the version we would probably go to next)
Try the same command as above, only using FFMpeg instead of vpxenc.exe.
That way you will know for sure that when Shotcut gets an upgraded FFMpeg it will work the way you want.
I just want to thank the team for getting hardware encoding (AMD) working in the latest release! Fantastic. So quick. Shotcut is definitely, steadily getting more awesome every time I revisit it. I hope more people will check it out and get past the learning curve. Much appreciated.
I couldn’t find a lot of forum topics on this, but I bookmarked this a while long ago, so my thanks will be put here (hope the bump isn’t too disturbing, maybe it will let anyone watching this topic that the feature is now implemented).