Beiträge von Joe24

  • H264 encode initial frame info incorrect

    Technically, a 1-sec GOP would be encoder Level 4.1, but changing encoder levels didn't make a difference to the results above.

    I've never had great luck with TMPGEnc Authoring Works accepting video which uses encoder Level 4.1. They say it's Blu-ray compatible, but I never found how to make it work. AW always flags the 4.1 tracks as incompatible with Blu-ray, by reason of encoder level. So I just use encoder Level 4.0, which works fine. TMPGEnc Authoring Works accepts either 1-sec or 2-sec GOPs with Level 4.0 (which should be 2-sec GOP only, according to spec).

    Lol, and as mentioned . . . TECHNICALLY, 1080p29.97 is non-compliant with Blu-ray anyway.

    In any case, all test files above were rendered using Voukoder, and therefore FFmpeg. And they all used NVENC on an Ampere card. None of my tests yielded a file with an extra leading I-frame, so this is quite clearly neither an FFmpeg issue, nor an NVENC issue.

    Zitat von avwtp

    can be produced directly using FFMEG

    If you are getting this problem even while using command-line FFmpeg, then we can also rule out Voukoder and its connector as the cause.

    If the error occurs in command-line FFmpeg across multiple framerates and encoders (you've mentioned both NVENC and x264), then there must be a problem with your encoding settings, or maybe even with your source file's encoding from Premiere.

    Out of curiosity, what are your Voukoder encode settings? And what exact command-line are you using for your FFmpeg encode?

  • H264 encode initial frame info incorrect

    Zitat von avwtp

    1) create BluRay complaint 1080p stream, with "1 sec" GOP (30 frame) for std 29.97 video.

    2) bring up SmartRender, add the clip, then in the "Format" panel click "Start Analysis". Notice it wants to render the first 2 sec. Now output the file and it creates a 61 frame GOP out of the original 3 GOPs (1, 30, 30).

    3) This re-rendered file is now not BluRay compliant.

    [...]

    if you bring up a Vouk or FFMpeg NVENC clip in SmartRender, enable "show frame status", you'll see the solitary I frame followed by the regular GOPs ... and a blank audio frame.


    I don't observe any frame-order problems with video files rendered by Vegas 20 using Voukoder/VoPro. Following the steps quoted above (except using GOP 60, which is actually the Blu-ray max for 29.97p video, and my preferred setting), the first few frames of the video are as follows, starting with frame 0: IBPBP.

    Switching to your setting of GOP 30, Smart Renderer now wants to re-encode most of the video file for whatever reason (see screenshot). But the frames still remain in the correct order (IBPBP), with no extra I-frame. I assume you have a reason for rendering as GOP 30, so I'm not going to address that.

    Tested some 1080p23.976 GOP 48 renders, and they cause no problems either.

    I suspect, as stated before, that your problem may lie with Premiere or your settings therein. AFAIK, FFmpeg just encodes whatever frames it's fed.

    See screenshots below. TMPGEnc Smart Renderer 6 doesn't complain about the video stream at all using GOP 60.

    These files were encoded using Vegas Pro 20 build 411, Voukoder 13.3, connector 1.7.1, NVENC h.264. I modified a preset I normally use for Blu-ray encoding, just changing frame rate and GOP size. Normally I run 1080p23.976 GOP 48 which is fully Blu-ray-compatible.


    GOP 60:


    GOP 30:

  • H264 encode initial frame info incorrect

    I've done plenty of TMPGEnc disc work with NVENC renders from Vegas/Voukoder/VoukoderPro/FFmpeg, and have never seen this. If FFmpeg itself was introducing errors, you'd think I'd have had this problem too... Which makes me wonder whether your issue might be with Premiere or the settings there-in? Or maybe even your I/B-frame settings in Voukoder/FFmpeg? Just my 2 cents.

  • Problème bitrate VP9

    Zitat von georgeschris

    Is a Nvenc VP9 version a possibility?

    Sure... if and when Nvidia builds a GPU that includes a VP9 encoding engine! So far they haven't done that.

    NVENC is hardware (a special module in your GPU), and not a software program. You can only use NVENC to encode the formats that the physical chip was designed for. So you can't retroactively add NVENC VP9 support to an existing GPU.

    Currently, NVENC supports formats: h.264, h.265, and AV1 (on 40-series GPUs).

    Nvidia NVENC - Wikipedia

  • Voukoder 13.4

    Zitat von Lan-Na

    I heard from my friend that the newer NV driver has a lot of bugs. So I haven't installed the newer NV driver. If you ask me which bug, I really can't say it.

    But I believe that many users choose a stable driver instead of a newer one.

    Sounds like some high-quality information there. 🤣🤣🤣

    The minimum NVIDIA driver for Voukoder 13.2/13.3 is v531.61, which came out in April 2023. Hardly the "newest" driver (current one as of writing is v545.92, issued Oct 26, 2023).

    Install an older driver from NVIDIA's website if you're in a panic about it. Between 531.61 and 545.92, there are around 20 different driver versions to choose from.

    I don't see a problem here.

  • VoukoderPro - Public Beta

    VoukoderPro is currently a beta version, so it has an expiry date, after which it will not work. This expiry date is extended from time to time as newer beta versions come out. I believe the final product will be a paid version.

    Voukoder classic is free.

  • Output file is not playable on Windows

    Voukoder 13.2beta4 works here. All good.

    • All NVENC-encoded files play normally, and audio is in sync.
    • Tested using the same h.264 and h.265 NVENC presets as before.
    • Tested Vegas 20 build 411 (connector 1.7.1) and Vegas 15.0 build 416 (connector 1.5.0).
    • Tested VLC v3.0.19 64-bit. Also downgraded to the same VLC v3.0.18 64-bit which I was using before, and still no problems observed.

  • Voukoder Pro - Codec H264 without Intel Quick Sync

    If you want to hardware-encode to h.264 format on an old computer, just buy a cheap video card and use the card's built-in NVENC or AMF hardware encoder (shown in your list above). Doesn't matter how old your CPU is for that.

    Or you can use the x264 software encoder, which will be very slow but should still work on older CPUs. Voukoder classic includes the x264 encoder. VoukoderPro so far does not.