I don't know if $date & $time matter, to be honest. If you really wanted to use them, they should be the date & time that the stem render process began (ie. not different for each output file produced).

@dax
it is easy to undo but it will have to reload all FX and items. Consider you have your favorite 1Go kontakt library on this track, and this delete / undo will be quite long as all samples will have to be reloaded again.

All plugins take more or less time to load and it's kind of platform dependant, some can have EZdrummer loaded in 3 seconds in SSD, some in 1 minutes on their old Win XP, having custom rules for that is completly unmanageable.

Tthere is few reason why someone could want to have muted track to be processed anyway (like some tracks which have only analyzer VST on it, or tracks used for FX with parameter modulation accross tracks like ReaLearn, or other things I might overloocked, maybe VCA, or track parameter linking etc).

So this would have to be optional or as seperate actions for custom actions.

Meanwhile, you can still manually toggle this preferences in the Option window and see how efficient it is!

Well you should take a look at Mespotine's Ultraschall LUA libraries. I'm not a programmer, but even I was drooling a little.

From what I remember of the last time I used the script* there were some difficult UX factors that I'm pretty sure I wrote about in detail in this thread.
One of them was setting a render region. I think that if no time selection exists, then it should render the entire project up until ~10 secs after the longest item in the project.

*I stopped because 50% I haven't had the need and 50% there was some intrinsic difficulty in how it operated.

Hey Raymond, I thought I'd test out the newest version. I selected some tracks, ran the script and it just started working without asking for filename wildcards, etc.
I would have guessed I should see a script dialogbox asking for location to save files, name of files, etc.

EDIT:
With Mespotine's progress, would it be possible for us to set our default export settings in the script? Or at least filename = $project - $tracknumber $track

@dax
The script use the Render with last setting directly,
cause the Render dilog popup isn't friendly with scripts (it trigger next code even if nothing is pressed) ^^
It is in this render setting dialog that you can set the default name and patterns.

The $tracknumber thing is definitly something I have to take care off though you are right. I'll implement it, with Leading zero depending on whole track number (so that exported names is easily sortable). I don't know how it is done natively, but leading zeros will be great.

EDIT:
With Mespotine's progress, would it be possible for us to set our default export settings in the script? Or at least filename = $project - $tracknumber $track

What do you mean exactly? One background-script, that forces a certain render-setting into projects?

Haven't checked, but you may be able to do that with Default-Project-settings.
Set the render-settings you want, open the Project-Settings, change something(and change it back if you want) and hit the "Save as default project settings"-button.

@mespotine
Dax is very excited about your API project (and he is right about that), but it is indeed not needed for this script IMHO :P

I think too.

My API-render-functions in a nutshell:
- You will be able to get/set everything in the RenderToFile-dialog. Still need to make some stuff more shiny, but I'm on my way.
- You can import/export render-settings from/to projectfiles
- RenderQueue shall be available(I hope I get it to work)
- RenderPresets shall be available, still need to make some stuff possible, but it should work quite good.

So in a few weeks, you have full control over rendering on a programmingside.

@mespotine
Good to know. In this case I only have to hook render pattern with the new native funciton from REAPER v9.764. The action explicitly say "render" without the "..." wich indicate that it will open a popup. So when click, it render. That's all

I've been trying to get the new native render feature to work and I just can't do it. It ignores my sidechain processing, whereas your script does not. Therefor, your script continues to be the only usable workaround for me.