|
|
|
01-23-2020, 12:36 AM
|
#6121
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
Forgive me if this is a stupid question, but are the modifiers defined in the .mst you're using?
|
Nothing to forgive, since this is a legitimate and not at all stupid question
Yes, I defined the widgets; adapted the code from the MCU.mst
When I hit a button, I see the correct codes and descriptors with the monitor option set in the learn window.
Itīs just that if, for instance, SHIFT button is toggled, it does not alter the codes of buttons pressed afterwards, which it should if I understood correctly how modifiers are supposed to work; so the modifier buttons just act like normal buttons.
If I define Shift+somebutton in the zon file nothing happens whe I toggle Shift and press somebutton afterwards.
I checked and compared all available updated mst and zon files but found no obvious errors in the syntax I use.
If there is no syntax issue and since modifiers seem to work fine with other controllers, itīeither the Nano or CSI in context with the Nano; but thatīs just me guessing wildly.
.mst
Code:
...
/Purple5
Widget Shift
Press 90 46 7f 90 46 00
WidgetEnd
/Purple6
Widget Option
Press 90 47 7f 90 47 00
WidgetEnd
/Purple7
Widget Control
Press 90 48 7f 90 48 00
WidgetEnd
/Purple8
Widget Alt
Press 90 49 7f 90 49 00
WidgetEnd
....
.zon
Code:
Zone "Buttons|"
....
/modifiers
Shift Shift
Option Option
Control Control
Alt Alt
...
ZoneEnd
Last edited by WaveTrans; 01-23-2020 at 12:47 AM.
|
|
|
01-23-2020, 01:21 AM
|
#6122
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Quote:
Originally Posted by Funkybot
You may want to consider sharing so the next person can have a more plug and play experience. Glad you got it up and running!
|
here are my files showing the mapping for FX Plugin control(ReaComp)and display on the Qcon ProX (but im sure it will work for any MCU type surface as the ProX is basically an MCU clone). All the relevant lines are marked with astericks(with notes) on the surface zone file.i also included the Reacomp zone file too.i hope it can help the next guy just starting out setting up CSI as everyone here helped me to learn this.
{CODE}Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
OnTrackSelection MapSelectedTrackFXToMenu ****************
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterChannel|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Shift Shift
Option Option
Control Control
Alt Alt
Blank2 ToggleLearnMode
Blank3 Reaper "40605"
Shift+Blank3 Reaper "40199"
Blank4 Reaper "40454"
Blank5 Reaper "40455"
Send ToggleMapSelectedTrackSends
Plugin ToggleMapSelectedTrackFXMenu***********(this activate the fxmenu for track
Plugin Reaper "_S&M_SHOWFXCHAINSEL"***********this will call up the FX windom for
EQ NoAction the track all in 1 press)
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
BankLeft TrackBank "-8"
BankRight TrackBank "8"
TimeDisplay TimeDisplay
smpteBeats CycleTimeDisplayModes
Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Reaper "1013"
Shift+Record Reaper "_S&M_CYCLACTION_6"
F1 Reaper "40157"
F2 Reaper "40931"
F2 Reaper "_SWSMARKERLIST13"
F4 Reaper "40702"
F5 Reaper "_S&M_CYCLACTION_4"
F6 Reaper "_44924b08811f144e9f88ca3a2918ff48"
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"
Save Reaper "40026"
Shift+Save Reaper "40022"
Undo Reaper "40029"
Shift+Undo Reaper "40030"
Normal Reaper "40173"
Marker Reaper "40172"
Option+Marker Reaper "40174"
Shift+Marker Reaper "40157"
Loop CycleTimeline
Click Reaper "40364"
Solo Reaper "40340"
Blank1 Reaper "_S&M_SHOWNOTESHELP"
Zoom Reaper "40113"
Up Reaper "40111"
Down Reaper "40112"
Left Reaper "1011"
Right Reaper "1012"
JogWheelRotaryCW Reaper "41667"
JogWheelRotaryCCW Reaper "41666"
/MasterFader MasterTrackVolume
ZoneEnd
Zone "Channel|"
TrackNavigator
VUMeter| TrackOutputMeterMaxPeakLR
/VUMeter| TrackOutputMeterAverageLR
DisplayUpper| TrackNameDisplay
DisplayLower| TrackPanDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
Rotary| TrackPan "0"
RecordArm| TrackRecordArm
Solo| TrackSolo
Mute| TrackMute
Select| TrackUniqueSelect
Shift+Select| TrackRangeSelect
Control+Select| TrackSelect
Shift+Control+Select| TogglePin
Option+Select| TrackFolderDive
Fader| TrackVolume
TrackTouch+Fader| TrackVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "Pan|1-8"
TrackNavigator
Rotary| TrackPan "0"
RotaryPush| GoZone PanWidth|
ZoneEnd
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth "1"
RotaryPush| GoZone Pan|
ZoneEnd
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
TrackTouch+DisplayUpper| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
Rotary| TrackSendPan
RotaryPush| NoAction
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterChannel|"
MasterTrackNavigator
MasterFader TrackVolume
MasterFaderTouch TrackTouch
ZoneEnd
Zone "FXMenu|1-8"**************************(this whole zone)
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
{/CODE]
Code:
Zone "VST: ReaComp (Cockos)" "ReaComp"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Thresh" (very important..the params start
DisplayLower1 FXParamValueDisplay 0 at 0 not 1)
Rotary1 FXParam 0
DisplayUpper2 FXParamNameDisplay 4 "PreCo"
DisplayLower2 FXParamValueDisplay 4
Rotary2 FXParam 4
DisplayUpper3 FXParamNameDisplay 2 "Attack"
DisplayLower3 FXParamValueDisplay 2
Rotary3 FXParam 2
DisplayUpper4 FXParamNameDisplay 3 "Release"
DisplayLower4 FXParamValueDisplay 3
Rotary4 FXParam 3
DisplayUpper5 FXParamNameDisplay 1 "Ratio"
DisplayLower5 FXParamValueDisplay 1
Rotary5 FXParam 1
DisplayUpper6 FXParamNameDisplay 14 "Knee"
DisplayLower6 FXParamValueDisplay 14
Rotary6 FXParam 14
DisplayUpper7 FXParamNameDisplay 6 "LPass"
DisplayLower7 FXParamValueDisplay 6
Rotary7 FXParam 6
DisplayUpper8 FXParamNameDisplay 7 "HPass"
DisplayLower8 FXParamValueDisplay 7
Rotary8 FXParam 7
Shift+DisplayUpper1 FXParamNameDisplay 13 "RMS"
Shift+DisplayLower1 FXParamValueDisplay 13
Shift+Rotary1 FXParam 13
Shift+DisplayUpper2 FXParamNameDisplay 11 "Wet"
Shift+DisplayLower2 FXParamValueDisplay 11
Shift+Rotary2 FXParam 11
Shift+DisplayUpper3 FXParamNameDisplay 10 "Dry"
Shift+DisplayLower3 FXParamValueDisplay 10
Shift+Rotary3 FXParam 10
Shift+DisplayUpper4 FXParamNameDisplay 15 "AuMkUp"
Shift+DisplayLower4 FXParamValueDisplay 15
Shift+Toggle+RotaryPush4 FXParam 15
Shift+DisplayUpper5 FXParamNameDisplay 12 "PreFil"
Shift+DisplayLower5 FXParamValueDisplay 12
Shift+Toggle+RotaryPush5 FXParam 12
Shift+DisplayUpper6 FXParamNameDisplay 16 "AuRel"
Shift+DisplayLower6 FXParamValueDisplay 16
Shift+Toggle+RotaryPush6 FXParam 16
Shift+DisplayUpper7 FXParamNameDisplay 17 "ClAttack"
Shift+DisplayLower7 FXParamValueDisplay 17
Shift+Toggle+RotaryPush7 FXParam 17
Shift+DisplayUpper8 NoAction
Shift+DisplayLower8 NoAction
ZoneEnd
hope this can help someone get a more plug n play
|
|
|
01-23-2020, 01:24 AM
|
#6123
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
damit i always botch the codes and quotes !!! sry im a dumby
|
|
|
01-23-2020, 06:05 AM
|
#6124
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by WaveTrans
Nothing to forgive, since this is a legitimate and not at all stupid question
Yes, I defined the widgets; adapted the code from the MCU.mst
When I hit a button, I see the correct codes and descriptors with the monitor option set in the learn window.
Itīs just that if, for instance, SHIFT button is toggled, it does not alter the codes of buttons pressed afterwards, which it should if I understood correctly how modifiers are supposed to work; so the modifier buttons just act like normal buttons.
If I define Shift+somebutton in the zon file nothing happens whe I toggle Shift and press somebutton afterwards.
I checked and compared all available updated mst and zon files but found no obvious errors in the syntax I use.
If there is no syntax issue and since modifiers seem to work fine with other controllers, itīeither the Nano or CSI in context with the Nano; but thatīs just me guessing wildly.
.mst
Code:
...
/Purple5
Widget Shift
Press 90 46 7f 90 46 00
WidgetEnd
/Purple6
Widget Option
Press 90 47 7f 90 47 00
WidgetEnd
/Purple7
Widget Control
Press 90 48 7f 90 48 00
WidgetEnd
/Purple8
Widget Alt
Press 90 49 7f 90 49 00
WidgetEnd
....
.zon
Code:
Zone "Buttons|"
....
/modifiers
Shift Shift
Option Option
Control Control
Alt Alt
...
ZoneEnd
|
Your syntax looks fine to me I think it's worth pointing out (although this probably isn't a solution to your issue) that the modifiers behave a little differently to all other buttons.
They have two modes of operation.
The first behaves just like the modifiers on a qwerty keyboard, that is to say the modifier is held down whilst another key is pressed.
The second requires a (very) short press on the modifier key and causes it to latch, so it no longer needs to be held down to be in effect. A second (very) short press will un-latch it.
Also, modifiers are global in nature. If Shift is held down on one surface, all surfaces are 'Shifted'.
|
|
|
01-23-2020, 06:11 AM
|
#6125
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Cragster
here are my files showing the mapping for FX Plugin control(ReaComp)and display on the Qcon ProX (but im sure it will work for any MCU type surface as the ProX is basically an MCU clone). All the relevant lines are marked with astericks(with notes) on the surface zone file.i also included the Reacomp zone file too.i hope it can help the next guy just starting out setting up CSI as everyone here helped me to learn this.
{CODE}Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
OnTrackSelection MapSelectedTrackFXToMenu ****************
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterChannel|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Shift Shift
Option Option
Control Control
Alt Alt
Blank2 ToggleLearnMode
Blank3 Reaper "40605"
Shift+Blank3 Reaper "40199"
Blank4 Reaper "40454"
Blank5 Reaper "40455"
Send ToggleMapSelectedTrackSends
Plugin ToggleMapSelectedTrackFXMenu***********(this activate the fxmenu for track
Plugin Reaper "_S&M_SHOWFXCHAINSEL"***********this will call up the FX windom for
EQ NoAction the track all in 1 press)
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
BankLeft TrackBank "-8"
BankRight TrackBank "8"
TimeDisplay TimeDisplay
smpteBeats CycleTimeDisplayModes
Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Reaper "1013"
Shift+Record Reaper "_S&M_CYCLACTION_6"
F1 Reaper "40157"
F2 Reaper "40931"
F2 Reaper "_SWSMARKERLIST13"
F4 Reaper "40702"
F5 Reaper "_S&M_CYCLACTION_4"
F6 Reaper "_44924b08811f144e9f88ca3a2918ff48"
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"
Save Reaper "40026"
Shift+Save Reaper "40022"
Undo Reaper "40029"
Shift+Undo Reaper "40030"
Normal Reaper "40173"
Marker Reaper "40172"
Option+Marker Reaper "40174"
Shift+Marker Reaper "40157"
Loop CycleTimeline
Click Reaper "40364"
Solo Reaper "40340"
Blank1 Reaper "_S&M_SHOWNOTESHELP"
Zoom Reaper "40113"
Up Reaper "40111"
Down Reaper "40112"
Left Reaper "1011"
Right Reaper "1012"
JogWheelRotaryCW Reaper "41667"
JogWheelRotaryCCW Reaper "41666"
/MasterFader MasterTrackVolume
ZoneEnd
Zone "Channel|"
TrackNavigator
VUMeter| TrackOutputMeterMaxPeakLR
/VUMeter| TrackOutputMeterAverageLR
DisplayUpper| TrackNameDisplay
DisplayLower| TrackPanDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
Rotary| TrackPan "0"
RecordArm| TrackRecordArm
Solo| TrackSolo
Mute| TrackMute
Select| TrackUniqueSelect
Shift+Select| TrackRangeSelect
Control+Select| TrackSelect
Shift+Control+Select| TogglePin
Option+Select| TrackFolderDive
Fader| TrackVolume
TrackTouch+Fader| TrackVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "Pan|1-8"
TrackNavigator
Rotary| TrackPan "0"
RotaryPush| GoZone PanWidth|
ZoneEnd
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth "1"
RotaryPush| GoZone Pan|
ZoneEnd
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
TrackTouch+DisplayUpper| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
Rotary| TrackSendPan
RotaryPush| NoAction
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterChannel|"
MasterTrackNavigator
MasterFader TrackVolume
MasterFaderTouch TrackTouch
ZoneEnd
Zone "FXMenu|1-8"**************************(this whole zone)
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
{/CODE]
Code:
Zone "VST: ReaComp (Cockos)" "ReaComp"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Thresh" (very important..the params start
DisplayLower1 FXParamValueDisplay 0 at 0 not 1)
Rotary1 FXParam 0
DisplayUpper2 FXParamNameDisplay 4 "PreCo"
DisplayLower2 FXParamValueDisplay 4
Rotary2 FXParam 4
DisplayUpper3 FXParamNameDisplay 2 "Attack"
DisplayLower3 FXParamValueDisplay 2
Rotary3 FXParam 2
DisplayUpper4 FXParamNameDisplay 3 "Release"
DisplayLower4 FXParamValueDisplay 3
Rotary4 FXParam 3
DisplayUpper5 FXParamNameDisplay 1 "Ratio"
DisplayLower5 FXParamValueDisplay 1
Rotary5 FXParam 1
DisplayUpper6 FXParamNameDisplay 14 "Knee"
DisplayLower6 FXParamValueDisplay 14
Rotary6 FXParam 14
DisplayUpper7 FXParamNameDisplay 6 "LPass"
DisplayLower7 FXParamValueDisplay 6
Rotary7 FXParam 6
DisplayUpper8 FXParamNameDisplay 7 "HPass"
DisplayLower8 FXParamValueDisplay 7
Rotary8 FXParam 7
Shift+DisplayUpper1 FXParamNameDisplay 13 "RMS"
Shift+DisplayLower1 FXParamValueDisplay 13
Shift+Rotary1 FXParam 13
Shift+DisplayUpper2 FXParamNameDisplay 11 "Wet"
Shift+DisplayLower2 FXParamValueDisplay 11
Shift+Rotary2 FXParam 11
Shift+DisplayUpper3 FXParamNameDisplay 10 "Dry"
Shift+DisplayLower3 FXParamValueDisplay 10
Shift+Rotary3 FXParam 10
Shift+DisplayUpper4 FXParamNameDisplay 15 "AuMkUp"
Shift+DisplayLower4 FXParamValueDisplay 15
Shift+Toggle+RotaryPush4 FXParam 15
Shift+DisplayUpper5 FXParamNameDisplay 12 "PreFil"
Shift+DisplayLower5 FXParamValueDisplay 12
Shift+Toggle+RotaryPush5 FXParam 12
Shift+DisplayUpper6 FXParamNameDisplay 16 "AuRel"
Shift+DisplayLower6 FXParamValueDisplay 16
Shift+Toggle+RotaryPush6 FXParam 16
Shift+DisplayUpper7 FXParamNameDisplay 17 "ClAttack"
Shift+DisplayLower7 FXParamValueDisplay 17
Shift+Toggle+RotaryPush7 FXParam 17
Shift+DisplayUpper8 NoAction
Shift+DisplayLower8 NoAction
ZoneEnd
hope this can help someone get a more plug n play
|
Thanks for posting your files One thing, if you want to add comments to your files, preceed the comment with a /, that way CSI will know to ignore what follows and when someone else comes along and copies and pastes the whole thing, it will still work.
|
|
|
01-23-2020, 06:49 AM
|
#6126
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Thanks. im trying. That was mainly for fx.there are still some buttons on there from where i got it.so when.im complete i will re post (the right way with my glasses on haha) and then someone can have a working file for the proX to start with.so if there are any new to CSI Qcon Prox'ers out there hang on...
|
|
|
01-23-2020, 07:08 AM
|
#6127
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by MixMonkey
Thanks for posting your files One thing, if you want to add comments to your files, preceed the comment with a /, that way CSI will know to ignore what follows and when someone else comes along and copies and pastes the whole thing, it will still work.
|
Just to add, I believe the whole row needs to start with a / for CSI to recognize the comment. I don't think you can add comments to the end of a line with comments on them.
Nice job getting that together Cragster!
Geoff, eagerly anticipating the updates you're working on. CSI has been a game-changer for me over here.
|
|
|
01-23-2020, 08:24 AM
|
#6128
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Here's a completely generic MCU.zon I made that lists all the buttons, but doesn't have any of my setup in it.
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
OnTrackSelection MapSelectedTrackFXToMenu
IncludedZones
"Buttons|"
"Channel|1-8"
"MasterTrack|"
IncludedZonesEnd
ZoneEnd
Zone "Buttons|"
Track NoAction
Send ToggleMapSelectedTrackSends
Pan NoAction
Plugin ToggleMapSelectedTrackFXMenu
EQ NoAction
Instrument NoAction
BankLeft TrackBank "-8"
BankRight TrackBank "8"
ChannelLeft TrackBank "-1"
ChannelRight TrackBank "1"
Flip NoAction
GlobalView NoAction
nameValue NoAction
smpteBeats CycleTimeDisplayModes
TimeDisplay TimeDisplay
F1 NoAction
F2 NoAction
F3 NoAction
F4 NoAction
F5 NoAction
F6 NoAction
F7 NoAction
F8 NoAction
MidiTracks NoAction
Inputs NoAction
AudioTracks NoAction
AudioInstrument NoAction
Aux NoAction
Busses NoAction
Outputs NoAction
User NoAction
Shift Shift
Option Option
Control Control
Alt Alt
Read TrackAutoMode "1"
Write TrackAutoMode "3"
Trim TrackAutoMode "0"
Touch TrackAutoMode "2"
Latch TrackAutoMode "4"
Group Reaper "42023"
Shift+Read GlobalAutoMode "1"
Shift+Write GlobalAutoMode "3"
Shift+Trim GlobalAutoMode "0"
Shift+Touch GlobalAutoMode "2"
Shift+Latch GlobalAutoMode "4"
Shift+Group Reaper "42024"
Save ToggleLearnMode
Undo NoAction
Cancel NoAction
Enter NoAction
Marker NoAction
Nudge NoAction
Cycle CycleTimeline
Drop NoAction
Replace NoAction
Click Reaper "40364"
Solo NoAction
Rewind Reaper 40084
FastForward Reaper 40085
Stop Stop
Play Play
Record Record
JogWheelRotaryCW Reaper "40647"
JogWheelRotaryCCW Reaper "40646"
Scrub NoAction
ZoneEnd
Zone "Channel|"
TrackNavigator
VUMeter| TrackOutputMeter
DisplayUpper| TrackNameDisplay
DisplayLower| TrackPanDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
Rotary| TrackPan "0"
RecordArm| TrackRecordArm
Solo| TrackSolo
Mute| TrackMute
Select| TrackUniqueSelect
Shift+Select| TrackRangeSelect
Control+Select| TrackSelect
Shift+Control+Select| TogglePin
Option+Select| TrackFolderDive
Fader| TrackVolume
TrackTouch+Fader| TrackVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "MasterTrack|"
MasterTrackNavigator
MasterFader TrackVolume
TrackTouch+MasterFader TrackVolume
MasterFaderTouch TrackTouch
ZoneEnd
Zone "Send|1-8"
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone "PanWidth|1-8"
TrackNavigator
Rotary| TrackPanWidth 1
DisplayLower| TrackPanWidthDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
RotaryPush| GoZone Home
ZoneEnd
Zone "FXMenu|1-8"
SelectedTrackNavigator
DisplayUpper| FXNameDisplay |
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot |
ZoneEnd
It comes with a couple of FX Zones, so you get to see something in the FX menu :
Code:
Zone "VST: ReaComp (Cockos)" "ReaCmp"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Thresh"
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0
Toggle+RotaryPush1 FXParam 19
DisplayUpper2 FXParamNameDisplay 1 "Ratio"
DisplayLower2 FXParamValueDisplay 1
Rotary2 FXParam 1
Toggle+RotaryPush2 FXParam 16
DisplayUpper3 FXParamNameDisplay 2 "Att"
DisplayLower3 FXParamValueDisplay 2
Rotary3 FXParam 2
Toggle+RotaryPush3 FXParam 17
DisplayUpper4 FXParamNameDisplay 3 "Rel"
DisplayLower4 FXParamValueDisplay 3
Rotary4 FXParam 3
Toggle+RotaryPush4 FXParam 16
DisplayUpper5 FXParamNameDisplay 11 "Wet"
DisplayLower5 FXParamValueDisplay 11
Rotary5 FXParam 11
Toggle+RotaryPush5 FXParam 15
DisplayUpper6 FXParamNameDisplay 10 "Dry"
DisplayLower6 FXParamValueDisplay 10
Rotary6 FXParam 10
Toggle+RotaryPush6 FXParam 18
DisplayUpper7 FXParamNameDisplay 7 "SC_HPF"
DisplayLower7 FXParamValueDisplay 7
Rotary7 FXParam 7
Toggle+RotaryPush7 FXParam 12
DisplayUpper8 FXParamNameDisplay 6 "SC_LPF"
DisplayLower8 FXParamValueDisplay 6
Rotary8 FXParam 6
Toggle+RotaryPush8 FXParam 12
Shift+DisplayUpper1 FXParamNameDisplay 4 "PrComp"
Shift+DisplayLower1 FXParamValueDisplay 4
Shift+Rotary1 FXParam 4
Shift+Toggle+RotaryPush1 NoAction
Shift+DisplayUpper2 FXParamNameDisplay 1 "Ratio"
Shift+DisplayLower2 FXParamValueDisplay 1
Shift+Rotary2 FXParam 1
Shift+Toggle+RotaryPush2 FXParam 16
Shift+DisplayUpper3 FXParamNameDisplay 14 "Knee"
Shift+DisplayLower3 FXParamValueDisplay 14
Shift+Rotary3 FXParam 14
Shift+Toggle+RotaryPush3 NoAction
Shift+DisplayUpper4 FXParamNameDisplay 3 "Rel"
Shift+DisplayLower4 FXParamValueDisplay 3
Shift+Rotary4 FXParam 3
Shift+Toggle+RotaryPush4 FXParam 16
Shift+DisplayUpper5 FXParamNameDisplay 11 "Wet"
Shift+DisplayLower5 FXParamValueDisplay 11
Shift+Rotary5 FXParam 11
Shift+Toggle+RotaryPush5 FXParam 15
Shift+DisplayUpper6 FXParamNameDisplay 18 "OvSmp"
Shift+DisplayLower6 FXParamValueDisplay 18
Shift+Rotary6 FXParam 18
Shift+Toggle+RotaryPush6 FXParam 18
Shift+DisplayUpper7 FXParamNameDisplay 7 "SC_HPF"
Shift+DisplayLower7 FXParamValueDisplay 7
Shift+Rotary7 FXParam 7
Shift+Toggle+RotaryPush7 FXParam 12
Shift+DisplayUpper8 FXParamNameDisplay 6 "SC_LPF"
Shift+DisplayLower8 FXParamValueDisplay 6
Shift+Rotary8 FXParam 6
Shift+Toggle+RotaryPush8 FXParam 12
ZoneEnd
Last edited by MixMonkey; 01-23-2020 at 08:48 AM.
Reason: Trailing comments are bad!
|
|
|
01-23-2020, 08:25 AM
|
#6129
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
...and
Code:
Zone "VST: ReaEQ (Cockos)" "ReaEQ"
SelectedTrackNavigator
DisplayUpper1 FXParamNameDisplay 0 "Freq1"
DisplayLower1 FXParamValueDisplay 0
Rotary1 FXParam 0
Toggle+RotaryPush1 FXParam 12
DisplayUpper2 FXParamNameDisplay 1 "Gain1"
DisplayLower2 FXParamValueDisplay 1
Rotary2 FXParam 1
Toggle+RotaryPush2 NoAction
DisplayUpper3 FXParamNameDisplay 3 "Freq2"
DisplayLower3 FXParamValueDisplay 3
Rotary3 FXParam 3
Toggle+RotaryPush3 NoAction
DisplayUpper4 FXParamNameDisplay 4 "Gain2"
DisplayLower4 FXParamValueDisplay 4
Rotary4 FXParam 4
Toggle+RotaryPush4 NoAction
DisplayUpper5 FXParamNameDisplay 6 "Freq3"
DisplayLower5 FXParamValueDisplay 6
Rotary5 FXParam 6
Toggle+RotaryPush5 NoAction
DisplayUpper6 FXParamNameDisplay 7 "Gain3"
DisplayLower6 FXParamValueDisplay 7
Rotary6 FXParam 7
Toggle+RotaryPush6 NoAction
DisplayUpper7 FXParamNameDisplay 9 "Freq4"
DisplayLower7 FXParamValueDisplay 9
Rotary7 FXParam 9
Toggle+RotaryPush7 NoAction
DisplayUpper8 FXParamNameDisplay 10 "Gain4"
DisplayLower8 FXParamValueDisplay 10
Rotary8 FXParam 10
Toggle+RotaryPush8 NoAction
Shift+DisplayUpper1 FXParamNameDisplay 2 "Q1"
Shift+DisplayLower1 FXParamValueDisplay 2
Shift+Rotary1 FXParam 2
Shift+Toggle+RotaryPush1 NoAction
Shift+DisplayUpper2 FXParamNameDisplay 1 "Gain1"
Shift+DisplayLower2 FXParamValueDisplay 1
Shift+Rotary2 FXParam 1
Shift+Toggle+RotaryPush2 NoAction
Shift+DisplayUpper3 FXParamNameDisplay 5 "Q2"
Shift+DisplayLower3 FXParamValueDisplay 5
Shift+Rotary3 FXParam 5
Shift+Toggle+RotaryPush3 NoAction
Shift+DisplayUpper4 FXParamNameDisplay 4 "Gain2"
Shift+DisplayLower4 FXParamValueDisplay 4
Shift+Rotary4 FXParam 4
Shift+Toggle+RotaryPush4 NoAction
Shift+DisplayUpper5 FXParamNameDisplay 8 "Q3"
Shift+DisplayLower5 FXParamValueDisplay 8
Shift+Rotary5 FXParam 8
Shift+Toggle+RotaryPush5 NoAction
Shift+DisplayUpper6 FXParamNameDisplay 7 "Gain3"
Shift+DisplayLower6 FXParamValueDisplay 7
Shift+Rotary6 FXParam 7
Shift+Toggle+RotaryPush6 NoAction
Shift+DisplayUpper7 FXParamNameDisplay 11 "Q4"
Shift+DisplayLower7 FXParamValueDisplay 11
Shift+Rotary7 FXParam 11
Shift+Toggle+RotaryPush7 NoAction
Shift+DisplayUpper8 FXParamNameDisplay 10 "Gain4"
Shift+DisplayLower8 FXParamValueDisplay 10
Shift+Rotary8 FXParam 10
Shift+Toggle+RotaryPush8 NoAction
ZoneEnd
|
|
|
01-23-2020, 08:26 AM
|
#6130
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by MixMonkey
I wondered about this too, but it seems to be ok.
|
At one point (a few weeks ago) I was advised against appending these to the same line but there have been lots of changes since then. I agree it would be much cleaner if this approach continues to work and can be recommended. Maybe Geoff can give an official yay or nay when he gets a chance.
|
|
|
01-23-2020, 08:44 AM
|
#6131
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Yeah, I'm really not big on allowing trailing comments.
It makes parsing cleanly much more difficult, translation -- I spend time writing parsing code instead of adding features, fixing bugs, etc.
__________________
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
|
|
|
01-23-2020, 08:46 AM
|
#6132
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Geoff Waddington
Yeah, I'm really not big on allowing trailing comments.
It makes parsing cleanly much more difficult, translation -- I spend time writing parsing code instead of adding features, fixing bugs, etc.
|
Let's not do it then
|
|
|
01-24-2020, 06:39 AM
|
#6133
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Tested the modifiers again and found that if I push the buttons very briefly
they work.
So thanks for the trouble shooting, MixMonkey
As so often, other issues came up
I reconfigured the ReaEQ.zon (see below) and tested it.
Seems modifier buttons have to be released by pressing again before a different modifier may be used (latch-unlatch); engaging and releasing buttons in rapid succession leads to irregular behaviour, meaning CIS apperas stuck in modifier mode and canīt be switched back to use of the unmodified button/rotary.
After a series of adjustements using rotaries with and without modifiers the conection between Reaper and the controller is lost frequently;
controller becomes irresponsive and/or the FXMenu crashes (not responding and unable to close/reopen.)
Re-/selecting FX or tracks with the mouse does not reconstitute connection.
finally a parameter display question:
Is there a way to display the Name/Values of the parameters adjusted in response to the buttons used?
Reason is, on a single channel controller directing each display to a different distinct channel does not work.
Code:
Zone "VST: ReaEQ (Cockos)" "ReaEQ"
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay "0" "Frequ1"
DisplayLower1 FXParamValueDisplay "0"
Rotary1 FXParam "0" "Freq-Band 1"
Shift+Rotary1 FXParam "1" "Gain-Band 1"
Option+Rotary1 FXParam "2" "Q-Band 1"
Rotary2 FXParam "3" "Freq-Band 2"
Shift+Rotary2 FXParam "4" "Gain-Band 2"
Option+Rotary2 FXParam "5" "Q-Band 2"
Rotary3 FXParam "6" "Freq-Band 3"
Shift+Rotary3 FXParam "7" "Gain-Band 3"
Option-Rotary3 FXParam "8" "Q-Band 3"
Rotary4 FXParam "9" "Freq-Band 4"
Shift+Rotary4 FXParam "10" "Gain-Band 4"
Option+Rotary4 FXParam "11" "Q-Band 4"
Rotary5 FXParam "12" "Freq-Band 5"
Shift+Rotary5 FXParam "13" "Gain-Band 5"
Option+Rotary5 FXParam "14" "Q-Band 5"
Rotary6 FXParam "15" "Freq-Band 6"
Shift+Fader6 FXParam "16" "Gain-Band 6"
Option+Rotary6 FXParam "17" "Q-Band 6"
Rotary7 FXParam "18" "Freq-Band 7"
Shift+Rotary7 FXParam "19" "Gain-Band 7"
Option+Rotary7 FXParam "20" "Q-Band 7"
Rotary8 FXParam "21" "Freq-Band 8"
Shift+Rotary8 FXParam "22" "Gain-Band 8"
Option+Rotary8 FXParam "23" "Q-Band 8"
ZoneEnd
Quote:
Originally Posted by MixMonkey
Your syntax looks fine to me I think it's worth pointing out (although this probably isn't a solution to your issue) that the modifiers behave a little differently to all other buttons.
They have two modes of operation.
The first behaves just like the modifiers on a qwerty keyboard, that is to say the modifier is held down whilst another key is pressed.
The second requires a (very) short press on the modifier key and causes it to latch, so it no longer needs to be held down to be in effect. A second (very) short press will un-latch it.
Also, modifiers are global in nature. If Shift is held down on one surface, all surfaces are 'Shifted'.
|
Last edited by WaveTrans; 01-24-2020 at 06:49 AM.
|
|
|
01-24-2020, 07:18 AM
|
#6134
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by WaveTrans
Tested the modifiers again and found that if I push the buttons very briefly
they work.
|
What does the MIDI data for those modifiers look like coming off the surface? If you press and hold the Shift button, what does that message (or messages) look like? What does the message look like when you release the Shift button?
Does the MIDI data transmitted by other buttons change when it's in shift mode? What surface is this?
I think the way most Shift buttons work is there's a press action and a release action in terms of the data. So you press and hold Shift, while you press and release play, and that combination creates Shift+Play. So any button with press and release messages could be setup to act as a Shift button in CSI.
What it sounds to me like your'e describing is that your surface goes into a kind of "Shift Mode" that it will remain in, and maybe buttons have different MIDI messages in that mode. That seems odd to me because that would mean the surface was designed where shift kind of sets the surface up in a second bank of buttons with different MIDI addresses.
I may just be confused by what you're describing, but I'd be curious to see the MIDI messages being sent by various buttons in shift mode to see if there's something we could do to improve it's behavior on your surface.
|
|
|
01-24-2020, 07:20 AM
|
#6135
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by WaveTrans
Tested the modifiers again and found that if I push the buttons very briefly
they work.
So thanks for the trouble shooting, MixMonkey
As so often, other issues came up
I reconfigured the ReaEQ.zon (see below) and tested it.
Seems modifier buttons have to be released by pressing again before a different modifier may be used (latch-unlatch); engaging and releasing buttons in rapid succession leads to irregular behaviour, meaning CIS apperas stuck in modifier mode and canīt be switched back to use of the unmodified button/rotary.
|
Do the modifiers work if you press and hold them, instead of latching them? This is the more 'normal' mode of operation.
The latching behaviour can be tricky because there usually isn't any visual indication of it being active.
Also there's a typo in your ReaEQ map:
should be a +, not -.
Regarding the FX menu, this has to be used with the SelectedTrackNavigator in the FX.zon file. You can't use it in conjunction with the FocusedFXNavigator. On a single channel controller, the FX menu doesn't make much sense anyway.
|
|
|
01-24-2020, 07:38 AM
|
#6136
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Quote:
Originally Posted by WaveTrans
Tested the modifiers again and found that if I push the buttons very briefly
they work.
So thanks for the trouble shooting, MixMonkey
As so often, other issues came up
I reconfigured the ReaEQ.zon (see below) and tested it.
Seems modifier buttons have to be released by pressing again before a different modifier may be used (latch-unlatch); engaging and releasing buttons in rapid succession leads to irregular behaviour, meaning CIS apperas stuck in modifier mode and canīt be switched back to use of the unmodified button/rotary.
After a series of adjustements using rotaries with and without modifiers the conection between Reaper and the controller is lost frequently;
controller becomes irresponsive and/or the FXMenu crashes (not responding and unable to close/reopen.)
Re-/selecting FX or tracks with the mouse does not reconstitute connection.
finally a parameter display question:
Is there a way to display the Name/Values of the parameters adjusted in response to the buttons used?
Reason is, on a single channel controller directing each display to a different distinct channel does not work.
Code:
Zone "VST: ReaEQ (Cockos)" "ReaEQ"
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay "0" "Frequ1"
DisplayLower1 FXParamValueDisplay "0"
Rotary1 FXParam "0" "Freq-Band 1"
Shift+Rotary1 FXParam "1" "Gain-Band 1"
Option+Rotary1 FXParam "2" "Q-Band 1"
Rotary2 FXParam "3" "Freq-Band 2"
Shift+Rotary2 FXParam "4" "Gain-Band 2"
Option+Rotary2 FXParam "5" "Q-Band 2"
Rotary3 FXParam "6" "Freq-Band 3"
Shift+Rotary3 FXParam "7" "Gain-Band 3"
Option-Rotary3 FXParam "8" "Q-Band 3"
Rotary4 FXParam "9" "Freq-Band 4"
Shift+Rotary4 FXParam "10" "Gain-Band 4"
Option+Rotary4 FXParam "11" "Q-Band 4"
Rotary5 FXParam "12" "Freq-Band 5"
Shift+Rotary5 FXParam "13" "Gain-Band 5"
Option+Rotary5 FXParam "14" "Q-Band 5"
Rotary6 FXParam "15" "Freq-Band 6"
Shift+Fader6 FXParam "16" "Gain-Band 6"
Option+Rotary6 FXParam "17" "Q-Band 6"
Rotary7 FXParam "18" "Freq-Band 7"
Shift+Rotary7 FXParam "19" "Gain-Band 7"
Option+Rotary7 FXParam "20" "Q-Band 7"
Rotary8 FXParam "21" "Freq-Band 8"
Shift+Rotary8 FXParam "22" "Gain-Band 8"
Option+Rotary8 FXParam "23" "Q-Band 8"
ZoneEnd
|
I dont know much but ill chime in on the display question. Did u try adding displayupper1 and displaylower1 to each parameter line in the zone together with whatever modifier rhat param used ?and for what its worth in the fx menu my modifiers hafta be held down while im using that param
|
|
|
01-24-2020, 07:42 AM
|
#6137
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Cragster
I dont know much but ill chime in on the display question. Did u try adding displayupper1 and displaylower1 to each parameter line in the zone together with whatever modifier rhat param used ?and for what its worth in the fx menu my modifiers hafta be held down while im using that param
|
What he said
See: https://forum.cockos.com/showpost.ph...postcount=6129
Last edited by MixMonkey; 01-24-2020 at 08:06 AM.
|
|
|
01-24-2020, 10:05 AM
|
#6138
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
Do the modifiers work if you press and hold them, instead of latching them? This is the more 'normal' mode of operation.
The latching behaviour can be tricky because there usually isn't any visual indication of it being active.
Also there's a typo in your ReaEQ map:
should be a +, not -.
Regarding the FX menu, this has to be used with the SelectedTrackNavigator in the FX.zon file. You can't use it in conjunction with the FocusedFXNavigator. On a single channel controller, the FX menu doesn't make much sense anyway.
|
Holding the modifier button it is; not latch-unlatch
Thanks.
Last edited by WaveTrans; 01-24-2020 at 10:17 AM.
|
|
|
01-24-2020, 10:14 AM
|
#6139
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
There is no difference between codes with or without modifier; but CSI seems to know the difference.
Thanks.
Quote:
Originally Posted by Funkybot
What does the MIDI data for those modifiers look like coming off the surface? If you press and hold the Shift button, what does that message (or messages) look like? What does the message look like when you release the Shift button?
Does the MIDI data transmitted by other buttons change when it's in shift mode? What surface is this?
I think the way most Shift buttons work is there's a press action and a release action in terms of the data. So you press and hold Shift, while you press and release play, and that combination creates Shift+Play. So any button with press and release messages could be setup to act as a Shift button in CSI.
What it sounds to me like your'e describing is that your surface goes into a kind of "Shift Mode" that it will remain in, and maybe buttons have different MIDI messages in that mode. That seems odd to me because that would mean the surface was designed where shift kind of sets the surface up in a second bank of buttons with different MIDI addresses.
I may just be confused by what you're describing, but I'd be curious to see the MIDI messages being sent by various buttons in shift mode to see if there's something we could do to improve it's behavior on your surface.
|
|
|
|
01-24-2020, 10:21 AM
|
#6140
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by Cragster
I dont know much but ill chime in on the display question. Did u try adding displayupper1 and displaylower1 to each parameter line in the zone together with whatever modifier rhat param used ?and for what its worth in the fx menu my modifiers hafta be held down while im using that param
|
Thanks.
Yes, tried that, only displays the last of the DisplayUpper/-Lower parameter and the displayed values sort of wobble.
|
|
|
01-24-2020, 10:21 AM
|
#6141
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
|
Thanks.
Yes tried that, but only the last display code is actually displayed and the values wobble.
|
|
|
01-24-2020, 10:45 AM
|
#6142
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by WaveTrans
Thanks.
Yes tried that, but only the last display code is actually displayed and the values wobble.
|
Ah, I see. I forgot that there is only one display (rather than 8).
I don't think there is currently a way to have the display show the parameter that is being adjusted (and jump between them) I think the reason that you get the wobble is becuase all the parameters are trying to access the display at once.
I take it you're using the nano's 4 rotaries to adjust FX parameters (in conjunction with modifiers to access more than 4)?
|
|
|
01-24-2020, 11:14 AM
|
#6143
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Quote:
Originally Posted by WaveTrans
Thanks.
Yes tried that, but only the last display code is actually displayed and the values wobble.
|
As @MixMonkey says, the wobble is a sure sign of double mapped (or in this case X8) controls and also a sure sign you are headed for Niagra Falls : ).
Most surfaces (but not all) eventually fall over from this traffic overload.
Turn on Midi Out Monitor, if you are stopped and you see lots of data streaming out, you will likely soon crash -- meaning your devices will become unresponsive.
And to the obvious question -- why isn't there code to prevent this -- because it's Reaper and we give you all the tools, including the ones to shoot yourself in the foot -- no restrictions here
Seriously, think of what would happen if you moved a Fader very fast - lots of data -- if we prevented that you could only do very slow fader moves -- there are many other examples...
__________________
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
|
|
|
01-24-2020, 11:26 AM
|
#6144
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
Ah, I see. I forgot that there is only one display (rather than 8).
I don't think there is currently a way to have the display show the parameter that is being adjusted (and jump between them) I think the reason that you get the wobble is becuase all the parameters are trying to access the display at once.
|
Yes, that fits my observations.
What would we need for that?
A display code respondent to a widget in context with a zone?
Just tried organising the FXzone with included zones but appears the same as without. (which may not be too much of a surprise)
Quote:
Originally Posted by MixMonkey
I take it you're using the nano's 4 rotaries to adjust FX parameters (in conjunction with modifiers to access more than 4)?
|
First draft is rotaries 1-8 for frequency bands 1-8 with the modifiers for
Q-Band (option) and Gain band (shift).
May not be the most efficient way, but I have to keep it repetitive and simple to make remembering the button layout easier
Hereīs the code
Code:
Zone "VST: ReaEQ (Cockos)" "ReaEQ"
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay "0" "Frequ1"
DisplayLower1 FXParamValueDisplay "0"
Rotary1 FXParam "0" "Freq-Band 1"
Shift+Rotary1 FXParam "1" "Gain-Band 1"
Option+Rotary1 FXParam "2" "Q-Band 1"
Rotary2 FXParam "3" "Freq-Band 2"
Shift+Rotary2 FXParam "4" "Gain-Band 2"
Option+Rotary2 FXParam "5" "Q-Band 2"
Rotary3 FXParam "6" "Freq-Band 3"
Shift+Rotary3 FXParam "7" "Gain-Band 3"
Option+Rotary3 FXParam "8" "Q-Band 3"
Rotary4 FXParam "9" "Freq-Band 4"
Shift+Rotary4 FXParam "10" "Gain-Band 4"
Option+Rotary4 FXParam "11" "Q-Band 4"
Rotary5 FXParam "12" "Freq-Band 5"
Shift+Rotary5 FXParam "13" "Gain-Band 5"
Option+Rotary5 FXParam "14" "Q-Band 5"
Rotary6 FXParam "15" "Freq-Band 6"
Shift+Fader6 FXParam "16" "Gain-Band 6"
Option+Rotary6 FXParam "17" "Q-Band 6"
Rotary7 FXParam "18" "Freq-Band 7"
Shift+Rotary7 FXParam "19" "Gain-Band 7"
Option+Rotary7 FXParam "20" "Q-Band 7"
Rotary8 FXParam "21" "Freq-Band 8"
Shift+Rotary8 FXParam "22" "Gain-Band 8"
Option+Rotary8 FXParam "23" "Q-Band 8"
ZoneEnd
|
|
|
01-24-2020, 11:31 AM
|
#6145
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by WaveTrans
Yes, that fits my observations.
What would we need for that?
A display code respondent to a widget in context with a zone?
Just tried organising the FXzone with included zones but appears the same as without. (which may not be too much of a surprise)
First draft is rotaries 1-8 for frequency bands 1-8 with the modifiers for
Q-Band and Gain band.
May not be the most efficient way, but I have to keep it repetitive and simple to make remembering the button layout easier
Hereīs the code
Code:
Zone "VST: ReaEQ (Cockos)" "ReaEQ"
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay "0" "Frequ1"
DisplayLower1 FXParamValueDisplay "0"
Rotary1 FXParam "0" "Freq-Band 1"
Shift+Rotary1 FXParam "1" "Gain-Band 1"
Option+Rotary1 FXParam "2" "Q-Band 1"
Rotary2 FXParam "3" "Freq-Band 2"
Shift+Rotary2 FXParam "4" "Gain-Band 2"
Option+Rotary2 FXParam "5" "Q-Band 2"
Rotary3 FXParam "6" "Freq-Band 3"
Shift+Rotary3 FXParam "7" "Gain-Band 3"
Option+Rotary3 FXParam "8" "Q-Band 3"
Rotary4 FXParam "9" "Freq-Band 4"
Shift+Rotary4 FXParam "10" "Gain-Band 4"
Option+Rotary4 FXParam "11" "Q-Band 4"
Rotary5 FXParam "12" "Freq-Band 5"
Shift+Rotary5 FXParam "13" "Gain-Band 5"
Option+Rotary5 FXParam "14" "Q-Band 5"
Rotary6 FXParam "15" "Freq-Band 6"
Shift+Fader6 FXParam "16" "Gain-Band 6"
Option+Rotary6 FXParam "17" "Q-Band 6"
Rotary7 FXParam "18" "Freq-Band 7"
Shift+Rotary7 FXParam "19" "Gain-Band 7"
Option+Rotary7 FXParam "20" "Q-Band 7"
Rotary8 FXParam "21" "Freq-Band 8"
Shift+Rotary8 FXParam "22" "Gain-Band 8"
Option+Rotary8 FXParam "23" "Q-Band 8"
ZoneEnd
|
I thought the Nano only had 4 Rotaries? Can you post your .mst?
|
|
|
01-24-2020, 11:41 AM
|
#6146
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by Geoff Waddington
As @MixMonkey says, the wobble is a sure sign of double mapped (or in this case X8) controls and also a sure sign you are headed for Niagra Falls : ).
Most surfaces (but not all) eventually fall over from this traffic overload.
Turn on Midi Out Monitor, if you are stopped and you see lots of data streaming out, you will likely soon crash -- meaning your devices will become unresponsive.
And to the obvious question -- why isn't there code to prevent this -- because it's Reaper and we give you all the tools, including the ones to shoot yourself in the foot -- no restrictions here
Seriously, think of what would happen if you moved a Fader very fast - lots of data -- if we prevented that you could only do very slow fader moves -- there are many other examples...
|
Thanks, Geoff, makes perfect sense.
I observe the wobble on all the double assignments.
May I take the opportunity and ask about displaying different, widget dependent parameters on a single channel controller?
In the mcu.zon files the display parameters are sent to differen channels but that canīt work with the single channel.
|
|
|
01-24-2020, 11:45 AM
|
#6147
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
I thought the Nano only had 4 Rotaries? Can you post your .mst?
|
The nano has 4 rotaries
(actually 5, but the one above the fader has the same code as the first one of the grouped four).
Topmost on the left hand side button row is a toggle button (5-8) to switch to a rotaries 5-8 mode.
If it is engaged, the codes for rotaries 5-8 (mcu) are sent.
Heres the IconNano.mst
it still is very similar to the mcu.mst and may therefore contain more widget definitions than needed but it works fine.
Code:
/RightCol1
Widget Track
Press 90 28 7f
FB_TwoState 90 28 7f 90 28 00
WidgetEnd
Widget Send
Press 90 29 7f
FB_TwoState 90 29 7f 90 29 00
WidgetEnd
Widget Pan
Press 90 2a 7f
FB_TwoState 90 2a 7f 90 2a 00
WidgetEnd
Widget Plugin
Press 90 2b 7f
FB_TwoState 90 2b 7f 90 2b 00
WidgetEnd
Widget EQ
Press 90 2c 7f
FB_TwoState 90 2c 7f 90 2c 00
WidgetEnd
/RightCol6
Widget Instrument
Press 90 2d 7f
FB_TwoState 90 2d 7f 90 2d 00
WidgetEnd
Widget BankLeft
Press 90 2E 7f
WidgetEnd
Widget BankRight
Press 90 2F 7f
WidgetEnd
/ 90 30 7f
Widget ChannelLeft
Encoder 90 18 7f
WidgetEnd
/ 90 31 7f
Widget ChannelRight
Encoder 90 19 7f
WidgetEnd
/Red1
Widget Flip
Press 90 32 7f
FB_TwoState 90 32 7f 90 32 00
WidgetEnd
/Red2
Widget Read
Press 90 4a 7f
FB_TwoState 90 4a 7f 90 4a 00
WidgetEnd
/Red3
Widget Write
Press 90 4b 7f
FB_TwoState 90 4b 7f 90 4b 00
WidgetEnd
/Red4
Widget Trim
Press 90 4c 7f
FB_TwoState 90 4c 7f 90 4c 00
WidgetEnd
/Red5 GlobalView
Widget Wiring
Press 90 33 7f
FB_TwoState 90 33 7f 90 33 00
WidgetEnd
/Red6
Widget Touch
Press 90 4d 7f
FB_TwoState 90 4d 7f 90 4d 00
WidgetEnd
/Red7
Widget Latch
Press 90 4e 7f
FB_TwoState 90 4e 7f 90 4e 00
WidgetEnd
/Red8 MCU: Group
Widget LatchPrev
Press 90 4f 7f
FB_TwoState 90 4f 7f 90 4f 00
WidgetEnd
/Blue1
Widget nameValue
Press 90 34 7f
WidgetEnd
/Blue5
Widget smpteBeats
Press 90 35 7f
WidgetEnd
/Widget TimeDisplay
/ FB_MCUTimeDisplay
/WidgetEnd
/Yellow1
Widget F1
Press 90 36 7f
WidgetEnd
/Yellow2
Widget F2
Press 90 37 7f
WidgetEnd
/Yellow3
Widget F3
Press 90 38 7f
WidgetEnd
/Yellow4
Widget F4
Press 90 39 7f
WidgetEnd
Widget F5 /Yellow5
Press 90 3a 7f
WidgetEnd
/Yellow6
Widget F6
Press 90 3b 7f
WidgetEnd
/Yellow7
Widget F7
Press 90 3c 7f
WidgetEnd
/Yellow8
Widget F8
Press 90 3d 7f
WidgetEnd
/Green1
Widget TrackLearn
Press 90 3e 7f
WidgetEnd
/Green2
Widget Inputs
Press 90 3f 7f
WidgetEnd
/Green3
Widget AudioTracks
Press 90 40 7f
WidgetEnd
/Green4
Widget AudioInstrument
Press 90 41 7f
WidgetEnd
/Green5
Widget Aux
Press 90 42 7f
WidgetEnd
/Green6 (MCU busses)
Widget Mixer
Press 90 43 7f
WidgetEnd
/Green7
Widget Outputs
Press 90 44 7f
WidgetEnd
/Green8 Master
Widget User
Press 90 45 7f
WidgetEnd
/Purple5
Widget Shift
Press 90 46 7f 90 46 00
WidgetEnd
/Purple6
Widget Option
Press 90 47 7f 90 47 00
WidgetEnd
/Purple7
Widget Control
Press 90 48 7f 90 48 00
WidgetEnd
/Purple8
Widget Alt
Press 90 49 7f 90 49 00
WidgetEnd
/Purple1
Widget Save
Press 90 50 7f 90 50 00
WidgetEnd
/Purple2
Widget Undo
Press 90 51 7f
WidgetEnd
/Purple3 (cancel)
Widget Redo
Press 90 52 7f
WidgetEnd
/Purple4
Widget Enter
Press 90 53 7f
WidgetEnd
/Blue2
Widget Marker
Press 90 54 7f
WidgetEnd
/Blue3
Widget Nudge
Press 90 55 7f
WidgetEnd
/Blue4
Widget RecordMode
Press 90 57 7f
WidgetEnd
/Blue6
Widget Replace
Press 90 58 7f
WidgetEnd
/Blue7
Widget Click
Press 90 59 7f
WidgetEnd
/Blue 8
Widget UnSoloAll
Press 90 5a 7f
FB_TwoState 90 5a 7f 90 5a 00
WidgetEnd
Widget Rewind
Press 90 5b 7f
FB_TwoState 90 5b 7f 90 5b 00
WidgetEnd
Widget FastForward
Press 90 5c 7f
FB_TwoState 90 5c 7f 90 5c 00
WidgetEnd
Widget Stop
Press 90 5d 7f
FB_TwoState 90 5d 7f 90 5d 00
WidgetEnd
Widget Play
Press 90 5e 7f
FB_TwoState 90 5e 7f 90 5e 00
WidgetEnd
Widget Record
Press 90 5f 7f
FB_TwoState 90 5f 7f 90 5f 00
WidgetEnd
Widget Up
Press 90 60 7f
WidgetEnd
Widget Down
Press 90 61 7f
WidgetEnd
Widget Left
Press 90 62 7f
WidgetEnd
Widget Right
Press 90 63 7f
WidgetEnd
Widget Zoom
Press 90 64 7f 90 64 00
FB_TwoState 90 64 7f 90 64 00
WidgetEnd
Widget Scrub
Press 90 65 7f 90 65 00
FB_TwoState 90 65 7f 90 65 00
WidgetEnd
Widget JogWheelRotaryCW
Press b0 3c 01
WidgetEnd
Widget JogWheelRotaryCW2
Press b0 3c 02
WidgetEnd
Widget JogWheelRotaryCW3
Press b0 3c 03
WidgetEnd
Widget JogWheelRotaryCW4
Press b0 3c 04
WidgetEnd
Widget JogWheelRotaryCW5
Press b0 3c 05
WidgetEnd
Widget JogWheelRotaryCW6
Press b0 3c 06
WidgetEnd
Widget JogWheelRotaryCW7
Press b0 3c 07
WidgetEnd
Widget JogWheelRotaryCCW
Press b0 3c 41
WidgetEnd
Widget JogWheelRotaryCCW2
Press b0 3c 42
WidgetEnd
Widget JogWheelRotaryCCW3
Press b0 3c 43
WidgetEnd
Widget JogWheelRotaryCC4
Press b0 3c 44
WidgetEnd
Widget JogWheelRotaryCCW5
Press b0 3c 45
WidgetEnd
Widget JogWheelRotaryCCW6
Press b0 3c 46
WidgetEnd
Widget JogWheelRotaryCCW7
Press b0 3c 47
WidgetEnd
Widget MasterFader
Fader14Bit e8 7f 7f
FB_Fader14Bit e8 7f 7f
WidgetEnd
Widget VUMeter1
FB_MCUVUMeter 0
WidgetEnd
Widget VUMeter2
FB_MCUVUMeter 1
WidgetEnd
Widget VUMeter3
FB_MCUVUMeter 2
WidgetEnd
Widget VUMeter4
FB_MCUVUMeter 3
WidgetEnd
Widget VUMeter5
FB_MCUVUMeter 4
WidgetEnd
Widget VUMeter6
FB_MCUVUMeter 5
WidgetEnd
Widget VUMeter7
FB_MCUVUMeter 6
WidgetEnd
Widget VUMeter8
FB_MCUVUMeter 7
WidgetEnd
Widget DisplayUpper1
FB_MCUDisplayUpper 0
WidgetEnd
Widget DisplayUpper2
FB_MCUDisplayUpper 1
WidgetEnd
Widget DisplayUpper3
FB_MCUDisplayUpper 2
WidgetEnd
Widget DisplayUpper4
FB_MCUDisplayUpper 3
WidgetEnd
Widget DisplayUpper5
FB_MCUDisplayUpper 4
WidgetEnd
Widget DisplayUpper6
FB_MCUDisplayUpper 5
WidgetEnd
Widget DisplayUpper7
FB_MCUDisplayUpper 6
WidgetEnd
Widget DisplayUpper8
FB_MCUDisplayUpper 7
WidgetEnd
Widget DisplayLower1
FB_MCUDisplayLower 0
WidgetEnd
Widget DisplayLower2
FB_MCUDisplayLower 1
WidgetEnd
Widget DisplayLower3
FB_MCUDisplayLower 2
WidgetEnd
Widget DisplayLower4
FB_MCUDisplayLower 3
WidgetEnd
Widget DisplayLower5
FB_MCUDisplayLower 4
WidgetEnd
Widget DisplayLower6
FB_MCUDisplayLower 5
WidgetEnd
Widget DisplayLower7
FB_MCUDisplayLower 6
WidgetEnd
Widget DisplayLower8
FB_MCUDisplayLower 7
WidgetEnd
Widget Fader1
Fader14Bit e0 7f 7f
FB_Fader14Bit e0 7f 7f
WidgetEnd
Widget Fader2
Fader14Bit e1 7f 7f
FB_Fader14Bit e1 7f 7f
WidgetEnd
Widget Fader3
Fader14Bit e2 7f 7f
FB_Fader14Bit e2 7f 7f
WidgetEnd
Widget Fader4
Fader14Bit e3 7f 7f
FB_Fader14Bit e3 7f 7f
WidgetEnd
Widget Fader5
Fader14Bit e4 7f 7f
FB_Fader14Bit e4 7f 7f
WidgetEnd
Widget Fader6
Fader14Bit e5 7f 7f
FB_Fader14Bit e5 7f 7f
WidgetEnd
Widget Fader7
Fader14Bit e6 7f 7f
FB_Fader14Bit e6 7f 7f
WidgetEnd
Widget Fader8
Fader14Bit e7 7f 7f
FB_Fader14Bit e7 7f 7f
WidgetEnd
Widget FaderTouch1
Press 90 68 7f 90 68 00
WidgetEnd
Widget FaderTouch2
Press 90 69 7f 90 69 00
WidgetEnd
Widget FaderTouch3
Press 90 6a 7f 90 6a 00
WidgetEnd
Widget FaderTouch4
Press 90 6b 7f 90 6b 00
WidgetEnd
Widget FaderTouch5
Press 90 6c 7f 90 6c 00
WidgetEnd
Widget FaderTouch6
Press 90 6d 7f 90 6d 00
WidgetEnd
Widget FaderTouch7
Press 90 6e 7f 90 6e 00
WidgetEnd
Widget FaderTouch8
Press 90 6f 7f 90 6f 00
WidgetEnd
Widget RotaryPush1
Press 90 20 7f
WidgetEnd
Widget RotaryPush2
Press 90 21 7f
WidgetEnd
Widget RotaryPush3
Press 90 22 7f
WidgetEnd
Widget RotaryPush4
Press 90 23 7f
WidgetEnd
Widget RotaryPush5
Press 90 24 7f
WidgetEnd
Widget RotaryPush6
Press 90 25 7f
WidgetEnd
Widget RotaryPush7
Press 90 26 7f
WidgetEnd
Widget RotaryPush8
Press 90 27 7f
WidgetEnd
Widget Rotary1
Encoder b0 10 7f
FB_Encoder b0 10 7f
WidgetEnd
Widget Rotary2
Encoder b0 11 7f
FB_Encoder b0 11 7f
WidgetEnd
Widget Rotary3
Encoder b0 12 7f
FB_Encoder b0 12 7f
WidgetEnd
Widget Rotary4
Encoder b0 13 7f
FB_Encoder b0 13 7f
WidgetEnd
Widget Rotary5
Encoder b0 14 7f
FB_Encoder b0 10 7f
WidgetEnd
Widget Rotary6
Encoder b0 15 7f
FB_Encoder b0 11 7f
WidgetEnd
Widget Rotary7
Encoder b0 16 7f
FB_Encoder b0 12 7f
WidgetEnd
Widget Rotary8
Encoder b0 17 7f
FB_Encoder b0 13 7f
WidgetEnd
Widget RecordArm1
Press 90 00 7f
FB_TwoState 90 00 7f 90 00 00
WidgetEnd
Widget Solo1
Press 90 08 7f
FB_TwoState 90 08 7f 90 08 00
WidgetEnd
Widget Mute1
Press 90 10 7f
FB_TwoState 90 10 7f 90 10 00
WidgetEnd
Widget Select1
Press 90 18 7f
FB_TwoState 90 18 7f 90 18 00
WidgetEnd
Widget Select2
Press 90 19 7f
FB_TwoState 90 19 7f 90 19 00
WidgetEnd
Widget Select3
Press 90 1a 7f
FB_TwoState 90 1a 7f 90 1a 00
WidgetEnd
Widget Select4
Press 90 1b 7f
FB_TwoState 90 1b 7f 90 1b 00
WidgetEnd
Widget Select5
Press 90 1c 7f
FB_TwoState 90 1c 7f 90 1c 00
WidgetEnd
Widget Select6
Press 90 1d 7f
FB_TwoState 90 1d 7f 90 1d 00
WidgetEnd
Widget Select7
Press 90 1e 7f
FB_TwoState 90 1e 7f 90 1e 00
WidgetEnd
Widget Select8
Press 90 1f 7f
FB_TwoState 90 1f 7f 90 1f 00
WidgetEnd
Last edited by WaveTrans; 01-24-2020 at 11:51 AM.
|
|
|
01-24-2020, 11:59 AM
|
#6148
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Quote:
Originally Posted by Geoff Waddington
As @MixMonkey says, the wobble is a sure sign of double mapped (or in this case X8) controls and also a sure sign you are headed for Niagra Falls : ).
Most surfaces (but not all) eventually fall over from this traffic overload.
Turn on Midi Out Monitor, if you are stopped and you see lots of data streaming out, you will likely soon crash -- meaning your devices will become unresponsive.
And to the obvious question -- why isn't there code to prevent this -- because it's Reaper and we give you all the tools, including the ones to shoot yourself in the foot -- no restrictions here
Seriously, think of what would happen if you moved a Fader very fast - lots of data -- if we prevented that you could only do very slow fader moves -- there are many other examples...
|
So then its not good practice to map 2 actions to 1 button ? Cause i have something like that where the button activates the function and brings up the window for it on the one button press. And i notice this particular button that i have the 2 actions mapped to it flickers. Almost like its getting ready to blow ..so to speak...so i shouldnt do this?
|
|
|
01-24-2020, 12:17 PM
|
#6149
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Quote:
Originally Posted by Cragster
So then its not good practice to map 2 actions to 1 button ? Cause i have something like that where the button activates the function and brings up the window for it on the one button press. And i notice this particular button that i have the 2 actions mapped to it flickers. Almost like its getting ready to blow ..so to speak...so i shouldnt do this?
|
Yeah, it's like a Star Trek phaser on overload, they always blink crazily just before they blow
Here's the gory geeky details.
Reaper can send out update data at an amazing rate.
This is good and keeps the interface snappy.
However some of the slower surfaces -- especially old "real MIDI" DIN connector types that are limited to 31 kBaud -- can be easily swamped.
So, to keep things snappy AND reduce traffic...
Each time a value is to be sent, CSI checks -- is it the same -- yes, don't send it it's redundant -- otherwise it is a new value and the surface should be updated.
The trouble here is the scan pass sees that Action 1 should be updated and goes ahead and does that.
Now Action 1 probably sends that same data a number of times but it never gets out of the box because it is the same.
Now consider what happens when you add Action 2.
The scan pass calls for the value for Action 1 and sends it -- all is good.
BUT, then it scans Action 2 and updates it.
That update goes to the same control.
Can you see what happens ?
It sees the value is different (after all it's the value for Action 1 that just got sent out) and goes ahead and sends it out.
On the next scan Action 1 goes to update and finds the value is NOT the same (it's now Action 2's value) and sends it out.
Now Action 2 comes along and does the same thing.
And on and on numerous times a second -- there's your wobble, and your disaster about to happen
You can map 2 Actions to a button, you just have to be careful about the feedback.
The code could probably be improved as well.
As we go forward into beta, we can tackle more nuanced things like this.
__________________
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
|
|
|
01-24-2020, 12:24 PM
|
#6150
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Quote:
Originally Posted by Geoff Waddington
Yeah, it's like a Star Trek phaser on overload, they always blink crazily just before they blow
Here's the gory geeky details.
Reaper can send out update data at an amazing rate.
This is good and keeps the interface snappy.
However some of the slower surfaces -- especially old "real MIDI" DIN connector types that are limited to 31 kBaud -- can be easily swamped.
So, to keep things snappy AND reduce traffic...
Each time a value is to be sent, CSI checks -- is it the same -- yes, don't send it it's redundant -- otherwise it is a new value and the surface should be updated.
The trouble here is the scan pass sees that Action 1 should be updated and goes ahead and does that.
Now Action 1 probably sends that same data a number of times but it never gets out of the box because it is the same.
Now consider what happens when you add Action 2.
The scan pass calls for the value for Action 1 and sends it -- all is good.
BUT, then it scans Action 2 and updates it.
That update goes to the same control.
Can you see what happens ?
It sees the value is different (after all it's the value for Action 1 that just got sent out) and goes ahead and sends it out.
On the next scan Action 1 goes to update and finds the value is NOT the same (it's now Action 2's value) and sends it out.
Now Action 2 comes along and does the same thing.
And on and on numerous times a second -- there's your wobble, and your disaster about to happen
You can map 2 Actions to a button, you just have to be careful about the feedback.
The code could probably be improved as well.
As we go forward into beta, we can tackle more nuanced things like this.
|
Thanks for the info Geoff ill be making that change right away. The convenience of it was nice but not at the cost of fryung my surface.
|
|
|
01-24-2020, 12:32 PM
|
#6151
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
I got that from something i happened along. Some page by a malcolmgroves on CSI . He has a bunch of notes like a manual. One of the sections is on invoking multiple actions. It says its as easy as mapping 2 functions to 1 button.i guess i gotta watch what info i get.
|
|
|
01-24-2020, 12:38 PM
|
#6152
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Quote:
Originally Posted by Cragster
I got that from something i happened along. Some page by a malcolmgroves on CSI . He has a bunch of notes like a manual. One of the sections is on invoking multiple actions. It says its as easy as mapping 2 functions to 1 button.i guess i gotta watch what info i get.
|
He's right, it is easy to do, you just have to watch it bit, that's all
__________________
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
|
|
|
01-24-2020, 12:49 PM
|
#6153
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 861
|
Quote:
Originally Posted by Geoff Waddington
He's right, it is easy to do, you just have to watch it bit, that's all
|
Thanks Geoff.ill just stick to 1 button 1 action
|
|
|
01-24-2020, 03:07 PM
|
#6154
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by Geoff Waddington
Yeah, it's like a Star Trek phaser on overload, they always blink crazily just before they blow
|
Canīt have that, took out all double assignments;
they are practical but the phaser comparison is quite convincing
Did I understand correctly that even if CSI opened the sends menu automatically when sends are toggled the same feedback issues will occur?
|
|
|
01-24-2020, 03:48 PM
|
#6155
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Geoff, if the button in question (that has more than one action assigned to it) doesn't generate feedback (just a plain old press) does the issue still occur?
|
|
|
01-24-2020, 03:58 PM
|
#6156
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by WaveTrans
The nano has 4 rotaries
(actually 5, but the one above the fader has the same code as the first one of the grouped four).
Topmost on the left hand side button row is a toggle button (5-8) to switch to a rotaries 5-8 mode.
If it is engaged, the codes for rotaries 5-8 (mcu) are sent.
|
Ok, get it now Didn't know about the "5-8" button.
|
|
|
01-24-2020, 04:09 PM
|
#6157
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by MixMonkey
Geoff, if the button in question (that has more than one action assigned to it) doesn't generate feedback (just a plain old press) does the issue still occur?
|
I'm wondering the same thing, never heard about this overload before and I'm pretty sure I got the idea for the "2 action/1 button" thing from this group...and use it at least 4 times in my setup.
the ONLY issue I have is that, in some cases when toggling a Reaper action, the button will stay lit instead of toggle. For example, I have a custom action for Transport that also toggles Mute of a talkback track. So, all my transports stay lit regardless of actual status
I haven't ever run into an issue with the functions themselves, only the feedback/light of the button state. And yes it also flashes sorta erratically.....but it all works.
|
|
|
01-24-2020, 04:12 PM
|
#6158
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Quote:
Originally Posted by MixMonkey
Geoff, if the button in question (that has more than one action assigned to it) doesn't generate feedback (just a plain old press) does the issue still occur?
|
It has nothing to do with the button, it's the FB processor, the second line.
Any info sent by the surface, CSI/Reaper can handle easily.
The other way is the trickier bit
We might be able to improve that by having some actions that don't generate feedback.
Reaper Actions will likely prove difficult -- some have FB some don't...
__________________
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
|
|
|
01-24-2020, 04:16 PM
|
#6159
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,254
|
Quote:
Originally Posted by poetnprophet
I'm wondering the same thing, never heard about this overload before and I'm pretty sure I got the idea for the "2 action/1 button" thing from this group...and use it at least 4 times in my setup.
the ONLY issue I have is that, in some cases when toggling a Reaper action, the button will stay lit instead of toggle. For example, I have a custom action for Transport that also toggles Mute of a talkback track. So, all my transports stay lit regardless of actual status
I haven't ever run into an issue with the functions themselves, only the feedback/light of the button state. And yes it also flashes sorta erratically.....but it all works.
|
Yup, if your surface can handle the traffic you're OK, although there is an awful lot of useless data being transmitted.
__________________
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
|
|
|
01-24-2020, 04:18 PM
|
#6160
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Geoff Waddington
It has nothing to do with the button, it's the FB processor, the second line.
|
I've been deleting the second (FB) line when I've had the double action flickering light issue (the MCU has more LED FB lights than it reasonably needs)
The light stays on permanently after this, but no more spurious messages.
|
|
|
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 03:54 AM.
|