This tweet has a screenshot. Voukoder appears as a render format in Vegas.
Thanks Nick. I'm assuming during installation it then puts some DLL files etc in a specific Vegas folder and then Vegas recognizes them and they show up as render options in Vegas?
This tweet has a screenshot. Voukoder appears as a render format in Vegas.
Thanks Nick. I'm assuming during installation it then puts some DLL files etc in a specific Vegas folder and then Vegas recognizes them and they show up as render options in Vegas?
@Rednroll I don't know specifically how it will work but from that screenshot it seems you would choose "Voukoder" as the render format then click something in the custom render settings dialog to get into Voukoder's dialog where you would choose the codec and settings.
Note that HappyOtterScripts can render with some of the 3rd-party codecs that Voukoder offers, with the advantage that you can do AviSynth processing on the way. The downside is that it renders via Frameserver, so Vegas integration is not as tight as an app that can show up as a Vegas render format.
This tweet has a screenshot. Voukoder appears as a render format in Vegas.
Thanks Nick. I'm assuming during installation it then puts some DLL files etc in a specific Vegas folder and then Vegas recognizes them and they show up as render options in Vegas?
@Rednroll I don't know specifically how it will work but from that screenshot it seems you would choose "Voukoder" as the render format then click something in the custom render settings dialog to get into Voukoder's dialog where you would choose the codec and settings.
Note that HappyOtterScripts can render with some of the 3rd-party codecs that Voukoder offers, with the advantage that you can do AviSynth processing on the way. The downside is that it renders via Frameserver, so Vegas integration is not as tight as an app that can show up as a Vegas render format.
Yes, "Voukoder for Vegas" is using the FileIO SDK and will work like any other renderer / exporter by just using "Render as ...". The most important thing is that no frameserver is necessary. You don't need to chain a bunch of tools and scripts together to do your export.
The installation requires two steps:
Install the "Voukoder Core" package. This is the open source component and contains the main functionality.
The "Voukoder for Vegas" connector. It connects vegas to the core component. There will be connectors for other NLEs available too.
I hope I can release a beta / test version soon. I am waiting for feedback from Magix currently. They are testing it right now.
Yes, "Voukoder for Vegas" is using the FileIO SDK and will work like any other renderer / exporter by just using "Render as ...". The most important thing is that no frameserver is necessary. You don't need to chain a bunch of tools and scripts together to do your export.
The installation requires two steps:
Install the "Voukoder Core" package. This is the open source component and contains the main functionality.
The "Voukoder for Vegas" connector. It connects vegas to the core component. There will be connectors for other NLEs available too.
I hope I can release a beta / test version soon. I am waiting for feedback from Magix currently. They are testing it right now.
Thank you very much!I'm looking forward to the good news!
This is a problem I was trying to figure out due to feedback that the encoders built into Vegas can be less than stellar, where many of the open source encoders have been reported to be much better, where I was just looking into ways to achieve using some of those open source encoders. So your timing is perfect for me and am very excited to try this.
The approach of voukoder is very interesting and it would add additional codecs and features to VEGAS. I think that Magix sees the same advantages and is therefore interested in supporting it.
BUT! Please do not underestimate the legal issues. I had similar issues in my VEGASpython project. The licenses of some solutions and service that I wanted to integrate did not allow the integration into commercial software like VEGAS, therefore I did not use them. Checking all different licenses of all components that can be involved is a very heavy job.
Therefore Magix is doing absolutely right in first checking the licenses of all components that will be integrated into VEGAS by using Voucoder. Otherwise they can get into severe problems.
From license point of view it is a big difference if you only use a tool as it is, as Happy Otter Scripts is doing, or if you integrate the components as DLLs (Dynamic Linked Libraries) into the software.
So, please be patient. And if Magix comes to the conclusion - what I not hope - that it is legally not possible to integrate VouCoder into VEGAS , then we have to accept this.
Voukoder is now open for Magix Vegas Pro 17 , i read this message on the forum Voukoder:
As today is a special day - actually it is my birthday - I think it's a good reason to give out the first public test version of the Voukoder for Vegas plugin. As I said, it is a first test version. Many things might not working properly , so if you notice anything wrong please report it to the forum here: Magix
What is the main reason to use the voukoder rendertemplate?
I downloaded it and used it on laptop and desktop. Working good. This is my experience on desktop Rendering a 4K HEVC 50p file(project) of 60 seconds length gives a HEVC file of 174 MB and rendering takes 345 sec.=5,75 x realtime. Rendering that file with a customized bitrate gives with the Magix HEVC codec a file of 171 MB and takes 83 sec.=1,38 x realtime