The successor app will have a completely new concept and will be very flexible. Multiple tracks in, multiple tracks out. Just think about what might be possible with this.
... and please participate here: https://www.voukoder.org/forum/thread/1155
Very ambitious and flexible! I hope it's not too hard to set up and use : )
Love this!
Is this just a concept drawing to show how the program would behave, or is this what you intend the UI to look like? That's some serious heavy-hitter stuff, either way!
I'm in love, dude.
I would say cut off the entire video filter section, and remove old audio codecs that are bad in export quality. Note that many AAC audio encoders doesn't even come close to the quality from QAAC.
The reason to remove video filter section is because Premiere, After FX, Davinci-resolve are video editors with plenty of filters already.
You need video filters or we can't change the resolution or framerate from what the project is.
You need video filters or we can't change the resolution or framerate from what the project is.
I'm not sure about other editors, but the premiere export tab allows you to do exactly that
You need video filters or we can't change the resolution or framerate from what the project is
Premiere, After FX, Davinci-resolve are video editors, which means, you just Google "how to change project framerate in Premiere/After FX/Davinci-resolve".
For "Voukoder's exclusive filters", they are not as advanced as After FX, nor dedicated to fix horridenous Anime BluRays as VapourSynth filters, and not academic purposed as OpenCV.
The other reason to cut off the filtering is for the sake of focusing software development to encoders and connectors.
One more reason to cut off the filtering is for performance and multiplatform compatibility, because you don't expect these filters will be updated to work properly on newer CPUs.
Here is a PowerShell based encoding script I've created recently. The multiplexing (mux) script looks like this Image
It has to support video stream, audio stream, subtitle stream and font stream. Then do compatibility checks to determine the output format should be .mov, .mkv, or .mp4, and this is how people would expect how a "pro" software behaves. Voukoder will sooner or later run into this kind of problem.
ZitatPremiere, After FX, Davinci-resolve are video editors, which means, you just Google "how to change project framerate in Premiere/After FX/Davinci-resolve".
Well, this comes down to how Voukoder works, not how the host editing software works, and the responsibility for that is the developer, not the user. Googling won't help I'm afraid, though thank you for your suggestion.
You can't change render resolution and framerate using Voukoder in Vegas Pro without filters. The native render templates work differently from Voukoder and even other third party renderers like MagicYUV make use of that functionality If Voukoder changes how it works so it can make resolution and framerate changes without filters that's fine by me. The filters are appreciably slower than how the native templates work as well so I wouldn't miss them if I could do the same thing a different way.
Changing project resolutions can affect the formatting of different Fx (stabilization, etc.) so it's necessary to set this properly at the project stage. If you edit in high resolution you can output at lower resolutions but the converse is not true. Also if you change project settings from 4K to HD you lose the full resolution of still images or other high-resolution images which is very important if you're doing a push-in zoom or cropping them (all track based Fx work at the project resolution rather than the media resolution).
That may work different in other NLEs but this is how it works in the one that I use. I'd hate to see Voukoder become less useful and functional.
Are there any updates to multichannel audio support in the Resolve plugin?
I was hoping Voukoder would be my solution for being able to render ProRes Proxy media for editorial purposes on Windows, but the lack of multichannel audio totally shattered my hopes!
Curious about the Video Input block. Are you having any luck getting a 32-bit floating point feed from any of the supported NLEs? I'm particularly interested in Vegas but also use your plugin with Resolve Studio.
I don't have Premiere to test with but if that's i416 format, I imagine the quality is pretty good. Hopefully some of the other NLEs will come across with similar support. Fwiw, I've also been studying frameserver output into ffmpeg and qsvencc and it seems to have the same feed as you, get getting similar quality with a v210 format from Vegas.
Thanks, I gave all the options a try measuring with ffmpeg6 psnr, ssim, amd vmaf. Your hb options do make a difference. I'll send you the analysis.
