Beiträge von Slipduwee

    I briefly tested Voukoder 12 b6. NVENC is still loading and working with 522.25 drivers installed. 👍

    QuickSync encoders are available, too. The b6 log has more information about attempts to load them.

    Even though it says the device is GTX 1080, I've confirmed that it's actually using Intel HD Graphics 530: Task Manager screenshot

    In the screenshot, the first section of activity was an encode with hevc_nvenc and the second was the same video encoded with hevc_qsv.

    (With h264_qsv & hevc_qsv, there's no option in Voukoder to set the lookahead value when using LA_ICQ rate control method, and the value is hardcoded to just 1 frame. "look_ahead" should probably have a field in the user config.)

    And last, but not least, the "tune" option for NVENC is now configurable in Voukoder 12b6! 🥳

    It's now possible to use the encoders in true lossless mode. I did a test and it works properly. Thank you very much for adding "tune" to the config.

    Game Ready Driver 522.25 has been released. I installed it and tried 12 beta 4. The NVENC encoders supported by my GPU are available and working.

    QuickSync encoder initialization errors:

    One final thing: My question about the hevc_nvenc option "tune" that enables lossless encoding has been deliberately ignored and I acknowledge that.

    2022-09-27.log

    Code
    [12:15:38] Loading: encoders/h264_qsv.json
    [12:15:38]   FFmpeg: WARNING: defaulting child_device_type to AV_HWDEVICE_TYPE_DXVA2 for compatibility with old commandlines. This behaviour will be removed in the future. Please explicitly set device type via "-init_hw_device" option.
    [12:15:39]   FFmpeg: Using D3D9Ex device.
    [12:15:39]   FFmpeg: Error initializing an MFX session: -3.
    [12:15:39] Unloading: encoders/h264_qsv.json
    [12:15:39] Loading: encoders/hevc_qsv.json
    [12:15:39]   FFmpeg: WARNING: defaulting child_device_type to AV_HWDEVICE_TYPE_DXVA2 for compatibility with old commandlines. This behaviour will be removed in the future. Please explicitly set device type via "-init_hw_device" option.
    [12:15:39]   FFmpeg: Using D3D9Ex device.
    [12:15:39]   FFmpeg: Error initializing an MFX session: -3.
    [12:15:39] Unloading: encoders/hevc_qsv.json

    A new NVIDIA driver was released today that I haven't installed, yet. But it's 517.48 and not 520 so probably won't make a difference here.

    Repeating the question from my previous post:

    Another question: is there a way to use hevc_nvenc in lossless mode with Voukoder? When I use FFMPEG in command line, I use -c:v hevc_nvenc -preset p4 -tune lossless but I don't see a way to set the tune option. The FFMPEG options string is at the bottom of the window, but can't be edited.

    I don't know when it was last working. I haven't used QuickSync in Voukoder in a very long time, probably years.

    I went back to 11.3.2 and while hevc_nvenc works again, the QSV encoders aren't available either.

    Out of curiosity I went back to 10.0. This time QSV encoders throw an error.

    Like I said, I usually use hevc_nvenc, so I didn't notice QSV hasn't been available - possibly for a long time. I'm glad you've already solved QSV and I'll try V12 again after NVIDIA releases new drivers. Thanks for the help.

    Another question: is there a way to use hevc_nvenc in lossless mode with Voukoder? When I use FFMPEG in command line, I use -c:v hevc_nvenc -preset p4 -tune lossless but I don't see a way to set the tune option. The FFMPEG options string is at the bottom of the window, but can't be edited.

    Integrated graphics drivers were updated from 100.9955 to 101.2111. No QSV encoders are available in Voukoder

    Log file with "enable low-level logging" active. I also ran a quick export in case that might show something interesting.

    2022-09-25.log - Pastebin.com
    Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
    pastebin.com

    I see all NVENC encoders failing to initialize and the QSV encoders load, then unload.

    To confirm my system or drivers didn't somehow get messed up, I tested encoding with NVENC and QuickSync with OBS. Both hardware encoders worked properly.

    I also tested an encode using hevc_nvenc with FFMPEG itself through command line, which also worked.

    I just installed v12 beta 1 and the hevc_nvenc encoder I usually use is no longer available. All the hardware encoders, including QSV, have disappeared from the list.

    Windows 10, Adobe Media Encoder 2022, premiere-connector-1.11.1, GTX 1080, driver version 516.94

    Screenshot

    Yes, it would have been helpful if I had reported it earlier. But here's the thing: I didn't know if the failed renders were because of Media Encoder, Premiere, Voukoder or something else, and I didn't investigate the issue until a couple of days ago.

    I got around to doing tests and reading log files when I had the time and the interest, which happened to be when I tried again to render a VR video on 9.1 RC1 (I don't render VR videos often), and the problem was still there.

    You have received my bug report, which is helpful enough to pinpoint the exact cause of the failed renders, as soon as I determined the issue was with Voukoder a of couple days ago and I had time to document it for a bug report yesterday. Enjoy. ✌

    After successfully rendering and encoding VR videos with Voukoder for a while, my attempts would instantly fail starting about a month ago. I didn't put any effort into solving the issue then, but I've looked at it again recently.

    I realized that clearing the video side data fields allowed the video to render. Adding any video side data causes the render to immediately fail. Here is AME's log for a failed render attempt.

    I enabled logging in Voukoder and this is what it says on a failed render attempt. Low-level logging is enabled.

    Simply disabling all video side data options allows the render to proceed. I first noticed this issue with one of the Voukoder 9 release candidates, but I just installed 9.1 and it's still happening so I decided to report it.