Reaper defaults to the /Reaper/Render directory when making a new project.
Just leave this setting empty, and it will always default to the project folder.
Then you can just specify a subfolder in the "directory" field of your usual render preset.
In mine I just write "Bounces" and so I get a subfolder in whatever project I have called "Bounces" with all renders inside.
Stem manager allows you to define a subfolder within that subfolder for each render group, but still - you should probably start off with the settings I just described, regardless of whether you use the script or not.
Allright, so I spent the last few days crushing a lot of bugs and adding new functionality with great help from everybody here, and especially thommazk which turned out to be a great bug finder! Thanks man!
Everything should be working much smoother now. If you do find some quirks, let me know!
Here are some things I'm definitely planning on adding (hopefully this week):
Overwrite files without asking (optional)
Allow for more than 9 render groups - I'll just make it user defineable up to 99
Hide tracks that are hidden in the TCP
Still thinking about an elegant way (UI wise) of disabling FX on specfic tracks on a stem by stem basis - pretty optimistic but it might require some work to get done right
Once those are in and working smoothly I'll make an video covering all the features in depth.
In the meantime, please let me know if there's anything else you'd like to see.
I'm planning on adding hidden tracks support in the coming week. Sounds like a good default behaviour to have it sync to the hidden/visible state of the TCP.
It's a little tricky with their folder depth, but it's manageable.
Perfect. Yes, I think syncing the visible state of TCP with your script makes a lot of sense. I'll stay tuned for the update and thanks again for coming up with the Stem Manager, soooo helpful!
Oh wow, this script is amazing ! I've only tested it a little bit, but it seems like you've already thought of most of the possible uses for it.
My only issue with this at the moment, is that when I set the folder and names for the stems, it reflects this change in the Reaper 'Render to File' Filename box. I usually have this set to "Project Name_Project No." etc, so would need to change it back to this after rendering any stems.
Is there anyway that I can prevent this, or can it restore the previous Filename that was set?
v1.0.0 is out!
Unfortunately I had to change the way default settings are saved and loaded, and the new way breaks current default settings.
However, settings saved with projects are still intact, so here's a way to reload and save the default settings for the future:
- Load a project which uses stem manager with the settings you want
- Click settings
- Click "Save as default settings"
- Now whenever you load Stem Manager on an empty project it should have the default settings, as intended.
For this to work, just make sure you update to v1.0.0 first.
This is amazing. And very nice tutorial video as well!
I’d like to understand something? Is there a way to bounce several tracks in one pass like Reaper’s « stem render selected tracks » but zeroing volume and pan on each track first. And most importantly in one single pass rather than in a lot of separate soloed renders?
I’m really looking into integrate this stem manager into my daily workflow.
This is amazing. And very nice tutorial video as well!
Thanks so much! I'll take the opportunity to tell you that ReaLive is unbelievable! Amazing work. I have some friends that swear by it and from what they showed me it's mind blowingly good.
Quote:
Originally Posted by lexaproductions
I’d like to understand something? Is there a way to bounce several tracks in one pass like Reaper’s « stem render selected tracks » but zeroing volume and pan on each track first. And most importantly in one single pass rather than in a lot of separate soloed renders?
First, since what it does is make "mixes" of soloed tracks, they can't be rendered in one pass.
Of course, if you are using « stem render selected tracks » option as a render source in the render preset you can definitely still use Stem Manager to automate some of the tasks - like making sure specific regions/markers/time selection is/are selected, running custom actions before and after and some naming and subfolder tasks, but it can't fundamentally change the way Reaper renders.
Here's what the script does for each stem:
- Solo/mute some tracks
- Run all kind of actions to prepare the render (load render preset, append folder to filename, change $stem to the stem name)
- Optionally run custom actions
- Render / add to render queue
- Optionally run some other custom actions
- Play+wait before rendering the next stem (to let reverbs die down)
Zeroing the faders is not built in, however it can be achieved like so:
If you give me a more specific use case maybe I can come up with something more elegant or find a way of integrating it into the script.
However, I'm not sure that making it a part of the core functionality is good, since again - the script is not primarily about rendering individual tracks (in which case zeroing the volume would make sense) but rather about rendering sets of tracks, in which case you'd probably (definitely?) want to keep their relative levels. Show me a use case for wanting to zero a whole set of tracks and I'll add it
Another thought: You can also always make sure that you're normalizing as part of the render preset, which might solve that issue while still maintaining the relative levels between each stem's tracks.
Thanks for the kind words. Tell your friends to give me a shout in the thread. I’m always interested to know how it’s used by others.
So to render separate tracks, I can still use the Reaper setting in the render window by making a preset and then trigger it using stem manager? That would still be a very viable option. Making reaper render presets and use SM to trigger them.
So to render separate tracks, I can still use the Reaper setting in the render window by making a preset and then trigger it using stem manager? That would still be a very viable option. Making reaper render presets and use SM to trigger them.
Yep, that's definitely possible.
You'll get a warning saying the render preset's source is not Master Mix, but it won't prevent you from rendering using it.
If you don't want a message to appear every time you render, be sure to check "don't show non critical errors before rendering".
And I'll definitely tell my friends to give you a shout
Your stem manager is amazing - using it on every project now!
One suggestion:
I really like the new render stats reaper offer (loudness, clipping etc)
Is there a way to see some of those stats (maybe the above two) on a single overview page after all stem manager renders completed?
This would allow me to see any issues with the rendered files.
The data is visible while rendering via stem manager, but for unattended renders of many stems it would be helpful to see them all after completion.
I found a bug, when i have reaper on my main 4k monitor of my miulti-monitor setup the script doesn't visibly show up but its active. It's not until I move the main screen down to one of my slate ravens does the script in it's entirety show up. I tried moving the script as well but i just disappears when i try to move it up.
Your stem manager is amazing - using it on every project now!
Thanks so much. I'm really glad to hear!
Quote:
Originally Posted by dadada
One suggestion:
I really like the new render stats reaper offer (loudness, clipping etc)
Is there a way to see some of those stats (maybe the above two) on a single overview page after all stem manager renders completed?
This would allow me to see any issues with the rendered files.
The data is visible while rendering via stem manager, but for unattended renders of many stems it would be helpful to see them all after completion.
That's a great idea. I need to see if there's a way I can access the stats html page's location and aggregate all of them somehow.
I'll work on it!
I found a bug, when i have reaper on my main 4k monitor of my miulti-monitor setup the script doesn't visibly show up but its active. It's not until I move the main screen down to one of my slate ravens does the script in it's entirety show up. I tried moving the script as well but i just disappears when i try to move it up.
Sorry for that - multi monitor setups are a bit tricky. I wonder if it's a ReaImGui thing or if it's something I'm doing wrong.
I can't seem to recreate it, but I do have something weird happening when both monitors are at different resolutions.
Can you elaborate a bit please? What operating system are you running? Are the monitors running at different resolutions?
Did it happen the first time you opened the script or only on subsequent runs?
Wow... this is a great and useful script for sure. I discovered it right on time for my preparation of 2023 templates. Thank you so much, can't wait to use this and the extra time it'll give me to make more music.
Hello.
First, thanks for the great work!
I use the script on my 2015 macbook without problems but on my M1 Mac Mini, I can't open the "settings" window. I get this error message:
"...ReaScripts/Rendering/Stem Manager/Odedd_Stem Manager.lua:444: number has no integer representation"
followed by "ImGui assertion failed"- popup window saying:
(g.CurrentWindowStack.Size == 1) && "Mismatched Begin/BeginChild vs End/EndChild calls: did you forget to call End/EndChild?"
is there a way for me to fix this? (I'm not a coder but also not completely unable to do tech stuff)
I'm using a Toshiba 23W_LCD_TV Screen with 1920x1080 resolution
I get this error message:
"...ReaScripts/Rendering/Stem Manager/Odedd_Stem Manager.lua:444: number has no integer representation"
Hi Randu.
Please make sure that an extension called "ReaImGui" (using the Reapack package manager) is updated to 0.8.3.
There was a small bug in 0.8.2 that caused problems with scripts using it, and it's solved now, as cfillion stated above.
I've read cfillion's post above (and everything else) before i posted my question and made sure version 0.8.3. is installed. I just double checked again and it is the correct version. I also reinstalled everything a few times but nothing changes.
Maybe I'm out of luck in this case.
Anyway thanks for your quick reply!
I've read cfillion's post above (and everything else) before i posted my question and made sure version 0.8.3. is installed. I just double checked again and it is the correct version. I also reinstalled everything a few times but nothing changes.
Maybe I'm out of luck in this case.
Anyway thanks for your quick reply!
If possible, could you please post (or DM me) a session file where it happens? It could be without items, FX, midi or audio in it, but it needs to have the same tracks.
I would help greatly help me understand what's going on.
Yesterday I Imported only the "Configuration" of the "Import Configuration" Window from my Laptop to my Mac Mini and now it works. (See Picture)
I don't know what I did to the settings that caused this. Would like to send you a Project but I'm afraid, now that it's working you will not be abled to trace the problem. I can send you the Config File if you like, but I would be hesitant to undo everything I did, now that it works :-) (and rescanning all the Plugins on a new mac is a pain)
But if you insist, I'll do it for you :-)
(I think the config file alone would be sufficient, because the error also ocurred with no tracks at all...)
Thanks anyway for your kind support. Let me know what you need to get to the bottom if this!
Just chiming in to say thank you for this!!! A dream functionality way past my usual manual snapshot process. So great.
Wondering if there’s be a way to queue multiple projects and “render immediately” to circumvent the “add to render queue” reloading projects for each stem. Which is an often slow process on my projects with lots of sample based instruments. Either way, just being able to do this on a per song basis is already a huge thing as is!
Just chiming in to say thank you for this!!! A dream functionality way past my usual manual snapshot process. So great.
You're welcome! I'm really happy when people find use for Stem Manager
Quote:
Originally Posted by mks
Wondering if there’s be a way to queue multiple projects and “render immediately” to circumvent the “add to render queue” reloading projects for each stem. Which is an often slow process on my projects with lots of sample based instruments. Either way, just being able to do this on a per song basis is already a huge thing as is!
That would require creating my own "render queue" which is a possibility, but is a bit of an undertaking for now. Maybe in the future. Right now I have some other script ideas I want to pursue
Also, I just released v1.1.0 with a fix for the way pre and post render actions are saved. The old way led to actions sometimes loading as other actions, especially after repack installs, and it's driven me crazy for quite a while.
I finally managed to crack down on the reason, so I released this update.
Odedd great script, thank you, but I feel it's got a little ways to go.
I realized this when I bouncing out Stems just the other day.
Now I realize it's called Stem Manager for a reason, but hear me out if this could also be used to export Multi-Tracks and MIDI that would be absolutely amazing. (example: File - Consolidate/Export Tracks)
This script would be great as a hybrid
As a user. I would like to export and render simultaneously with and without effects
DI's as well as processed. MIDI to Audio while also saving the MIDI
Idk how everyone else works, but I Typically send 3 folders to my clients
-Stems
-Multi-Tracks
- MIDI
I want to be able to bypass effects of the busses as well as on the individual tracks.
I Need printed effects on my sources example: Guitar Amps
Aswell as the Raw Di's
Render MIDI to audio tracks and save the MIDI
and Finally if you could bypass automation as well as print with automation that would also be another great feature.
And if it's something that can be recalled from session to session using the names you give your tracks or busses kind of like how SWS Auto color works to color your tracks that would also save so much time.
I know it may be advantageous and I can't imagine how much time you've already spent on Stem Manger. But I feel I'd be remised if I didn't share my thoughts after unfortunatly realizing I couldn't use Stem Manger for everything and still had to spend hours to export a single song.
Thank you for your time and consideration and all that you do Odedd. I'm sure everyone in the community appreciates your work including myself. Thank you.
I just... love it!! This is perfect! I've been looking for a good solution for the stems in a game I'm working on. The ability of muting AND soloing allows me to make alternate tracks for the same instrument and place them as sends. It's genius!!
Incredible work.
Now we just need the ability to save and load stem presets. Having to add stems using the + button every time I open a new project makes it kinda pointless when your stems count and naming is always the same (working on a film or tv show for example)
__________________
Mac Pro 2010, 12 Core , ram 64gb
Macbook pro 2011, i7, ram 16gb
Antelope Audio Zen Studio
Incredible work.
Now we just need the ability to save and load stem presets.
Thank you very much!
That's a good idea actually.
I mean, right now you can sort of save presets by using projects templates with the stems already set-up inside stem manager in the project, and they will carry over to every project made from this template (see the end of the tutorial video)
That's what I do for my mixes, but I recently started noticing it would be easier to also have the ability to save/load presets.
Will do at some point in the near future. I just recently started writing my next script, so I might do these while I'm at it.
Linear Mode
