View Single Post
Old 08-07-2019, 05:59 PM   #3814
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,599
Default

Quote:
Originally Posted by Geoff Waddington View Post
Well, there is a way to get access to those indexes, but.....

It will require an FXZone format change...

The original thinking was to simplify the file formats as much as possible for the user.

That's why we used FXParam Name.

It'a actually a PITA code wise.

FX don't allow you to query an index unless the FX is live -- that is you have a working instance of it inserted somewhere.

What really happens is the Zone Activation on a particular FX (yay, we have a live one) causes the FXParam name to be used to look up the index, but as you point out it takes the first one it encounters.

Now, I doubt I would mention this if folks had to enter this manually -- too much room for error, but we have an opportunity to fix this now that you've done such great work with the Configurator tool.

Here's what I propose for the new format:

Code:
Zone "VST: ReaComp (Cockos)"
	SelectedTrackNavigator
	Threshold FXParam 0 Thresh "Thrsh"
	Attack FXParam 2 Attack
	Release FXParam 3 Release "Rel"
	Ratio FXParam 1 Ratio
	Compressor FXParam 19 Bypass "Byp"
	Parallel FXParam 20 Wet
ZoneEnd
Now if we could just find those indices.

Aha, they are right in front of us

It's simply the order they appear.

The first one is 0, the next 1, the next 2, etc.

So you could simply use the index of the dropdown(or something similar) to auto gen the numbers needed for the new format.

I was hoping this duplicates problem wasn't that bad, but we're getting far too many anecdotes this early, better to fix it now and be done with it, what do you think folks ?
If it isn't going to be a ton of work for you, I'm happy to change the configurator (and about 200 plugins, third time's the charm)
MixMonkey is online now   Reply With Quote