|
|
|
09-25-2021, 06:24 PM
|
#15001
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Made a thread in the Feature requests channel. Feel free to add to it if I missed anything or you want to relay it a different way.
|
|
|
09-25-2021, 09:00 PM
|
#15002
|
Human being with feelings
Join Date: Aug 2013
Location: Mesa, AZ
Posts: 288
|
Control 24
Quote:
Originally Posted by Geoff Waddington
Check out Neyrinck V-Control pro and see if that is what you are looking for -- not sure if it uses EuCon, think it might be MCU/HUI midi
|
Geoff
I will check it out
Thanks
|
|
|
09-26-2021, 04:06 AM
|
#15003
|
Human being with feelings
Join Date: Jan 2017
Location: London
Posts: 328
|
Quote:
Originally Posted by MixMonkey
Try the attached files with V1.1 (included). Which DAW mode have you chosen in the 360 software?
|
This is working great, thank you, MixMonkey!
I have dB display when writing automation and I can multi-select automation type which is excellent.
This is brilliant and I saw that you have also provided me with many more Zone files. I will investigate what those are doing and will start customising them to my needs.
Can't wait to come up for air and get working in detail with Reaper and CSI.
__________________
PC Ryzen 7950x|W11 Pro|Reaper (latest)
2x RME HDSPe MADI FX | SSL UF8|UF1|UC1
PC Ryzen 5950X|W11 Pro|AudioGridder Server
|
|
|
09-26-2021, 05:35 AM
|
#15004
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by MixR
This is working great, thank you, MixMonkey!
I have dB display when writing automation and I can multi-select automation type which is excellent.
|
That's good news!
Quote:
This is brilliant and I saw that you have also provided me with many more Zone files. I will investigate what those are doing and will start customising them to my needs.
Can't wait to come up for air and get working in detail with Reaper and CSI.
|
Actually, all I did was split up your existing Zone file into the individual Zone files required by CSI V1.1, changed the Navigator names where needed and corrected a few errors.
Regarding the choice of DAW mode on the UF8 for CSI, it would appear from the manual that Cubase mode would enable the 8 buttons on the left hand side of the unit, but that's about it.
The choice of 'best' mode for use with CSI really comes down to which mode enables MIDI message output from the most surface buttons.
If you have a spare 5 minutes and a MIDI monitor app (like https://www.snoize.com/midimonitor/) it could be worth your while taking a look at what is output from the 360 app when you push various surface buttons in various surface modes. If a button outputs a MIDI message, it can be used with CSI.
|
|
|
09-26-2021, 06:01 AM
|
#15005
|
Human being with feelings
Join Date: Jan 2017
Location: London
Posts: 328
|
Quote:
Originally Posted by MixMonkey
That's good news!
Actually, all I did was split up your existing Zone file into the individual Zone files required by CSI V1.1, changed the Navigator names where needed and corrected a few errors.
Regarding the choice of DAW mode on the UF8 for CSI, it would appear from the manual that Cubase mode would enable the 8 buttons on the left hand side of the unit, but that's about it.
The choice of 'best' mode for use with CSI really comes down to which mode enables MIDI message output from the most surface buttons.
If you have a spare 5 minutes and a MIDI monitor app (like https://www.snoize.com/midimonitor/) it could be worth your while taking a look at what is output from the 360 app when you push various surface buttons in various surface modes. If a button outputs a MIDI message, it can be used with CSI.
|
Those are very good suggestions and I will look into them in detail once I have delivered the current project I am working on. I went with Studio One because Cubase supports only two automation mode buttons but as I get more into CSI and the UF8 I may well switch to Cubase and map the automation buttons elsewhere.
It's high time SSL open up programmability of the UF8 as the MCU protocol seems very limited in this day and age.
I thought an eight character scribble strip on the ProControl was limited and now I have six on the UF8...that's only one out of a thousand things that could be better if the unit could be programmed as a generic MIDI controller.
__________________
PC Ryzen 7950x|W11 Pro|Reaper (latest)
2x RME HDSPe MADI FX | SSL UF8|UF1|UC1
PC Ryzen 5950X|W11 Pro|AudioGridder Server
|
|
|
09-26-2021, 07:37 AM
|
#15006
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by MixR
I went with Studio One because Cubase supports only two automation mode buttons but as I get more into CSI and the UF8 I may well switch to Cubase and map the automation buttons elsewhere.
|
I see, swings and roundabouts then. SSL just need to assign an unused MIDI message to those ‘dead’ buttons
|
|
|
09-26-2021, 10:48 AM
|
#15007
|
Human being with feelings
Join Date: Dec 2017
Posts: 188
|
Does anyone have the files required to get a Frontier Alphatrack to work with CSI?
If not - could anyone suggest which file should i start from? And i'll have a go a creating one for the Sinarch site.
Thanks in advance
|
|
|
09-27-2021, 11:50 AM
|
#15008
|
Human being with feelings
Join Date: Jun 2018
Posts: 705
|
Quote:
Originally Posted by MisterGTR
Does anyone have the files required to get a Frontier Alphatrack to work with CSI?
If not - could anyone suggest which file should i start from? And i'll have a go a creating one for the Sinarch site.
Thanks in advance
|
Hi MisterGTR,
Just to point out that the files on my site are Pre v1.1 And a lot of things change when that version came out. In the past, you could have multiple Zones in the same text file. Now each zone needs it's discrete text file. That's one of the big changes, but there were others. I believe Funkybot made a Wiki Page dedicated to these changes.
Hope that helps.
|
|
|
09-28-2021, 02:58 AM
|
#15009
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Thinking about my OSC layout and had a question.
How do you guys go into and out of automation modes?
Are we generally using something that works on selected tracks? i.e. I have 3 selected tracks and one shortcut puts all 3 selected tracks into touch mode?
Or is it more something thats per track based?
I have 4 buttons on the fader strip now. Solo, mute, and record I assume are locks for 3 of those spots. Phase could be the 4th, but if automation modes are more track based then I suppose I could make a drop down/pop up menu for the modes. Anybody have an opinion?
|
|
|
09-28-2021, 05:18 AM
|
#15010
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by cjewellstudios
Thinking about my OSC layout and had a question.
How do you guys go into and out of automation modes?
Are we generally using something that works on selected tracks? i.e. I have 3 selected tracks and one shortcut puts all 3 selected tracks into touch mode?
Or is it more something thats per track based?
I have 4 buttons on the fader strip now. Solo, mute, and record I assume are locks for 3 of those spots. Phase could be the 4th, but if automation modes are more track based then I suppose I could make a drop down/pop up menu for the modes. Anybody have an opinion?
|
If your surface model contains more than one fader, you'll need a 'Select' button as well
Regarding automation, traditionally this was done with a button on the channel, not least because a channel could be a very long way from the console centre section (think 72 channel+ SSL )
Now that there's no hard link between surface channels and tracks, a small number of faders can cover a large number of tracks and the 'centre' section is likely to be within arms reach (think Mackie MCU et al) In this situation it makes more sense to group the autmation mode buttons in the centre section and change a channel or channels from there after first having made a selction using the Select buttons on the channels thamselves.
That said, it is very helpful to be able to see the automation status of all the channels at once, rather than relying on the automation mode button LEDs, which require the channels to be selected one by one to determine their status. True, you could look at the screen, but c'mon, this is the CSI thread! .
Fortunately, there a CSI action for this. I have:
Code:
Alt+DisplayLower| TrackAutoModeDisplay
...in the Channel Zone. There are also Reaper Actions that will toggle the auto mode of the selected channel between Trim and Touch or cycle round all the auto modes. So if you wanted to build in auto control from the individual channels, you could.
|
|
|
09-28-2021, 06:02 AM
|
#15011
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by MixMonkey
If your surface model contains more than one fader, you'll need a 'Select' button as well
Regarding automation, traditionally this was done with a button on the channel, not least because a channel could be a very long way from the console centre section (think 72 channel+ SSL )
Now that there's no hard link between surface channels and tracks, a small number of faders can cover a large number of tracks and the 'centre' section is likely to be within arms reach (think Mackie MCU et al) In this situation it makes more sense to group the autmation mode buttons in the centre section and change a channel or channels from there after first having made a selction using the Select buttons on the channels thamselves.
That said, it is very helpful to be able to see the automation status of all the channels at once, rather than relying on the automation mode button LEDs, which require the channels to be selected one by one to determine their status. True, you could look at the screen, but c'mon, this is the CSI thread! .
Fortunately, there a CSI action for this. I have:
Code:
Alt+DisplayLower| TrackAutoModeDisplay
...in the Channel Zone. There are also Reaper Actions that will toggle the auto mode of the selected channel between Trim and Touch or cycle round all the auto modes. So if you wanted to build in auto control from the individual channels, you could.
|
Thank you that was exactly the answer I was looking for
You'll be able to select the channel by touching the track name at the top of the strip. You'll also be able to pin the track by touching the bottom.
I'll have a display for the auto modes and use the selected track method with a drop down or pop up menu located somewhere else.
That potentially frees up the 4th button again. I almost never use phase but that's really the only thing that could go there. I'm getting real close on this thing. In a week or two I'll send it out privately to whoever wants to take it for a test drive, then I'll make my own thread for it as to not clog up this one anymore
|
|
|
09-29-2021, 06:03 AM
|
#15012
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,818
|
CSI may have a dependancy.
Just did a complete reinstall of Windows 10 here. CSI isn't even showing up in the csurf dropdown menu of the preferences, in either my reimported setup or a fresh new portable install of Reaper.
Not showing up!
That leads me to believe that CSI is depending on some system library or something.
What do I need to have installed ?
To test, I'm currently installing Steam and starting a game. It's installing the VC library, downloading DirectX, .Net 3.5 and some other stuff. We'll see how that goes.
== EDIT ==
One of those things enabled CSI to show up just fine.
When in doubt, install a game .
Last edited by airon; 09-29-2021 at 06:18 AM.
|
|
|
09-29-2021, 06:28 AM
|
#15013
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
trouble with xtouch
Im having trouble getting xtouch to send and recieve at the same time
I think it is some sort of midi conflict or something to do with the midi ID numbers in reaper as I had it working for a bit by playing with those, then adjusting the CSI settings.
I can get klinke & MCU to work so it's not the control surface. Any ideas?
|
|
|
09-29-2021, 06:45 AM
|
#15014
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
Im having trouble getting xtouch to send and recieve at the same time
I think it is some sort of midi conflict or something to do with the midi ID numbers in reaper as I had it working for a bit by playing with those, then adjusting the CSI settings.
I can get klinke & MCU to work so it's not the control surface. Any ideas?
|
Is it disabled in the MIDI Devices prefs?
|
|
|
09-29-2021, 06:48 AM
|
#15015
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Is it disabled in the MIDI Devices prefs?
|
yes.
works with a fresh portable install, so someting in the config files???
|
|
|
09-29-2021, 07:02 AM
|
#15016
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
yes.
works with a fresh portable install, so someting in the config files???
|
Maybe trash: reaper-midihw.ini and rebuild?
|
|
|
09-29-2021, 07:46 AM
|
#15017
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Maybe trash: reaper-midihw.ini and rebuild?
|
I already tried renaming it to .bak so reaper makes a new one, if thats what you mean.
|
|
|
09-29-2021, 07:49 AM
|
#15018
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
I already tried renaming it to .bak so reaper makes a new one, if thats what you mean.
|
Yep, that's it. Did you then rebuild your CSI prefs?
|
|
|
09-29-2021, 07:49 AM
|
#15019
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
I could try the same with other ini files tomorrow.
|
|
|
09-29-2021, 07:51 AM
|
#15020
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Yep, that's it. Did you then rebuild your CSI prefs?
|
I changed the midi port in the csi menu, yes. No luck.
|
|
|
09-29-2021, 07:52 AM
|
#15021
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
I could try the same with other ini files tomorrow.
|
When you say it worked with a portable install, were you using the same CSI folder as before?
|
|
|
09-29-2021, 07:55 AM
|
#15022
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by airon
CSI may have a dependancy.
Just did a complete reinstall of Windows 10 here. CSI isn't even showing up in the csurf dropdown menu of the preferences, in either my reimported setup or a fresh new portable install of Reaper.
Not showing up!
That leads me to believe that CSI is depending on some system library or something.
What do I need to have installed ?
To test, I'm currently installing Steam and starting a game. It's installing the VC library, downloading DirectX, .Net 3.5 and some other stuff. We'll see how that goes.
== EDIT ==
One of those things enabled CSI to show up just fine.
When in doubt, install a game .
|
Wiki page on Installing CSI, step 9:
Quote:
Click on the empty dropdown beside "control surface mode" and select Control Surface Integrator - this will now show the settings for CSI. If Control Surface Integrator is not visible, you might have to install the Microsoft Visual C++ 2019 runtime 32bit | 64bit and restart Reaper.
|
|
|
|
09-29-2021, 08:16 AM
|
#15023
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
When you say it worked with a portable install, were you using the same CSI folder as before?
|
I think I copy&pasted the .dll and CSI folder
It all started when I put in korg uninstall midi utility, so I could walk a friend through removing old midi ports that may have been exceeding the windows limit.
Since then I uninstalled all midi drivers and put xtouch back first. It worked until I reinstalled sound card!?
|
|
|
09-29-2021, 08:41 AM
|
#15024
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
It worked until I reinstalled sound card!?
|
Does your sound card also have MIDI ports?. Maybe disable them too.
|
|
|
09-29-2021, 08:58 AM
|
#15025
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Does your sound card also have MIDI ports?. Maybe disable them too.
|
I think there disabled, ill hopefully have a look tomorrow.
The faders default back to the middle but still control the tracks in reaper. Perhaps its not going to the home zone properly when reaper restarts... or some other issue in my .zon files??
|
|
|
09-29-2021, 09:57 AM
|
#15026
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
I think there disabled, ill hopefully have a look tomorrow.
The faders default back to the middle but still control the tracks in reaper. Perhaps its not going to the home zone properly when reaper restarts... or some other issue in my .zon files??
|
Faders going to the middle position is a classic symptom of not disabling the device in the MIDI Devices prefs. The faders are controlled by pitch bend messages, and pitch bend is usually reset to 0 on stop and/or play.
It's unlikely to be an issue in the .zon files as you said the same files worked correctly in your portable install.
|
|
|
09-29-2021, 10:17 AM
|
#15027
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Faders going to the middle position is a classic symptom of not disabling the device in the MIDI Devices prefs. The faders are controlled by pitch bend messages, and pitch bend is usually reset to 0 on stop and/or play.
It's unlikely to be an issue in the .zon files as you said the same files worked correctly in your portable install.
|
Could it be something wrong in windows registry? Fragments of old driver entries?
|
|
|
09-29-2021, 10:20 AM
|
#15028
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
Could it be something wrong in windows registry? Fragments of old driver entries?
|
Wouldn't your portable install use the same registry?
|
|
|
09-29-2021, 10:27 AM
|
#15029
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Steviekeys, I've been at work and not following the back and forth, but my go to response for troubleshooting is this...
Post screen prints of your:
1. Reaper -> Preferences -> MIDI Devices with the MIDI in/out ports for the device in question
2. CSI Device Preferences (channels, sends, FXmenu, ports, surface and zone settings)
3. Reaper\User Plugins\ folder contents
4. Reaper\CSI\ folder contents
5. CSI.ini file content
6. Tell us your Reaper version number
It's tedious, but we need to be able to see what you see.
You can post the images directly in the thread. I think in your case, if you just post screen prints of #1 and #2 we'd probably get it sorted.
|
|
|
09-29-2021, 10:42 AM
|
#15030
|
Human being with feelings
Join Date: Apr 2021
Posts: 6
|
Send MIDI CC or event?
Hello CSI crew. I'm to configure a button of my XT to change a single FX parameter on my Monitor FX chain whether the window is open or not, and the best I have come up with is to assign the FX parameter to a midi function and trigger that with a button press. I'm struggling to get the XT to send just a midi CC or note, would love some guidance if anyone has it. Otherwise, if someone has a better solution to this problem, my ears are open!
Cheers!
|
|
|
09-29-2021, 02:21 PM
|
#15031
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by MixMonkey
Wouldn't your portable install use the same registry?
|
🤔 Ah... good point!
|
|
|
09-29-2021, 02:23 PM
|
#15032
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
Quote:
Originally Posted by Funkybot
Steviekeys, I've been at work and not following the back and forth, but my go to response for troubleshooting is this...
Post screen prints of your:
1. Reaper -> Preferences -> MIDI Devices with the MIDI in/out ports for the device in question
2. CSI Device Preferences (channels, sends, FXmenu, ports, surface and zone settings)
3. Reaper\User Plugins\ folder contents
4. Reaper\CSI\ folder contents
5. CSI.ini file content
6. Tell us your Reaper version number
It's tedious, but we need to be able to see what you see.
You can post the images directly in the thread. I think in your case, if you just post screen prints of #1 and #2 we'd probably get it sorted.
|
Ok, will give it a go tomorrow thanks.
|
|
|
09-29-2021, 04:22 PM
|
#15033
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by BerlinAudioProds
Hello CSI crew. I'm to configure a button of my XT to change a single FX parameter on my Monitor FX chain whether the window is open or not, and the best I have come up with is to assign the FX parameter to a midi function and trigger that with a button press. I'm struggling to get the XT to send just a midi CC or note, would love some guidance if anyone has it. Otherwise, if someone has a better solution to this problem, my ears are open!
Cheers!
|
Unfortunately, sending MIDI from the surface is disabled when using it as a control surface, so you've probably found the best solution. I'm not that familiar with the monitor FX chain, but I'll take a look and see if a better answer is possible.
|
|
|
09-29-2021, 04:29 PM
|
#15034
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
I swapped my main ini file with one from a fresh install...
xtouch worked...
I then....
renderwarn_h=294
dynsplit_x=208
dynsplit_y=149
mf_sdir=E:\
csurf_cnt=1
csurf_0=CSI 0 0
csurf_1=CSI 0 0 removed this line from my original
soloip=1
and it now works!
Thanks
|
|
|
09-29-2021, 04:32 PM
|
#15035
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
I swapped my main ini file with one from a fresh install...
xtouch worked...
I then....
renderwarn_h=294
dynsplit_x=208
dynsplit_y=149
mf_sdir=E:\
csurf_cnt=1
csurf_0=CSI 0 0
csurf_1=CSI 0 0 removed this line from my original
soloip=1
and it now works!
Thanks
|
Splendid! I'll remember that one for the future!
|
|
|
09-29-2021, 04:43 PM
|
#15036
|
Human being with feelings
Join Date: Jun 2016
Location: UK
Posts: 285
|
I Don't know how I ended up with two entries or what it does, just a lucky guess that it shouldn't be there
|
|
|
09-29-2021, 04:50 PM
|
#15037
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,887
|
Quote:
Originally Posted by Steviekeys
I Don't know how I ended up with two entries or what it does, just a lucky guess that it shouldn't be there
|
Didn't look right though did it? Two entries for CSI in the init
|
|
|
09-30-2021, 02:31 AM
|
#15038
|
Human being with feelings
Join Date: Oct 2015
Posts: 18
|
Hi there! I'm using CSI for a while, I have a MCU unit and an extender on thre left side. I'm really impressed by the possibilities, this is amazing!
However, I've noticed when I go to the Receives mode, if there are more than 16 receives, the unit doesn't bank passed the 16 receive. The "third bank" appears on the surface just for a fraction of a second and bounces back to he second bank. I can see the faders moving to whatever position they are on the 17 and next receives, they go up or down according to the level of the receives, and they return to the second bank position instantly. Same thing happens with the display. I changed the number of send in the config window but no luck.
The Sends page works just fine, I can bank along wathever number of sends I have on the selected channel.
I'm using the .zon files that come with the instalation.
Another issue I found is the Pre-Post selection with the Rotary push on both modes, Sends and Receives: They switch between "PostFad" and "Post FX" on the display, but nothing changes on Reaper. Also, the "Pre" text never shows on the display, even when the sends or receives are configured as "Pre".
Any ideas?
These are my send and receives .zon files:
Quote:
Zone "SelectedTrackSendSlot"
Send GoZone Home
SelectedTrackSendSlotNavigator
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendPanDisplay
Control+DisplayLower| TrackSendPrePostDisplay
Control+RotaryPush| TrackSendPrePost
Fader|Touch+DisplayLower| TrackSendVolumeDisplay
Mute| TrackSendMute
Rotary| TrackSendPan
Fader| TrackSendVolume
BankLeft SendSlotBank -8
BankRight SendSlotBank 8
ZoneEnd
Zone "SelectedTrackReceiveSlot"
Track MapTrackSendsSlotToWidgets
Send MapSelectedTrackSendsSlotToWidgets
Plugin MapSelectedTrackFXToMenu
Instrument GoZone Home
SelectedTrackReceiveSlotNavigator
DisplayUpper| TrackReceiveNameDisplay
DisplayLower| TrackReceivePanDisplay
Fader|Touch+DisplayLower| TrackReceiveVolumeDisplay
Alt+DisplayLower| TrackReceivePanDisplay
Shift+DisplayLower| TrackReceivePrePostDisplay
Shift+RotaryPush| TrackReceivePrePost
Mute| TrackReceiveMute
Rotary| TrackReceivePan
Alt+Rotary| TrackReceivePan
Fader| TrackReceiveVolume
BankLeft ReceiveSlotBank -8
BankRight ReceiveSlotBank 8
SubZone1 ReceiveSlotBank -1
SubZone2 ReceiveSlotBank 1
ZoneEnd
|
Last edited by Uqbar; 09-30-2021 at 05:35 AM.
|
|
|
09-30-2021, 02:58 AM
|
#15039
|
Human being with feelings
Join Date: Oct 2015
Posts: 18
|
I have some suggestions too
The default naming for the tracks that are not named is "Track n". If the track count is over 9, and taking into account the display of some units does only have 7 characters per channel, the display shows "Track 1Track 1Track 1..." on the channels from 10 to 19. Same thing for the 20 to 29 but with "Track 2Track 2..."
I was thinking about the possibility to change the default track naming to just the number (and even better if they are centered on the channel display) instead of "Track n" to solve this issue. It also would show a less cluttered display by default. At the end, we already know they are tracks, right?
I'm aware that that's easily solved by not being lazy and naming the tracks properly but some times in the heat of the work you may want to add a bunch of tracks for recording straight away, let's say background vocals.
Going along with this idea, what about having a display mode that that shows the channel number instead of the name of the track, for using as an alternative view with the push of some button? This can be a useful for instant feedback on large projects where there's a possibilty of having channels with similar names, or just to quickly know in wich bank you are.
What do you think?
|
|
|
09-30-2021, 03:47 AM
|
#15040
|
Human being with feelings
Join Date: Dec 2019
Posts: 15
|
MapFocusedFXToWidgets and GoFXSlot
Hi, this project is a godsend
Is use this controller https://www.asparion.de/en/electronics/d400.html and have almost everything working, except for this:
1. MapFocusedFXToWidgets makes me control the active floating FX. However, if I activate anothier FX window with the mouse, the control surface shows seemingly random values and I need to activate the home zone and MapFocusedFXToWidgets again, to make it work. It would be great if I could just switch FX windows with the mouse and have the surface follow.
2. GoFXSlot does not seem to do anything. These are my settings:
Code:
Zone Buttons
...
Assignable2 MapSelectedTrackFXToMenu
ZoneEnd
Zone "SelectedTrackFXMenu"
SelectedTrackFXMenuNavigator
DisplayUpper| FXMenuNameDisplay
DisplayLower| NoAction
Mute| Reaper "_S&M_FXBYP|" //Bypass FX Slot
RecordArm| GoFXSlot
ZoneEnd
Since my surface does not have rotaries above the faders, I want to use the record buttons of the channels to activate a plugin. The Plugins of the selected track do show up in the display, but I am not able to activate (or bypass) a plugin. I tried different buttons and also other syntaxes like 'GoFXSlot|' of 'GoFXSlot |'. Also, RecordArm| does work in the Channel zone.
I have the latest versions of CSI (1.1, uploaded August 21, 2021 at 12:24 AM) and Reaper (6.36) running.
Thanks for helping!
|
|
|
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:34 PM.
|