|
|
|
04-09-2020, 07:25 AM
|
#8041
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
Hi Geoff. Here are my mappings for my modifier buttons i am desperately trying to have stay lit when i press them and am in that mode. i also included my automation button mappings that work correctly. when i press any of the automation buttons they stay lit. im trying to get the modifiers to do the same. i tried to duplicate the mapping from the automation buttons to the modifiers but no go.i actually tried a bunch of differnt mappings. fb twostate and others. do u have any suggestions for these modifiers to stay lit. they do light while im holding them but go out when i let go.
Code:
Widget Shift
Press 90 46 7f 90 46 00
WidgetEnd
Widget Option
Press 90 47 7f 90 47 00
WidgetEnd
Widget Control
Press 90 48 7f 90 48 00
WidgetEnd
Widget Alt
Press 90 49 7f 90 49 00
WidgetEnd
Widget Read
Press 90 4a 7f
FB_TwoState 90 4a 7f 90 4a 00
WidgetEnd
Widget Write
Press 90 4b 7f
FB_TwoState 90 4b 7f 90 4b 00
WidgetEnd
Widget Trim
Press 90 4c 7f
FB_TwoState 90 4c 7f 90 4c 00
WidgetEnd
Widget Touch
Press 90 4d 7f
FB_TwoState 90 4d 7f 90 4d 00
WidgetEnd
Widget Latch
Press 90 4e 7f
FB_TwoState 90 4e 7f 90 4e 00
WidgetEnd
and zone
Code:
Zone "Buttons|"
Shift Shift
Option Option
Control Control
Alt Alt
Read TrackAutoMode "1"
Shift+Read GlobalAutoMode "1"
Write TrackAutoMode "3"
Shift+Write GlobalAutoMode "3"
Trim TrackAutoMode "0"
Shift+Trim GlobalAutoMode "0"
Touch TrackAutoMode "2"
Shift+Touch GlobalAutoMode "2"
Latch TrackAutoMode "4"
Shift+Latch GlobalAutoMode "4"
i trying to get modifiers to work as the automation does.stays lit when i press.the automations are i guess radio button types. when i press one the others go out .i dont know.hope i explained this right. just trying to have buttons stay lit when pressed.thanks for your help
|
No they are not Radio types, just buttons that accept feedback from CSI.
Look closely at your Widget definitions.
See how the Automation buttons define a Press AND an FB_TwoState.
The FB_Two_State is what tells CSI to send feedback, and also defines the midi messages necessary.
So just do this:
Code:
Widget Shift
Press 90 46 7f 90 46 00
FB_TwoState 90 46 7f 90 46 00
WidgetEnd
Widget Option
Press 90 47 7f 90 47 00
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
Widget Control
Press 90 48 7f 90 48 00
FB_TwoState 90 48 7f 90 48 00
WidgetEnd
Widget Alt
Press 90 49 7f 90 49 00
FB_TwoState 90 49 7f 90 49 00
WidgetEnd
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-09-2020, 07:27 AM
|
#8042
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
You might need the ability to locally override.
Think there is a reasonable solution though.
The syntax is:
Code:
someButton3 someAction3 [ LogTaper.scn ]
The behaviour:
Look in folder where the .zon file resides.
If there is a folder named Tables and there is a LogTaper.scn in there, use it.
If not look in CSI/Tables for LogTaper.scn.
If you can't find it there, bail, and don't assign stepped values.
What do you think ?
|
This sounds fine If you didn't need the local overide, the files would reside in CSI/Tables.
|
|
|
04-09-2020, 07:28 AM
|
#8043
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by rschlierbeck
Thanks MixMonkey.That was very helpful. I see now that I have altered the setup of my BCR2000 through Behringer's configuration tool so my encoders and buttons are not going to match what other people have. But your example got me connected so now I have something to build from.
|
You're welcome I don't know how far you've got with it, but I have a completed BCR2000.mst if you're interested.
|
|
|
04-09-2020, 07:47 AM
|
#8044
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
No they are not Radio types, just buttons that accept feedback from CSI.
Look closely at your Widget definitions.
See how the Automation buttons define a Press AND an FB_TwoState.
The FB_Two_State is what tells CSI to send feedback, and also defines the midi messages necessary.
So just do this:
Code:
Widget Shift
Press 90 46 7f 90 46 00
FB_TwoState 90 46 7f 90 46 00
WidgetEnd
Widget Option
Press 90 47 7f 90 47 00
FB_TwoState 90 47 7f 90 47 00
WidgetEnd
Widget Control
Press 90 48 7f 90 48 00
FB_TwoState 90 48 7f 90 48 00
WidgetEnd
Widget Alt
Press 90 49 7f 90 49 00
FB_TwoState 90 49 7f 90 49 00
WidgetEnd
|
thanks Geoff but yes i tried that. just tried it again to be sure and no go.im assuming its the surface ? is there anything else i can try ?
|
|
|
04-09-2020, 08:00 AM
|
#8045
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
thanks Geoff but yes i tried that. just tried it again to be sure and no go.im assuming its the surface ? is there anything else i can try ?
|
Ok, to see if it is indeed the surface do this temporarily:
Code:
Zone "Buttons|"
Read Shift
Write Option
Trim Control
Latch Alt
// remove the following lines temporarily to prevent the dreaded double mappings :)
Read TrackAutoMode "1"
Shift+Read GlobalAutoMode "1"
Write TrackAutoMode "3"
Shift+Write GlobalAutoMode "3"
Trim TrackAutoMode "0"
Shift+Trim GlobalAutoMode "0"
Touch TrackAutoMode "2"
Shift+Touch GlobalAutoMode "2"
Latch TrackAutoMode "4"
Shift+Latch GlobalAutoMode "4"
Let us know what happens.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-09-2020, 08:27 AM
|
#8046
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by tdc
This custom ReaScript does not show state, so I will need to investigate another method, potentially making use of a Cycle Action.
|
Not sure if this will help, but when you create a custom action there are two radio buttons that dictate how the state will be reported. One is for "if Reaper can determine that all states are active" and the other is "if Reaper determines all states are active or cannot be determined."
You can even try using a Cycle Action and see if that helps. I forget what the exact context was but I recently found that Reaper's toolbar wasn't reporting a button state the way I wanted, but when I created a cycle action and used that instead, it did what I wanted.
As always, experimentation is key. There's usually a way.
|
|
|
04-09-2020, 08:43 AM
|
#8047
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
Ok, to see if it is indeed the surface do this temporarily:
Code:
Zone "Buttons|"
Read Shift
Write Option
Trim Control
Latch Alt
// remove the following lines temporarily to prevent the dreaded double mappings :)
Read TrackAutoMode "1"
Shift+Read GlobalAutoMode "1"
Write TrackAutoMode "3"
Shift+Write GlobalAutoMode "3"
Trim TrackAutoMode "0"
Shift+Trim GlobalAutoMode "0"
Touch TrackAutoMode "2"
Shift+Touch GlobalAutoMode "2"
Latch TrackAutoMode "4"
Shift+Latch GlobalAutoMode "4"
Let us know what happens.
|
im not entirely sure what you said to do here but if i read it correctly i disabled all the automation lines. and turned those automation buttons into modifiers ? just to let you know there is a button template that goes over the buttons and there are seperate buttons for automation and modifiers.so im trying to stick to the overlay template. but i did disable automation mapping and switched those buttons to modifiers .(read write trim touch now is shift opt cont alt in the zone).is that what you wanted me to do ? well i did that and if i press for example the shift (which was previously read) it lights and goes into shift mode and stays lit but i cant come out of it unless i refresh the surface. im sry Geoff im a bit confused
the automation buttons work great. its the modifier buttons i want to stay lit
Last edited by Cragster; 04-09-2020 at 09:10 AM.
|
|
|
04-09-2020, 10:10 AM
|
#8048
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
im not entirely sure what you said to do here but if i read it correctly i disabled all the automation lines. and turned those automation buttons into modifiers ? just to let you know there is a button template that goes over the buttons and there are seperate buttons for automation and modifiers.so im trying to stick to the overlay template. but i did disable automation mapping and switched those buttons to modifiers .(read write trim touch now is shift opt cont alt in the zone).is that what you wanted me to do ? well i did that and if i press for example the shift (which was previously read) it lights and goes into shift mode and stays lit but i cant come out of it unless i refresh the surface. im sry Geoff im a bit confused
the automation buttons work great. its the modifier buttons i want to stay lit
|
I know the automation buttons work, that's why we want to use them for testing
So, make a copy of the .zon file so you can go back.
Open the original and REMOVE all the automaton stuff, we don't want to use automation right now and we don't want those definitions messing up our test, we want to use the Automation buttons to test modifier actions because we know they light up properly -- once again this is for testing only
Change the automation buttons to be the modifier buttons.
Code:
Zone "Buttons|"
Read Shift
Write Option
Trim Control
Latch Alt
ZoneEnd
Now test this.
Do the automation buttons correctly reflect the modifiers to which they are mapped ?
If yes, there is something wrong on the surface side with the surface modifier buttons.
If no, there is something funky in the Zone definition.
Just trying to isolate which, so we can solve this.
Do you see what we are trying to do here ?
If anything is unclear, ask away
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-09-2020, 11:09 AM
|
#8049
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
I know the automation buttons work, that's why we want to use them for testing
So, make a copy of the .zon file so you can go back.
Open the original and REMOVE all the automaton stuff, we don't want to use automation right now and we don't want those definitions messing up our test, we want to use the Automation buttons to test modifier actions because we know they light up properly -- once again this is for testing only
Change the automation buttons to be the modifier buttons.
Code:
Zone "Buttons|"
Read Shift
Write Option
Trim Control
Latch Alt
ZoneEnd
Now test this.
Do the automation buttons correctly reflect the modifiers to which they are mapped ?
If yes, there is something wrong on the surface side with the surface modifier buttons.
If no, there is something funky in the Zone definition.
Just trying to isolate which, so we can solve this.
Do you see what we are trying to do here ?
If anything is unclear, ask away
|
Ok thanks Geoff. So i did read that right. Yes thats what i did. I / slashed out all the automation lines and turned the automation buttons into the modifier buttons and they did correctly reflect the modifier they were mapped to. Well almost .when pressed it would go into that modifier mode and stay lit. But it would be stuck there. Probly cause the way i have thise automation buttons mapped in the mst ? They are slightly different in the mst.i included them in that first post i sent you. But yes they did work the modifiers .just had to refresh the surface to exit them. And sry as you know im a little slow sometimes with this stuff. So that means its a surface problem ?
|
|
|
04-09-2020, 11:48 AM
|
#8050
|
Human being with feelings
Join Date: Sep 2014
Posts: 68
|
Quote:
Originally Posted by MixMonkey
You're welcome I don't know how far you've got with it, but I have a completed BCR2000.mst if you're interested.
|
Yes, thank you. That would be great. I have one that I cobbled together but I would like to see how someone else (with a better understanding of this) has set it up.
Through this exercise I remembered that i had actually programmed my BCR differently to function with my plugins and the REAPER mapping. So I've had to dig out the programming guide and software again to see what I had done. Now I have to opportunity to program presets on the BCR that better match how CSI will use it. It's great that the devices are so flexible but it puts the responsibility on me to get it right.
What do you find works best for the encoders? I have the choice to set them as:
Absolute (0-127)
Absolute 14 bit (0-16383)
Relative
Relative 14 bit
Increment/Decrement
|
|
|
04-09-2020, 12:01 PM
|
#8051
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
Ok thanks Geoff. So i did read that right. Yes thats what i did. I / slashed out all the automation lines and turned the automation buttons into the modifier buttons and they did correctly reflect the modifier they were mapped to. Well almost .when pressed it would go into that modifier mode and stay lit. But it would be stuck there. Probly cause the way i have thise automation buttons mapped in the mst ? They are slightly different in the mst.i included them in that first post i sent you. But yes they did work the modifiers .just had to refresh the surface to exit them. And sry as you know im a little slow sometimes with this stuff. So that means its a surface problem ?
|
Haha, I think I know the problem, well maybe
If you tap a modifier (e.g. Shift), it "Latches" -- aka stays on.
You are now in Shift mode.
Want to get out?
Just hold down Shift for a second and let go - light goes off.
If you want to temporarily Shift just hold it down whilst pressing another button.
That's why it is so important to have modifiers with lights
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-09-2020, 12:54 PM
|
#8052
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
Haha, I think I know the problem, well maybe
If you tap a modifier (e.g. Shift), it "Latches" -- aka stays on.
You are now in Shift mode.
Want to get out?
Just hold down Shift for a second and let go - light goes off.
If you want to temporarily Shift just hold it down whilst pressing another button.
That's why it is so important to have modifiers with lights
|
Yes i know all that. Which is why i want the modifiers to stay lit . So what do i do now ? I obviously want to put the modifiers and automation buttons back to the right way. So its the surface as to why they wont stay lit in latch mode ? Wen i quick press the modifier to latch it diesnt stay lit. It does wen i map them to the automation buttons but not we they are mapped to the actual modifier buttons
Last edited by Cragster; 04-09-2020 at 01:00 PM.
|
|
|
04-09-2020, 01:04 PM
|
#8053
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Quote:
Originally Posted by Geoff Waddington
Yes, it needs to know the state of the action in order to set the light, so it is at the mercy of what ever the action reports.
If you look in the Reaper actions list you will see your custom action that launches the script and the State column will be blank, meaning it does not report state changes.
There may be a way to setup custom actions to report state, I don't know, maybe someone will chime in.
|
Well, that's tonight's mixing goosed!! Time to get these lights fixed
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
04-09-2020, 01:30 PM
|
#8054
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by rschlierbeck
What do you find works best for the encoders? I have the choice to set them as:
Absolute (0-127)
Absolute 14 bit (0-16383)
Relative
Relative 14 bit
Increment/Decrement
|
I stuck with Absolute (0-127), because the inc/dec modes didn't seem to allow feedback to the LED encoder ring.
I've attached the BCR2000.mst. It comes with both a sysex file and a .bcr file to load the appropriate settings into the unit (pick a patch you're not using) It looks like you're using BCManager so probably go for the .bcr.
The button LEDs are a problem because there doesn't seem to be a way of stopping the unit controlling the LEDs internally, but see how you get on.
Last edited by MixMonkey; 09-06-2020 at 11:44 AM.
|
|
|
04-09-2020, 01:44 PM
|
#8055
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by Cragster
Yes i know all that. Which is why i want the modifiers to stay lit . So what do i do now ? I obviously want to put the modifiers and automation buttons back to the right way. So its the surface as to why they wont stay lit in latch mode ? Wen i quick press the modifier to latch it diesnt stay lit. It does wen i map them to the automation buttons but not we they are mapped to the actual modifier buttons
|
They should stay lit when they are latched.
In order to help, I need some info.
When you press the Read button which is mapped to Shift does it light up ?
When you let it go, does the light go off.
If you tap it does it stay lit ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Last edited by Geoff Waddington; 04-09-2020 at 01:54 PM.
|
|
|
04-09-2020, 02:05 PM
|
#8056
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by Geoff Waddington
They should stay lit when they are latched.
In order to help, I need some info.
When you press the Read button which is mapped to Shift does it light up ?
When you let it go, does the light go off.
If you tap it does int stay lit ?
|
Im unfortunately at work now and not at my computer (im a night shifter).but when i was i remember yes it did light when i pressed read mapped to shift.it did not go out wen i let go.and yes it did stay lit when i tapped it.but ill try it all again to be sure. I remember i had to refresh the surface to get out of the latch.thats all i was able to try before i had to get off to work. We can pick this back up tmr if thats ok when im back at my computer and i can try your suggestions . And thank you Geoff so far for your help. I realky appreciate it .im obviously not a recording engineer or computer programmer like you guys and i get lost alot on this forum.but i try my best to chip in. So it means alot that your helping me. Thanks man !!!.ill try to catch you tmr and hope to get this working.
|
|
|
04-09-2020, 04:45 PM
|
#8057
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Ok, was busy for the last few days optimizing for speed, hadn't done a tuneup in a while, managed to get some real improvements.
These quick tests were done to measure the "update load" -- the load caused by CSI just periodically updating the surfaces. There is no input (no button pushing etc.), this is to get a ballpark idea of just the refreshing that occurs all the time.
Happy to report update load down by up to 85% in some of the best cases.
The following tests were done on a late 2012 Mac Mini (2.3 GHz quad i7) running 10.14.6 and Reaper 6.0.
This is a 1420 Track torture test that won't actually run on this box, but you can bank the tracks while it is stopped, so it is valuable as a nice beefy test case.
The EuCon rig (2 Mixes and a Transport) is set up as a 512 Channel EuCon console -- took about 8 minutes for EuControl to concoct it, but it didn't fall over, and ran beautifully once it got online
Banking was almost as responsive as with the 16 Channel / 140 Track standard project used for everyday testing.
Here are the results of a few runs. These are for a single pass, usually the refresh rate for surfaces is set between 15 - 30 Hz so multiply these numbers by about 20 to get a feel for how much of a second CSI eats up -- hint - it's not much
A majority of tracks have an FX or 3 on them plus a few Sends.
1420 Track project
512 Channel EuCon console
Don't forget these are microseconds, divide by 1000 to get milliseconds.
Rebuild Track List - 599 microseconds
Console1 - HandleExternalInput - 2 microseconds
LaunchPad - HandleExternalInput - 2 microseconds
iPad - HandleExternalInput - 10 microseconds
iPhone - HandleExternalInput - 8 microseconds
EuCon - HandleExternalInput - 1 microseconds
Console1 - Request Update - 49 microseconds
LaunchPad - Request Update - 196 microseconds
iPad - Request Update - 12 microseconds
iPhone - Request Update - 12 microseconds
EuCon - Request Update - 513 microseconds
Update Edit Mode Window - 3 microseconds
Total duration = 1407
Rebuild Track List - 391 microseconds
Console1 - HandleExternalInput - 2 microseconds
LaunchPad - HandleExternalInput - 2 microseconds
iPad - HandleExternalInput - 12 microseconds
iPhone - HandleExternalInput - 8 microseconds
EuCon - HandleExternalInput - 2 microseconds
Console1 - Request Update - 35 microseconds
LaunchPad - Request Update - 225 microseconds
iPad - Request Update - 27 microseconds
iPhone - Request Update - 14 microseconds
EuCon - Request Update - 507 microseconds
Update Edit Mode Window - 1 microseconds
Total duration = 1226
Rebuild Track List - 417 microseconds
Console1 - HandleExternalInput - 3 microseconds
LaunchPad - HandleExternalInput - 2 microseconds
iPad - HandleExternalInput - 11 microseconds
iPhone - HandleExternalInput - 10 microseconds
EuCon - HandleExternalInput - 4 microseconds
Console1 - Request Update - 36 microseconds
LaunchPad - Request Update - 258 microseconds
iPad - Request Update - 26 microseconds
iPhone - Request Update - 23 microseconds
EuCon - Request Update - 520 microseconds
Update Edit Mode Window - 2 microseconds
Total duration = 1312
Rebuild Track List - 429 microseconds
Console1 - HandleExternalInput - 2 microseconds
LaunchPad - HandleExternalInput - 3 microseconds
iPad - HandleExternalInput - 12 microseconds
iPhone - HandleExternalInput - 13 microseconds
EuCon - HandleExternalInput - 2 microseconds
Console1 - Request Update - 43 microseconds
LaunchPad - Request Update - 199 microseconds
iPad - Request Update - 20 microseconds
iPhone - Request Update - 20 microseconds
EuCon - Request Update - 530 microseconds
Update Edit Mode Window - 2 microseconds
Total duration = 1275
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-09-2020, 04:48 PM
|
#8058
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
Track Sends but no FXMenu
OK, I'm just about going crazy here...
So. MST has two widgets; Send and Plugin
Code:
Widget Send
Press 90 29 7f
FB_TwoState 90 29 7f 90 29 00
WidgetEnd
Widget Plugin
Press 90 2B 7f
FB_TwoState 90 2B 7f 90 2B 00
WidgetEnd
Both have LEDs and turn on/off when pressed. (Good start!)
Both are assigned in the ZON file in the 'Buttons|' zone to the following actions:
Code:
Send ToggleMapSelectedTrackSends
Plugin ToggleMapSelectedTrackFXMenu
The Send|1-8 zone is as follows:
Code:
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
And works perfectly when the SEND button is pressed, switching the displays to show the sends and their volumes, with the Faders setting to ) or whatever the send volume is. And returning to normal view once pressed again.
The FXMenu, however, is driving me crazy! I've tried as you see in the 'Button|' zone above, and I've tried it as a 'GoZone FXMenu|' (which stops the LED working?). And neither do anything at all? Here's the FXMenu Zone.
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
What I'm expecting that to do is Show the FX in Slots 1-8 across Channel Displays 1-8 and allow me to select the FX with a push of the relevant Rotary...
Am I missing something really simple?
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
04-09-2020, 05:10 PM
|
#8059
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by spkr4thdd
OK, I'm just about going crazy here...
So. MST has two widgets; Send and Plugin
Code:
Widget Send
Press 90 29 7f
FB_TwoState 90 29 7f 90 29 00
WidgetEnd
Widget Plugin
Press 90 2B 7f
FB_TwoState 90 2B 7f 90 2B 00
WidgetEnd
Both have LEDs and turn on/off when pressed. (Good start!)
Both are assigned in the ZON file in the 'Buttons|' zone to the following actions:
Code:
Send ToggleMapSelectedTrackSends
Plugin ToggleMapSelectedTrackFXMenu
The Send|1-8 zone is as follows:
Code:
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
And works perfectly when the SEND button is pressed, switching the displays to show the sends and their volumes, with the Faders setting to ) or whatever the send volume is. And returning to normal view once pressed again.
The FXMenu, however, is driving me crazy! I've tried as you see in the 'Button|' zone above, and I've tried it as a 'GoZone FXMenu|' (which stops the LED working?). And neither do anything at all? Here's the FXMenu Zone.
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
What I'm expecting that to do is Show the FX in Slots 1-8 across Channel Displays 1-8 and allow me to select the FX with a push of the relevant Rotary...
Am I missing something really simple?
|
Are your plugin zones also set to selectedtracknavigator ?i use the fx menu/selected track navigator as opposed to the focus fx navigator and they do show up sloted across the display
|
|
|
04-09-2020, 05:11 PM
|
#8060
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by spkr4thdd
OK, I'm just about going crazy here...
So. MST has two widgets; Send and Plugin
Code:
Widget Send
Press 90 29 7f
FB_TwoState 90 29 7f 90 29 00
WidgetEnd
Widget Plugin
Press 90 2B 7f
FB_TwoState 90 2B 7f 90 2B 00
WidgetEnd
Both have LEDs and turn on/off when pressed. (Good start!)
Both are assigned in the ZON file in the 'Buttons|' zone to the following actions:
Code:
Send ToggleMapSelectedTrackSends
Plugin ToggleMapSelectedTrackFXMenu
The Send|1-8 zone is as follows:
Code:
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
And works perfectly when the SEND button is pressed, switching the displays to show the sends and their volumes, with the Faders setting to ) or whatever the send volume is. And returning to normal view once pressed again.
The FXMenu, however, is driving me crazy! I've tried as you see in the 'Button|' zone above, and I've tried it as a 'GoZone FXMenu|' (which stops the LED working?). And neither do anything at all? Here's the FXMenu Zone.
Code:
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
What I'm expecting that to do is Show the FX in Slots 1-8 across Channel Displays 1-8 and allow me to select the FX with a push of the relevant Rotary...
Am I missing something really simple?
|
Do you have:
Code:
Zone Home
OnTrackSelection MapSelectedTrackFXToMenu
in your Home Zone?
|
|
|
04-09-2020, 05:16 PM
|
#8061
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
@ spkr4thdd. Make sure your plugin zones are mapped to selectedtracknavigator and DONT check the auto fx box in the csi setup window
And what mixmonkey said
|
|
|
04-09-2020, 05:37 PM
|
#8062
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
I have a question for you guys. Can i have more then one fx plugin zone file with the same name in one folder ? Or do i have to split them up into different folders and access them using "pages" ? I hope i worded that right. Thanks all
|
|
|
04-09-2020, 05:39 PM
|
#8063
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Cragster
I have a question for you guys. Can i have more then one fx plugin zone file with the same name in one folder ? Or do i have to split them up into different folders and access them using "pages" ? I hope i worded that right. Thanks all
|
No, all the FX Zones have to have unique names. What are you trying to achieve?
|
|
|
04-09-2020, 05:55 PM
|
#8064
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
No, all the FX Zones have to have unique names. What are you trying to achieve?
|
Ok let me see if i can explain this right. I know u experienced recording guy are gonna cringe at this but im not an engineer.i know what sound i want but sometimes i have trouble getting there.so ive been using this izotope mothership like plugin. I love the presets they have and it gets me close then i just tweek the parameters from there. Anyway this one plugin has all the plugins in one...eq...2 compressors..transient shaper etc etc and the UI is a mile long.so i want to make seperate zone files for each module...ie one for the eq ..one each for the compressors and so on.cause its too much for one zone file .but all these seperate zone files will obviously have the same plugin name. So i was thinking of splitting them up into different surface folders and calling them up using csi pages. Can i do that ? I already mapped the eq module. So im ready to move on to the next module. Ok did i explain that right ? I do use regular plugins alot also but sometimes i just cant find the sound im looking for and more times then not this izotope super plugin gets me close
|
|
|
04-09-2020, 06:19 PM
|
#8065
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Cragster
Ok let me see if i can explain this right. I know u experienced recording guy are gonna cringe at this but im not an engineer.i know what sound i want but sometimes i have trouble getting there.so ive been using this izotope mothership like plugin. I love the presets they have and it gets me close then i just tweek the parameters from there. Anyway this one plugin has all the plugins in one...eq...2 compressors..transient shaper etc etc and the UI is a mile long.so i want to make seperate zone files for each module...ie one for the eq ..one each for the compressors and so on.cause its too much for one zone file .but all these seperate zone files will obviously have the same plugin name. So i was thinking of splitting them up into different surface folders and calling them up using csi pages. Can i do that ? I already mapped the eq module. So im ready to move on to the next module. Ok did i explain that right ? I do use regular plugins alot also but sometimes i just cant find the sound im looking for and more times then not this izotope super plugin gets me close
|
Ok, I think I get it
You could split the various modules into in sub-zones like this:
Code:
Zone "VST: Oxford Dynamics (Sonnox)" "OxDyn"
SelectedTrackNavigator
/
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-1"
DisplayLowerA1 FXParamValueDisplay 45
RotaryA1 FXParam 45
Toggle+RotaryPushA1 FXParam 44
/
DisplayUpperA2 NoAction
DisplayLowerA2 NoAction
RotaryA2 NoAction
Toggle+RotaryPushA2 NoAction
/
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
Toggle+RotaryPushA3 NoAction
/
DisplayUpperA4 NoAction
DisplayLowerA4 NoAction
RotaryA4 NoAction
Toggle+RotaryPushA4 NoAction
/
DisplayUpperA5 FXParamNameDisplay 39 "EQ_Sig"
DisplayLowerA5 FXParamValueDisplay 39
RotaryA5 FXParam 39
Toggle+RotaryPushA5 FXParam 39
/
DisplayUpperA6 FXParamNameDisplay 30 "Input"
DisplayLowerA6 FXParamValueDisplay 30
RotaryA6 FXParam 30
Toggle+RotaryPushA6 NoAction
/
DisplayUpperA7 FXParamNameDisplay 32 "LFQ"
DisplayLowerA7 FXParamValueDisplay 32
RotaryA7 FXParam 32
Toggle+RotaryPushA7 FXParam 37
/
DisplayUpperA8 FXParamNameDisplay 33 "HFQ"
DisplayLowerA8 FXParamValueDisplay 33
RotaryA8 FXParam 33
Toggle+RotaryPushA8 FXParam 38
/
DisplayUpperB1 FXParamNameDisplay 42 "Warmth"
DisplayLowerB1 FXParamValueDisplay 42
RotaryB1 FXParam 42
Toggle+RotaryPushB1 FXParam 41
/
DisplayUpperB2 FXParamNameDisplay 43 "WTrim"
DisplayLowerB2 FXParamValueDisplay 43
RotaryB2 FXParam 43
Toggle+RotaryPushB2 NoAction
/
DisplayUpperB3 FXParamNameDisplay 1 "Dither"
DisplayLowerB3 FXParamValueDisplay 1
RotaryB3 FXParam 1 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushB3 FXParam 1 [ 0.0 0.50 1.0 ]
/
DisplayUpperB4 NoAction
DisplayLowerB4 NoAction
RotaryB4 NoAction
Toggle+RotaryPushB4 NoAction
/
DisplayUpperB5 FXParamNameDisplay 40 "EQ_SC"
DisplayLowerB5 FXParamValueDisplay 40
RotaryB5 FXParam 40
Toggle+RotaryPushB5 FXParam 40
/
DisplayUpperB6 FXParamNameDisplay 29 "SC_In"
DisplayLowerB6 FXParamValueDisplay 29
RotaryB6 FXParam 29
Toggle+RotaryPushB6 FXParam 29
/
DisplayUpperB7 FXParamNameDisplay 31 "LF"
DisplayLowerB7 FXParamValueDisplay 31
RotaryB7 FXParam 31
Toggle+RotaryPushB7 FXParam 37
/
DisplayUpperB8 FXParamNameDisplay 34 "HF"
DisplayLowerB8 FXParamValueDisplay 34
RotaryB8 FXParam 34
Toggle+RotaryPushB8 FXParam 38
/
DisplayUpperC1 FXParamNameDisplay 25 "LThrsh"
DisplayLowerC1 FXParamValueDisplay 25
RotaryC1 FXParam 25
Toggle+RotaryPushC1 FXParam 24
/
DisplayUpperC2 NoAction
DisplayLowerC2 NoAction
RotaryC2 NoAction
Toggle+RotaryPushC2 NoAction
/
DisplayUpperC3 FXParamNameDisplay 26 "LAtt"
DisplayLowerC3 FXParamValueDisplay 26
RotaryC3 FXParam 26
Toggle+RotaryPushC3 NoAction
/
DisplayUpperC4 FXParamNameDisplay 27 "LHold"
DisplayLowerC4 FXParamValueDisplay 27
RotaryC4 FXParam 27
Toggle+RotaryPushC4 NoAction
/
DisplayUpperC5 FXParamNameDisplay 28 "LRel"
DisplayLowerC5 FXParamValueDisplay 28
RotaryC5 FXParam 28
Toggle+RotaryPushC5 NoAction
/
DisplayUpperC6 NoAction
DisplayLowerC6 NoAction
RotaryC6 NoAction
Toggle+RotaryPushC6 NoAction
/
DisplayUpperC7 FXParamNameDisplay 35 "LFGain"
DisplayLowerC7 FXParamValueDisplay 35
RotaryC7 FXParam 35
Toggle+RotaryPushC7 NoAction
/
DisplayUpperC8 FXParamNameDisplay 36 "HFGain"
DisplayLowerC8 FXParamValueDisplay 36
RotaryC8 FXParam 36
Toggle+RotaryPushC8 NoAction
/
DisplayUpperD1 FXParamNameDisplay 16 "CThrsh"
DisplayLowerD1 FXParamValueDisplay 16
RotaryD1 FXParam 16
Toggle+RotaryPushD1 FXParam 15
/
DisplayUpperD2 FXParamNameDisplay 20 "CRatio"
DisplayLowerD2 FXParamValueDisplay 20
RotaryD2 FXParam 20
Toggle+RotaryPushD2 NoAction
/
DisplayUpperD3 FXParamNameDisplay 17 "CAtt"
DisplayLowerD3 FXParamValueDisplay 17
RotaryD3 FXParam 17
Toggle+RotaryPushD3 NoAction
/
DisplayUpperD4 FXParamNameDisplay 18 "CHold"
DisplayLowerD4 FXParamValueDisplay 18
RotaryD4 FXParam 18
Toggle+RotaryPushD4 NoAction
/
DisplayUpperD5 FXParamNameDisplay 19 "CRel"
DisplayLowerD5 FXParamValueDisplay 19
RotaryD5 FXParam 19
Toggle+RotaryPushD5 NoAction
/
DisplayUpperD6 FXParamNameDisplay 22 "CKnee"
DisplayLowerD6 FXParamValueDisplay 22
RotaryD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ]
Toggle+RotaryPushD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ]
/
DisplayUpperD7 FXParamNameDisplay 23 "CType"
DisplayLowerD7 FXParamValueDisplay 23
RotaryD7 FXParam 23 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushD7 FXParam 23 [ 0.0 0.50 1.0 ]
/
DisplayUpperD8 FXParamNameDisplay 21 "CMkeUp"
DisplayLowerD8 FXParamValueDisplay 21
RotaryD8 FXParam 21
Toggle+RotaryPushD8 NoAction
/
ZoneEnd
/
Zone "VST: Oxford Dynamics (Sonnox)-2"
SelectedTrackNavigator
ParentZone "VST: Oxford Dynamics (Sonnox)"
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-2"
DisplayLowerA1 FXParamValueDisplay 45
RotaryA1 FXParam 45
Toggle+RotaryPushA1 FXParam 44
/
DisplayUpperA2 NoAction
DisplayLowerA2 NoAction
RotaryA2 NoAction
Toggle+RotaryPushA2 NoAction
/
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
Toggle+RotaryPushA3 NoAction
/
DisplayUpperA4 NoAction
DisplayLowerA4 NoAction
RotaryA4 NoAction
Toggle+RotaryPushA4 NoAction
/
DisplayUpperA5 NoAction
DisplayLowerA5 NoAction
RotaryA5 NoAction
Toggle+RotaryPushA5 NoAction
/
DisplayUpperA6 NoAction
DisplayLowerA6 NoAction
RotaryA6 NoAction
Toggle+RotaryPushA6 NoAction
/
DisplayUpperA7 NoAction
DisplayLowerA7 NoAction
RotaryA7 NoAction
Toggle+RotaryPushA7 NoAction
/
DisplayUpperA8 NoAction
DisplayLowerA8 NoAction
RotaryA8 NoAction
Toggle+RotaryPushA8 NoAction
/
DisplayUpperB1 NoAction
DisplayLowerB1 NoAction
RotaryB1 NoAction
Toggle+RotaryPushB1 NoAction
/
DisplayUpperB2 NoAction
DisplayLowerB2 NoAction
RotaryB2 NoAction
Toggle+RotaryPushB2 NoAction
/
DisplayUpperB3 NoAction
DisplayLowerB3 NoAction
RotaryB3 NoAction
Toggle+RotaryPushB3 NoAction
/
DisplayUpperB4 NoAction
DisplayLowerB4 NoAction
RotaryB4 NoAction
Toggle+RotaryPushB4 NoAction
/
DisplayUpperB5 NoAction
DisplayLowerB5 NoAction
RotaryB5 NoAction
Toggle+RotaryPushB5 NoAction
/
DisplayUpperB6 NoAction
DisplayLowerB6 NoAction
RotaryB6 NoAction
Toggle+RotaryPushB6 NoAction
/
DisplayUpperB7 NoAction
DisplayLowerB7 NoAction
RotaryB7 NoAction
Toggle+RotaryPushB7 NoAction
/
DisplayUpperB8 NoAction
DisplayLowerB8 NoAction
RotaryB8 NoAction
Toggle+RotaryPushB8 NoAction
/
DisplayUpperC1 FXParamNameDisplay 3 "GThrsh"
DisplayLowerC1 FXParamValueDisplay 3
RotaryC1 FXParam 3
Toggle+RotaryPushC1 FXParam 2
/
DisplayUpperC2 NoAction
DisplayLowerC2 NoAction
RotaryC2 NoAction
Toggle+RotaryPushC2 NoAction
/
DisplayUpperC3 FXParamNameDisplay 4 "GAtt"
DisplayLowerC3 FXParamValueDisplay 4
RotaryC3 FXParam 4
Toggle+RotaryPushC3 NoAction
/
DisplayUpperC4 FXParamNameDisplay 5 "GHold"
DisplayLowerC4 FXParamValueDisplay 5
RotaryC4 FXParam 5
Toggle+RotaryPushC4 NoAction
/
DisplayUpperC5 FXParamNameDisplay 6 "GRel"
DisplayLowerC5 FXParamValueDisplay 6
RotaryC5 FXParam 6
Toggle+RotaryPushC5 NoAction
/
DisplayUpperC6 FXParamNameDisplay 7 "GRange"
DisplayLowerC6 FXParamValueDisplay 7
RotaryC6 FXParam 7
Toggle+RotaryPushC6 NoAction
/
DisplayUpperC7 NoAction
DisplayLowerC7 NoAction
RotaryC7 NoAction
Toggle+RotaryPushC7 NoAction
/
DisplayUpperC8 NoAction
DisplayLowerC8 NoAction
RotaryC8 NoAction
Toggle+RotaryPushC8 NoAction
/
DisplayUpperD1 FXParamNameDisplay 9 "EThrsh"
DisplayLowerD1 FXParamValueDisplay 9
RotaryD1 FXParam 9
Toggle+RotaryPushD1 FXParam 8
/
DisplayUpperD2 FXParamNameDisplay 13 "ERatio"
DisplayLowerD2 FXParamValueDisplay 13
RotaryD2 FXParam 13
Toggle+RotaryPushD2 NoAction
/
DisplayUpperD3 FXParamNameDisplay 10 "EAtt"
DisplayLowerD3 FXParamValueDisplay 10
RotaryD3 FXParam 10
Toggle+RotaryPushD3 NoAction
/
DisplayUpperD4 FXParamNameDisplay 11 "EHold"
DisplayLowerD4 FXParamValueDisplay 11
RotaryD4 FXParam 11
Toggle+RotaryPushD4 NoAction
/
DisplayUpperD5 FXParamNameDisplay 12 "ERel"
DisplayLowerD5 FXParamValueDisplay 12
RotaryD5 FXParam 12
Toggle+RotaryPushD5 NoAction
/
DisplayUpperD6 FXParamNameDisplay 14 "ERange"
DisplayLowerD6 FXParamValueDisplay 14
RotaryD6 FXParam 14
Toggle+RotaryPushD6 NoAction
/
DisplayUpperD7 NoAction
DisplayLowerD7 NoAction
RotaryD7 NoAction
Toggle+RotaryPushD7 NoAction
/
DisplayUpperD8 NoAction
DisplayLowerD8 NoAction
RotaryD8 NoAction
Toggle+RotaryPushD8 NoAction
/
ZoneEnd
|
|
|
04-09-2020, 06:19 PM
|
#8066
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Pt2
The original Zone, "VST: Oxford Dynamics (Sonnox)" has the compressor, limiter, SC EQ and Warmth. The sub-Zone, "VST: Oxford Dynamics (Sonnox)-2" has the Gate and Expander. I switch between the Zones using the Marker and ChanStrip buttons.
You make as many sub-zones as you like, just make sure each has a different name (I just use numbers tagged on to end of the original Zone name) and put the ParentZone line in each of the sub-zones to make sure they are de-activated when the original Zone is de-activated.
|
|
|
04-09-2020, 06:36 PM
|
#8067
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Quote:
Originally Posted by Geoff Waddington
Ok, was busy for the last few days optimizing for speed, hadn't done a tuneup in a while, managed to get some real improvements.
512 Channel EuCon console
|
A real achievement Geoff! Your virtual 512 Channel beast is 4 times larger than Luc Besson's 144 Channel surface.
|
|
|
04-09-2020, 06:40 PM
|
#8068
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
Ok, I think I get it
You could split the various modules into in sub-zones like this:
Code:
Zone "VST: Oxford Dynamics (Sonnox)" "OxDyn"
SelectedTrackNavigator
/
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-1"
DisplayLowerA1 FXParamValueDisplay 45
RotaryA1 FXParam 45
Toggle+RotaryPushA1 FXParam 44
/
DisplayUpperA2 NoAction
DisplayLowerA2 NoAction
RotaryA2 NoAction
Toggle+RotaryPushA2 NoAction
/
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
Toggle+RotaryPushA3 NoAction
/
DisplayUpperA4 NoAction
DisplayLowerA4 NoAction
RotaryA4 NoAction
Toggle+RotaryPushA4 NoAction
/
DisplayUpperA5 FXParamNameDisplay 39 "EQ_Sig"
DisplayLowerA5 FXParamValueDisplay 39
RotaryA5 FXParam 39
Toggle+RotaryPushA5 FXParam 39
/
DisplayUpperA6 FXParamNameDisplay 30 "Input"
DisplayLowerA6 FXParamValueDisplay 30
RotaryA6 FXParam 30
Toggle+RotaryPushA6 NoAction
/
DisplayUpperA7 FXParamNameDisplay 32 "LFQ"
DisplayLowerA7 FXParamValueDisplay 32
RotaryA7 FXParam 32
Toggle+RotaryPushA7 FXParam 37
/
DisplayUpperA8 FXParamNameDisplay 33 "HFQ"
DisplayLowerA8 FXParamValueDisplay 33
RotaryA8 FXParam 33
Toggle+RotaryPushA8 FXParam 38
/
DisplayUpperB1 FXParamNameDisplay 42 "Warmth"
DisplayLowerB1 FXParamValueDisplay 42
RotaryB1 FXParam 42
Toggle+RotaryPushB1 FXParam 41
/
DisplayUpperB2 FXParamNameDisplay 43 "WTrim"
DisplayLowerB2 FXParamValueDisplay 43
RotaryB2 FXParam 43
Toggle+RotaryPushB2 NoAction
/
DisplayUpperB3 FXParamNameDisplay 1 "Dither"
DisplayLowerB3 FXParamValueDisplay 1
RotaryB3 FXParam 1 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushB3 FXParam 1 [ 0.0 0.50 1.0 ]
/
DisplayUpperB4 NoAction
DisplayLowerB4 NoAction
RotaryB4 NoAction
Toggle+RotaryPushB4 NoAction
/
DisplayUpperB5 FXParamNameDisplay 40 "EQ_SC"
DisplayLowerB5 FXParamValueDisplay 40
RotaryB5 FXParam 40
Toggle+RotaryPushB5 FXParam 40
/
DisplayUpperB6 FXParamNameDisplay 29 "SC_In"
DisplayLowerB6 FXParamValueDisplay 29
RotaryB6 FXParam 29
Toggle+RotaryPushB6 FXParam 29
/
DisplayUpperB7 FXParamNameDisplay 31 "LF"
DisplayLowerB7 FXParamValueDisplay 31
RotaryB7 FXParam 31
Toggle+RotaryPushB7 FXParam 37
/
DisplayUpperB8 FXParamNameDisplay 34 "HF"
DisplayLowerB8 FXParamValueDisplay 34
RotaryB8 FXParam 34
Toggle+RotaryPushB8 FXParam 38
/
DisplayUpperC1 FXParamNameDisplay 25 "LThrsh"
DisplayLowerC1 FXParamValueDisplay 25
RotaryC1 FXParam 25
Toggle+RotaryPushC1 FXParam 24
/
DisplayUpperC2 NoAction
DisplayLowerC2 NoAction
RotaryC2 NoAction
Toggle+RotaryPushC2 NoAction
/
DisplayUpperC3 FXParamNameDisplay 26 "LAtt"
DisplayLowerC3 FXParamValueDisplay 26
RotaryC3 FXParam 26
Toggle+RotaryPushC3 NoAction
/
DisplayUpperC4 FXParamNameDisplay 27 "LHold"
DisplayLowerC4 FXParamValueDisplay 27
RotaryC4 FXParam 27
Toggle+RotaryPushC4 NoAction
/
DisplayUpperC5 FXParamNameDisplay 28 "LRel"
DisplayLowerC5 FXParamValueDisplay 28
RotaryC5 FXParam 28
Toggle+RotaryPushC5 NoAction
/
DisplayUpperC6 NoAction
DisplayLowerC6 NoAction
RotaryC6 NoAction
Toggle+RotaryPushC6 NoAction
/
DisplayUpperC7 FXParamNameDisplay 35 "LFGain"
DisplayLowerC7 FXParamValueDisplay 35
RotaryC7 FXParam 35
Toggle+RotaryPushC7 NoAction
/
DisplayUpperC8 FXParamNameDisplay 36 "HFGain"
DisplayLowerC8 FXParamValueDisplay 36
RotaryC8 FXParam 36
Toggle+RotaryPushC8 NoAction
/
DisplayUpperD1 FXParamNameDisplay 16 "CThrsh"
DisplayLowerD1 FXParamValueDisplay 16
RotaryD1 FXParam 16
Toggle+RotaryPushD1 FXParam 15
/
DisplayUpperD2 FXParamNameDisplay 20 "CRatio"
DisplayLowerD2 FXParamValueDisplay 20
RotaryD2 FXParam 20
Toggle+RotaryPushD2 NoAction
/
DisplayUpperD3 FXParamNameDisplay 17 "CAtt"
DisplayLowerD3 FXParamValueDisplay 17
RotaryD3 FXParam 17
Toggle+RotaryPushD3 NoAction
/
DisplayUpperD4 FXParamNameDisplay 18 "CHold"
DisplayLowerD4 FXParamValueDisplay 18
RotaryD4 FXParam 18
Toggle+RotaryPushD4 NoAction
/
DisplayUpperD5 FXParamNameDisplay 19 "CRel"
DisplayLowerD5 FXParamValueDisplay 19
RotaryD5 FXParam 19
Toggle+RotaryPushD5 NoAction
/
DisplayUpperD6 FXParamNameDisplay 22 "CKnee"
DisplayLowerD6 FXParamValueDisplay 22
RotaryD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ]
Toggle+RotaryPushD6 FXParam 22 [ 0.0 0.25 0.50 0.75 1.0 ]
/
DisplayUpperD7 FXParamNameDisplay 23 "CType"
DisplayLowerD7 FXParamValueDisplay 23
RotaryD7 FXParam 23 [ 0.0 0.50 1.0 ]
Toggle+RotaryPushD7 FXParam 23 [ 0.0 0.50 1.0 ]
/
DisplayUpperD8 FXParamNameDisplay 21 "CMkeUp"
DisplayLowerD8 FXParamValueDisplay 21
RotaryD8 FXParam 21
Toggle+RotaryPushD8 NoAction
/
ZoneEnd
/
Zone "VST: Oxford Dynamics (Sonnox)-2"
SelectedTrackNavigator
ParentZone "VST: Oxford Dynamics (Sonnox)"
Marker GoZone "VST: Oxford Dynamics (Sonnox)"
ChanStrip GoZone "VST: Oxford Dynamics (Sonnox)-2"
/
DisplayUpperA1 FXParamNameDisplay 45 "OxDyn-2"
DisplayLowerA1 FXParamValueDisplay 45
RotaryA1 FXParam 45
Toggle+RotaryPushA1 FXParam 44
/
DisplayUpperA2 NoAction
DisplayLowerA2 NoAction
RotaryA2 NoAction
Toggle+RotaryPushA2 NoAction
/
DisplayUpperA3 NoAction
DisplayLowerA3 NoAction
RotaryA3 NoAction
Toggle+RotaryPushA3 NoAction
/
DisplayUpperA4 NoAction
DisplayLowerA4 NoAction
RotaryA4 NoAction
Toggle+RotaryPushA4 NoAction
/
DisplayUpperA5 NoAction
DisplayLowerA5 NoAction
RotaryA5 NoAction
Toggle+RotaryPushA5 NoAction
/
DisplayUpperA6 NoAction
DisplayLowerA6 NoAction
RotaryA6 NoAction
Toggle+RotaryPushA6 NoAction
/
DisplayUpperA7 NoAction
DisplayLowerA7 NoAction
RotaryA7 NoAction
Toggle+RotaryPushA7 NoAction
/
DisplayUpperA8 NoAction
DisplayLowerA8 NoAction
RotaryA8 NoAction
Toggle+RotaryPushA8 NoAction
/
DisplayUpperB1 NoAction
DisplayLowerB1 NoAction
RotaryB1 NoAction
Toggle+RotaryPushB1 NoAction
/
DisplayUpperB2 NoAction
DisplayLowerB2 NoAction
RotaryB2 NoAction
Toggle+RotaryPushB2 NoAction
/
DisplayUpperB3 NoAction
DisplayLowerB3 NoAction
RotaryB3 NoAction
Toggle+RotaryPushB3 NoAction
/
DisplayUpperB4 NoAction
DisplayLowerB4 NoAction
RotaryB4 NoAction
Toggle+RotaryPushB4 NoAction
/
DisplayUpperB5 NoAction
DisplayLowerB5 NoAction
RotaryB5 NoAction
Toggle+RotaryPushB5 NoAction
/
DisplayUpperB6 NoAction
DisplayLowerB6 NoAction
RotaryB6 NoAction
Toggle+RotaryPushB6 NoAction
/
DisplayUpperB7 NoAction
DisplayLowerB7 NoAction
RotaryB7 NoAction
Toggle+RotaryPushB7 NoAction
/
DisplayUpperB8 NoAction
DisplayLowerB8 NoAction
RotaryB8 NoAction
Toggle+RotaryPushB8 NoAction
/
DisplayUpperC1 FXParamNameDisplay 3 "GThrsh"
DisplayLowerC1 FXParamValueDisplay 3
RotaryC1 FXParam 3
Toggle+RotaryPushC1 FXParam 2
/
DisplayUpperC2 NoAction
DisplayLowerC2 NoAction
RotaryC2 NoAction
Toggle+RotaryPushC2 NoAction
/
DisplayUpperC3 FXParamNameDisplay 4 "GAtt"
DisplayLowerC3 FXParamValueDisplay 4
RotaryC3 FXParam 4
Toggle+RotaryPushC3 NoAction
/
DisplayUpperC4 FXParamNameDisplay 5 "GHold"
DisplayLowerC4 FXParamValueDisplay 5
RotaryC4 FXParam 5
Toggle+RotaryPushC4 NoAction
/
DisplayUpperC5 FXParamNameDisplay 6 "GRel"
DisplayLowerC5 FXParamValueDisplay 6
RotaryC5 FXParam 6
Toggle+RotaryPushC5 NoAction
/
DisplayUpperC6 FXParamNameDisplay 7 "GRange"
DisplayLowerC6 FXParamValueDisplay 7
RotaryC6 FXParam 7
Toggle+RotaryPushC6 NoAction
/
DisplayUpperC7 NoAction
DisplayLowerC7 NoAction
RotaryC7 NoAction
Toggle+RotaryPushC7 NoAction
/
DisplayUpperC8 NoAction
DisplayLowerC8 NoAction
RotaryC8 NoAction
Toggle+RotaryPushC8 NoAction
/
DisplayUpperD1 FXParamNameDisplay 9 "EThrsh"
DisplayLowerD1 FXParamValueDisplay 9
RotaryD1 FXParam 9
Toggle+RotaryPushD1 FXParam 8
/
DisplayUpperD2 FXParamNameDisplay 13 "ERatio"
DisplayLowerD2 FXParamValueDisplay 13
RotaryD2 FXParam 13
Toggle+RotaryPushD2 NoAction
/
DisplayUpperD3 FXParamNameDisplay 10 "EAtt"
DisplayLowerD3 FXParamValueDisplay 10
RotaryD3 FXParam 10
Toggle+RotaryPushD3 NoAction
/
DisplayUpperD4 FXParamNameDisplay 11 "EHold"
DisplayLowerD4 FXParamValueDisplay 11
RotaryD4 FXParam 11
Toggle+RotaryPushD4 NoAction
/
DisplayUpperD5 FXParamNameDisplay 12 "ERel"
DisplayLowerD5 FXParamValueDisplay 12
RotaryD5 FXParam 12
Toggle+RotaryPushD5 NoAction
/
DisplayUpperD6 FXParamNameDisplay 14 "ERange"
DisplayLowerD6 FXParamValueDisplay 14
RotaryD6 FXParam 14
Toggle+RotaryPushD6 NoAction
/
DisplayUpperD7 NoAction
DisplayLowerD7 NoAction
RotaryD7 NoAction
Toggle+RotaryPushD7 NoAction
/
DisplayUpperD8 NoAction
DisplayLowerD8 NoAction
RotaryD8 NoAction
Toggle+RotaryPushD8 NoAction
/
ZoneEnd
|
Ok thank you. I got what your doing. Your go zoning to the different modules . I didnt even think of that. Thanks !!! That seems like a much easier way. Ill start working that route
|
|
|
04-09-2020, 06:44 PM
|
#8069
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Cragster
Ok thank you. I got what your doing. Your go zoning to the different modules . I didnt even think of that. Thanks !!! That seems like a much easier way. Ill start working that route
|
Cool You can include the GoZone buttons within the Zone/sub-Zone's if that suits you better.
|
|
|
04-09-2020, 06:44 PM
|
#8070
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Hi Geoff,
Just continuing with my OSC issue from yesterday as noted in Post #8011
https://forum.cockos.com/showpost.ph...postcount=8011
Can you confirm that the ost and zon files are correct?
|
|
|
04-09-2020, 06:52 PM
|
#8071
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by MixMonkey
Cool You can include the GoZone buttons within the Zone/sub-Zone's if that suits you better.
|
Thanks mixmonkey!!
|
|
|
04-10-2020, 01:46 AM
|
#8072
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Oh No!
A new extension to the Elgato StreamDeck series has just been released which adds MIDI and OSC output. (MacOS only at present, Windows is planned. Here is the git of the developer https://github.com/tsbkelly/Streamdeck-Midibutton, perhaps send him some encouragement for the port)
I have been using one for a few years as my controller for studio monitoring ( sending out Keycommands to Keyboard Maestro to trigger Macros that would then send out MIDI to my RME device to control the I/O for monitoring) and the philips lighting system. Was a bit of a mess to set up but has been flawless.
I just added the new extensions and have been able to create a new page for Reaper CSI, and am now successfully sending out messages such as Shift and recalling actions to perform cuts and crossfades or whatever I can imagine.
Now THIS is why I was keen to move from Pro Tools!
Last edited by tdc; 04-10-2020 at 07:33 AM.
Reason: Added info on the git.
|
|
|
04-10-2020, 02:04 AM
|
#8073
|
Human being with feelings
Join Date: Apr 2020
Location: Scotland
Posts: 155
|
It's Aliiiive!
Quote:
Originally Posted by Cragster
Are your plugin zones also set to selectedtracknavigator ?i use the fx menu/selected track navigator as opposed to the focus fx navigator and they do show up sloted across the display
|
Quote:
Originally Posted by MixMonkey
Do you have:
Code:
Zone Home
OnTrackSelection MapSelectedTrackFXToMenu
in your Home Zone?
|
Guys, thanks so much for the quick responses. Applied both your 'fixes'/advice and now have happily functioning Send and Plugin buttons... now to get the displays working properly in FX mode, and map those FX!
__________________
Slainté, Grae
Mac mini M2 Pro [MacOS 13.5.2] | Reaper 7.11(ARM) | CSI (Exp) & DBM4R (Latest) | Behringer X-Touch (1.21)
|
|
|
04-10-2020, 02:06 AM
|
#8074
|
Human being with feelings
Join Date: Jan 2017
Posts: 252
|
Dive into contextual toolbars
Hi - just like to know if this is possible...? (Mackie MCU ) old version
I have all my plugins separated into eq/saturation/comp/sendfx/ - (8 in total) on hotkeys for contextual toolbars.
eg - f15 floats all eq's as buttons in toolbar - mouse select which one, toolbar auto closes.
I would like to:
Press "track" to get fx - as it works at the moment, but then use the 8 rotary's to select which of the toolbars i want by pressing them, then scroll the menu of fx on that toolbar with the rotary and select a plugin.
If i can get this to work, i'm a long way towards not needing the mouse, which is my aim..
I'm not very good at this . At all. But if it's possible in the eyes of those that know, i'll stick with it
Many thanks
|
|
|
04-10-2020, 03:10 AM
|
#8075
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by tdc
A real achievement Geoff! Your virtual 512 Channel beast is 4 times larger than Luc Besson's 144 Channel surface.
|
Cool, wonder if he uses Reaper ?
Seriously, these stress tests are to assess scaling impact more than anything.
The typical, everyday project that is used for testing has 134 Tracks, about 20 of which are non blank and contain audio, as well as a few FX and Sends each.
The average time for one pass is about .5 milliseconds.
The average time for a pass on the stress test project is about 1.5 milliseconds.
Now, that is heavily optimized, but does show that CSI scales very well.
It is also a serves as a "pushing the edges" stability test, it also paases that.
All of this contributes to the hope that CSI will be reasonably responsive and stable under normal use.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-10-2020, 03:18 AM
|
#8076
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by tdc
|
Sure, but first I need some info from you:
Open the edit mode window (go to Reaper actions and type csi -- it's the only one)
in the lower left there is a section named "Monitor".
Check the "Show Input from Surfaces" box.
Press Play.
Select all and copy what you see in that window.
Post the results here.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-10-2020, 03:22 AM
|
#8077
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by tdc
Oh No!
A new extension to the Elgato StreamDeck series has just been released which adds MIDI and OSC output.
I have been using one for a few years as my controller for studio monitoring ( sending out Keycommands to Keyboard Maestro to trigger Macros that would then send out MIDI to my RME device to control the I/O for monitoring) and the philips lighting system. Was a bit of a mess to set up but has been flawless.
I just added the new extensions and have been able to create a new page for Reaper CSI, and am now successfully sending out messages such as Shift and recalling actions to perform cuts and crossfades or whatever I can imagine.
Now THIS is why I was keen to move from Pro Tools!
|
OUTSTANDING !!!
I have Hue as well, so it's on the to do list, press record and the big red light outside the door comes on, stuff like that , in fact planned from day one
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-10-2020, 03:31 AM
|
#8078
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by UNdark
Hi - just like to know if this is possible...? (Mackie MCU ) old version
I have all my plugins separated into eq/saturation/comp/sendfx/ - (8 in total) on hotkeys for contextual toolbars.
eg - f15 floats all eq's as buttons in toolbar - mouse select which one, toolbar auto closes.
I would like to:
Press "track" to get fx - as it works at the moment, but then use the 8 rotary's to select which of the toolbars i want by pressing them, then scroll the menu of fx on that toolbar with the rotary and select a plugin.
If i can get this to work, i'm a long way towards not needing the mouse, which is my aim..
I'm not very good at this . At all. But if it's possible in the eyes of those that know, i'll stick with it
Many thanks
|
Chime in folks, you're a lot more creative than I
I think @MixMonkey has a setup very similar to this perhaps he has some ideas, @ MixMonkey, you out there ?
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
04-10-2020, 04:46 AM
|
#8079
|
Human being with feelings
Join Date: Oct 2019
Location: Sydney
Posts: 471
|
Quote:
Originally Posted by Geoff Waddington
Sure, but first I need some info from you:
Open the edit mode window (go to Reaper actions and type csi -- it's the only one)
in the lower left there is a section named "Monitor".
Check the "Show Input from Surfaces" box.
Press Play.
Select all and copy what you see in that window.
Post the results here.
|
Thanks Geoff. In prepping the stuff for you I discovered an error in my naming the Rotary Pots with a lower case R in the ZON file, and also a missing e on Volume... Doh.
But, these changes were part of my testing process and they were working on previous sessions. In the testing this evening, I think the main issue for me was to do with Port Binding UDP stuff. Whilst the OSC module in CSI appears to be happy to be refreshed with out a Reboot, if you are adjusting your networking, this needs a reboot.
I grabbed the latest CSI beta this morning, and the MIDI module still requires a full Reaper reboot to refresh. Not sure if you added in your adjustment to try and remedy this?
|
|
|
04-10-2020, 05:31 AM
|
#8080
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by tdc
Thanks Geoff. In prepping the stuff for you I discovered an error in my naming the Rotary Pots with a lower case R in the ZON file, and also a missing e on Volume... Doh.
But, these changes were part of my testing process and they were working on previous sessions. In the testing this evening, I think the main issue for me was to do with Port Binding UDP stuff. Whilst the OSC module in CSI appears to be happy to be refreshed with out a Reboot, if you are adjusting your networking, this needs a reboot.
|
So, are you saying everything is working now ?
Quote:
Originally Posted by tdc
I grabbed the latest CSI beta this morning, and the MIDI module still requires a full Reaper reboot to refresh. Not sure if you added in your adjustment to try and remedy this?
|
Next build.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 12:25 AM.
|