Control Surface Integration (CSI) Technical Feature Discussion

[MixMonkey]

Originally Posted by Cragster

Ok thank you much !!!! Ill post those things as soon as i can. If its a reaper thing i can live with it. Actually the pan worked much better the standard way as opposed to the acceleration way.which is why i was thinking its something in my mapping.But i want to take advantage of this feature for plugins params. So i guess it might be a give and take ? Anyway thank you ill get back to you

Just for Pan, try defining the first 3 or 4 acceleration values as something quite small, that way when Pan starts to move you won’t get the big jump.

[Cragster]

Originally Posted by MixMonkey

Just for Pan, try defining the first 3 or 4 acceleration values as something quite small, that way when Pan starts to move you won’t get the big jump.

Ok thank youn. Ill play around with it and see what i can come up with

[Geoff Waddington]

New build is up.

Should see improved FX Insert Window behaviour.

EuCon now defaults to Show FX Windows.

The EuCon.zon file now has the RTZ button mapped to Show/Hide the FX Windows, if you want that behaviour.

[spkr4thdd]

Just out of interest, how many here are using MCU/X-Touch controllers?

And are any of you using Slate plugins?

[MixMonkey]

Originally Posted by spkr4thdd

Just out of interest, how many here are using MCU/X-Touch controllers?

And are any of you using Slate plugins?

Me, MCU,XT,C4. Slate VBC, Trigger. I think I have VMR somewhere, but it's fallen into disuse since Acustica/Nebula.

[Geoff Waddington]

Originally Posted by Funkybot

Appreciate you doing the EuCon mapping of UAD plugins. Please feel free to continue! I also prefer not having the other track names appear, so that's appreciated here. Just looks cleaner to me.

Just gave it a quick smoke test and so far so good except:

Pre-Condition: EuCon/Artist mix set to Mix/Pan button on the left.

1. Load up an empty project
2. Add a track
3. Add the UAD Harrison 32C (for example)

GUI opens in Reaper as expected.

4. Click the Insert button on the left-hand side

Result: the Harrison 32C GUI closes.

If a GUI is open, whenever you activate the Insert button, the GUI closes.

Behaviour is now:

Pre-Condition: EuCon/Artist mix set to Mix/Pan button on the left.

1. Load up an empty project
2. Add a track
3. Add the UAD Harrison 32C (for example)

GUI does not open in Reaper as expected

4. Click the Insert button on the left-hand side
5. Press Select

Result: the Harrison 32C GUI opens.

It's a bit of a workaround, but the rest seems to work fine now

[Funkybot]

Sounds much better. Will check it out later today Geoff (didn't get a chance last night).

[Geoff Waddington]

Originally Posted by RobinGShore

Also there's a bug with Eucon layouts, it's acutally something that's also been present in your old Eucon plugin since way back. If I load a Reaper project that has Eucon layouts saved with it, Eucon won't see the layouts, instead it'll use the layouts from the last Reaper project that was opened (or if it's the first project to be opened since starting Reaper it'll just show all blank layouts). If I restart EuControl it will then show the correct layouts, but if I happen to save the Reaper project before doing this my layouts will be written over and I won't be able to get them back.

Was playing around with this today, couldn't get it to misbehave, but did notice a EuControl quirk.

At project load, if you then go to EuControl and are already on the Layouts tab, you will not see the restored Layout.

Just select the Assign tab, then the Layout tab, to get it to refresh.

Also, didn't hear back, did you ever get going again, you were having issues last post I recall.

[Tonda]

HI Geoff,

Nice to have the possibility to open/close the plugin windows with the RTZ button (Eucon).
Thanks!

However, I've noticed some strange behaviour...
The last plugin window, the last plugin of the chain with a zone defined, stays always on top. Clicking with the mouse on another plugin doesn't help, it won't become the top window.
It would be helpful if the plugin of the selected page becomes the top window, that way you always have focus on the plugin you are editing right now. Plugins without a defined zone does not respond to the RTZ button, which is perfect of course, but this window never will be the top window, too. I suspect that clicking on one of the plugins sends a command to the console, which reopens the windows in order of the fx chain, but only the ones with a zone defined.

Hope the description is clear...

Best!
Ton

[tdc]

Great new development Geoff!

How do us S3 users access the RTZ function given the surface doesnt have one?

[TVbene]

If I followed up correctly, LED feedback for indicating the active zone is still not closer to reality? When I looked at MixMonkey's "poor man's radio buttons" I remembered this idea by LDEVO a while ago: This way it's not about storing LED states and making sure only one is lit up but just about doing this manually with every button press. Just a LEDOn or LEDOff command followed by one or multiple FB_TwoState buttons.

Originally Posted by LDEVO

Zone "Buttons|"
Link GoZone "FaderFXParam" LEDOn "Link"
Pan GoZone "RotaryPan" LEDOn "Pan" "Channel" "Scroll"
Channel GoZone "RotaryChannel" LEDOn "Channel" LEDOff "Pan" "Scroll"
Scroll GoZone "RotaryScrub" LEDOn "Scroll" LEDOff "Pan" "Channel"
ZoneEnd

[...]

Zone "FaderFXParam"
FocusedFXNavigator
Fader FocusedFXParam
FaderTouch TrackTouch
Link GoZone "Home" LEDOff "Link"
ZoneEnd

[...]

Wouldn't this be a way for these cases where LED feedback is necessary and there's no corresponding Reaper parameter for it?

[Cragster]

Originally Posted by TVbene

If I followed up correctly, LED feedback for indicating the active zone is still not closer to reality? When I looked at MixMonkey's "poor man's radio buttons" I remembered this idea by LDEVO a while ago: This way it's not about storing LED states and making sure only one is lit up but just about doing this manually with every button press. Just a LEDOn or LEDOff command followed by one or multiple FB_TwoState buttons.



Wouldn't this be a way for these cases where LED feedback is necessary and there's no corresponding Reaper parameter for it?

!!!!! Would love to have control over the button lights

[WaveTrans]

Hi, I´m afraid I somehow lost track with the newes developments, espc. stepping.

Does this

	Toggle+RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

still work with this synthax or is there a new one?

Just checking since this plugin used to work last time but doesn´t anymore with respect to the Relase and Attack control.

I´m grateful for any advice!

Here´s the code

 
Zone "VST: FREE87 FR-COMP (eaReckon)" "FREE87"
	FocusedFXNavigator
/	SelectedTrackNavigator  
/
	DisplayUpper1 FXParamNameDisplay "4" "Thrshld"
	DisplayLower1 FXParamValueDisplay "4"
	Rotary1 FXParam "4" "Thrshld" 
	RotaryPush1 NoAction
	Toggle+RotaryPush1 FXParam "0" "Attack" [ 0.3 0.6 1.0 ]
/	
	Rotary2 FXParam "1" "MakeUp" 
	RotaryPush2 NoAction 
	Toggle+RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]
/   
	Rotary3 Reaper "65535" 
	RotaryPush3 NoAction 
	Toggle+RotaryPush3 FXParam "2"
/	
	Rotary4 FXParam "6" "Wet"
	RotaryPush4 NoAction
	Toggle+RotaryPush4 FXParam "5"
/ 
/ No Actions
	Fader1 NoAction
	Fader2 NoAction
	Fader3 NoAction
	Fader4 NoAction
	Fader5 NoAction
	Fader6 NoAction
	Fader7 NoAction
	Fader8 NoAction
/
	Rotary5 NoAction
	Rotary6 NoAction
	Rotary7 NoAction
	Rotary8 NoAction
/
	RotaryPush5 NoAction
	RotaryPush6 NoAction
	RotaryPush7 NoAction
	RotaryPush8 NoAction
ZoneEnd

[Funkybot]

Originally Posted by WaveTrans

Hi, I´m afraid I somehow lost track with the newes developments, espc. stepping.

	Toggle+RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

Did you try without the toggle modifier? I recall toggle not being necessary with stepped parameters. Only on/off type switches.

I'd give this a shot first if you haven't already:

RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

[Cragster]

Originally Posted by Funkybot

Did you try without the toggle modifier? I recall toggle not being necessary with stepped parameters. Only on/off type switches.

I'd give this a shot first if you haven't already:

RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

Yes funkybot right. I have a few like that that work with the new acceleration syntax

[Cragster]

Originally Posted by WaveTrans

Hi, I´m afraid I somehow lost track with the newes developments, espc. stepping.

Does this

	Toggle+RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

still work with this synthax or is there a new one?

Just checking since this plugin used to work last time but doesn´t anymore with respect to the Relase and Attack control.

I´m grateful for any advice!

Here´s the code

 
Zone "VST: FREE87 FR-COMP (eaReckon)" "FREE87"
	FocusedFXNavigator
/	SelectedTrackNavigator  
/
	DisplayUpper1 FXParamNameDisplay "4" "Thrshld"
	DisplayLower1 FXParamValueDisplay "4"
	Rotary1 FXParam "4" "Thrshld" 
	RotaryPush1 NoAction
	Toggle+RotaryPush1 FXParam "0" "Attack" [ 0.3 0.6 1.0 ]
/	
	Rotary2 FXParam "1" "MakeUp" 
	RotaryPush2 NoAction 
	Toggle+RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]
/   
	Rotary3 Reaper "65535" 
	RotaryPush3 NoAction 
	Toggle+RotaryPush3 FXParam "2"
/	
	Rotary4 FXParam "6" "Wet"
	RotaryPush4 NoAction
	Toggle+RotaryPush4 FXParam "5"
/ 
/ No Actions
	Fader1 NoAction
	Fader2 NoAction
	Fader3 NoAction
	Fader4 NoAction
	Fader5 NoAction
	Fader6 NoAction
	Fader7 NoAction
	Fader8 NoAction
/
	Rotary5 NoAction
	Rotary6 NoAction
	Rotary7 NoAction
	Rotary8 NoAction
/
	RotaryPush5 NoAction
	RotaryPush6 NoAction
	RotaryPush7 NoAction
	RotaryPush8 NoAction
ZoneEnd

But i think the mst needs to be updated to the new if you didn't already. The other guys will know for sure
Edit. My bad your referring to the rotarypush. Not the rotary. Carry on nothing to listen to here lol

[Cragster]

Hey Geoff your CSI just sold Icon yet another surface haha. I just added a little straight 50 button surface into my mix. Why ? Well cause i ran out of of buttons lol. Sry just loving life in my studio with this CSI.
I know ive said it a million times already but

THANK YOU GEOFF

[WaveTrans]

Originally Posted by Funkybot

Did you try without the toggle modifier? I recall toggle not being necessary with stepped parameters. Only on/off type switches.

I'd give this a shot first if you haven't already:

RotaryPush2 FXParam "3" "Release" [ 0.3 0.6 1.0 ]

Thanks Funkybot and Cragster.

Set it up with RotaryPush and it works again.

Does that mean step-values are exclusively for RotaryPush?

Just wondering since stepped Toggle+RotaryPush worked until very soon.

Implementation of Encoder values and all this fancy new stuff would be really nice, but as I said above, I somehow lost track, so it´ll have to wait till it´s described in the manual.

Thanks again, Gentlemen!

Edit shows that this coding Toggle+RotaryPush doesn´t work in other plugs either.

[MixMonkey]

Originally Posted by WaveTrans

Does that mean step-values are exclusively for RotaryPush?

No, stepped values also work with Rotary, where they a capable of being accelerated.

If you have a lot of plugins to modify, this regex definition can be helpful (to find and replace the "Toggle+" with nothing)

(Toggle\+)(?=RotaryPush\D\d\sFXParam\s\d+\s\[)

It will remove the "Toggle+", but only from parameters where "Toggle+" is followed by " [" (ie where there are stepped values following).

[Funkybot]

Originally Posted by WaveTrans

Implementation of Encoder values and all this fancy new stuff would be really nice, but as I said above, I somehow lost track, so it´ll have to wait till it´s described in the manual.

The manual got some MAJOR updates around encoders this week:

https://github.com/malcolmgroves/rea.../wiki/Encoders

...give it a look and feel free to post feedback here about where something may not be clear or can be worded better. Rewriting that section was a big undertaking and I'm all for continuous improvement so I'm open to suggestions.

One thing to note: "Stepped Parameters" are covered on that page, but they apply to more than just encoders. So if you're looking for "how to do stepped parameters" maybe that should be it's own page, but I'd also want to cover stepped parameters specific to encoders because they can really mess up an encoder mapping if you don't know what to do. In short: I'm still not sure where/how the best way to show stepped parameters is. Maybe they need their own page. Open to feedback.

[Cragster]

Originally Posted by Funkybot

The manual got some MAJOR updates around encoders this week:

https://github.com/malcolmgroves/rea.../wiki/Encoders

...give it a look and feel free to post feedback here about where something may not be clear or can be worded better. Rewriting that section was a big undertaking and I'm all for continuous improvement so I'm open to suggestions.

One thing to note: "Stepped Parameters" are covered on that page, but they apply to more than just encoders. So if you're looking for "how to do stepped parameters" maybe that should be it's own page, but I'd also want to cover stepped parameters specific to encoders because they can really mess up an encoder mapping if you don't know what to do. In short: I'm still not sure where/how the best way to show stepped parameters is. Maybe they need their own page. Open to feedback.

Hey since u brought up the wiki i have a question. I was making an mst for my new surface.its just a surface with 50 buttons. Nothing else. I was going through the buttons in midi ox you know to get the values. They all throw out a message on press and one on release.... ie 90 4a 7f and 90 4a 00.(thats just an example im not at my computer)So i was on the wiki trying to figure out how to make the mst .how do i know when to just use the press message?

 
widget button1
  Press 90 4a 7f
WidgetEnd

Or when to use both the press and release message

Widget button1
  Press 90 4a 7f 90 4a 00
WidgetEnd

And then theres one with FB twostate but thats for lighting the button right ? The wiki is great but it wasnt entirely clear which one to use. Does it depend on whatever action im tieing to that button in a zone file ? Sry i know this is a way beginner question but ive always just used the included msts. So i just wanted to understand better which to use . Thanks all

[Funkybot]

Cragster, my general rule of thumb is: if the surface transmits release messages, then tell CSI about them in the widget. The .mst file is all about the "defining the capabilities of the surface" so that should include release messages where they get sent. You'll also ABSOLUTELY need release messages if you want to get the best behavior out of modifiers like Shift, Alt, Option, Ctrl. If you started getting weird behavior with them included, then you could always remove the release messages from the widget, but I don't think there's any harm in defining them where they exist and it's probably recommended.

And yes, FB_TwoState is all about lighting the button. But remember: it's highly contingent on what Reaper action is assigned to that button and whether that action properly reports it state. I have a few buttons where I commented out the FB_TwoState line for the widget because it was keeping lights on when I didn't want them on, and just turning lights off entirely made more sense.

[Funkybot]

Geoff, I'm getting a bug here with FocusedFXParam on a particular project. As best I can explain it, here's what's happening:

1. I open this project
2. I open an FX that happens to be located in the back half of the track count, focus a parameter
3. Press Shift+F2 to enter FocusedFXParam mode and...

Nothing happens. Weird. Now...

4. Try a different FX, something towards the start of the track list

Result: something comes up, but it's not the FXParam in focus. The Parameter looks like it belongs to an entirely different plugin. Now, if I move around and click different parameters in this synth or effect, it'll show me different parameters other than what's in focus. Again, looking like they belong to an entirely different plugin.

It feels like somehow the FXParam values being sent to the surface got mixed up along the way. So FocusedFXParams towards the start of the project are actually getting mixed up and controlling FX Parameters that belong to FX later on in the project. Example: Controlling the Cutoff of the Instrument on Track 1 may actually be controlling the compressor threshold of a plugin on Track 12. Then selecting a parameter on that plugin on Track 12 controls nothing at all. Like the parameter lists have been shifted.

But if I do an empty Reaper project, add a Track, add en effect, everything seems to work.

Zone Home
	OnTrackSelection MapSelectedTrackSendsToWidgets
	IncludedZones
		"SelectedChannel|"	
		"Buttons|"
                "MasterChannel|"
		"JogWheelHack|"
	IncludedZonesEnd
ZoneEnd

Zone "SelectedChannel|"
	SelectedTrackNavigator

        Zoom				Shift	

	F1 				TrackAutoMode 1 	//Read
	F2 				TrackAutoMode 3 	//Write
	F3 				TrackAutoMode 0 	//Trim
	F4 				TrackAutoMode 2 	//touch
	F5				TrackAutoMode 4 	//Latch
	F6				Reaper 40364 		//Toggle metronome
	Shift+F1			GoZone Home
	Shift+F2			GoZone FocusedFXParam
ZoneEnd

Zone "FocusedFXParam"
        Fader1 FocusedFXParam
	DisplayUpper1 FocusedFXParamNameDisplay
	DisplayLower1 FocusedFXParamValueDisplay
ZoneEnd

[Cragster]

Originally Posted by Funkybot

Cragster, my general rule of thumb is: if the surface transmits release messages, then tell CSI about them in the widget. The .mst file is all about the "defining the capabilities of the surface" so that should include release messages where they get sent. You'll also ABSOLUTELY need release messages if you want to get the best behavior out of modifiers like Shift, Alt, Option, Ctrl. If you started getting weird behavior with them included, then you could always remove the release messages from the widget, but I don't think there's any harm in defining them where they exist and it's probably recommended.

And yes, FB_TwoState is all about lighting the button. But remember: it's highly contingent on what Reaper action is assigned to that button and whether that action properly reports it state. I have a few buttons where I commented out the FB_TwoState line for the widget because it was keeping lights on when I didn't want them on, and just turning lights off entirely made more sense.

Hey thank you very much. Explained perfectly

[spkr4thdd]

Originally Posted by Funkybot

Geoff, I'm getting a bug here with FocusedFXParam on a particular project. As best I can explain it, here's what's happening:

1. I open this project
2. I open an FX that happens to be located in the back half of the track count, focus a parameter
3. Press Shift+F2 to enter FocusedFXParam mode and...

Nothing happens. Weird. Now...

4. Try a different FX, something towards the start of the track list

Result: something comes up, but it's not the FXParam in focus. The Parameter looks like it belongs to an entirely different plugin. Now, if I move around and click different parameters in this synth or effect, it'll show me different parameters other than what's in focus. Again, looking like they belong to an entirely different plugin

OK, while not identical, this smacks of the same issue as I found when writing the zon for my VMR... it worked for an early track in the project, but the further down the row I got the less likely it was to work. And when it didn't seem to work, if I armed Write mode it would show that was receiving an action for another FX somewhere in the mix...

I'll try to find some time to dive back in to it and detail the errors fully, but m earlier post on this has some of my initial findings.

[inertia]

Finally gotten around to setting up the Console 1 with CSI.

Do we have any collections of zone files somewhere for FX control?

I am mapping the BX SSL 4KE and will gladly start uploading my FX maps as I do them if not already done.

[Funkybot]

Geoff, found a potential bug with encoders+FB_Fader7Bit and trying to invert a parameter.

So this works as expected:

Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

But trying to invert the direction does not.

Invert+Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

Adding invert makes it kind of toggle through steps backwards in an unexpected way and messes with the encoder feedback, which I think is the issue. My widget looks like this:

Widget Rotary1
	Encoder b0 00 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]
	FB_Fader7Bit b0 00 00
WidgetEnd

Using ReaComp, I want to flip it so CW turns "decrease the threshold" (in my mind that's increasing the threshold).

[Funkybot]

Originally Posted by inertia

Finally gotten around to setting up the Console 1 with CSI.

Do we have any collections of zone files somewhere for FX control?

I am mapping the BX SSL 4KE and will gladly start uploading my FX maps as I do them if not already done.

You should definitely share any fx.zon's you do for the Console1! Or any other surface!

[Nick Morris]

Is it possible to use CSI to make the avid artist transport scroll through tracks? Meaning turning the wheel and track selection goes to next track or previous track depending on direction of the wheel turn?

I know there is an action for this, but can it be used like I want with the wheel?

[RobinGShore]

Originally Posted by Geoff Waddington

Also, didn't hear back, did you ever get going again, you were having issues last post I recall.

Sorry, was busy all last week and didn't have time try again. It's working again for me now. I've still been using your old Eucon plugin for my actual day to day work, but I'm gonna give the CSI version a proper test drive over the next few days and will let you know any thoughts/issues I come across

[Cragster]

Originally Posted by Funkybot

Geoff, found a potential bug with encoders+FB_Fader7Bit and trying to invert a parameter.

So this works as expected:

Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

But trying to invert the direction does not.

Invert+Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

Adding invert makes it kind of toggle through steps backwards in an unexpected way and messes with the encoder feedback, which I think is the issue. My widget looks like this:

Widget Rotary1
	Encoder b0 00 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]
	FB_Fader7Bit b0 00 00
WidgetEnd

Using ReaComp, I want to flip it so CW turns "decrease the threshold" (in my mind that's increasing the threshold).

Did you try just changing the steps [(0.075 0.05 0.033 etc)]. i know that used to work on steps. I dont know just an idea. Someday i will pay back all the help you gave me

[MixMonkey]

Originally Posted by Funkybot

Geoff, found a potential bug with encoders+FB_Fader7Bit and trying to invert a parameter.

So this works as expected:

Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

But trying to invert the direction does not.

Invert+Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

Adding invert makes it kind of toggle through steps backwards in an unexpected way and messes with the encoder feedback, which I think is the issue. My widget looks like this:

Widget Rotary1
	Encoder b0 00 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]
	FB_Fader7Bit b0 00 00
WidgetEnd

Using ReaComp, I want to flip it so CW turns "decrease the threshold" (in my mind that's increasing the threshold).

These aren't steps, they're acceleration coefficients:

Invert+Rotary1 FXParam "0" "Thresh" [ (0.001,0.0015,0.002,0.0025,0.005,0.0075,0.0125,0.0215,0.033,0.05,0.075) ]

Steps would be:

Invert+Rotary1 FXParam "0" "Thresh" [ 0.001 0.0015 0.002 0.0025 0.005 0.0075 0.0125 0.0215 0.033 0.05 0.075 ]

[Funkybot]

Yes, I know those aren't steps. I don't know why I said "toggle through the steps backwards" that wasn't very clear on my part. I should've said "move through the parameter backwards."

What I was trying to do was:

1. Keep encoder acceleration
2. Reverse the direction I need to turn the knob to decrease the threshold

At first I just assumed it was the acceleration that didn't work with invert, but the more I thought about the more I think it's actually the combination of the encoder+Fader_7Bit widget. I think when I use the invert modifier, the FB processor is still expecting normal behavior even though the encoder step direction should have been reversed. So I'm turning the encoder up and expecting the FB to go down, but that's not happening. Or maybe invert+encoders just act a little funky together.

[MixMonkey]

Originally Posted by Funkybot

Yes, I know those aren't steps. If they were, I would have just reversed the order.

What I was trying to do was:

1. Keep encoder acceleration
2. Reverse the direction I need to turn the knob to decrease the threshold

At first I just assumed it was the acceleration that didn't work with invert, but the more I thought about the more I think it's actually the combination of the encoder+Fader_7Bit widget. I think when I use the invert modifier, the FB processor is still expecting normal behavior even though the encoder step direction should have been reversed. So I'm turning the encoder up and expecting the FB to go down, but that's not happening. Or maybe invert+encoders just act a little funky together.

Ah, I see Did you try it without the FB? (just comment out the FB in the .mst) This may affect the bounds, but the encoder should still work.

My guess would be the same as your conclusion- Invert+Encoders = weirdness.

[Funkybot]

Originally Posted by MixMonkey

Ah, I see Did you try it without the FB? (just comment out the FB in the .mst) This may affect the bounds, but the encoder should still work.

My guess would be the same as your conclusion- Invert+Encoders = weirdness.

I'm a little embarrassed I didn't think to comment out the feedback until you suggested it. Will try it out after work and report back.

[inertia]

I am having trouble getting FocusedFXNavigator to work with the plugins and my Console 1

Here is my Console 1 zone

Zone "Home"
//OnTrackSelection GoZone "Channel"
OnFXFocus MapFocusedFXToWidgets
DisplayFX SetShowFXWindows
Mode ToggleMapSelectedTrackFX
Preset GoZone "Home"
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
//Shape ToggleLearnMode
// Option+Volume FocusedFXParam
ZoneEnd

and here is my Slate fx zone

Zone "VST: VBC FG-Grey (Slate Digital)"
FocusedFXNavigator
Volume FXParam 0 "Make-Up Gain"
Toggle+Invert+Compressor FXParam 1 "Bypass"
Attack FXParam 2 "Attack"
Toggle+Invert+Solo FXParam 3 "Auto Release"
Release FXParam 4 "Release"
Ratio FXParam 5 "Ratio"
Parallel FXParam 6 "Mix"
FXParam 7 "Meter Selector"
Character FXParam 8 "HPF"
Threshold FXParam 9 "Threshold"
Toggle+Invert+Compressor FXParam 10 "Bypass"
FXParam 11 "Wet"
CompressorMeter FXParam "GainReductionDB"
ZoneEnd


The mapping works fine with SelectedTrackNavigaton.

[Funkybot]

Originally Posted by MixMonkey

Ah, I see Did you try it without the FB? (just comment out the FB in the .mst) This may affect the bounds, but the encoder should still work.

My guess would be the same as your conclusion- Invert+Encoders = weirdness.

Ok, so I commented out the feedback, and it made no difference.

Invert+SomeEncoder just doesn't work as expected.

My expectation would be that this:

	Encoder b0 00 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]

Effectively became this once Invert was added as a modifier:

	Encoder b0 00 7f [ > 3f 3e 3d 3c 3b 3a 39 38 36 33 2f < 41 42 43 44 45 46 47 48 4a 4d 51 ]

[Geoff Waddington]

Originally Posted by Funkybot

Ok, so I commented out the feedback, and it made no difference.

Invert+SomeEncoder just doesn't work as expected.

My expectation would be that this:

	Encoder b0 00 7f [ < 3f 3e 3d 3c 3b 3a 39 38 36 33 2f > 41 42 43 44 45 46 47 48 4a 4d 51 ]

Effectively became this once Invert was added as a modifier:

	Encoder b0 00 7f [ > 3f 3e 3d 3c 3b 3a 39 38 36 33 2f < 41 42 43 44 45 46 47 48 4a 4d 51 ]

Yeah, Invert is not made for stepped values, just reverse the list

[Geoff Waddington]

New builds are up.

Hard few days of work

EuCon now has support for formatted FX param values as well as control over thermometer styles on a per parameter / per Action basis.

See the Harrison mapping in the EuCon folder for some ideas, and try it out if you have a Harrison, the CSI concept shows itself well in that mapping.

For instance:
2nd rotary shows "Low" -- until you touch/turn it -- then it shows DB boost cut
The thermometer is set to boost/cut style.

3rd rotary always shows low frequency in Hz -- no need to explain, and the "Low" label on the channel to the left orients you.
The thermometer is set to point style.

And so on for Low Mid, Hi Mid, HI, you get the idea

Have fun, and let me know how it goes

[Funkybot]

Originally Posted by Geoff Waddington

Yeah, Invert is not made for stepped values, just reverse the list

But Geoff, they're not stepped values. That's acceleration.

We should be able to invert a standard Encoder with acceleration (and no steps).