by Todd R » Wed Feb 19, 2025 8:11 am
Dave Labrecque wrote:Sorry, I misunderstood your initial post. I thought you were saying you could save individual presets to open by default with each custom INI plugin name.
So it sounds like you're actually naming the individual instances of a plugin with names customized for your individual session? And then when you go to the next project, you have all these INI names from the prior session showing up in your FX Choices?
1) seems like a bit of background work to do this for the first session, but it seems to be worth it, so good on ya
2) if it hasn't occurred to you, you can use the FX Choices Group functions to split off each custom, per-session naming scheme into its own group so that they don't annoy you as you move on to other projects. Of course, over time that's going to be a lot of groups accumulating, and SAW only has room for thirty. I guess a fix to that would be to archive these custom INIs with each project, preferably with each applicable EDL (separate subfolders) so as not to potentially get things mixed up. But that would mean moving the INIs back to the VST_Plugins folder if/when you need to revisit a session in the future.
RE: Metaplugin as a way to define default plugin presets... yeah, I guess that would work. Bulky, with extra clicks and windows to deal with, but it should work.
yes, Dave, penny has dropped your end :-P
That is exactly what I'm doing
well. it is actually it is very easy because I save VST presets named to reasonably match the ini pointer
I don't see issues going forward and makes life so much easier
Metaplugin adds a layer of complexity, I'm afraid
for example, I used a reverb extension in Reason running as a VST3 in Metaplugin called by SAW ini pointer file
But I do not want Reason launching every time open the SAW job!
So I bounced to reverb effect
[quote="Dave Labrecque"]Sorry, I misunderstood your initial post. I thought you were saying you could save individual presets to open by default with each custom INI plugin name.
So it sounds like you're actually naming the individual instances of a plugin with names customized for your individual session? And then when you go to the next project, you have all these INI names from the prior session showing up in your FX Choices?
1) seems like a bit of background work to do this for the first session, but it seems to be worth it, so good on ya
2) if it hasn't occurred to you, you can use the FX Choices Group functions to split off each custom, per-session naming scheme into its own group so that they don't annoy you as you move on to other projects. Of course, over time that's going to be a lot of groups accumulating, and SAW only has room for thirty. I guess a fix to that would be to archive these custom INIs with each project, preferably with each applicable EDL (separate subfolders) so as not to potentially get things mixed up. But that would mean moving the INIs back to the VST_Plugins folder if/when you need to revisit a session in the future.
RE: Metaplugin as a way to define default plugin presets... yeah, I guess that would work. Bulky, with extra clicks and windows to deal with, but it should work.[/QUOTE]
yes, Dave, penny has dropped your end :-P
That is exactly what I'm doing
well. it is actually it is very easy because I save VST presets named to reasonably match the ini pointer
I don't see issues going forward and makes life so much easier
Metaplugin adds a layer of complexity, I'm afraid
for example, I used a reverb extension in Reason running as a VST3 in Metaplugin called by SAW ini pointer file
But I do not want Reason launching every time open the SAW job!
So I bounced to reverb effect
