|
|
|
02-24-2021, 11:33 AM
|
#761
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by Geoff Waddington
As stated, we decided to concentrate on getting Touch automation to function properly, which precluded other uses of the fader touch feature.
|
What exactly was the conflict between the two?
|
|
|
02-24-2021, 05:36 PM
|
#762
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by DeBased
OK cool, won't have time immediately but will have a go soon. So as far as we know, colour scribble strips require implementing CTRL mode right? And CTRL is essentially MIDI wrapped in its own protocol?
|
Don't know anything about CTRL mode, but once again the CSI source might help, there are some pretty weird midi widget colour implementations in there
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
02-24-2021, 05:42 PM
|
#763
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by DeBased
What exactly was the conflict between the two?
|
If you look at control_surface_Reaper_actions.h around line 157 in the TrackVolume action you will see that, in addition to setting the touched state, it does some volume manipulation -- this is necessary because of Reaper design, it needs a set point before it starts writing automation.
I think there could be some pretty weird side effects if you start using touch for other purposes.
However, if you don't use touch automation, you could simply change the .mst file accordingly and use the touch feature separately as a switch, up to you...
__________________
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
|
|
|
02-25-2021, 01:37 AM
|
#764
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by Geoff Waddington
If you look at control_surface_Reaper_actions.h around line 157 in the TrackVolume action you will see that, in addition to setting the touched state, it does some volume manipulation -- this is necessary because of Reaper design, it needs a set point before it starts writing automation.
I think there could be some pretty weird side effects if you start using touch for other purposes.
However, if you don't use touch automation, you could simply change the .mst file accordingly and use the touch feature separately as a switch, up to you...
|
Thanks, I'll check it out. BTW I should have said 'XCtrl', not CTRL (that's the mode for custom MIDI messages).
I have the basic scribble colour/text message from full RGB working (but not implemented anything CSI specific yet):
It seems (TBC) that the Xctrl messages (including the scribble msg) are only received via the DIN MIDI in port, not the USB port. However according to the reverse-engineering doc by FK, the hybrid Xctrl/MC or Xctrl/HUI modes split some controls into each camp, so they can be accessed both via USB (MC/HUI) and Xctrl (DIN MIDI) respectively.
Last edited by DeBased; 02-25-2021 at 01:44 AM.
|
|
|
02-25-2021, 10:28 AM
|
#765
|
Human being with feelings
Join Date: Jun 2012
Posts: 277
|
Does CSI have MIDI machine code support? Asking just about actions, not some position or stuff like they
|
|
|
02-25-2021, 11:31 AM
|
#766
|
Human being with feelings
Join Date: Jun 2012
Posts: 277
|
Alesis HD24 as control surface
The Alesis HD24 sends and receives Midi Machine Code and Sysex. Are these supported? I tried to set it up but the MMC messages aren't consistent, and when I assign f0 7f 7f to play, that message occurs multiple times while the HD24 is playing, and messes everything up for me.
Here's the input from the surface when I (very quickly) press play and then stop.
Sample one:
Code:
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 05 00
IN <- Alesis HD24 f1 10 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 20 00
IN <- Alesis HD24 f1 30 00
IN <- Alesis HD24 f1 40 00
IN <- Alesis HD24 f1 50 00
IN <- Alesis HD24 f1 60 00
IN <- Alesis HD24 f1 76 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 07 00
IN <- Alesis HD24 f1 10 00
And here's the second time:
Code:
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 08 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 11 00
IN <- Alesis HD24 f1 25 00
IN <- Alesis HD24 f1 30 00
IN <- Alesis HD24 f1 40 00
IN <- Alesis HD24 f1 50 00
IN <- Alesis HD24 f1 60 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 76 00
IN <- Alesis HD24 f1 0a 00
IN <- Alesis HD24 f1 11 00
Any way to make a play and stop widget to deal with that mess? Or is it a lost cause?
|
|
|
02-26-2021, 06:15 AM
|
#767
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,184
|
Quote:
Originally Posted by buddhajuke
The Alesis HD24 sends and receives Midi Machine Code and Sysex. Are these supported? I tried to set it up but the MMC messages aren't consistent, and when I assign f0 7f 7f to play, that message occurs multiple times while the HD24 is playing, and messes everything up for me.
Here's the input from the surface when I (very quickly) press play and then stop.
Sample one:
Code:
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 05 00
IN <- Alesis HD24 f1 10 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 20 00
IN <- Alesis HD24 f1 30 00
IN <- Alesis HD24 f1 40 00
IN <- Alesis HD24 f1 50 00
IN <- Alesis HD24 f1 60 00
IN <- Alesis HD24 f1 76 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 07 00
IN <- Alesis HD24 f1 10 00
And here's the second time:
Code:
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 08 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 11 00
IN <- Alesis HD24 f1 25 00
IN <- Alesis HD24 f1 30 00
IN <- Alesis HD24 f1 40 00
IN <- Alesis HD24 f1 50 00
IN <- Alesis HD24 f1 60 00
IN <- Alesis HD24 f0 7f 7f
IN <- Alesis HD24 f1 76 00
IN <- Alesis HD24 f1 0a 00
IN <- Alesis HD24 f1 11 00
Any way to make a play and stop widget to deal with that mess? Or is it a lost cause?
|
The Reaper midi implementation allows for sending SysEx, but not receiving it, understandably, because it's a PITA to parse.
So it's a non starter for CSI or anything else, as far as I 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
|
|
|
02-26-2021, 10:48 AM
|
#768
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
I have track-coloured X-touch scribble strips working.
Watch it in action: https://www.dropbox.com/s/07oefj9icj0lpwb/demo.mp4?dl=0
If you're on Windows with an X-touch, try it: https://www.dropbox.com/s/ahqj40nn32...alpha.zip?dl=0
You'll need to use the included .mst file (or just add its new display type to your own, the rest is the same right now).
You also need to connect via the DIN MIDI in/out, and put your surface into "XCtrl" mode with "MIDI" (hold track Select #1 while powering up, then make changes with the two rotaries and press it again to save).
The catch is, while lots of stuff works as before (buttons, faders, LEDs, transport, jog wheel), some things need updating for XCtrl: Time display is broken, encoder feedback is messed up. Let me know what else.
This was tricky and I'm short on time, anybody else willing to pitch in for the rest?
Last edited by DeBased; 02-26-2021 at 11:10 AM.
|
|
|
02-27-2021, 02:34 PM
|
#769
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by Geoff Waddington
If you look at control_surface_Reaper_actions.h around line 157 in the TrackVolume action you will see that, in addition to setting the touched state, it does some volume manipulation -- this is necessary because of Reaper design, it needs a set point before it starts writing automation.
I think there could be some pretty weird side effects if you start using touch for other purposes.
|
could we allow touch track-selection if no track is in automation mode? that might be a usable workaround.
|
|
|
03-01-2021, 10:03 AM
|
#770
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by DeBased
could we allow touch track-selection if no track is in automation mode? that might be a usable workaround.
|
You could set up seperate CSI pages for this and have both. For example...
Setup a page and call it maybe "Fadertouch" and have the necessary mst and zone files to support Fadertouch
Then setup another page and call it maybe "TouchAutomation" and have the necessary mst and zone files to support Touch automation
Then just map a button on each page to go back n forth
Button1 GoPage Fadertouch
Button1 GoPage TouchAutomation
Or one of them can just be your Home page.which is how I'm doing it. Fadertouch is important for me as is the touch automation feature so I have this work around to have both. I just tried it and all seemed ok. But didnt get a chance yet to really test thoroughly to make sure nothing weird happens.
But anyway maybe this could work for you as well
|
|
|
03-01-2021, 05:36 PM
|
#771
|
Human being with feelings
Join Date: Jul 2009
Posts: 7,571
|
is there a shortcut to reloading .zon files or do you have to restart reaper?
|
|
|
03-01-2021, 05:41 PM
|
#772
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by EpicSounds
is there a shortcut to reloading .zon files or do you have to restart reaper?
|
Use Reaper's stock "Refresh All Surfaces" action.
|
|
|
03-02-2021, 05:58 AM
|
#773
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by Cragster
You could set up seperate CSI pages for this and have both. For example...
|
Cool, I haven't had much chance to explore CSI or the X-touch yet (still focused on programming my XCtrl mod) so haven't looked into what pages can do you, but that sounds great.
I actually just hacked in touch track selection to test, not realising you can already do it. How would you set this up in your .zon file?
|
|
|
03-02-2021, 11:05 AM
|
#774
|
Human being with feelings
Join Date: Jul 2009
Posts: 7,571
|
Quote:
Originally Posted by Funkybot
Use Reaper's stock "Refresh All Surfaces" action.
|
perfect thank you.
|
|
|
03-02-2021, 05:43 PM
|
#775
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by DeBased
Cool, I haven't had much chance to explore CSI or the X-touch yet (still focused on programming my XCtrl mod) so haven't looked into what pages can do you, but that sounds great.
I actually just hacked in touch track selection to test, not realising you can already do it. How would you set this up in your .zon file?
|
You would need this in your mst file (in addition to your Fader widgets)
Code:
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
Etc....
And this in your Channel Zone in the zone file
Code:
FaderTouch| TrackTouch
And this also is tied into the display. When the fader is touched it will give you alternate display.for example..
Code:
DisplayUpper| TrackNameDisplay
DisplayLower| TrackPanDisplay
TrackTouch+DisplayLower| TrackVolumeDisplay
But you would have to remove the current touch widget included with fader widget.(the current touch for automation). Cant have both in the same mst file which is why i suggested a seperate page. that will give you the ability to use 2 completely differnt mst and/or zone files. when your ready to do some automating you just switch over to that page
Last edited by Cragster; 03-02-2021 at 05:49 PM.
|
|
|
03-02-2021, 11:17 PM
|
#776
|
Human being with feelings
Join Date: Jan 2017
Posts: 252
|
button lights on MCU
Hi - When i made the vid about installing for mac,i was using the version from last May,- where the sends "toggled" on the send button. Geoff explained this caused issues so now two buttons for send state/global view - no problem.
I'm going to make another vid and thought i better use the latest version.
The issue i have on the MCU is: no light appears when i select the send button. I'm not familiar with how to get lights on buttons to work - the versions i used previously just lit up when selected (and assigned)
Any one able to help me get the button light back on please?
Many thanks
|
|
|
03-03-2021, 05:26 AM
|
#777
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by UNdark
Hi - When i made the vid about installing for mac,i was using the version from last May,- where the sends "toggled" on the send button. Geoff explained this caused issues so now two buttons for send state/global view - no problem.
I'm going to make another vid and thought i better use the latest version.
The issue i have on the MCU is: no light appears when i select the send button. I'm not familiar with how to get lights on buttons to work - the versions i used previously just lit up when selected (and assigned)
Any one able to help me get the button light back on please?
Many thanks
|
The FB_TwoState line in the mst is for lighting the buttons. But only if that action has an on/off state in reaper or csi I believe. Otherwise it will be random. Meaning the light will always be on or off.
So check to see if your send widget ( if that's what ur using) has the FB_TwoState
|
|
|
03-03-2021, 05:53 AM
|
#778
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by Cragster
The FB_TwoState line in the mst is for lighting the buttons. But only if that action has an on/off state in reaper or csi I believe. Otherwise it will be random. Meaning the light will always be on or off.
So check to see if your send widget ( if that's what ur using) has the FB_TwoState
|
I don't think it's random exactly.
I'm pretty sure the logic is, if it has a function tied to it in the current zone, then the light will be on. At least that's my experience. If it's not mapped or its mapped to NoAction then the light will be off.
|
|
|
03-03-2021, 05:59 AM
|
#779
|
Human being with feelings
Join Date: Apr 2019
Location: Inman, SC USA
Posts: 859
|
Quote:
Originally Posted by cjewellstudios
I don't think it's random exactly.
I'm pretty sure the logic is, if it has a function tied to it in the current zone, then the light will be on. At least that's my experience. If it's not mapped or its mapped to NoAction then the light will be off.
|
Thanks for the info. I really wasnt sure. I've tried the FB_TwoState on some things and it would either stay lit or not light at all. So I thought maybe it was random. Still learning myself with CSI
|
|
|
03-03-2021, 07:17 AM
|
#780
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by Cragster
You would need this in your mst file (in addition to your Fader widgets)
|
Thanks .
|
|
|
03-03-2021, 08:07 AM
|
#781
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by cjewellstudios
I don't think it's random exactly.
I'm pretty sure the logic is, if it has a function tied to it in the current zone, then the light will be on. At least that's my experience. If it's not mapped or its mapped to NoAction then the light will be off.
|
That may be the case, but I've got my Track Bank lights lit up and Channel Select lights off in one zone even though both are mapped. I think the type of action has something to do with it but never figured it out. I usually just comment out the feedback or ignore it.
|
|
|
03-03-2021, 12:45 PM
|
#782
|
Human being with feelings
Join Date: Jan 2017
Posts: 252
|
button lights on MCU
Thanks Cragster and Charlie.
I would prefer the toggle on the send button but i thought that wasn't the protocol with the present mcu mapping. I haven't change what the send assignment in the dowloaded zon file contained... just no light - no big problem - its's clear as day on the mcu track led, if it's tracks or sends, just wonderin..
Thanks for the replies
|
|
|
03-03-2021, 01:41 PM
|
#783
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by Funkybot
That may be the case, but I've got my Track Bank lights lit up and Channel Select lights off in one zone even though both are mapped. I think the type of action has something to do with it but never figured it out. I usually just comment out the feedback or ignore it.
|
I assume that's because track select has a toggle function and CSI shows you the toggle state. i.e. Track not selected = light off
If it doesn't have a toggle state, like bank for example, or any reaper action (except cycle actions that report the correct toggle ) I believe CSI lights up the button.
|
|
|
03-05-2021, 02:54 AM
|
#784
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
More OSC woes:
I'm trying Open Stage Control.
I have input to CSI:
Code:
IN <- openstagecontroltest /fader_1 0.360000
IN <- openstagecontroltest /fader_1 0.340000
IN <- openstagecontroltest /button_1 1.000000
IN <- openstagecontroltest /button_1 0.000000
But that's acting like it doesn't see the .ost or .zon files
Code:
Widget fader_1
FB_Processor /fader_1
WidgetEnd
Widget button_1
FB_Processor /button_1
WidgetEnd
Code:
Zone Home
OnFXFocus MapFocusedFXToWidgets
IncludedZones
"Channel"
"Buttons"
IncludedZonesEnd
ZoneEnd
Zone "Channel"
TrackNavigator
fader_| TrackVolume
ZoneEnd
Zone "Buttons"
button_1 Play
ZoneEnd
Open Stage control is infinitely more complicated than TouchOSC so there maybe something with the osc id/address I'm getting wrong. Not sure. There was also someone who tried Open Stage Control a while back and ran into some network issues. I don't seem to be having the trouble they are but I also haven't gotten as far yet.
Does anyone see any potential problems?
EDIT: It looks like I can specify a message type in the preArgs section in the editor. Maybe it has something to do with that I've left that blank at the moment.
Last edited by cjewellstudios; 03-05-2021 at 05:10 AM.
|
|
|
03-05-2021, 08:19 AM
|
#785
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by cjewellstudios
Open Stage control is infinitely more complicated than TouchOSC so there maybe something with the osc id/address I'm getting wrong. Not sure. There was also someone who tried Open Stage Control a while back and ran into some network issues. I don't seem to be having the trouble they are but I also haven't gotten as far yet.
|
What were the shortcomings with TouchOSC?
|
|
|
03-05-2021, 08:26 AM
|
#786
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by MixMonkey
What were the shortcomings with TouchOSC?
|
Intermittent connectivity. Also sometimes it connects but only some of the information makes it through. Extremely frustrating.
Havent had any success hardwiring either. iPad 2's are too old to be able to configure the ethernet settings like you can on your ipad pro and android devices usually need to be rooted to do the same thing.
With open stage control you run your own server and can access it from local host so with that in mind I'd be able to use a regular monitor as a 2nd monitor for my pc , and eventually a touchscreen monitor.
Running it on the same pc should mean I wont have intermittent connectivity.
I could also buy an ipad 4th gen and a new adapter. But open stage control is pretty sweet too so I was exploring that for a bit.
|
|
|
03-06-2021, 03:58 AM
|
#787
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
Hey guys,
I see that some of you are running the X Touch One (same as me) with the current version of CSI. I currently have a setup running very nicely with a previous version of CSI (before it was 1.x) but I noticed my custom configuration won't work if I update to the current version of CSI.
A couple of questions:
1) Is it just a question of simple changes in my configuration or am I better off starting from scratch? If the latter, would anyone (maybe Funkybot?) mind sharing their configuration with me so I can adjust it from there?
2) Are there any major benefits with the current CSI version over the previous beta/alpha versions?
I just assume it would be a good idea to adjust my configuration to the current format so it is future proof but I thought I'd check first.
Thanks a lot!
Last edited by susbemol; 03-06-2021 at 12:42 PM.
|
|
|
03-06-2021, 06:09 AM
|
#788
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by susbemol
Hey guys,
I see that some of you are running the X Touch One (same as me) with the current version of CSI. I currently have a setup running very nicely with a previous version of CSI (before it was 1.x) but I noticed my custom configuration won't work if I update to the current version of CSI.
A couple of questions:
1) Is it just a question of simple changes in my configuration or am I better off starting from scratch? If the later, would anyone (maybe Funkybot?) mind sharing their configuration with me so I can adjust it from there?
2) Are there any major benefits with the current CSI version over the previous beta/alpha versions?
I just assume it would be a good idea to adjust my configuration to the current format so it is future proof but I thought I'd check first.
Thanks a lot!
|
I assume Funkybot's configuration for the X-Touch One is in the CSI download.
There are a few changes since you last updated. Most of which are under the hood. In particular there were a few automation bugs that I think are taken care of now.
There is a succinct list of changes that I'm sure Funkybot will chime in with, but yeah definitely update and configure to your needs.
|
|
|
03-06-2021, 08:29 AM
|
#789
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
Thanks for the heads up. I found Funkybot's one in the config files download ( https://siniarch.wixsite.com/csiconfigfiles) but this says it was for the previous beta. I wonder if this was changed at all for the current version? @Funkybot
|
|
|
03-06-2021, 09:00 AM
|
#790
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by susbemol
Thanks for the heads up. I found Funkybot's one in the config files download ( https://siniarch.wixsite.com/csiconfigfiles) but this says it was for the previous beta. I wonder if this was changed at all for the current version? @Funkybot
|
The newer version is included with the stock CSI 1.0 download already. Check the files in the .zip file, they’re in there.
|
|
|
03-06-2021, 09:00 AM
|
#791
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
Quote:
Originally Posted by Funkybot
The newer version is included with the stock CSI 1.0 download already. Check the files in the .zip file, they’re in there.
|
Brilliant, thanks!
|
|
|
03-06-2021, 10:43 AM
|
#793
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Another great video Jon! I'm sure that's going to increase awareness about CSI.
|
|
|
03-06-2021, 12:42 PM
|
#794
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
So much great stuff here, thanks everyone!
I have been able to setup everything as I want, except for one element. Previously, when I pressed the CHANNEL SELECT < > buttons on my X Touch One, the track would also be selected, in other words "TrackUniqueSelect" would automatically be executed which no longer seems to be the case. Is there a way of making it behave this way again?
Last edited by susbemol; 03-06-2021 at 02:56 PM.
Reason: spelling
|
|
|
03-06-2021, 02:33 PM
|
#795
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
PLEASE SEND HELP lol
Open Stage Control looks amazing.
I was able to figure out my problem above. My .ost widgets did not specify Control, only feedback. (Whoops)
So fixing that I was able to get one way communication.
So far no matter what I've done I havent been able to get csi to send back to open stage control.
Can anyone take a look at the Open Stage control project and try and get two way communication and then tell me what the hell you did?! Lol
I'm pretty sure I have it set up where it should work but nothing so far. Any help would be immensely appreciated.
|
|
|
03-06-2021, 04:28 PM
|
#796
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by EpicSounds
|
Great Video Jon!
|
|
|
03-07-2021, 03:32 AM
|
#797
|
Human being with feelings
Join Date: Jan 2019
Location: Belgique Braine l'Alleud
Posts: 29
|
Hello to all.
Sorry for English, I don't speak it and use google translate.
I bought this surface and installed CSI but I'm not very good at setting it up.
I understood that this was happening in the .ZON file.
Can you help me with the configuration of the Jogwheel.
At the moment it just moves the window but I would like it to work in the basic intended way as moving the cursor with sound.
I would also like the F1 function keys .... to be used for automations but I don't know the Reaper #s.
In fact it would be good to have the same uses as what is originally intended by Behringer on the template.
Sorry if the topic has already been covered but I have already spent hours researching.
There are 2 ZON files for the X touch supplied with CSI which of the 2 is better used?
|
|
|
03-07-2021, 09:18 AM
|
#798
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Hi Jean-Pierre, I'm assuming you're talking about an X-Touch One since you mention the two sets of files. If yes, then read on...
Quote:
Originally Posted by Jean-Pierre
Can you help me with the configuration of the Jogwheel.
At the moment it just moves the window but I would like it to work in the basic intended way as moving the cursor with sound.
|
I don't think this is possible. There's no native Reaper action I'm aware of for audio scrubbing. If anyone knows a way to do it, please post here.
Quote:
Originally Posted by Jean-Pierre
I would also like the F1 function keys .... to be used for automations but I don't know the Reaper #s.
|
Open the Actions List in Reaper. Locate the action you are looking for, right click it, then select "Copy selected action Command ID." That copies the number to the clipboard. Then just paste that into the actions list.
Also, you can run the action: SWS/S&M: Dump action list (all actions). This puts an actions.txt file in your Reaper Resource path with all the actions and their ID #'s.
Quote:
Originally Posted by Jean-Pierre
In fact it would be good to have the same uses as what is originally intended by Behringer on the template.
|
Once you get the hang of modifying CSI, you can do this yourself. There are a lot of templates for the X-Touch One, and I didn't find the Reaper one best fit my workflow so I created a custom one. The one I actually use isn't the one in the CSI.zip, but I kept that one as close to the hardware itself to act as a starting point.
Quote:
Originally Posted by Jean-Pierre
There are 2 ZON files for the X touch supplied with CSI which of the 2 is better used?
|
One is designed to operate to map the selected track to the surface. The other is designed not to do that, where the selected fader on the surface can be different than the selected track in Reaper. Up to you to determine which workflow you prefer.
Good luck!
|
|
|
03-07-2021, 10:08 AM
|
#799
|
Human being with feelings
Join Date: Jan 2019
Location: Belgique Braine l'Alleud
Posts: 29
|
[QUOTE=Funkybot;2415213]Hi Jean-Pierre, I'm assuming you're talking about an X-Touch One since you mention the two sets of files. If yes, then read on...
I don't think this is possible. There's no native Reaper action I'm aware of for audio scrubbing. If anyone knows a way to do it, please post here.
I'm not sure why this works with a standard installation which doesn't follow tracks with a mouse click and it doesn't work with CSI
|
|
|
03-07-2021, 10:53 AM
|
#800
|
Human being with feelings
Join Date: Mar 2018
Location: Norfolk, UK
Posts: 350
|
After all this time, i've finally found a few hours today to get my head around CSI. And now i have, i love it! (Thanks to @epicsounds / Reaper Blog for covering it recently, which nudged me to give it another go).
I couldn't see any way of natively paging through parameters for a plugin, so i started devising a workaround.
As a test i've been working on a Korg NanoKontrol2 mapping, and i've found a way of creating pages of parameters for FX plugins, plus providing light feedback to the controller so i know which page i'm on.
I have only been reading the manual online and not really dived into user discussions yet, so if there's a better way - or infact a better way to set paging up i'm all ears.
Anyway, this is my .zon file for Steinberg Retrologue as an example:-
Code:
Zone "VST3i: Retrologue (Steinberg Media Technologies)"
FocusedFXNavigator
IncludedZones
"VST3i: Retrologue (Steinberg Media Technologies) RENDER"
IncludedZonesEnd
RecordArm1 Reaper ""
Rotary1 FXParam 65 "Filter Cutoff"
Rotary2 FXParam 66 "Filter Resonance"
Rotary3 FXParam 67 "Filter Distortion"
Rotary4 FXParam 68 "Filter Env Amount"
Rotary5 FXParam 69 "Filter Key Follow"
Fader1 FXParam 73 "DCA Attack"
Fader2 FXParam 74 "DCA Decay"
Fader3 FXParam 75 "DCA Sustain"
Fader4 FXParam 76 "DCA Release"
Fader5 FXParam 77 "DCF Attack"
Fader6 FXParam 78 "DCF Decay"
Fader7 FXParam 79 "DCF Sustain"
Fader8 FXParam 80 "DCF Release"
ZoneEnd
Zone "VST3i: Retrologue (Steinberg Media Technologies) RENDER"
Mute1 Reaper ""
Mute2 Reaper ""
Mute3 Reaper ""
RecordArm1 NoAction
RecordArm2 NoAction
RecordArm3 NoAction
RecordArm1 GoZone "VST3i: Retrologue (Steinberg Media Technologies)"
RecordArm2 GoZone "VST3i: Retrologue (Steinberg Media Technologies) P2"
RecordArm3 GoZone "VST3i: Retrologue (Steinberg Media Technologies) P3"
ZoneEnd
Zone "VST3i: Retrologue (Steinberg Media Technologies) P2"
IncludedZones
"VST3i: Retrologue (Steinberg Media Technologies) RENDER"
IncludedZonesEnd
RecordArm2 Reaper ""
Rotary1 FXParam 15 "Osc 1 Octave"
Rotary2 FXParam 16 "Osc 1 Coarse"
Rotary3 FXParam 17 "Osc 1 Fine"
Rotary4 FXParam 18 "Osc 1 Type"
Rotary5 FXParam 19 "Osc 1 Retrigger"
Rotary6 FXParam 20 "Osc 1 Phase"
Rotary7 FXParam 21 "Osc 1 Waveform"
Rotary8 FXParam 22 "Osc 1 Shape"
Fader1 FXParam 23 "Osc 1 Multi Detune"
Fader2 FXParam 24 "Osc 1 Multi Voices"
Fader3 FXParam 25 "Osc 1 Level"
Fader4 FXParam 26 "Osc 1 Enable"
ZoneEnd
Zone "VST3i: Retrologue (Steinberg Media Technologies) P3"
IncludedZones
"VST3i: Retrologue (Steinberg Media Technologies) RENDER"
IncludedZonesEnd
RecordArm3 Reaper ""
Rotary1 FXParam 27 "Osc 2 Octave"
Rotary2 FXParam 28 "Osc 2 Coarse"
Rotary3 FXParam 29 "Osc 2 Fine"
Rotary4 FXParam 30 "Osc 2 Type"
Rotary5 FXParam 31 "Osc 2 Retrigger"
Rotary6 FXParam 32 "Osc 2 Phase"
Rotary7 FXParam 33 "Osc 2 Waveform"
Rotary8 FXParam 34 "Osc 2 Shape"
Fader1 FXParam 35 "Osc 2 Multi Detune"
Fader2 FXParam 36 "Osc 2 Multi Voices"
Fader3 FXParam 37 "Osc 2 Level"
Fader4 FXParam 38 "Osc 2 Enable"
ZoneEnd
So to explain, the basic concept was to create Zones with prefixes as:-
RENDER = This renders the controller lights after each page turn/or on init
P1 = Page 1
P2 = Page 2 etc...
Basically 'RENDER' zone is called on each page selection. What it does is sets the Mute buttons to the page count (i.e. 3 pages, Mute1,Mute2, Mute3 are lit using 'Reaper ""'). And then the Record buttons are all unlit using NoAction. Then each page zone will relit the page currently selected.
So an example of a 3 page FX mapping, currently on page 2 would look like this on the controller:-
Code:
[M] [M] [M] [ ] [ ] [ ] [ ] [ ]
[ ] [R] [ ] [ ] [ ] [ ] [ ] [ ]
If you moved to page 3, like this:-
Code:
[M] [M] [M] [ ] [ ] [ ] [ ] [ ]
[ ] [ ] [R] [ ] [ ] [ ] [ ] [ ]
Within the 'RENDER' zone i can setup number of pages, and when each page (P2, P3 etc) is selected an additional mapping 'Reaper ""' is used to show the page currently selected.
It's working really well so far. If anyone else has a NanoKontrol2 then i'll upload all the files when i'm done if it helps anyone, creating new mappings is quite easy too.
|
|
|
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:28 AM.
|