@jetdv Need some time to test, first test looks promising...many thanks again Edward...will save me a lot of time.

@jetdv After some testing, I can say your script works perfect. It renders the selected project files in batch in order as selected, a real time saver for me and probably others. Many Thanks again Edward.

Just a small improvement for me would be, if the script remembers the last used rendertemplate and renderlocation.

Next feature request: Could the generated and necessary audio peak files (.sfk) automatically be flagged as "hidden" and therefore not showing up in the mediafolders OR make a dedicated audio peak folder were those audio peak files are stored, like the pre-rendered files folder. Were you can manually decide to delete them when not necessary anymore.

@3POINT As this was just a tutorial to show 1) how to render in various ways and 2) how to use a form to collect information, it's certainly not "fully featured". The form is really not even laid out all that well! And, yes, many additional features could be added.

By default, I'm showing that it's only showing VEG files when selecting the projects to render. As for the output files, the script has nothing to do with files such as the .sfk files. VEGAS creates those automatically and I have no control over the location. Could the script then "look" for the sfk file and mark it as "hidden"? I'm going to say yes but then what if you later deleted the renders but forgot about the "hidden" files? You'd slowly fill up your drive with unwanted .sfk files. And, no, they can't be put in a separate folder or VEGAS would just create them again if you loaded the file to the timeline. All of that is automatic by VEGAS. I suppose the script could look for them and then delete them after the render was complete.

Could we have a way of setting which renderer is the "default" one? Absolutely. Right now it's just showing the "first" one that it finds when reading all renderers. What *is* your default renderer? For example, if you want one of the Magix AVC ones, just type MAGIX AVC in the box before clicking on the dropdown arrow. If you want one of the Magix HEVC ones, just type MAGIX HEVC in the box before clicking on the dropdown arrow.

Yes, I understand that's not exactly what you're asking for. But maybe we can create some new tutorials to add some more features to this script. So we need to come up with a list of practical features that can be added to the existing tutorial version to create more tutorials to add these features. We'll put saving and recalling the "last used" renderer as one of those new features. I do believe this should go in its own separate thread, though, if you want to come up with a list of features to add to the existing tutorial version.

OR make a dedicated audio peak folder were those audio peak files are stored

+1

This is an option, for example, in Reaper.

Adding request:

When you hover over an activated icon, don't lose the activation color.

@jetdv Sorry I'm just going to bed (23:15 local time in Germany). I will answer in detail tomorrow. Goodnight.

I would like to see a faster proxy generator and a way to switch them on and off. As I move to high resolution, 4K and higher, proxies have become more important to me again. Vegas hasn't improved this subsystem since the FHD on slow CPU days.

There are encoders out there that can run several times faster, by using new hardware features, than the built in proxy coder. So it would nice if Vegas Pro would at least make using external proxies easier to intergrade to the Vegas Pro workflow.

@3POINT As this was just a tutorial to show 1) how to render in various ways and 2) how to use a form to collect information, it's certainly not "fully featured". The form is really not even laid out all that well! And, yes, many additional features could be added.

By default, I'm showing that it's only showing VEG files when selecting the projects to render. As for the output files, the script has nothing to do with files such as the .sfk files. VEGAS creates those automatically and I have no control over the location. Could the script then "look" for the sfk file and mark it as "hidden"? I'm going to say yes but then what if you later deleted the renders but forgot about the "hidden" files? You'd slowly fill up your drive with unwanted .sfk files. And, no, they can't be put in a separate folder or VEGAS would just create them again if you loaded the file to the timeline. All of that is automatic by VEGAS. I suppose the script could look for them and then delete them after the render was complete.

Could we have a way of setting which renderer is the "default" one? Absolutely. Right now it's just showing the "first" one that it finds when reading all renderers. What *is* your default renderer? For example, if you want one of the Magix AVC ones, just type MAGIX AVC in the box before clicking on the dropdown arrow. If you want one of the Magix HEVC ones, just type MAGIX HEVC in the box before clicking on the dropdown arrow.

Yes, I understand that's not exactly what you're asking for. But maybe we can create some new tutorials to add some more features to this script. So we need to come up with a list of practical features that can be added to the existing tutorial version to create more tutorials to add these features. We'll put saving and recalling the "last used" renderer as one of those new features. I do believe this should go in its own separate thread, though, if you want to come up with a list of features to add to the existing tutorial version.

Edward, my request for a feature about handling of the audio peak files (.sfk) has nothing to do with your batch project render script, it was a complete new request for a feature.

About improvements of your render script:

My default render template is mainly the default Voukoder rendertemplate, so for me it would be nice when starting your batch render script it would start with that rendertemplate. If this is not possible, maybe it's possible to show only the rendertemplates that are marked as favorites (like filtering in the Vegas rendertemplates dialog) instead of all present rendertemplates.

Also my default renderlocation is always a fixed VegasPro folder on another HDD than were my source files are stored.

Still asking for this since V!8. Having a lot of plugins, it would be much better than having them listed alphabetically, that they are in the folders (like it used to be in Vegas) to make navigating and finding the right one easy. Using the Plugin Manager takes up needed real estate in the VP window. Why not have it like it was before VP18?

Still asking for this since V!8. Having a lot of plugins, it would be much better than having them listed alphabetically, that they are in the folders (like it used to be in Vegas) to make navigating and finding the right one easy.

@Reyfox  ... Interestingly, the folder breakdown does appear when accessing FX via the FX icon on a video event - as per:

And yes, I much prefer this approach - it would be much better IMO if the main FX window reflected this - as used to be the case in older VP versions.

But being presumptuous, I'll take a wild guess that you have a selection of VFX that you regularly use. These can be saved to the FX Favorites folder - and that makes FX searching so much easier for those regularly used FX.

@Dexcon, yes, there are those preferred effects, but looking for something slightly different, it's painful. It becomes trial and error to see what they do, instead of knowing what category they fall under.

@Dexcon, yes, there are those preferred effects, but looking for something slightly different, it's painful. It becomes trial and error to see what they do, instead of knowing what category they fall under.

 

To mark particular one as a favorite!.. and not as favorites 😠

And maybe a search window in the fx tab to get faster to what you want

@Wiew for sure. But the Video FX tab used to be that way before VP18. So now, I use the Plugin Manager to do the same thing, but it takes up space in the window.

I'll survive. It's just one of those things as to why it was changed in the first place after years of having it a certain way. I don't see how this could have been considered an improvement.

@Wiew Did you miss this one in the FX tab?

@j-v @Reyfox  I know it is in the fx tab ,

But I normally go by the fx button on the clip

and I don't think that top field of the fx pop-up tab offers any added value because everything is already below,

so I think it would be better to make it a search field

I would like an ingestion tool. Over on the Reddit group, so many of the problems come down to people using poor quality source footage or incompatible formats. I know the main source code of Vegas is difficult to modify, so I'd propose a separate tool for 'pre-import' that advises of footage that is a problem and can convert it for ease of use in Vegas itself. Many Vegas users don't know anything about codecs and containers (let alone stuff like VFR) so a tool to mitigate that would, I think, be useful. I was very pleased to see the advisory messages about certain files in recent versions.

I'd also like them to make Vegas Image and Vegas Effects free as an enticement to use Vegas, but that's not a feature request.

Vegas would lose money giving away Effects and Image since they belong to another software company.

I'd also like them to make Vegas Image and Vegas Effects free as an enticement to use Vegas, but that's not a feature request.

Fun ON 😁
I would also like, when I buy a new car, to be able to fill up with fuel for free - but that's not a feature request either.
Fun OFF 😭

I would like an ingestion tool. Over on the Reddit group, so many of the problems come down to people using poor quality source footage or incompatible formats. I know the main source code of Vegas is difficult to modify, so I'd propose a separate tool for 'pre-import' that advises of footage that is a problem and can convert it for ease of use in Vegas itself. Many Vegas users don't know anything about codecs and containers (let alone stuff like VFR) so a tool to mitigate that would, I think, be useful. I was very pleased to see the advisory messages about certain files in recent versions.

I'd also like them to make Vegas Image and Vegas Effects free as an enticement to use Vegas, but that's not a feature request.

I've definitely brought this up to the development team before, as well as integrating this tool into the welcome screen.

I would like an ingestion tool.

Big +1 from me. Instead of just warning about long GOP, etc. let the user fix it right there and then and have a better editing experience.

please upgrade VEGAS Text & Titles with advance tools like in ProType Titler, as VEGAS is deprecated ProType Titler and will delete this feature soon in future. so we need a advance Text & Titler with advance & fully with customizable tools & animation.