|
|
|
11-23-2019, 02:23 AM
|
#5401
|
Human being with feelings
Join Date: Apr 2018
Posts: 10
|
I've been experimenting with things quite a bit since having gotten the modifiers to work and understanding a bit more how the whole thing is layed out, and I've read quite a bit through the topic looking for info, but there is one thing I don't get how to do (if possible at that point):
Say you have 1 fader, and multiple buttons, and want to use the fader to manage the levels of the sends of the currently selected track.
My problem is I want to redirect THAT fader to different outputs depending on that other factor (which button has been pressed)
What seemed the most logical to me was to create a zone corresponding to each button, and to get the fader input from there, sending it to the track send whose number corresponds to the one of the button. However, I don't get how to choose which send the fader would be routed to? Every example I have found seem to take X faders/encoders and send them to X track volumes or track send volumes (without reordering them), so is what I wanna do even possible?
It seemed to me it could be using multiple pages but really that seems like a LOT of hassle...
|
|
|
11-23-2019, 03:29 AM
|
#5402
|
Human being with feelings
Join Date: Jul 2011
Location: Northern Ireland
Posts: 902
|
Quote:
Originally Posted by Geoff Waddington
How about ToggleFolderDrilldown for the Action name ?
As usual you are free to assign any action to any surface controls you like
|
Yeah or just ToggleFolder
|
|
|
11-23-2019, 05:19 PM
|
#5403
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Freex
Yeah or just ToggleFolder
|
Yeah, that's better.
__________________
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
|
|
|
11-23-2019, 05:28 PM
|
#5404
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Korwent
I've been experimenting with things quite a bit since having gotten the modifiers to work and understanding a bit more how the whole thing is layed out, and I've read quite a bit through the topic looking for info, but there is one thing I don't get how to do (if possible at that point):
Say you have 1 fader, and multiple buttons, and want to use the fader to manage the levels of the sends of the currently selected track.
My problem is I want to redirect THAT fader to different outputs depending on that other factor (which button has been pressed)
What seemed the most logical to me was to create a zone corresponding to each button, and to get the fader input from there, sending it to the track send whose number corresponds to the one of the button. However, I don't get how to choose which send the fader would be routed to? Every example I have found seem to take X faders/encoders and send them to X track volumes or track send volumes (without reordering them), so is what I wanna do even possible?
It seemed to me it could be using multiple pages but really that seems like a LOT of hassle...
|
Assuming your widget names are:
Fader1
Button1
Button2
Button3
Button4
Code:
Zone Send1
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send2
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send3
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send4
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Buttons
Button1 GoZone Send1
Button2 GoZone Send2
Button3 GoZone Send3
Button4 GoZone Send4
ZoneEnd
Don't forget to have the selected track send mapping enabled.
__________________
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
|
|
|
11-23-2019, 05:51 PM
|
#5405
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Been thinking about MasterTrack.
Before we go beta we will dump
MasterTrackVolume
MasterTrackUniqueSelect
etc.
They will be replaced by MasterTrackNavigator.
Then, you can just use TrackVolume, etc. as elsewhere -- much more consistent.
If you have a Master Track, you will now need a separate Zone -- like Channels -- included in the Home Zone:
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
IncludedZones
Buttons
Channel|1-8
MasterChannel
IncludedZonesEnd
ZoneEnd
Zone MasterChannel
MasterTrackNavigator
MasterFader TrackVolume
MasterMute TrackMute
...
ZoneEnd
__________________
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; 11-23-2019 at 05:58 PM.
|
|
|
11-24-2019, 12:17 AM
|
#5406
|
Human being with feelings
Join Date: Mar 2018
Posts: 105
|
X-Touch or X-Touch one support?
I downloaded CSI and noticed that Behringer X-Touch one is kind of supported. How about X-Touch Universal? It´s a bit odd if cheaper one has more support than more robust one. Or do I misunderstood whole thing? I'm not hurry, so I have delayed my controller order until I get this thing sorted out.
|
|
|
11-24-2019, 03:15 AM
|
#5407
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,685
|
As the creation of configuration files is greatly community driven, the devices that are supported out of the box depends on same.
I seem to remember discussions on the "universal" (AKA "USB" ?). Hence there might be config files available on request.
-Michael
|
|
|
11-24-2019, 03:35 AM
|
#5408
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by mschnell
As the creation of configuration files is greatly community driven, the devices that are supported out of the box depends on same.
I seem to remember discussions on the "universal" (AKA "USB" ?). Hence there might be config files available on request.
-Michael
|
Yeah, as part of the run up to beta we are requesting any and all .mst/.ost/.zon files.
Step right up folks
__________________
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
|
|
|
11-24-2019, 03:54 AM
|
#5409
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Having to put Press+ in front of almost every Action is needlessly complex, and looks plain awful.
It also needlessly complicates the internal code.
On the other hand we don't want to restrict the .mst/.ost capabilities definition -- or do we ?
Except for the modifiers and a very few other Actions we usually just want the Press, we can ignore the Release.
Can we have our cake and eat it too ?
Yup.
We just need to do this:
Code:
Widget Shift
Press 90 46 7f
WidgetEnd
Widget Shift_R
Press 90 46 7f 90 46 00
WidgetEnd
Widget Play
Press 90 5e 7f
FB_TwoState 90 5e 7f 90 5e 00
WidgetEnd
Now the .zon files will look MUCH cleaner, and we can still choose which behaviour we want -- including the release variant (SomeControl _R) if available.
The slight added expense is an extra definition in the .mst/.ost file for the buttons that transmit Release.
I think that's fine, since the .mst/.ost files are very rarely touched after initial definition.
What say you folks ?
__________________
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
|
|
|
11-24-2019, 04:07 AM
|
#5410
|
Human being with feelings
Join Date: Jun 2014
Posts: 152
|
Quote:
Originally Posted by Geoff Waddington
Assuming your widget names are:
Fader1
Button1
Button2
Button3
Button4
Code:
Zone Send1
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send2
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send3
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Send4
SelectedTrackNavigator
Fader1 TrackSendVolume
ZoneEnd
Zone Buttons
Button1 GoZone Send1
Button2 GoZone Send2
Button3 GoZone Send3
Button4 GoZone Send4
ZoneEnd
Don't forget to have the selected track send mapping enabled.
|
I tried this today but can only control the first send this way. Where is the actual send selection happening?
By "Don't forget to have the selected track send mapping enabled" do you mean the checkbox for "Auto Map Sends" in preferences? I did enable that just in case.
Thanks!
|
|
|
11-24-2019, 04:18 AM
|
#5411
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by n0ne
I tried this today but can only control the first send this way. Where is the actual send selection happening?
By "Don't forget to have the selected track send mapping enabled" do you mean the checkbox for "Auto Map Sends" in preferences? I did enable that just in case.
Thanks!
|
The selection is hardwired -- SelectedTrackNavigator + Send1 means the first Send slot on the selected Track, and so on.
I didn't actually try this, so there could be a bug -- don't knock yourself out try ing to make it work, I'll try it here and let you know.
__________________
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
|
|
|
11-24-2019, 09:18 AM
|
#5412
|
Human being with feelings
Join Date: Jun 2014
Posts: 152
|
Awesome! I'll wait for that than.
I've got post of the Icon Platoform Nano mapped now except for the Master VU Meter. I'll share it soon. Cool to know whats possible with this!
|
|
|
11-24-2019, 09:40 AM
|
#5413
|
Human being with feelings
Join Date: Jan 2019
Location: VT, USA
Posts: 11
|
Quote:
Originally Posted by pwallin
I downloaded CSI and noticed that Behringer X-Touch one is kind of supported. How about X-Touch Universal? It´s a bit odd if cheaper one has more support than more robust one. Or do I misunderstood whole thing? I'm not hurry, so I have delayed my controller order until I get this thing sorted out.
|
The MCU files will get you close. Check my post history for a .pdf of the midi map for the Universal so you can tweak your own. Wish I could offer you more, but I've kind of given up on this for the time being. With a 2 year old running around, I have neither the time nor the patience to figure this out.
|
|
|
11-24-2019, 10:14 AM
|
#5414
|
Human being with feelings
Join Date: Mar 2018
Posts: 105
|
X-Touch support?
Quote:
Originally Posted by pwallin
I downloaded CSI and noticed that Behringer X-Touch one is kind of supported. How about X-Touch Universal? It´s a bit odd if cheaper one has more support than more robust one. Or do I misunderstood whole thing? I'm not hurry, so I have delayed my controller order until I get this thing sorted out.
|
To clarify a bit. If I use "X-Touch mini.mst" Does that work with 8 -fader X-Touch?
|
|
|
11-24-2019, 10:25 AM
|
#5415
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
|
Speaking of MCU, is anyone here working on (i.e. keeping up with CSI changes) a MCU setup?
If so, would this person share it here (or is there one already I mised)?
Reason I'm asking, I could/like to test with my BCR faking a MCU, but too busy currently to follow CSI development myself unfortunately.
E.g. the (I think) recently added metering capability is not included in the stock MCU setup files yet, are they?
|
|
|
11-24-2019, 03:17 PM
|
#5416
|
Human being with feelings
Join Date: Nov 2014
Posts: 798
|
Hi Geoff, is it possible yet to fully map to the console 1 plugin via csi, including feedback?
I would like to stop using the proprietary mapping, because it doesn't support tabs, and the auto track selection is really buggy.
|
|
|
11-24-2019, 03:57 PM
|
#5417
|
Human being with feelings
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
|
Quote:
Originally Posted by Geoff Waddington
Having to put Press+ in front of almost every Action is needlessly complex, and looks plain awful.
It also needlessly complicates the internal code.
On the other hand we don't want to restrict the .mst/.ost capabilities definition -- or do we ?
Except for the modifiers and a very few other Actions we usually just want the Press, we can ignore the Release.
Can we have our cake and eat it too ?
Yup.
We just need to do this:
Code:
Widget Shift
Press 90 46 7f
WidgetEnd
Widget Shift_R
Press 90 46 7f 90 46 00
WidgetEnd
Widget Play
Press 90 5e 7f
FB_TwoState 90 5e 7f 90 5e 00
WidgetEnd
Now the .zon files will look MUCH cleaner, and we can still choose which behaviour we want -- including the release variant (SomeControl _R) if available.
The slight added expense is an extra definition in the .mst/.ost file for the buttons that transmit Release.
I think that's fine, since the .mst/.ost files are very rarely touched after initial definition.
What say you folks ?
|
My only concern would be confusion when someone is creating their Zone. Will it be more confusing for people to see multiple widgets in the Learn window with almost the same name as the physical control?
Especially given I think most people will use the GUI rather than hand-editing their zone files, I'm unconvinced. I could put up with the zone files being a little uglier for the few who venture in there, if it means the Learn window is clearer.
If we do go this way, then it needs to be clearer than just an R suffix.
Cheers
Malcolm
|
|
|
11-24-2019, 04:51 PM
|
#5418
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by nofish
Speaking of MCU, is anyone here working on (i.e. keeping up with CSI changes) a MCU setup?
If so, would this person share it here (or is there one already I mised)?
Reason I'm asking, I could/like to test with my BCR faking a MCU, but too busy currently to follow CSI development myself unfortunately.
E.g. the (I think) recently added metering capability is not included in the stock MCU setup files yet, are they?
|
Yeah the meters should work just fine. They will be included with the beta.
__________________
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
|
|
|
11-24-2019, 04:52 PM
|
#5419
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Travesty
Hi Geoff, is it possible yet to fully map to the console 1 plugin via csi, including feedback?
I would like to stop using the proprietary mapping, because it doesn't support tabs, and the auto track selection is really buggy.
|
Yes, everything except the 3 position buttons -- we'll add them later.
__________________
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
|
|
|
11-24-2019, 04:55 PM
|
#5420
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
|
Quote:
Originally Posted by Geoff Waddington
Yeah the meters should work just fine. They will be included with the beta.
|
Cool, thanks.
|
|
|
11-24-2019, 05:00 PM
|
#5421
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MalcolmG
My only concern would be confusion when someone is creating their Zone. Will it be more confusing for people to see multiple widgets in the Learn window with almost the same name as the physical control?
Especially given I think most people will use the GUI rather than hand-editing their zone files, I'm unconvinced. I could put up with the zone files being a little uglier for the few who venture in there, if it means the Learn window is clearer.
If we do go this way, then it needs to be clearer than just an R suffix.
Cheers
Malcolm
|
Yup, makes sense theoretically, and is in line with what I've been thinking up until now.
But evaluating the use cases leads to one inevitable conclusion -- although it seems right that we don't restrict the release message in the .mst/.ost file we actually use release VERY frequently.
Let's take a look at the Actions -- almost all of them have no interest in release -- Shift, Option, Control, and Alt being the obvious exceptions.
Put another way, most Actions are latching as opposed to momentary.
So given this new, use case based analysis, I think it is safe to say we should always build the Press only widget as the default, and only add the release variant where needed, which is infrequently.
__________________
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; 11-24-2019 at 06:46 PM.
|
|
|
11-24-2019, 07:16 PM
|
#5422
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by nofish
Speaking of MCU, is anyone here working on (i.e. keeping up with CSI changes) a MCU setup?
If so, would this person share it here (or is there one already I mised)?
Reason I'm asking, I could/like to test with my BCR faking a MCU, but too busy currently to follow CSI development myself unfortunately.
E.g. the (I think) recently added metering capability is not included in the stock MCU setup files yet, are they?
|
I have an MCU based system, here's my MCU.zon file:
Code:
Zone Home
OnTrackSelection MapSelectedTrackSendsToWidgets
OnTrackSelection MapSelectedTrackFXToMenu
/ OnFXFocus MapFocusedFXToWidgets
IncludedZones
Buttons
Channel|1-8
IncludedZonesEnd
ZoneEnd
Zone Send|1-8
SelectedTrackNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
TrackTouch+Fader| TrackSendVolume
FaderTouch| TrackTouch
ZoneEnd
Zone Buttons
/ Track
Send ToggleMapSelectedTrackSends
/ Pan
Plugin ToggleMapSelectedTrackFXMenu
/ EQ
/ Instrument
BankLeft TrackBank -8
BankRight TrackBank 8
ChannelLeft TrackBank -1
ChannelRight TrackBank 1
/Show only track receives
/ Flip
/Return from track receives
/ GlobalView
/Show all tracks
Shift+GlobalView Reaper _SWSTL_SHOWALL
/Show screen/track/item sets window
nameValue Reaper 40422
smpteBeats CycleTimeDisplayModes
TimeDisplay TimeDisplay
/Load track view set
F1 Reaper 40444
F2 Reaper 40445
F3 Reaper 40446
F4 Reaper 40447
F5 Reaper 40448
F6 Reaper 40449
F7 Reaper 40450
F8 Reaper 40451
/Save track view set
Shift+F1 Reaper 40464
Shift+F2 Reaper 40465
Shift+F3 Reaper 40466
Shift+F4 Reaper 40467
Shift+F5 Reaper 40468
Shift+F6 Reaper 40469
Shift+F7 Reaper 40470
Shift+F8 Reaper 40471
/Load window set
MidiTracks Reaper 40454
Inputs Reaper 40455
AudioTracks Reaper 40456
AudioInstrument Reaper 40457
Aux Reaper 40458
Busses Reaper 40459
Outputs Reaper 40460
User Reaper 40461
/Save window set
Shift+MidiTracks Reaper 40474
Shift+Inputs Reaper 40475
Shift+AudioTracks Reaper 40476
Shift+AudioInstrument Reaper 40477
Shift+Aux Reaper 40478
Shift+Busses Reaper 40479
Shift+Outputs Reaper 40480
Shift+User Reaper 40481
Shift Shift
Option Option
Control Control
Alt Alt
Read TrackAutoMode 1
Write TrackAutoMode 3
Trim TrackAutoMode 0
Touch TrackAutoMode 2
Latch TrackAutoMode 4
/Set track automation mode to latch preview
Group Reaper 42023
Shift+Read GlobalAutoMode 1
Shift+Write GlobalAutoMode 3
Shift+Trim GlobalAutoMode 0
Shift+Touch GlobalAutoMode 2
Shift+Latch GlobalAutoMode 4
/Set all tracks automation mode to latch preview
Shift+Group Reaper 42024
Save ToggleLearnMode
Undo Reaper 40072
/Toggle show children of selected tracks
Cancel Reaper 41665
/Show all tracks
Enter Reaper _SWSTL_SHOWALL
/Open marker list
Marker Reaper _SWSMARKERLIST1
/Insert marker at current position
Control+Marker Reaper 40157
/Delete marker near cursor
Shift+Marker Reaper 40613
/Item edit: Toggle open/close nudge/set dialog
Nudge Reaper 41228
Cycle CycleTimeline
/Toggle Scroll playback
/ Drop Reaper 40036
/Toggle Scroll record
/ Drop Reaper 40262
/Toggle show docker
Replace Reaper 40279
/Toggle metronome
Click Reaper 40364
/Toggle surface scroll, Channel 17 LHS
Solo ToggleScrollLink 17
/Go to prev marker/region
/ Rewind Reaper _SWS_SELPREVMORR
Rewind Reaper 40172
/Go to next marker/region
/ FastForward Reaper _SWS_SELNEXTMORR
FastForward Reaper 40173
Stop Stop
Play Play
Record Record
/Move cursor right to grid division
JogWheelRotaryCW Reaper 40647
/Move cursor left to grid division
JogWheelRotaryCCW Reaper 40646
/ Scrub
MasterFader MasterTrackVolume
ZoneEnd
Zone Channel|1-8
TrackNavigator
VUMeter| TrackOutputMeter
DisplayUpper| TrackNameDisplay
DisplayLower| TrackPanDisplay
TrackTouch+DisplayUpper| TrackVolumeDisplay
RotaryPush| GoZone Pan|
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
DisplayUpper| TrackPanDisplay
TrackTouch+DisplayUpper| TrackVolumeDisplay
RotaryPush| GoZone PanWidth|
ZoneEnd
Zone PanWidth|1-8
TrackNavigator
Rotary| TrackPanWidth 1
DisplayUpper| TrackPanWidthDisplay
TrackTouch+DisplayUpper| TrackVolumeDisplay
RotaryPush| GoZone Channel|
ZoneEnd
I'm constantly trying out different things (usually with buttons) so it's a bit messy. I suggest you comment out/delete anything that you don't need.
I've attached the MCU.mst which is standard, apart from the jog wheel and I may have commented out a few FB line to make LEDs turn off.
Last edited by MixMonkey; 04-09-2020 at 01:29 PM.
|
|
|
11-24-2019, 08:03 PM
|
#5423
|
Human being with feelings
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
|
Quote:
Originally Posted by Geoff Waddington
Yup, makes sense theoretically, and is in line with what I've been thinking up until now.
But evaluating the use cases leads to one inevitable conclusion -- although it seems right that we don't restrict the release message in the .mst/.ost file we actually use release VERY frequently.
Let's take a look at the Actions -- almost all of them have no interest in release -- Shift, Option, Control, and Alt being the obvious exceptions.
Put another way, most Actions are latching as opposed to momentary.
So given this new, use case based analysis, I think it is safe to say we should always build the Press only widget as the default, and only add the release variant where needed, which is infrequently.
|
OK, good point. Forgive the devil's advocating, but an alternative would be to define them once with both messages, make the default Press only, and have a Release modifier instead of a Press modifier?
A bit odd, but I still worry that having the same widget show multiple times in the Learn window will throw inexperienced people off.
A third option here would be to standardise the suffixes, and have the Learn window be smart enough to show them as variants of one widget. Maybe a little tree/hierarchy, :
MyButton
- Press
- Press\Release
More work in the GUI, but clearer I think than just multiple items with very similar names.
Worst case, I'd strongly advocate for making the Widget names descriptive, like:
MyButton_Press
MyButton_PressRelease
Cheers
Malcolm
|
|
|
11-24-2019, 08:20 PM
|
#5424
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MalcolmG
OK, good point. Forgive the devil's advocating, but an alternative would be to define them once with both messages, make the default Press only, and have a Release modifier instead of a Press modifier?
|
Well, there's a also selfish, safety reason here code wise.
It never turns out well having stray signals wandering around the circuits
There's actually quite a bit of fairly ugly logic that determines what to ignore when
There is something conceptually elegant in a minimalistic way about the Widget generating the "correct" signal.
Quote:
Originally Posted by MalcolmG
A bit odd, but I still worry that having the same widget show multiple times in the Learn window will throw inexperienced people off.
|
Not sure it would turn out that way.
For instance, there is no reason to have a non release version of the Shift Widget.
Probably will happen rarely, if at all, that there are 2 definitions.
Quote:
Originally Posted by MalcolmG
A third option here would be to standardise the suffixes, and have the Learn window be smart enough to show them as variants of one widget. Maybe a little tree/hierarchy, :
MyButton
- Press
- Press\Release
More work in the GUI, but clearer I think than just multiple items with very similar names.
|
Hmmm...
Quite complex
Quote:
Originally Posted by MalcolmG
Worst case, I'd strongly advocate for making the Widget names descriptive, like:
MyButton_Press
MyButton_PressRelease
Cheers
Malcolm
|
Agree.
__________________
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
|
|
|
11-24-2019, 08:38 PM
|
#5425
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,096
|
Thanks for sharing your files MixMonkey.
Just tried with them and can confirm meters* and jog wheel working. Excellent!
*Well the BCR doesn't really have 'meters', I abuse the LED rings for it, so it's rather just serving as activity indicators but useful nonetheless.
If someone's interested how it looks, I once recorded a video of my trusty BCR with Klinke's plugin, the bottom row of LEDs is the 'meters' moving LOL. Looks the same with CSI.
https://s1100.photobucket.com/user/n...eters.mp4.html
Last edited by nofish; 11-24-2019 at 08:48 PM.
|
|
|
11-24-2019, 11:10 PM
|
#5426
|
Human being with feelings
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
|
Quote:
Originally Posted by Geoff Waddington
Not sure it would turn out that way.
For instance, there is no reason to have a non release version of the Shift Widget.
Probably will happen rarely, if at all, that there are 2 definitions.
|
OK, then I'm confused
I thought that's exactly what you were suggesting. ie. that if we have a surface with buttons that send a release, we define them as two widgets, so the user can decide which one they want to use?
What have I missed?
Update: Ahh, ok, got it. I just re-read your first post for about the 5th time and then the penny dropped. You're using the Release of the Shift as a substitute for the Release of the Play. OK, I think I've caught up to everyone else now.
As long as I can still define a Release when I need it, I'm happy. The intersection of those who specifically need a release on a non-Modifier widget AND are only using the Learn window might be quite small.
Last edited by MalcolmG; 11-24-2019 at 11:15 PM.
|
|
|
11-25-2019, 04:16 AM
|
#5427
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MalcolmG
OK, then I'm confused
I thought that's exactly what you were suggesting. ie. that if we have a surface with buttons that send a release, we define them as two widgets, so the user can decide which one they want to use?
What have I missed?
Update: Ahh, ok, got it. I just re-read your first post for about the 5th time and then the penny dropped. You're using the Release of the Shift as a substitute for the Release of the Play. OK, I think I've caught up to everyone else now.
As long as I can still define a Release when I need it, I'm happy. The intersection of those who specifically need a release on a non-Modifier widget AND are only using the Learn window might be quite small.
|
Ahhh, the wonderful world of Ux (user experience)
When I press Shift, I expect SomeButton to do something different.
When I release Shift I expect SomeButton to go back to normal.
I expect a button named Shift to generate release.
On the other hand, when I Press select, I expect a Track to select.
When I release Select I do not expect the Track to de-select.
I expect a button named Select to generate Press only.
Once again, you can do anything you want, we are talking default behaviour for maximum positive Ux.
In fact we are really talking about the Widgets (leftmost) window in Learn Mode.
So, counterintuitive to pure logic, and taking Ux into account, the Widgets window should contain the name Shift, meaning a Widget that generates a release.
Likewise, a Widget named Select would be expected to generate only a Press.
In other words, let's define the outliers a la:
Shift_NoRelease
Select_WithRelease
when we need them.
__________________
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
|
|
|
11-25-2019, 04:18 AM
|
#5428
|
Human being with feelings
Join Date: Apr 2018
Posts: 10
|
Quote:
Originally Posted by Geoff Waddington
The selection is hardwired -- SelectedTrackNavigator + Send1 means the first Send slot on the selected Track, and so on.
I didn't actually try this, so there could be a bug -- don't knock yourself out try ing to make it work, I'll try it here and let you know.
|
Same issue here, I'll wait for your test too then!
|
|
|
11-25-2019, 06:24 AM
|
#5429
|
Human being with feelings
Join Date: Nov 2019
Location: Hamburg/Germany
Posts: 10
|
Digidesign 003 no Led feedback for Mute nore Select
Strangely, my 003 seems to light up the Indicator-LED for SOLO1, but I don't get any feedback for select nor mute.
I wonder if this is caused by the controller itself or by me overlooking something?
in my .mst it goes like
Widget Solo1
Press 90 01 40
FB_TwoState 90 01 40 90 01 00
WidgetEnd
....
Widget Mute1
Press 90 02 40
FB_TwoState 90 02 40 90 02 00
WidgetEnd
Where as in Protools the controller communicates as follows:
For Mute
From 90 02 40
to 90 02 20
to 90 02 00
Could you enlighten me (pun intended) on how to implement the missing information that has to be sent to the controller within my .mst ?
I allready gave
Widget Mute1
Press 90 02 40
FB_TwoState 90 02 20 90 02 00
WidgetEnd
a try, without success.
_cheers
|
|
|
11-25-2019, 06:32 AM
|
#5430
|
Human being with feelings
Join Date: Nov 2014
Posts: 798
|
Quote:
Originally Posted by Geoff Waddington
Yes, everything except the 3 position buttons -- we'll add them later.
|
Great. Do you have the mapping files available online already? I had a look in the alpha pack, but the ones in there didn't seem to be complete.
|
|
|
11-25-2019, 10:42 AM
|
#5431
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
Quote:
Originally Posted by Geoff Waddington
Not quite sure what you mean here, please elaborate.
|
hey Geoff, sorry for the delay. What I was trying to describe were two ways to use folder mode. For individual tracks, where you select the track you want to expand/collapse. And, for the entire lot of folder tracks where you could expand/collapse all at once.
In particular to the latter specifically, Reaper native actions don't account for hidden tracks in the MCP because the action only represents the TCP. For example:
I have 2 views triggered by the page buttons: MCP view and TCP view. The mixer will correspond to what's available onscreen. The MCP has more tracks, the TCP is only for tracks with items (to edit, envelopes, etc), so no reverb, delay, parallel processing returns in the TCP view....those are hidden. But if I am in the MCP view and if I toggle the native reaper action to collapse folders, if those FX return tracks are inside of those folders (those tracks are hidden in the TCP but visible in MCP), they will not collapse in the MCP, I'm assuming because they are already hidden from the TCP. I'm honestly not sure if Klinke's plugin addresses this, I'll try it out and let you know. Maybe there's nothing you can even do about it....
|
|
|
11-25-2019, 11:15 AM
|
#5432
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Slumbersom
Strangely, my 003 seems to light up the Indicator-LED for SOLO1, but I don't get any feedback for select nor mute.
I wonder if this is caused by the controller itself or by me overlooking something?
in my .mst it goes like
Widget Solo1
Press 90 01 40
FB_TwoState 90 01 40 90 01 00
WidgetEnd
....
Widget Mute1
Press 90 02 40
FB_TwoState 90 02 40 90 02 00
WidgetEnd
Where as in Protools the controller communicates as follows:
For Mute
From 90 02 40
to 90 02 20
to 90 02 00
Could you enlighten me (pun intended) on how to implement the missing information that has to be sent to the controller within my .mst ?
I allready gave
Widget Mute1
Press 90 02 40
FB_TwoState 90 02 20 90 02 00
WidgetEnd
a try, without success.
_cheers
|
Yeah, the feedback is the trickiest bit -- usually the best way is to search for a midi implementation document for the device, have you done that ?
__________________
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
|
|
|
11-25-2019, 11:16 AM
|
#5433
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Travesty
Great. Do you have the mapping files available online already? I had a look in the alpha pack, but the ones in there didn't seem to be complete.
|
Nope, haven't even done them yet, but they will be there for the beta.
__________________
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
|
|
|
11-25-2019, 11:20 AM
|
#5434
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by poetnprophet
hey Geoff, sorry for the delay. What I was trying to describe were two ways to use folder mode. For individual tracks, where you select the track you want to expand/collapse. And, for the entire lot of folder tracks where you could expand/collapse all at once.
In particular to the latter specifically, Reaper native actions don't account for hidden tracks in the MCP because the action only represents the TCP. For example:
I have 2 views triggered by the page buttons: MCP view and TCP view. The mixer will correspond to what's available onscreen. The MCP has more tracks, the TCP is only for tracks with items (to edit, envelopes, etc), so no reverb, delay, parallel processing returns in the TCP view....those are hidden. But if I am in the MCP view and if I toggle the native reaper action to collapse folders, if those FX return tracks are inside of those folders (those tracks are hidden in the TCP but visible in MCP), they will not collapse in the MCP, I'm assuming because they are already hidden from the TCP. I'm honestly not sure if Klinke's plugin addresses this, I'll try it out and let you know. Maybe there's nothing you can even do about it....
|
Wow, that does sound like rocket science
We made TCP/MCP a per Page concept just to avoid scenarios like this
Thus I would say the CSI design only allows changes in the context of either TCP or MCP visibility...
__________________
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
|
|
|
11-25-2019, 11:53 AM
|
#5435
|
Human being with feelings
Join Date: Nov 2019
Location: Hamburg/Germany
Posts: 10
|
Quote:
Originally Posted by Geoff Waddington
Yeah, the feedback is the trickiest bit -- usually the best way is to search for a midi implementation document for the device, have you done that ?
|
Yes, I did. The 003 Midi Mode Guide. But sadly there is no documentation on the
Midi within its first state, wich is meant to be used in PT only. And this is where all the fun is at, like cycle, save, undo or mix window - wich I allready asigned.^^
Any suggestions are welcome!
Last edited by Slumbersom; 11-25-2019 at 11:57 AM.
Reason: typo
|
|
|
11-25-2019, 06:51 PM
|
#5436
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
The code for Press has been removed.
MasterTrackNavigator has been added
MasterTrackVolume, MasterTrackTouch, etc., have been removed.
Do you folks want me to put the build up so you can get your .zon files in shape, or do you want to wait until the actual beta ?
__________________
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; 11-26-2019 at 03:23 AM.
|
|
|
11-26-2019, 05:37 AM
|
#5437
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
|
Quote:
Originally Posted by Geoff Waddington
Do you folks want me to put the build up so you can get your .zon files in shape, or do you want to wait until the actual beta ?
|
Let's have at it!
Quick question regarding rotary increment/decrement encoders.
So, everytime we turn one of these, it sends a series of either increment or decrement codes, depending on the direction of rotation.
My question is: What determines the amount the controlled parameter changes with every "tick", be it pan, a send or a plugin parameter?
Do we have any control over this "minimum" change or is it hardwired into the parameter itself (inside the plugin, say)?
I'm starting to think about these things because, frankly, CSI is working pretty darn well now
|
|
|
11-26-2019, 09:14 AM
|
#5438
|
Human being with feelings
Join Date: Mar 2018
Posts: 105
|
Quote:
Originally Posted by 40Hurts
The MCU files will get you close. Check my post history for a .pdf of the midi map for the Universal so you can tweak your own. Wish I could offer you more, but I've kind of given up on this for the time being. With a 2 year old running around, I have neither the time nor the patience to figure this out.
|
Okay, thanks for the reply.
-Pasi-
|
|
|
11-26-2019, 01:20 PM
|
#5439
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,685
|
Quote:
Originally Posted by MixMonkey
Quick question regarding rotary increment/decrement encoders.
So, everytime we turn one of these, it sends a series of either increment or decrement codes, depending on the direction of rotation.
|
1) Which devices do have those ?
2) this kind of controllers are very useful. They also can be used to work in place of up/down Buttons. I suppose that CSI supports this, amyway.
3) "Normal" rotary controllers with feedback can be converted to incremental controllers by (e.g. with 7 Bit ) interpreting > 64 as inc and <64 as dec and sending them a "mid" value of 64 after something has been received.
I already suggested this to allow for using a rotary for scrolling tacks (e.g. with an XTouch Compact that features many Rotaries, but not that many non-dedicated buttons).
-Michael
Last edited by mschnell; 11-26-2019 at 10:08 PM.
|
|
|
11-26-2019, 04:19 PM
|
#5440
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by MixMonkey
Let's have at it!
Quick question regarding rotary increment/decrement encoders.
So, everytime we turn one of these, it sends a series of either increment or decrement codes, depending on the direction of rotation.
My question is: What determines the amount the controlled parameter changes with every "tick", be it pan, a send or a plugin parameter?
Do we have any control over this "minimum" change or is it hardwired into the parameter itself (inside the plugin, say)?
I'm starting to think about these things because, frankly, CSI is working pretty darn well now
|
Right now it's hardwired, but yes, acceleration is on the roadmap -- has been for about 2 years or so
__________________
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 01:12 AM.
|