Posts by dr0

    Sadly, the thread for results posting gives me an "Access denied. You’re not authorized to view this page." message, so, I hope that's okay if I post it here.


    Previously I thought that my ancient 11-year old laptop was completely useless in terms of video editing. And it still might be so. What I recently learned and what really surprised me is that even a GeForce 310M with 512MB of DDR3 memory can significantly speed up the rendering of GPU-accelerated effects. So, looks like it is often worth enabling CUDA in Premiere Pro's project settings even with such an underpowered GPU with only 16 CUDA cores (even GTX 1050 Ti, which isn't considered to be a fast GPU by today's standards, has 768 CUDA cores).


    Timeline with a single 60-second long 720p 30fps x264 video with multiple heavy GPU-accelerated effects applied to it - CUDA - 96 seconds / 18 fps


    Timeline with a single 60-second long 720p 30fps x264 video with multiple heavy GPU-accelerated effects applied to it - SOFTWARE ONLY - 388 seconds / 4 fps


    Timeline with a single 60-socond long 720p 30fps x264 video with a single GPU-accelerated effect applied to it - CUDA - 41 secons / 43 fps


    Timeline with a single 60-second long 720p 30fps x264 video with a single GPU-accelerated effect applied to it - SOFTWARE ONLY - 99 seconds / 18 fps


    imeline with a single 60-second long 720p 30fps x264 video without any effect applied to it - CUDA - 7 seconds / 238 fps


    Timeline with a single 60-second long 720p 30fps x264 video without any effect applied to it - SOFTWARE ONLY - 7 seconds / 234 fps

    I just tried to do a multi-resolution export in AME, as was shown in this video tutorial: https://youtu.be/Er7LcrtyCBo


    It worked with built into AME H.264 CPU encoder just fine. But, when I tried Voukoder (both H.264 NVENC and a regular H.264), AME was crashing every time I started my render queue. Am I doing something wrong, or is there some kind of limitation in Voukoder / FFmpeg that prevents multiple videos from being encoded at the same time?

    javad490 you can try to decrease the Max GOP Size, say, to match your FPS value, in order to improve your seek performance. Keep in mind though that this will increase your file size.


    It's probably better to use VBR instead of CBR. I usually use CQP18 as I prefer to target quality rather than file size.


    AFAIK, GTX 1050 does not support b-frames for HEVC encoding, so you might want to stick to AVC with 3 b-frames instead.


    Your RC Lookahead is too high.


    Personally, I wouldn't use b-frames as references, especially for CQP encodes.

    It's great that they have finally added (a non-QuickSync) hardware encoding in 14.3. They have also added hardware decoding in a later release, which is also nice.


    But still, Voukoder has quite a few advantages over Adobe's solution, that I can name off the top of my head:


    1) As was already mentioned, Voukoder is more than just an HWA QuickSync/NVENC/AMF encoder for AVC/HEVC, as it supports many other codecs.

    2) As was also already mentioned, it allows for very comprehensive fine-tuning of encoding parameters.

    3) It supports older Premiere Pro versions, going all the way back to Creative Suite.

    4) It can be used in After Effects directly.

    5) It supports various non-Adobe host applications.


    I think it was the first time I actually examined it, I had it opened in Avidemux to tweak something. I was surprised to see there's only P-frames (no B-frames), which in itself isn't a big deal, but even worse, there's no additional I-frames insertion on scene changes.

    Thanks for bringing this up!

    I've been using Avidemux on and off for ages, but only now have I realized that it actually has a current frame type indicator, oh well. Now I won't have to create custom AviSynth scripts for AvsP, or set up a separate installation of MPC-HC/BE with ffdshow output module in order to examine a frame-type-structure of a video.

    The resulting YouTube video looks fine to me. QP27 seems a bit high tho. AFIAK, it is recommended to stay in the range of QP17-QP23 for optimal quality/size ratio. Since your GPU has 7th Gen NVENC, it's justifiable for you to use H.265 instead of H.264. My current GPU has a 6th Gen NVENC, so there's no point for me to use H.265 (without B-frames), since H.264, even with only 2 consecutive B-frames outputs a bit smaller files with nearly the same quality.


    These are my main H.264 NVENC settings for Voukoder and HandBrake: bf=2 preset=slow profile=high qp=18 rc=constqp


    And these are the settings that YouTube recommends to be used for uploads: Recommended upload encoding settings

    Vouk, thanks for such a quick feature update! You're the best!


    I am slightly confused though, why you ask if cineform is already supported in Adobe, has been for several years by now?

    As I mentioned in my original post, I'm still using quite dated Adobe Creative Suite 6 Master Collection, which doesn't have some of the latest features of Creative Cloud. I hadn't updated for so long mainly because CS6 does 99% of what I need, almost never crashes (unlike CC), doesn't require a subscription, and has somewhat lower hardware requirements (compared to the latest CC counterparts).

    The current Voukoder only supports encoders that can be integrated with FFmpeg. Unfortunately the FFmpeg guys decided to not implement it as it doesn't work on any other platform than x86.

    Oh, I didn't know about that. Thanks for pointing it out.

    I am currently working on the Voukoder successor that will support encoders like this one. But there are a couple of months work ahead.

    Nice! I'll be looking forward to it. Any chance that it would still be compatible with CS6?

    Hello everyone! Recently, I discovered Voukoder and was blown away by how good it works with Media Encoder CS6, After Effects CS6, and Premiere Pro CS6. So, first of all, I wanted to say thank you to Vouk for his work!


    It's great that Voukoder has ProRes support but having CineForm in addition to it would be even better in my opinion.


    I tried to encode a few videos into CineForm with VirtualDub2 and noticed that it encodes noticeably faster than ProRes and it gives even better scrubbing preformance in Pro Pro and AE. In term of file size they're close enough.