Render Stems (selected tracks) through master FX?

[daxliniere]

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).

[daxliniere]

Originally Posted by X-Raym

@dax
A wildcard for existing output filename ? Do you mean the track name, as it is currently ?
I dont understand how the whole render file name could be a wildcard for the rendered file name.

Not track name, the normal output file name of the project.

For example, I did a mix with this filename: Band - Who Are You (Anatole remix) v2. For my stems I wanted them to look like this:

STEMS - Band - Who Are You (Anatole remix) v2 - 01 Kick
STEMS - Band - Who Are You (Anatole remix) v2 - 02 Hihat
etc...

This would be entered as STEMS - $output - $tracknumber $track

[X-Raym]

@dax
Ok you mean the Render Pattern (it is how it is called in the .rpp), I don't know if it is possible to get that from script.


But indeed, in the end I think I think it would be better if all was completly transparent: the script could by itself

• activate the Region Matrix render,
• set selected tracks in Region Matrix,
• create the =RENDER region from time/selection or if not from =START, =END,
• (maybe set the wildcard to $region if it is possible to get the previous one)
• and restore all back to initial state after that.

This would require more dev time and add complexlity to the script, but it would be far more easy to set up.

[Jeronimo]

I've been using the script quite a bit lately!
Thanks for all the work X-Raym!

[daxliniere]

Originally Posted by X-Raym

But indeed, in the end I think I think it would be better if all was completly transparent: the script could by itself

Sure, that would be ideal, but I can tell it would be more work.

[daxliniere]

Just thinking out loud...
REAPER has a function to not process muted tracks which saves CPU time at the expensive of slightly slower 'unmute' times.

Could stem renders be completed faster if your script automatically muted non-used tracks?

I realise this would add more difficulty, since you would need to add logic to check which tracks rely on other tracks (i.e. check where the sends are routed).

Could be a great addition if it works.


-D.

[daxliniere]

Originally Posted by daxliniere

Just thinking out loud...
REAPER has a function to not process muted tracks which saves CPU time at the expensive of slightly slower 'unmute' times.

Could stem renders be completed faster if your script automatically muted non-used tracks?

I realise this would add more difficulty, since you would need to add logic to check which tracks rely on other tracks (i.e. check where the sends are routed).

Another solution would be for the script to delete any tracks that don't contribute to the sound of the stem track being rendered.

[Jeronimo]

I've been using the script for a bit now and I must say: it works perfectly!
I wouldn't change anything

[X-Raym]

@Jeronimo
THx

@dax

Another solution would be for the script to delete any tracks that don't contribute to the sound of the stem track being rendered.

This would be extremly bad for performance.

[Jeronimo]

Originally Posted by X-Raym

@Jeronimo
THx

No brother! Thank you!!! It really helps with my workflow!

[_Stevie_]

It's really a great script and a huge time saver. Somehow shocking that this hasn't been integrated natively.

(Not a huge fan of the render queue, since it re-opens the project. This can really kill a computer, depending on how demanding a project is)

[daxliniere]

Originally Posted by X-Raym

@dax

This would be extremly bad for performance.

Hey Raymond, why do you think that would be the case? It's very easy to undo the delete step if that's what you were thinking about.

[X-Raym]

@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.

[daxliniere]

Ahh yes, good point.
Perhaps an exclusion for those?

Or maybe easier and better for your script to toggle REAPER's "Don't process muted tracks" option before rendering?

[X-Raym]

Perhaps an exclusion for those?

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.

Or maybe easier and better for your script to toggle REAPER's "Don't process muted tracks" option before rendering?

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!