Custom FFmpeg parameters will not work as I don't use an "ffmpeg.exe" with voukoder. Lots of other tools are basically GUI frontends for "ffmpeg.exe". Voukoder instead is using the libav part of FFMpeg using its C API, not the command line program.
I am still planning to add support for all/most filters available in FFmpeg and you can apply/configure/reorder them in Voukoder itself without using any command lines. I am actually working on this right now.
This is not a voukoder logo. It is the default logo of the CMS software.
Yes, you are absolutely right! Voukoder absolutely needs a logo! I have this on my lists from alomost since the beginning.
Unfortunately I am not good with this myself and I need a prefessional designer for this.
Some guy from india wanted to design a logo some months ago but the results were not very satisfying.
If you know a really good designer for creating a logo and/or corporate identity please let me know.
Released Voukoder 2.0.6
Changes:
Fixes:
Thanks to my top patrons on patreon: Gronkh
Should be fixed in the next version!
I'll look it up in the SDK documentation once I have time for this. To make it simple the video and audio settings will apply to all streams.
Is that also possible with CS6? I am using the CS6 SDK for backwards compatibility.
There was a request on twitter to extend this plugin to a standalone encoder. If i ever do that i will add multiple streams.
You could be right. I did not see any functionality to get audio data for more than one track.
In theory it is possible for voukoder to write multiple audio and also multiple video streams... even timecode streams, subtitle streams and so on. But this also requires a UI rework to manage these different stream types.
Currently this is not possible. This would be a major rework of almost everything.
NT 4.0 introduced the Windows 95 look. 3.51 still looked like Windows 3.11. I miss that style too. This was the good old time when windows was not overloaded.
I got the idea when looking at the screenshots. All of the them had the classic theme enabled.
And I spent DAYS to install a full development environment in a windows 7 VM. I still want to fix it though.
Hopefully the wxWidgets guys look into it and see if they can fix it also for the classic theme.
I was able to find a solution! The error only happens when using the "Classic Windows" desktop theme.
You can work around this with switching to the Windows 7 / 8.1 standard desktop theme.
I asked the wxWidgets forum for help: https://forums.wxwidgets.org/viewtopic.php?f=23&t=45828
I am installing Windows 7 and CS 6 now. Let's see if I can reproduce it.
Can you try this version? Its built against the Windows 8.1 SDK. Hopefully it is more compatible.
I don't think it has to do with dependencies. In that case it would always crash... not on the second attempt only. Seems i need to setup a windows 7 vm to debug this.
This is a really interesting one. The colon is used internally by FFmpeg as a separator. I somehow need to replace the separators to some very unusual values which would be a breaking change to existing settings.
Now:
profile=slow,preset=medium,x264-params=abc=def:debock=1:2:xy=z
Possible: (But it'd conflicts with the other comma separators)
profile=slow,preset=medium,x264-params=abc=def:debock=1,2:xy=z
Solution: (As a breaking change)
profile=slow|preset=medium|x264-params=abc=def:debock=1,2:xy=z
Seems I have to introduce a versioning here.
btw. This also affects other, similar options (i.e. "partitions")
I need to add the "tier" option to libx265 again.
Both of you are using windows 7, right?
