Instead I have used "-threads=8 -token-parts=3" and went to VP8 and that took the cpu usage up to being around 65% and the encoding time to around 50 minutes which is still a lot more the the 23 minutes the premiere pro H264 encoder takes. Setting a value of 4 or 5 will turn off "rate distortion optimisation" which has a big impact on quality. ![]() The help text for the webm codec says: about this: However I think using "-cpu-used=4" = not a good comparison with H264. ![]() I have been experimenting with the parameters that can be passed to the codec. Here's a close-up screenshot of the results: I made an H.264 using Premiere's encoder and VP8 and VP9 clips using the plug-in. In this case it's a 1080p clip encoded at 500 kb/s (0.5 Mb/s). ![]() Here's a test I ran: encode the same clip in the different codecs using some masochistic bit rate so you can really see the artifacts. And VP9 encoding…well, let's just say it's a lot faster than it used to be, thanks to multithreading and countless other optimizations. Today you can play VP9 in Firefox, Chrome, VLC, and other standards-compliant software. When I posted the first beta, VP9 was experimental, had hardly any application support, and was incredibly slow to encode. One thing that has been interesting to watch is how the VP9 codec has come along. And it will continue to evolve, especially as Google continues to develop their libvpx encoder. In that time the plug-in has evolved greatly based on feedback from users and from Google itself. After well over a year in public beta, today we're calling the free WebM plug-in for Premiere Pro officially released.
0 Comments
Leave a Reply. |