Beiträge von Vouk

  • Voukoder 4 - bugged presets and/or reframes setting

    Zitat

    [23:45:36] FFmpeg: InitializeEncoder failed: invalid param (8): Invalid Level.

    It is rather the NVIDIA driver that complains about the issue. I remember we've had this issue since the first days of Voukoder. Strange that you report other version don't have this issue ...

    Unfortunately I can't do anything about it. I am always using the latest FFmpeg version.

  • GIF support

    As Voukoder is using FFmpeg internally it uses the encoders/muxers FFmpeg provides. As far as i know FFmpeg does not offer any further advanced compression functionality.

  • Voukoder 4

    Release Notes

    If you like Voukoder and especially if it helps saving time and money in your business - please consider supporting the project by paypal or on patreon. Thank you.

    I am also looking for sponsors and partners. Please contact me if you are interested.

    Important

    Make sure you are using the latest connector for your application(s)!

    Changes

    • Increased floating point values precision to 3 decimal places
    • Added animated GIF support
    • Added still image support (BMP and TIFF)
    • Added "atrim" filter to correct the audio track offset

    Fixes

    • Fixed loading the correct order of filters
    • Added low-level logfile for debugging
    • Fixed sequential exports with different frame sizes are failing
    • Showing video and audio pages only if they are selected in the NLE

    Notes

    For using NVENC encoders driver version 436.15 or newer is required.

    Credits

    Thanks to my all supporters - especially the platinum tier patrons ValnirÆsirsson and Gronkh!

    Download

    https://github.com/Vouk/voukoder/releases/tag/4

  • GIF support

    You need to disable the audio track in the exportas an animated GIF can not contain any audio tracks. I noticed this does not work with VEGAS currently. I have to fix the in the VEGAS connector.

  • 24bit TrueHD

    Unfortunately not.

  • The mystery of delayed AAC audio tracks

    Symptoms

    After importing a multitrack MP4 file - or even single audio files that you have extracted from some footage - you might have noticed something like this: Some audio tracks seem to be delayed by various milliseconds and appear to be out of sync to each other.

    On the first sight it looks completely wrong and it appears as a faulty encoder. Well, it actually fully complies with the AAC specification and is completely valid.

    If you take a closer look you notice that tracks encoded with AAC have a delay of a multiple of 1024 samples. Usually AAC encoders produces an offset of 1024 samples (or 21.33 ms at 48 kHz) and the FDK-AAC encoder adds an offset of 1024 samples per channel (like 42,66 ms for stereo at 48 kHz).

    Cause

    Each audio sample/package can be identified by a timestamp. In a 48 kHz audio file you have 48000 samples per second (or one sample is 20.83 µs long).

    When playing the file in a software- or hardware player the player syncs all streams based on their timestamps and everything should be perfectly in sync. The offsets are ignored.

    Solution?

    Lots of people asked me to add an option in Voukoder to correct the audio track shift by a certain amount of milliseconds (usually 43ms) to make it rather look like this:

    Well, it is possible to this and it can be done using FFmpegs "atrim" audio filter (which will be added to Voukoder soon) but the best solutions is to not use AAC for intermediate clips. Consider using raw PCM instead. Only use a lossy codec (like AAC) for the final file - if necessary.