[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.
You might turn on low-level logging and provide the voukoder log file. There should be more info about the issue. But i guess it is an FFmpeg limitation.
shamo42 If you keep it busy, does it continue after a longer time? Maybe after 1 minute?
Lan-Na No, i need to Improve the connector to be able to select gif. It does not depend on a voukoder release.
Lan-Na Can you please stop cross-posting this in various forums, twitter and threads? I am working on it.
Steve Rhoden (Hentys) Voukoder does not need the .NET framework
I'll investigate that.
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.
You can save a preset in Premiere or create a template in VEGAS with your favorite settings. user presets in Voukoder are not scheduled yet but will most likely come with the next version.
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.
Make sure you are using the latest connector for your application(s)!
For using NVENC encoders driver version 436.15 or newer is required.
Thanks to my all supporters - especially the platinum tier patrons ValnirÆsirsson and Gronkh!
The GTX 1650 is based on the Turing architecture which does not support interlaced encoding anymore. Does it work if you deinterlace the media media and do a progressive export?
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.
So I don't get the point of including GIF export in the first place.
Does it harm anyone? Maybe there are other use cases and workflows than yours?
Nice to hear you are happy now.
Thread closed.
ffmpeg version N-96835-g177c68e Copyright (c) 2000-2020 the FFmpeg developers
built with Microsoft (R) C/C++-Optimierungscompiler Version 19.16.27032.1 fuer x64
configuration: --toolchain=msvc --extra-cflags='-MD -I/c/TeamCity/buildAgent/work/ffmpeg_nightly_release/build/include' --extra-ldflags='-LIBPATH:/c/TeamCity/buildAgent/work/ffmpeg_nightly_release/build/lib' --prefix=/c/TeamCity/buildAgent/work/ffmpeg_nightly_release/build --pkg-config-flags=--static --disable-doc --disable-shared --enable-static --enable-runtime-cpudetect --disable-devices --disable-demuxers --disable-decoders --disable-network --enable-w32threads --enable-gpl --enable-nvenc --enable-amf --enable-libmfx --enable-libvorbis --enable-libsnappy --enable-libvpx --enable-libfdk-aac --enable-libmp3lame --enable-libzimg --enable-libx264 --enable-libopus --enable-libx265
libavutil 56. 42.100 / 56. 42.100
libavcodec 58. 73.102 / 58. 73.102
libavformat 58. 39.101 / 58. 39.101
libavdevice 58. 9.103 / 58. 9.103
libavfilter 7. 77.100 / 7. 77.100
libswscale 5. 6.100 / 5. 6.100
libswresample 3. 6.100 / 3. 6.100
libpostproc 55. 6.100 / 55. 6.100
Encoder truehd [TrueHD]:
General capabilities: delay small exp
Threading capabilities: none
Supported sample rates: 44100 48000 88200 96000 176400 192000
Supported sample formats: s16
Supported channel layouts: stereo 5.0 5.1Unfortunately not.
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).
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.
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.
Because it is not the final version of version 4 yet. It is just a release candidate - a pre-release.
Plus... I am not sure if i should keep that auto update in there ...
This is not the final version 4 release. Use it on your own risk.
For using NVENC encoders driver version 436.15 or newer is required.
Please enter
%LOCALAPPDATA%\Voukoder\Logs
in windows explorer and send me the voukoder logfile.
But I guess it is that huge frame size... does it work with 4K oder FHD content?
Please be more specific and provide a logfile.
It's a bit difficult for me to override it, as it doesn't match the encoders default value. But i'll see what i can do.
FFmpeg is always a nightly build. So with every release of Voukoder you'll always get the latest version of the source code.