Filterscape State Variables 1, 2 & midi?

[bmrzycki]

I was tinkering with Filterscape last night and noticed two interesting things about the StateVariable1 and StateVariable2:

1. You can't midi map to the "hockey puck" with the right click method
2. The controllers don't set to 0 (or some other default) when double clicking on them.

I was hoping to use the pucks similar to the XY pads on Z2 but it looks like the only way to move the outer edge is with the mouse. BTW, I know the inner ball can be modulated nicely with the radius and angle knobs.

[Urs]

Oh... gotta fix that!

[bmrzycki]

Oh... gotta fix that!

Sorry to keep giving you more work

Thanks for the response.

[bmrzycki]

I was using FSVA in REAPER last night and trying to automate with REAPER envelopes some EQ Gain and Q settings at certain points in the song. Much to my surprise I couldn't find exported VST variables in FSVA (or FSQ6 or FS) to automate EQ Gain or Q. I checked for snapshot and global but neither were there.

Since this is time based on the song position and not really related to any sort of looping modulation, I can't do this within FSVA. Any reason the variables wouldn't be exported?

As a side note, it'd be really nice to have a 1:1 map of variables and the UI widget they're attached to. Wiggling knobs and looking in the LCD is time consuming at best and switches don't even show up in there, so it's a matter of trial and error automating them externally.

[Urs]

Brian,

the number of automatable parameters was cut down to 128 due to ongoing requests i.e. of Ableton Live users.

The parameter "Snapshot Morph" can definately be automated (unless there's a bug).

The whole idea of the Filterscape design was having to automate one single parameter to change the whole eq...

Hmmm, I never really thought about having to clear up the relation between gui and automated parameter. In Logic I'd just record a knob tweak and a track would appear all set up for this parameter. Good point though... Might be filed in the Improvements thread

Later,

Urs

[bmrzycki]

the number of automatable parameters was cut down to 128 due to ongoing requests i.e. of Ableton Live users.

I don't understand. I can see < 128 parameters in REAPER for FS. Here's a screenshot sohowing 172 FS variables:


http://img518.imageshack.us/img518/2584 ... perqi3.jpg

The list for Z2 is about twice as long or roughly 360 variables.

The parameter "Snapshot Morph" can definately be automated (unless there's a bug).

The whole idea of the Filterscape design was having to automate one single parameter to change the whole eq...

Yes, you can see snapshot morph in column 3. The reason I'd like to be able access the global EQ parameters in automation is to add emphasis to a morphing preset.

For example. I'm FSing a Pad and the lead drops off. At this point I want to add the mids and highs back into the mix from the Pad. The FS is still morphing, I just want to replace what was removed to make space for the Lead.

If you're worried about being tight on variables you could replace the FM and FMS block since that modulates modulator sources; something I don't think would be very useful. But then again, you're already over 128 as it is.

Hmmm, I never really thought about having to clear up the relation between gui and automated parameter. In Logic I'd just record a knob tweak and a track would appear all set up for this parameter. Good point though... Might be filed in the Improvements thread

I am going to talk to the REAPER devs over in the Cockos forum about envelope automation improvements as it's a bit difficult to use at the moment. You can see in the screen shot above it's really hazy what is attached to what. It gets even worse in the Z2 list when there are about 5-6 variable names that show up 2 or more times.

I like how in some of the names, they're prefixed with things like Mod: or Active #. That helps a lot and could be extended with things like LFO1: or ENV2: or FLT1:.

[Urs]

Mostly agreed...

The AU version has it tidied up as in AU parameters can always be grouped.

Yeah, maybe I'll add the module name... optionally...

I'm very scared that if I do changes, compatibility to existing projects is compromised. So any changes in the automatables policy must be optional...

Urs