Posts by iAvoe

    In that case you can even skip Voukoder, just render a lossless footage and write multiple commands in a batch file (asuming you are on Windows) to use x265/x264/SVT-AV1/QAAC encoders one by one, and multiplex with ffmpeg, roughly such as:

    ::Video Encode
    ffmpeg -i "Sequence 01.mp4" -an -f yuv4mpegpipe -strict unofficial - | x265.exe --y4m - --output "v0.100.hevc"
    ::Audio Encode
    qaac64.exe --cvbr 320 -b 16 -r 44100 --threading -o "v0.100.aac" "Sequence 01.wav"
    D:\ffmpeg.exe -i "v0.100.hevc" -i "v0.100.aac" -c copy "Complete_Product.mp4"

    I remember VMAF is pretty CPU heavy (likely to be wrong), I would say leave it for a faster rendering or more compression, plus we have some decent x265 settings loaded in there already.I personally would say transport film grain optimization algorithm (FGO, by DarkShikari?) in x264 to x265 & AV1 would be a greater boost in lossy encoding quality than VMAF, though

    Looks like a color space interpretation error but I have never dealt with that, try make a new copy of this project, and then specify BT.601 instead of default BT.709 in the following 3 locations:

    Premiere Sequence Setting - Work Color Space: BT.601

    Premiere Media Export - Video tab - Color Space: BT.601

    Voukoder Configuration page - Select encoder - Side Data tab - MasterDisplay: Primaries=BT.601

    In most of cases I've seen, its the media player. I would say download mpv and check again. Btw the only video filter in Premiere (afaik) that could make that kind of color difference is "Brightness & Satuation"

    And, unless new compression methods show up, AV1 is more of a cranked up x265 with depreciated features due to slowness added back, but I could be wrong since I have not been following updates

    AV1 is still under dev, and does not provide a stable image output, and you might not able to view render results on mobile phones unless you have a good media player app. Generally not recommeded for reliability dependant workloads

    Thanks for your detailed reply

    OBS works fine

    NVIDIA Driver should be recent enough (has auto update)

    Resizable bar is not enabled

    It looks like would be VEGAS Pro, Voukoder or Connector's fault then, try replace them.

    I don't think the file system or operating system could cause this kind of error, but you can try CHKDSK, SFC and DISM commands in CMD (they have built-in help file to check for usage)


    [18:10:02] FFmpeg: Failed unlocking input buffer!: generic error (20): (Ú8

    The card was an RTX 3080 with 32GB RAM, and the error looks like came from the software


    Record with OBS, select NVENC encoder and see if recording fails

    Disable audio output (not likely to be the case)

    Or just use HEVC encoder since you've got a strong CPU for encoding tasks


    Driver was outdated;

    Second handed card that was loaded with a mining BIOS (not likely);

    Operating System build is outdated (not recorded in log);

    Resizable-Bar is enabled, try disable it;

    x264 and x65 from ffmpeg are advantageous in double pass encoding. In single pass, you already have software/native encoding in Resolve, which I consider equivalent in speed/performance.

    As far as I know only single pass is available in Voukoder yet, for SDK constraints. If you want double pass x264/x265, you may export to DNxHD in Resolve and double-pass with ffmpeg/Handbrake later.

    2 pass encoding is basically analyze how much quantization compression per frame (x264), or per block/unit (x265) in pass1, then in pass2 encoder adjust the quantization compression level more evenly. So overall you still get lower quality (and slower) than CRF mode (constant rate factor, 1 pass), if you give a higher bitrate in pass2, then you defeat the purpose of 2 pass, so at least in video production/editing phase, it's not recommended to use 2 pass at all :)

    I've never used Vegas, but I'm comfortable with simply working on multiple projects, only the "last station" being final. If you want some lossless codec (Cineform or ProRes) in intermediate rendering, in this case you won't necessarily need Voukoder; if you want lossy codec just go for exporting the whole project.

    I've created a pull request to submit the parameters, it just needs some time to be tested and updated to next/later release. Currently you need to go to Option tab, and find, apply the settings yourself :)

    Unfortunately hevc lossless does not seem to be implemented in Voukoder even though it is implemented perfectly in ffmpeg with a transcode script such as this:

    ffmpeg -i "INFILE.MOV" -c:v libx265 -x265-params lossless=1 "OUTFILE.MOV"

    x264 cannot actually achieve lossless. It's lossless setting is close but ProRes422 is generally a little better quality, faster rendering, and smaller. MagicYUV is another possible option.

    Well, if we already have hardware encoding with studio version, that doesn't nearly defeat the purpose of Voukoder? I very much appreciate Voukoder and it's a great piece of software, but except ProRes, VP9 and AV1 (which are very welcome of course and I applaud the developer), studio version already provides QuicSync H264 and H265. I have found they are faster, actually.

    In terms of quality, x264 and x265 are better than hardware solutions, because hardware solution requires money to make larger circuts that implements code the software solution already does (if the encoder section costs under 100USD, they are no match with software encoding), the only advantage is in lossless codecs where the hardware encode runs cooler and faster.