|
|
|
11-21-2020, 06:37 PM
|
#11641
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Hey, might just be me missing something obvious, but can someone check to see if MCUTrackPan is working to control PanWidth and PanRight? I'm not getting either right now. I'm using the build from yesterday.
Last edited by Funkybot; 11-21-2020 at 06:42 PM.
|
|
|
11-21-2020, 06:45 PM
|
#11642
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
[QUOTE=Mistik;2367971]Ah, I see. Hopefully coming in a future update then
Did you manage to get the DisplayUpper and Lower to work on the master channel? I can't seem to get it display info for the master channel either. It just says "master" on the lower display when I switch to the master track..
Cheers[/QUOTE
There is no upper display for the master track on the ProX. As you probly know the ProX has the 2 displays. the bottom display does not work with CSI. Just the upper does which is split into upper and lower. and that bottom display does have a space for the master but making that bottom display work with CSI unfortunately is not on Geoffs list. Hes done so much with this CSI so its all good.
|
|
|
11-21-2020, 07:00 PM
|
#11643
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Found the issue with MCUTrackPan not working.
This works...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f
WidgetEnd
This doesn't...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f 90 20 00
WidgetEnd
...I forgot I was experimenting with adding the release messages a few days ago. Moral the story: don't add release messages to the toggle line.
Last edited by Funkybot; 11-21-2020 at 07:06 PM.
|
|
|
11-21-2020, 07:05 PM
|
#11644
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Geoff,
Here's a set of X-Touch One files. Two zone folders: one for SelectedTrackNavigator, one for the standard TrackNavigator.
I completely rewrote these files using the widget names on the device and trying to stay pretty true to the device labels where possible. Except for Scrub, which I used a Shift button. This should get any new user up and running pretty well.
Last edited by Funkybot; 06-19-2021 at 11:22 AM.
|
|
|
11-21-2020, 07:11 PM
|
#11645
|
Human being with feelings
Join Date: May 2013
Location: New York
Posts: 780
|
Quote:
Originally Posted by Geoff Waddington
Ah intermittent problems, my favourite
OK, looks like we're into a workaround game here
The more info you can give me the better, maybe there's a clue in there on how best to proceed...
|
Ok, been noodling around trying to come up with more feedback for you about automation read mode. First off it's probably worth noting that from a practical standpoint there's not actually a reason to move a fader if a track is in read mode, so one could make the case that none of this is that important. That said, it's not uncommon for me to accidentally grab a fader when it's in read, or even just to clumsily nudge an adjacent fader or knob on a track that I'm adjusting. Indeed, the main reason I ever use read mode is to make sure I prevent myself from changing things, so from that standpoint the most important thing isn't that the controller faders mirror exactly what's going on with the reaper gui, but just that there's no way for me to screw with the mix when tracks are in read and that everything still plays back correctly. In other words it wouldn't bother me that much if the faders didn't jump back on there own when playback is stopped, as long as they return to the correct position when I need them to. Namely, when playback is stopped or started, when the edit cursor position changes, and perhaps most importantly, when the automation mode is switched from read to another mode. Not sure what's possible, but if there's a way you could force the faders to re-read the envelope value when any of those things happen that could fix things for the most part.
Beyond that, I'm noticing a new problem that cropped up with the latest versions when you re-worked read mode. If I have two faders that are both controlling the same track in Reaper (for instance I might have a bank of faders that's auto-assigned based on what's visible in Reaper, but then another fader that always controls the selected track) and the track they're controlling is in read mode, moving one of those faders will cause the other fader to rapidly jump up and down as it tries to reconcile between the value of the moving fader and the value of the envelope it's reading from. This wouldn't bother me so much, but it's really loud and distracting when it happens and I also worry that it could be bad for the motor. This wasn't a problem in the old Eucon extension. It looks like the difference is, that in the old extension when a track is in read mode and I move the fader and watch the numbers on the scribble strip, the values in eucon change and don't return to their initial value until I let go. In CSI, when I do this the value on the scribble strip stays put even though the fader is moving. I'm guessing this is what causes the jumpy second fader. It seems like the approach from the old extension might be a better way of going about things, if possible. Here's another video I made demonstrating all of this (are these videos helpful? I can never tell if I'm doing a good enough job explaining this stuff in text as these issues feel kind of esoteric). https://www.youtube.com/watch?v=Ky0e...ature=youtu.be
|
|
|
11-21-2020, 07:21 PM
|
#11646
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by Cragster
Yes . in the 0.92 version they do. 1.0 no. when i switch pages those 2 surfaces i have just for sends and fx should go blank and faders drop .at least i think they should . they do in the 0.92 version.all the track names and stuff from the previous page hangs around until i hit mapselected buttons.and i have all that channel tracking stuff slashed out for those 2 surfaces on that page .also when switch to a track with less fx slots then the one before those slots hang around as NoMap on the display which messes up my light system. I dont know if that was intended but its not like that in that 92 build. I just like that better.
thanks for your reply Geoff. Is this a bug ?
|
Yes, that's a bug, will investigate.
__________________
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-21-2020, 07:22 PM
|
#11647
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by MixMonkey
Here's some setup files for the Mackie MCU, XT and C4. They have the V1.0 definitions.
|
Thanks, will include them in next build.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
11-21-2020, 07:23 PM
|
#11648
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
[QUOTE=Cragster;2367977]
Quote:
Originally Posted by Mistik
Ah, I see. Hopefully coming in a future update then
Did you manage to get the DisplayUpper and Lower to work on the master channel? I can't seem to get it display info for the master channel either. It just says "master" on the lower display when I switch to the master track..
Cheers[/QUOTE
There is no upper display for the master track on the ProX. As you probly know the ProX has the 2 displays. the bottom display does not work with CSI. Just the upper does which is split into upper and lower. and that bottom display does have a space for the master but making that bottom display work with CSI unfortunately is not on Geoffs list. Hes done so much with this CSI so its all good.
|
It's on the list, just have to get to it
__________________
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-21-2020, 07:24 PM
|
#11649
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by Funkybot
Geoff,
Here's a set of X-Touch One files. Two zone folders: one for SelectedTrackNavigator, one for the standard TrackNavigator.
I completely rewrote these files using the widget names on the device and trying to stay pretty true to the device labels where possible. Except for Scrub, which I used a Shift button. This should get any new user up and running pretty well.
|
Thanks, will include these in the next build.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
11-21-2020, 07:34 PM
|
#11650
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by RobinGShore
Ok, been noodling around trying to come up with more feedback for you about automation read mode. First off it's probably worth noting that from a practical standpoint there's not actually a reason to move a fader if a track is in read mode, so one could make the case that none of this is that important. That said, it's not uncommon for me to accidentally grab a fader when it's in read, or even just to clumsily nudge an adjacent fader or knob on a track that I'm adjusting. Indeed, the main reason I ever use read mode is to make sure I prevent myself from changing things, so from that standpoint the most important thing isn't that the controller faders mirror exactly what's going on with the reaper gui, but just that there's no way for me to screw with the mix when tracks are in read and that everything still plays back correctly. In other words it wouldn't bother me that much if the faders didn't jump back on there own when playback is stopped, as long as they return to the correct position when I need them to. Namely, when playback is stopped or started, when the edit cursor position changes, and perhaps most importantly, when the automation mode is switched from read to another mode. Not sure what's possible, but if there's a way you could force the faders to re-read the envelope value when any of those things happen that could fix things for the most part.
Beyond that, I'm noticing a new problem that cropped up with the latest versions when you re-worked read mode. If I have two faders that are both controlling the same track in Reaper (for instance I might have a bank of faders that's auto-assigned based on what's visible in Reaper, but then another fader that always controls the selected track) and the track they're controlling is in read mode, moving one of those faders will cause the other fader to rapidly jump up and down as it tries to reconcile between the value of the moving fader and the value of the envelope it's reading from. This wouldn't bother me so much, but it's really loud and distracting when it happens and I also worry that it could be bad for the motor. This wasn't a problem in the old Eucon extension. It looks like the difference is, that in the old extension when a track is in read mode and I move the fader and watch the numbers on the scribble strip, the values in eucon change and don't return to their initial value until I let go. In CSI, when I do this the value on the scribble strip stays put even though the fader is moving. I'm guessing this is what causes the jumpy second fader. It seems like the approach from the old extension might be a better way of going about things, if possible. Here's another video I made demonstrating all of this (are these videos helpful? I can never tell if I'm doing a good enough job explaining this stuff in text as these issues feel kind of esoteric). https://www.youtube.com/watch?v=Ky0e...ature=youtu.be
|
Ok, so while I take a deeper look into the old extension to attempt to fix this (not quite sure if that's possible with the CSI architecture), I'll put the behaviour back to pre read mode fix in order to get rid of that annoying and possibly hardware detrimental chatter.
__________________
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-21-2020, 07:34 PM
|
#11651
|
Human being with feelings
Join Date: Mar 2011
Posts: 18
|
Quote:
Originally Posted by Funkybot
That might depend on if those virtual instruments expose their modwheel parameter to automation. CSI needs automation parameters to connect to. So if the plugin had a virtual modwheel on the GUI and that were an automatable parameter, sure, you could assign CSI to that.
|
I would mainly be using kontakt and it doesn't look like it allows host automation for the modwheel. I was hoping I could quickly move from control surface mode to working with midi without having to disable csi and enable the nano as a midi controller. Maybe I can find some kind of work around yet, thanks for now!
|
|
|
11-21-2020, 07:42 PM
|
#11652
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by dirtrider
I would mainly be using kontakt and it doesn't look like it allows host automation for the modwheel. I was hoping I could quickly move from control surface mode to working with midi without having to disable csi and enable the nano as a midi controller. Maybe I can find some kind of work around yet, thanks for now!
|
I feel your pain. It amazes me no one sells a small form factor modwheel, or a modwheel pitchwheel combo. I've got a System-8 as my primary controller and I hate the trigger/joystick thing. Would love a small desktop modwheel.
|
|
|
11-21-2020, 07:44 PM
|
#11653
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Geoff, here's one more.
Pretty esoteric little device, but if you have other former Cubase users, they may get some life out of this little old box. I have this setup mostly for sends and modifiers, and it's actually quite handy when combined with the X-Touch One which isn't good at sends or modifiers.
Last edited by Funkybot; 06-19-2021 at 11:22 AM.
|
|
|
11-21-2020, 07:51 PM
|
#11654
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by Funkybot
Found the issue with MCUTrackPan not working.
This works...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f
WidgetEnd
This doesn't...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f 90 20 00
WidgetEnd
...I forgot I was experimenting with adding the release messages a few days ago. Moral the story: don't add release messages to the toggle line.
|
Yes, that was designed for push only, as you have discovered , probably worth noting in the wiki, hint, hint
__________________
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-21-2020, 07:52 PM
|
#11655
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
New build is up.
CSI v1_0.zip
Added surfaces and zone files.
Backed out the EuCon read mode fix.
__________________
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-21-2020, 08:21 PM
|
#11656
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Geoff, it looks like CycleTrackAutoMode is no longer working. I just tried to add it to .zon with no luck.
Going off the example in the wiki:
Code:
Shift+RecordArm| TrackUniqueSelect
Shift+RecordArm| CycleTrackAutoMode [ 0 1 3 2 4 5 ]
...I'm getting nothing. Tried both with the TrackNavigator and SelectedTrackNavigator.
I honestly hadn't tried using it since the May builds so I'm not sure if it ever worked post-refactoring.
|
|
|
11-21-2020, 11:15 PM
|
#11657
|
Human being with feelings
Join Date: Nov 2018
Posts: 17
|
Icon Platform Nano
Quote:
Originally Posted by Geoff Waddington
New build is up.
CSI v1_0.zip
Added surfaces and zone files.
Backed out the EuCon read mode fix.
|
Hey Geoff, thanks a bunch for all your work.
Tested and working with my Icon Platform Nano 1.14.
I'm sharing my .mst and .zon files in case there are some other nano users who will find them handy.
EDIT: I've even included some basic instructions on how to set up the Nano with CSI for those starting out.
Might save somebody a day (ahem... DAYS) of trial and error :P
Download link:
https://e.pcloud.link/publink/show?c...jhj9kIlzA6RRik
Cheers!
__________________
IconPlatformNano v1.1 - tested with CSI 1.0, nano firmware v1.14
Download here: http://e.pc.cd/NWhotalK
Last edited by Mistik; 11-22-2020 at 12:13 AM.
|
|
|
11-22-2020, 01:28 AM
|
#11658
|
Human being with feelings
Join Date: May 2019
Posts: 38
|
Hi Guys!
I have learned a lot about this CSI thing in a couple of days and I have made some good progress programming my Icon QCon Pro X. Thanks for all your help with my previous post!
However, now my problem is that I can't separate the "Hold" action from the "Press" action.. Meaning that when I hold a button, it will still do the press action. I want my Rotary Push to reset Pan in the center when I push it, and Go to "Width" Zone when I hold.. But now it will still reset my Pan when I hold it.
I have assigned release data for my RotaryPush Widgets but still can't get it to work.
Here is my RotaryPush surface example:
Widget RotaryPush1
Press 90 20 7f 90 20 00
WidgetEnd
Here is My Zone example:
Zone "Pan"
TrackNavigator
DisplayLower| TrackPanDisplay
Rotary| TrackPan "1"
Hold+RotaryPush| GoZone PanWidth
RotaryPush| TrackUniqueSelect
RotaryPush| Reaper _XENAKIOS_PANTRACKSCENTER
Fader| TrackVolume
FaderTouch+Fader| GoZone Channel
Blank1 GoZone "Channel"
ZoneEnd
Also, how can I make my Pro XS Extender to follow better my actions in main unit? Example: When I use a rotary knob in my main unit, it will go to "Pan" Zone and change the lower display from volume to pan but it will do it only in my main unit and not in the extender. How can I make them follow each other?
|
|
|
11-22-2020, 01:35 AM
|
#11659
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
Are you using OnFXFocus or the FXMenu?
|
Hi, I use onFXFocus in the .zones
Code:
OnTrackSelection MapSelectedTrackSendsToWidgets
OnFXFocus MapFocusedFXToWidgets
and
Code:
Zone "VST: ReaVerb (Cockos)" ReaVerb
FocusedFXNavigator
in the fx.zones
Edit: meanwhile I tried SelecteTackNavigator in FX zones with MapSelectedTrackFXToWidgets but didn´t work.
Last edited by WaveTrans; 11-22-2020 at 05:53 AM.
|
|
|
11-22-2020, 04:11 AM
|
#11660
|
Human being with feelings
Join Date: Nov 2020
Location: Canary Islands
Posts: 1
|
Control Focused FX Without FX Zones
Hello All !!! First of all, Sorry for my English; and thanks to Geoff and all of you for your work !!
I`ve been messing around with CSI for a week now, maybe there`s already a solution for what I`m trying to do, but i`m unable to find anything,... this thread is soooooo complex at the moment.
My goal is getting to control the FX I select from the insert slots with a different approach that the FXZone Files.
I have a Behringer X-Touch and Trying to map the focused FX Parameters to the 8 Encoders and Faders in the surface without having a specific FXZone File; Displaying in the upper and lower scribbled strips the ParamNames that reaper gives.
At the momment It works for the first FX of the chain, but when i change to the other ones, nothing happens. If I change to other tracks it works nicely; but again, only with the first FX on the chain. As you can see avobe i tryed the ToggleMapFocusedFX feature,... but it doesn´t make a difference...
just a summary of my code with the relative parts. I promise, I´ll upload my whole code when it´s finished, an with comments so everybody understands what i´m doing...
Very bad with these programming stuff; but i Think I´ve got some cool stuff couldnñt find anywhere... (Flip function, display changing when touching a fader or moving a knob,...)
Thanks in advance for your help !!!
[code]
Zone Home
IncludedZones
"Buttons"
IncludedZonesEnd
ZoneEnd
Zone "Buttons"
Inst GoZone "SelectedFX"
ZoneEnd
Zone "SelectedFX"
OnFXFocus MapFocusedTrackFXToWidgets
FocusedFXNavigator
DisplayUpper1 FXParamNameDisplay 0
DisplayUpper2 FXParamNameDisplay 1
DisplayUpper3 FXParamNameDisplay 2
DisplayUpper4 FXParamNameDisplay 3
DisplayUpper5 FXParamNameDisplay 4
DisplayUpper6 FXParamNameDisplay 5
DisplayUpper7 FXParamNameDisplay 6
DisplayUpper8 FXParamNameDisplay 7
DisplayLower1 FXParamNameDisplay 8
DisplayLower2 FXParamNameDisplay 9
DisplayLower3 FXParamNameDisplay 10
DisplayLower4 FXParamNameDisplay 11
DisplayLower5 FXParamNameDisplay 12
DisplayLower6 FXParamNameDisplay 13
DisplayLower7 FXParamNameDisplay 14
DisplayLower8 FXParamNameDisplay 15
Rotary1 FXParam 0
Rotary2 FXParam 1
Rotary3 FXParam 2
Rotary4 FXParam 3
Rotary5 FXParam 4
Rotary6 FXParam 5
Rotary7 FXParam 6
Rotary8 FXParam 7
Fader1 FXParam 8
Fader2 FXParam 9
Fader3 FXParam 10
Fader4 FXParam 11
Fader5 FXParam 12
Fader6 FXParam 13
Fader7 FXParam 14
Fader8 FXParam 15
F8 ToggleMapFocusedFX
Inst GoZone "Home"
ZoneEnd
[code/]
|
|
|
11-22-2020, 04:33 AM
|
#11661
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by Funkybot
Have you tried this?
Code:
Zone "Buttons"
Send MapSelectedTrackSendsToWidgets
Plugin MapSelectedTrackFXToMenu
ZoneEnd
Zone "Send"
SendNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Fader| TrackSendVolume
ZoneEnd
Zone "FXMenu"
FXMenuNavigator
DisplayUpper| FXMenuNameDisplay
DisplayLower| NoAction
Rotary| NoAction
RotaryPush| GoFXSlot
ZoneEnd
I don't have an 8-channel MCU device (well, I could use my Artist Mix that way, but stick to Eucon) but that's what I got from checking out the included mcu.zon which isn't final. Eventually we'll get more updated .zon's out there.
|
In previous versions of CSI ticking "Sync Zones Across Surfaces" and "Auto Map Focuse FX" to make both surfaces work together, now it is 1 channel 0 Sends/FX for the nano and 8 channels/all for the Xplus.
This sorted I tested all variations I could think of using virtual modifiers and button calls of all kinds of actions from the MapSends and MapFx sortiment. Nothing works. Got a few nast chrashes while testing.
So I tried the MCU files coming with the newest build, buttons respond but no mapping sends nor FX.
Don´t know what to do now.
|
|
|
11-22-2020, 05:40 AM
|
#11662
|
Human being with feelings
Join Date: Mar 2011
Posts: 18
|
Quote:
Originally Posted by Mistik
Hey Geoff, thanks a bunch for all your work.
Tested and working with my Icon Platform Nano 1.14.
I'm sharing my .mst and .zon files in case there are some other nano users who will find them handy.
EDIT: I've even included some basic instructions on how to set up the Nano with CSI for those starting out.
Might save somebody a day (ahem... DAYS) of trial and error :P
Download link:
https://e.pcloud.link/publink/show?c...jhj9kIlzA6RRik
Cheers!
|
Thanks so much for doing that! I ordered a Nano which will hopefully arrive on Wednesday, so this will be very helpful to get me started.
|
|
|
11-22-2020, 07:40 AM
|
#11663
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,836
|
Quote:
Originally Posted by Funkybot
Found the issue with MCUTrackPan not working.
This works...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f
WidgetEnd
This doesn't...
Code:
Widget Rotary1
Encoder b0 10 7f [ < 41-48 > 01-08 ]
FB_Encoder b0 10 7f
Toggle 90 20 7f 90 20 00
WidgetEnd
...I forgot I was experimenting with adding the release messages a few days ago. Moral the story: don't add release messages to the toggle line.
|
Wow, totally missed this one. When did the composite Rotary/Toggle thing come along? I still have Rotary and RotaryPush
|
|
|
11-22-2020, 07:46 AM
|
#11664
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by dirtrider
I would mainly be using kontakt and it doesn't look like it allows host automation for the modwheel. I was hoping I could quickly move from control surface mode to working with midi without having to disable csi and enable the nano as a midi controller. Maybe I can find some kind of work around yet, thanks for now!
|
So kontakt may not do that, but a plugin like this would:
https://www.pluginguru.com/products/modmate/
It's free.
I'm fairly sure you could just insert that before kontakt and use csi to control that.
There maybe plugins within Reaper that do the same thing. Reacontrolmidi may work (there's cc stuff at the bottom of the plugin) or there maybe JS midi plugins as well. You can map JS plugins to csi but it usually requires you to input the range manually (not sure if that's in the wiki and I don't want to guess here, so if you need that, or someone else does, just quote me and I'll respond when I can look at my zones)
|
|
|
11-22-2020, 07:53 AM
|
#11665
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,836
|
Quote:
Originally Posted by WaveTrans
Hi, I use onFXFocus in the .zones
Code:
OnTrackSelection MapSelectedTrackSendsToWidgets
OnFXFocus MapFocusedFXToWidgets
and
Code:
Zone "VST: ReaVerb (Cockos)" ReaVerb
FocusedFXNavigator
in the fx.zones
Edit: meanwhile I tried SelecteTackNavigator in FX zones with MapSelectedTrackFXToWidgets but didn´t work.
|
Ok, thanks. This guy has a working setup for the nano, maybe try that.
Do you use the X+ to map regular channels or does it map sends and FX when you select a track/focus an FX?
|
|
|
11-22-2020, 07:58 AM
|
#11666
|
Human being with feelings
Join Date: Oct 2012
Posts: 57
|
Hello Funkybot,
(Sorry I don't know how to sleekly format my forum posts. I put your writing in quotes and then responded to each item.)
I went into my Zone file, cleared it and pasted the exact code you suggested. I then restarted/rescanned control/osc. No response.
"If not, what does the UpperButton look like in the BCR.mst? MixMonkey knows way more about CSI than I do, so I wouldn't normally dare question an .mst or .zon file he created, but it's very possible that the BCR template is very old and the button syntax changed since. Otherwise, I've never seen buttons like in that particular .mst."
UpperBotton in my MST reads as such (see attachment below):
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
"So I'd then suggest opening up the .mst file and change this...
Code:
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
and make it look like this...
Code:
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
"
I then went to my MST file, deleted what read as
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
and pasted:
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
rescanned, but still no response...
Another things worth noting is I keep on getting what seems to be an error message whenever I rescan CSI. I attached the photo below. Also attached is a snapshot to show you what the MST file I downloaded looks like.
Thank you!
|
|
|
11-22-2020, 08:19 AM
|
#11667
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by MixMonkey
Wow, totally missed this one. When did the composite Rotary/Toggle thing come along? I still have Rotary and RotaryPush
|
This is in addition to RotaryPush. So keep those. This was added with MCUTrackPan to make it work with Pan, PanWidth, but also PanL, and PanR respectively.
|
|
|
11-22-2020, 08:25 AM
|
#11668
|
Human being with feelings
Join Date: Nov 2018
Posts: 17
|
Quote:
Originally Posted by dirtrider
Thanks so much for doing that! I ordered a Nano which will hopefully arrive on Wednesday, so this will be very helpful to get me started.
|
Good to hear!
Let me know if you have any questions.
Cheers
__________________
IconPlatformNano v1.1 - tested with CSI 1.0, nano firmware v1.14
Download here: http://e.pc.cd/NWhotalK
|
|
|
11-22-2020, 08:51 AM
|
#11669
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by Weston Minissali
Hello Funkybot,
(Sorry I don't know how to sleekly format my forum posts. I put your writing in quotes and then responded to each item.)
I went into my Zone file, cleared it and pasted the exact code you suggested. I then restarted/rescanned control/osc. No response.
"If not, what does the UpperButton look like in the BCR.mst? MixMonkey knows way more about CSI than I do, so I wouldn't normally dare question an .mst or .zon file he created, but it's very possible that the BCR template is very old and the button syntax changed since. Otherwise, I've never seen buttons like in that particular .mst."
UpperBotton in my MST reads as such (see attachment below):
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
"So I'd then suggest opening up the .mst file and change this...
Code:
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
and make it look like this...
Code:
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
"
I then went to my MST file, deleted what read as
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
and pasted:
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
rescanned, but still no response...
Another things worth noting is I keep on getting what seems to be an error message whenever I rescan CSI. I attached the photo below. Also attached is a snapshot to show you what the MST file I downloaded looks like.
Thank you!
|
Honestly, based on those errors, tt looks like your .zon folder is a bit of a mess. Delete everything in your .zon folder except for your BCR2000.zon, and make the BCR2000.zon look like this:
Code:
Zone Home
IncludedZones
"Buttons"
IncludedZonesEnd
ZoneEnd
Zone "Buttons"
UpperButton1 Play
UpperButton2 Stop
UpperButton3 Reaper 40364 //Toggle Metronome
ZoneEnd
...nothing else.
Next, comes the tedious part. Your .mst is so old the syntax will no longer work with CSI. But you need the press/fader addresses. You may want to start from scratch or clean up your existing .mst, up to you. But anyway, from your current .mst file you'll have to make each of these...
Code:
RotaryPushG11 Press 90 00 7f
...
RotaryG11 Fader7BitFB b0 01 7f b0 01 00
...
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
...
...look like these:
Code:
Widget RotaryPushG11
Press 90 00 7f 90 00 00
WidgetEnd
Widget RotaryG11
Fader7bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
You have to do that for each line in the .mst. Make sure you carry over the exact address from the original .mst but use the format above. Save your new file as BCR2000.mst.
You'll notice I added the release messages to the Press widgets. I'm assuming the BCR2000 transmits release messages. If you don't know what the release message is, look at UpperButton1: 90 20 7f is the press of the button, 90 20 00 is the release of the button. If you load up a MIDI monitor (CSI has one, you can use others), press the button. If you see the 90 20 00 message, then you should define that in the .mst like I did in the examples above.
You'll also notice that the Rotary widgets also include an extra line for "Toggle" followed immediately by the RotaryPush address data (with no release message). That's needed for MCUTrackPan. If you're not going to use these rotaries as Pans, then skip the "toggle" line.
I'd also probably go in order (start with widget A1 then work up from there) just to make it cleaner.
If you want to do 3 or 4 widgets then zip up and post the content here (both .mst and .zon), I can double check and let you know if you're on the right track.
Also to create quotes and code in the forum do this:
[squote]
Text you're quoting
[/squote]
[bode]
Your code.
[/bode]
But replace the words "squote" and "bode" with quote and code respectively.
Last edited by Funkybot; 11-22-2020 at 09:00 AM.
|
|
|
11-22-2020, 09:02 AM
|
#11670
|
Human being with feelings
Join Date: Mar 2011
Posts: 18
|
Quote:
Originally Posted by cjewellstudios
So kontakt may not do that, but a plugin like this would:
https://www.pluginguru.com/products/modmate/
It's free.
I'm fairly sure you could just insert that before kontakt and use csi to control that.
There maybe plugins within Reaper that do the same thing. Reacontrolmidi may work (there's cc stuff at the bottom of the plugin) or there maybe JS midi plugins as well. You can map JS plugins to csi but it usually requires you to input the range manually (not sure if that's in the wiki and I don't want to guess here, so if you need that, or someone else does, just quote me and I'll respond when I can look at my zones)
|
Thanks! I tried Reamidicontrol and it looks like it will work. I may have to pick your brain a bit more, once I start setting up my zones.
|
|
|
11-22-2020, 09:13 AM
|
#11671
|
Human being with feelings
Join Date: Oct 2012
Posts: 57
|
Quote:
Originally Posted by Funkybot
Honestly, based on those errors, tt looks like your .zon folder is a bit of a mess. Delete everything in your .zon folder except for your BCR2000.zon, and make the BCR2000.zon look like this:
Code:
Zone Home
IncludedZones
"Buttons"
IncludedZonesEnd
ZoneEnd
Zone "Buttons"
UpperButton1 Play
UpperButton2 Stop
UpperButton3 Reaper 40364 //Toggle Metronome
ZoneEnd
...nothing else.
Next, comes the tedious part. Your .mst is so old the syntax will no longer work with CSI. But you need the press/fader addresses. You may want to start from scratch or clean up your existing .mst, up to you. But anyway, from your current .mst file you'll have to make each of these...
Code:
RotaryPushG11 Press 90 00 7f
...
RotaryG11 Fader7BitFB b0 01 7f b0 01 00
...
UpperButton1 PressReleaseFB 90 20 7f 90 20 00
...
...look like these:
Code:
Widget RotaryPushG11
Press 90 00 7f 90 00 00
WidgetEnd
Widget RotaryG11
Fader7bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
You have to do that for each line in the .mst. Make sure you carry over the exact address from the original .mst but use the format above. Save your new file as BCR2000.mst.
You'll notice I added the release messages to the Press widgets. I'm assuming the BCR2000 transmits release messages. If you don't know what the release message is, look at UpperButton1: 90 20 7f is the press of the button, 90 20 00 is the release of the button. If you load up a MIDI monitor (CSI has one, you can use others), press the button. If you see the 90 20 00 message, then you should define that in the .mst like I did in the examples above.
You'll also notice that the Rotary widgets also include an extra line for "Toggle" followed immediately by the RotaryPush address data (with no release message). That's needed for MCUTrackPan. If you're not going to use these rotaries as Pans, then skip the "toggle" line.
I'd also probably go in order (start with widget A1 then work up from there) just to make it cleaner.
If you want to do 3 or 4 widgets then zip up and post the content here (both .mst and .zon), I can double check and let you know if you're on the right track.
Also to create quotes and code in the forum do this:
[squote]
Text you're quoting
[/squote]
[bode]
Your code.
[/bode]
But replace the words "squote" and "bode" with quote and code respectively.
|
Okay thanks so much for the breakdown. I'll get working on this now and will be in touch ASAP.
|
|
|
11-22-2020, 10:09 AM
|
#11672
|
Human being with feelings
Join Date: Oct 2012
Posts: 57
|
The top Rotaries on the BCR (which also have a push function) I will be using for Pans. Do you I input the following for every rotary verbatim?
or is there a changing value from one rotary to the next ?
This is what I've input into my new mst, all look good?
Code:
Widget RotaryG11
Fader7Bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
Widget RotaryG12
Fader7Bit b0 02 7f
FB_Fader7Bit b0 02 7f
Toggle 90 00 7f
WidgetEnd
Widget RotaryG13
Fader7Bit b0 03 7f
FB_Fader7Bit b0 03 7f
Toggle 90 00 7F
WidgetEnd
Widget RotaryG14
Fader7Bit b0 04 7f
FB_Fader7Bit b0 04 07f
Toggle 90 00 7f
WidgetEnd
Thanks
-w
Last edited by Weston Minissali; 11-22-2020 at 10:17 AM.
|
|
|
11-22-2020, 10:14 AM
|
#11673
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
Quote:
Originally Posted by Funkybot
Geoff, it looks like CycleTrackAutoMode is no longer working. I just tried to add it to .zon with no luck.
Going off the example in the wiki:
Code:
Shift+RecordArm| TrackUniqueSelect
Shift+RecordArm| CycleTrackAutoMode [ 0 1 3 2 4 5 ]
...I'm getting nothing. Tried both with the TrackNavigator and SelectedTrackNavigator.
I honestly hadn't tried using it since the May builds so I'm not sure if it ever worked post-refactoring.
|
Yup, see next post
__________________
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-22-2020, 10:16 AM
|
#11674
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,151
|
New builds are up.
CSI v1_0.zip
reaper_csurf_EuCon.zip
CycleTrackAutoMode is back, and better, it used to work only for SelectedTrack, now it gets context from Navigator.
TrackAutoMode is also improved, it used to work only for SelectedTrack, now it gets context from Navigator.
EuCon users please note that EuConCycleTrackAutoMode, is gone, CycleTrackAutoMode takes its place, so make sure to get the latest EuCon.zon file.
__________________
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-22-2020, 10:22 AM
|
#11675
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Nice! Will check out the new automation cycle mode later today.
Added a page on the Wiki to cover the MCUTrackPan and MCUTrackPanDisplay actions:
https://github.com/GeoffAWaddington/...ki/MCUTrackPan
|
|
|
11-22-2020, 11:46 AM
|
#11676
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by Weston Minissali
The top Rotaries on the BCR (which also have a push function) I will be using for Pans. Do you I input the following for every rotary verbatim?
or is there a changing value from one rotary to the next ?
This is what I've input into my new mst, all look good?
Code:
Widget RotaryG11
Fader7Bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
Widget RotaryG12
Fader7Bit b0 02 7f
FB_Fader7Bit b0 02 7f
Toggle 90 00 7f
WidgetEnd
Widget RotaryG13
Fader7Bit b0 03 7f
FB_Fader7Bit b0 03 7f
Toggle 90 00 7F
WidgetEnd
Widget RotaryG14
Fader7Bit b0 04 7f
FB_Fader7Bit b0 04 07f
Toggle 90 00 7f
WidgetEnd
Thanks
-w
|
If you will be using those rotaries for pan then yes. That looks good.
For maximum flexibility, you'll still want to also keep the RotaryPush widgets for use in FX maps, so you'd also want to have...
Code:
Widget RotaryPushG11
Press 90 00 7f 90 00 00
WidgetEnd
So for each Rotary, you may end up with both...
Code:
Widget RotaryG11
Fader7Bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
Widget RotaryPushG11
Press 90 00 7f 90 00 00
WidgetEnd
Hope that makes sense.
Quesiton, does the BCR allow for endless rotary encoders? Or are they just straight up continuous knobs?
|
|
|
11-22-2020, 12:00 PM
|
#11677
|
Human being with feelings
Join Date: Oct 2012
Posts: 57
|
@Funkybot
Quote:
Quesiton, does the BCR allow for endless rotary encoders? Or are they just straight up continuous knobs?
|
By endless are you asking if they continually rotate with not fixed low or high value? If so, yes they are endless encoders.
I just got your last response so I might have to tweak the rotary/push encoders but at this point here is a summary of where my MST file is at. Instead of pasting every last thing, I used ... to skip some. Just want to include enough to give you a good picture.
Here's my MST as of now:
Code:
Widget RotaryG11
Fader7Bit b0 01 7f
FB_Fader7bit b0 01 7f
Toggle 90 00 7f
WidgetEnd
...
Widget RotaryG18
Fader7Bit b0 08 7f
FB_Fader7Bit b0 08 7f
Toggle 90 00 7f
WidgetEnd
/
Widget RotaryG21
Fader7Bit b0 09 7f
FB_Fader7Bit b0 09 7f
Toggle 90 00 7f
WidgetEnd
...
Widget RotaryG48
Fader7Bit b0 20 7f
FB_Fader7Bit b0 20 7f
Toggle 90 00 7f
WidgetEnd
Code:
Widget RotaryPushG11
Press 90 00 7f 90 00 00
WidgetEnd
...
Widget RotaryPushG48
Press 90 1f 7f 90 00 00
WidgetEnd
Code:
Widget UpperButton1
Press 90 20 7f 90 20 00
FB_TwoState 90 20 7f 90 20 00
WidgetEnd
...
Widget LowerButton8
Press 90 2f 7f 90 2f 00
FB_TwoState 90 2f 7f 90 2f 00
WidgetEnd
Code:
Widget RotaryA1
Fader7bit b0 21 7f
FB_Fader7bit b0 21 7f
WidgetEnd
Widget RotaryC8
Fader7bit b0 38 7f
FB_Fader7bit b0 38 7f
WidgetEnd
Code:
Widget UserButton1
Press 90 30 7f 90 30 00
FB_TwoState 90 30 7f 90 30 00
WidgetEnd
...
Widget UserButton4
Press 90 33 7f 90 33 00
FB_TwoState 90 33 7f 90 33 00
WidgetEnd
Here are a few example of what I'd like to achieve in my zon file.
UserButton1- Play
UserButton2- Stop
UserButton4- Record
RotaryG11- Pan track 1
UpperButton- Solo Track 1
BottomButton- Mute Track 1
RotaryA1- Track 1 Volume
What would a zon file look like to achieve these parameters?
Really appreciate you walking me through this
|
|
|
11-22-2020, 12:02 PM
|
#11678
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Geoff, not sure if this is a bug or by design but...
If I setup my X-Touch One with 1 Fader and SelectedTrackNavigator, that 1 fader "steals" track 1 from my 8 fader Artist Mix. So the Artist Mix will always begin on Track 2 as though the X-Touch One is using the TrackNavigator and not the SelectedTrackNavigator.
So when I setup my X-Touch One with SelectedTrackNavigator in CSI, to avoid any unwanted stealing, I have to setup the X-Touch One with 0 faders, which is unintuitive. It's like as soon as you say "1 Fader" in the setup, it kind of assumes your using TrackNavigator and kind of ignores the SelectedTrackNavigator.
For reference, my channel zone looks like this:
Code:
Zone "SelectedChannel"
SelectedTrackNavigator
DisplayUpper1 TrackNameDisplay
DisplayLower1 MCUTrackPanDisplay
Fader1 TrackVolume
RotaryPush1 NoAction
Rotary1 MCUTrackPan
ZoneEnd
...like I said, it's no biggie. You just have to know to set it up as 0 faders, which works as expected, but I think that could be confusing to new users.
|
|
|
11-22-2020, 12:11 PM
|
#11679
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by Weston Minissali
@Funkybot
Here are a few example of what I'd like to achieve in my zon file.
UserButton1- Play
UserButton2- Stop
UserButton4- Record
RotaryG11- Pan track 1
UpperButton- Solo Track 1
BottomButton- Mute Track 1
RotaryA1- Track 1 Volume
What would a zon file look like to achieve these parameters?
Really appreciate you walking me through this
|
Sure! Here you go...
Code:
Zone Home
IncludedZones
"Buttons"
"Channel"
IncludedZonesEnd
ZoneEnd
Zone "Buttons"
UserButton1 Play
UserButton2 Stop
UserButton4 Recodrd
ZoneEnd
Zone "Channel"
TrackNavigator
RotaryG| MCUTrackPan
UpperButton| TrackSolo
BottomButton| TrackMute
RotaryA| TrackVolume
ZoneEnd
Now...one thing to keep in mind, when combined with TrackNavigator those pipes act like variables for channel number. So you don't need to write A1 TrackVolume1, A2 TrackVolume2...this is much cleaner. So let's say you you want to create 8 faders, 8 pans, 8 solos, 8 mutes...to do that you'll need widgets for:
RotaryG1 thru RotaryG8
UpperButton1 thru UpperButton8
BottomButton1 thru BottomButton8
RotaryA1 thru RotaryA8
...and in CSI's preferences, when you add the device, you'll set it up for 8 faders. In the zone file, the | character replaces the widget numbers.
And for this to work just don't do anything weird like create RotaryA1 to A4 along the first half of the bottom row and RotaryB1 to B4 on the second half of the bottom row. You'd want to make those A1 to A8 if you want all of them to act as faders. Hope that makes sense.
Last edited by Funkybot; 11-22-2020 at 12:19 PM.
|
|
|
11-22-2020, 12:17 PM
|
#11680
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
|
Quote:
Originally Posted by Geoff Waddington
CycleTrackAutoMode is back, and better, it used to work only for SelectedTrack, now it gets context from Navigator.
TrackAutoMode is also improved, it used to work only for SelectedTrack, now it gets context from Navigator.
|
Only tested CycleTrackAutoMode but it worked great on both MIDI and Eucon surfaces.
|
|
|
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 06:13 AM.
|