Go Back   Cockos Incorporated Forums > REAPER Forums > MIDI Hardware, Control Surfaces, and OSC

Reply
 
Thread Tools Display Modes
Old 12-14-2018, 01:46 PM   #2241
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

Hi Poetnprophet,

Thanks for replying! I made quite some progress, described in the post just before yours. It is starting to work quite well, the last major thing that does not work yet are the VU meters. And the jog wheel, but I understand that that is not implemented yet so I'll just be patient.

Do you have any suggestions about getting CSI visible in Reaper on my Win 8.1 machine?

Indeed, I have the older QCon Pro, not the X. It seems to be quite compatible with the MCU.

I am going to look through the Reaper actions list to find the functions I want to map to buttons on my QCon, the most important ones being the expand/collapse folder actions.
If you ever find the time to share your files I'd be very grateful, I am sure I'll get some good suggestions from them.

I still don't understand most of the special lines in the .rst and .axt file, but I will read through the thread and see if I can find more information about them.

I am looking forward to figuring out the BCR mapping, I think I understand the concept of the .fxt file, so it will just take some work to do it. I love the power and flexibility of this setup!
dixo is online now   Reply With Quote
Old 12-14-2018, 02:13 PM   #2242
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

Reaper action 41665 toggles the visibility of the children of the selected track(s) in the MCP.
I mapped that to a button on the QCon, so now I can collapse/expand folder tracks at will. Very nice, possibly even better than the folder mode of Klinke MCU...

Last edited by dixo; 12-14-2018 at 03:21 PM.
dixo is online now   Reply With Quote
Old 12-14-2018, 03:13 PM   #2243
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

I have added the line:

smpteBeats CycleTimeDisplayModes

to my QConPro.axt file, to cycle the mode of the time display by pressing the "SMPTE/Beats" button on the QCon. This works, but it does not clear the display before changing the contents. This leaves various digits lit where they were supposed to be blank (e.g. between bar, beat and beat fraction), making it almost unreadable. Not sure if this is QCon specific, or that the MCU has similar behaviour. I think it also happened with the Klinke extension, so it may be the QCon...

Geoff, would it be possible to clear the time display when changing the mode?

Last edited by dixo; 12-14-2018 at 03:25 PM.
dixo is online now   Reply With Quote
Old 12-15-2018, 09:34 AM   #2244
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

hey Dixo, sorry for the delay. Here is my rst file. There are some lines commented out since those buttons don't exist. Also I have the master channel section for the ProX master meter but it doesn't work at this time.

/Track PressFB 90 28 7f 90 28 00
/Send PressFB 90 29 7f 90 29 00
Pan PressFB 90 2a 7f 90 2a 00
Plugin PressFB 90 2b 7f 90 2b 00
/EQ PressFB 90 2c 7f 90 2c 00
/Instrument PressFB 90 2d 7f 90 2d 00

BankLeft Press 90 2E 7f
BankRight Press 90 2F 7f
ChannelLeft Press 90 30 7f
ChannelRight Press 90 31 7f
Flip PressFB 90 32 7f 90 32 00
/GlobalView PressFB 90 33 7f 90 33 00

nameValue Press 90 34 7f
smpteBeats Press 90 35 7f
TimeDisplay MCUTimeDisplay

F1 PressFB 90 36 7f 90 36 00
F2 Press 90 37 7f
F3 Press 90 38 7f
F4 Press 90 39 7f
F5 Press 90 3a 7f
F6 Press 90 3b 7f
F7 Press 90 3c 7f
F8 Press 90 3d 7f

/MidiTracks Press 90 3E 7f
/Inputs Press 90 3F 7f
/AudioTracks Press 90 40 7f
/AudioInstrument Press 90 41 7f
/Aux Press 90 42 7f
/Busses Press 90 43 7f
/Outputs Press 90 44 7f
/User Press 90 45 7f

Shift PressRelease 90 46 7f 90 46 00
Option PressRelease 90 47 7f 90 47 00
Control PressRelease 90 48 7f 90 48 00
Alt PressRelease 90 49 7f 90 49 00

Read PressFB 90 4a 7f 90 4a 00
Write PressFB 90 4b 7f 90 4b 00
Trim PressFB 90 4c 7f 90 4c 00
Touch PressFB 90 4d 7f 90 4d 00
Latch PressFB 90 4e 7f 90 4e 00
Group PressFB 90 4f 7f 90 4f 00

Save Press 90 50 7f
Undo Press 90 51 7f
/Cancel Press 90 52 7f
/Enter Press 90 53 7f

Marker PressFB 90 54 7f 90 54 00
Normal PressFB 90 55 7f 90 55 00

Loop PressFB 90 56 7f 90 56 00
Record PressFB 90 57 7f 90 57 00
/Replace PressFB 90 58 7f 90 58 00
Click PressFB 90 59 7f 90 59 00
Solo PressFB 90 5a 7f 90 5a 00

Last PressFB 90 5b 7f 90 5b 00
Next PressFB 90 5c 7f 90 5c 00
Stop PressFB 90 5d 7f 90 5d 00
Play PressFB 90 5e 7f 90 5e 00
Record PressFB 90 5f 7f 90 5f 00

Up Press 90 60 7f
Down Press 90 61 7f
Left Press 90 62 7f
Right Press 90 63 7f

Zoom PressReleaseFB 90 64 7f 90 64 00
Scrub PressReleaseFB 90 65 7f 90 65 00

JogWheelRotary EncoderFB b0 3c 7f b0 3c 00

MasterChannel
MasterFader Fader14BitFB -60.0 12.0 e8 7f 7f e8 00 00
MasterChannelMeterLeft QConProXMasterVUMeter
MasterChannelMeterRight QConProXMasterVUMeter
MasterFaderTouch PressRelease 90 70 7f 90 70 00
MasterChannelEnd

Channel
VUMeter MCUVUMeter
Fader Fader14BitFB -60.0 12.0 e0 7f 7f e0 00 00
DisplayUpper MCUDisplayUpper
DisplayLower MCUDisplayLower
FaderTouch PressRelease 90 68 7f 90 68 00
RotaryPush Press 90 20 7f
Rotary EncoderFB b0 10 7f b0 10 00
RecordArm PressFB 90 00 7f 90 00 00
Solo PressFB 90 08 7f 90 08 00
Mute PressFB 90 10 7f 90 10 00
Select PressFB 90 18 7f 90 18 00
ChannelEnd
poetnprophet is offline   Reply With Quote
Old 12-15-2018, 09:40 AM   #2245
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Here is my axt file for general use:

ChannelLeft TrackBank -1
ChannelRight TrackBank 1
BankLeft TrackBank -8
BankRight TrackBank 8
TimeDisplay TimeDisplay
smpteBeats CycleTimeDisplayModes
Last Reaper 41043
Next Reaper 41042
Stop Stop
Play Play
Record Record
F1 Reaper 40078
F2 Reaper 40906
F3 Reaper _RSe3ad1140dc733c3ccfe65a67ec53bfc634535821
F4 NextPage
F5 Reaper 40175
F6 Reaper _44924b08811f144e9f88ca3a2918ff48
F7 PinSelectedTracks
F8 UnpinSelectedTracks
Read Reaper 40401
Write Reaper 40403
Trim Reaper 40400
Touch Reaper 40402
Latch Reaper 40404
Group Reaper 42023
Shift+Read Reaper 40086
Shift+Write Reaper 40090
Shift+Trim Reaper 40088
Shift+Touch Reaper 40087
Shift+Latch Reaper 40266
Shift+Group Reaper 42024
Save Reaper 40026
Shift+Save Reaper 40022
Undo Reaper 40029
Shift+Undo Reaper 40030
Marker Reaper 40172
Shift+Marker Reaper 40157
Option+Marker Reaper 40174
/Nudge Reaper 40173
Loop CycleTimeline
/Click Reaper 40364
Pan Reaper _d84d5026095ef643bb683960a071125d
Plugin Reaper _S&M_WNTGL5

MasterFader MasterTrackVolume
MasterChannelMeterLeft MasterTrackOutputMeter 0
MasterChannelMeterRight MasterTrackOutputMeter 1
MasterFaderTouch MasterTrackTouch
MasterFaderTouch MasterTrackUniqueSelect

VUMeter TrackOutputMeter 0
VUMeter TrackOutputMeter 1
DisplayUpper TrackNameDisplay
DisplayLower TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader TrackVolume
FaderTouch TrackTouch
FaderTouch TrackUniqueSelect
Rotary TrackCycle RotaryPush "TrackPan 0" "TrackPanWidth 1"
Select TrackUniqueSelect
Shift+Select TrackRangeSelect
Control+Select TrackSelect
RecordArm TrackRecordArm
Mute TrackMute
Solo TrackSolo

Here is my axt for SEND mode. Notice how it's mostly the same, except the channel strips do/control slightly differently, and he Click button is in use to move through sends...maybe a couple of other things. This is an example of how to setup another PAGE to have different functions with your surface. The F7/F8 cycle your different pages, if you have them.

ChannelLeft TrackBank -1
ChannelRight TrackBank 1
BankLeft TrackBank -8
BankRight TrackBank 8
TimeDisplay TimeDisplay
smpteBeats CycleTimeDisplayModes
Last Reaper 41043
Next Reaper 41042
Stop Stop
Play Play
Record Record
F1 Reaper 40078
F2 Reaper 40906
F3 Reaper _RSe3ad1140dc733c3ccfe65a67ec53bfc634535821
F4 NextPage
F5 Reaper 40175
F6 Reaper _44924b08811f144e9f88ca3a2918ff48
F7 PinSelectedTracks
F8 UnpinSelectedTracks
Read Reaper 40401
Write Reaper 40403
Trim Reaper 40400
Touch Reaper 40402
Latch Reaper 40404
Group Reaper 42023
Shift+Read Reaper 40086
Shift+Write Reaper 40090
Shift+Trim Reaper 40088
Shift+Touch Reaper 40087
Shift+Latch Reaper 40266
Shift+Group Reaper 42024
Save Reaper 40026
Shift+Save Reaper 40022
Undo Reaper 40029
Shift+Undo Reaper 40030
Marker Reaper 40172
Shift+Marker Reaper 40157
Option+Marker Reaper 40174
/Nudge Reaper 40173
Loop CycleTimeline
Click TrackSendBank -1
Normal TrackSendBank 1
Plugin Reaper _S&M_WNTGL5

Pan Reaper _d84d5026095ef643bb683960a071125d

MasterFader MasterTrackVolume
MasterChannelMeterLeft MasterTrackOutputMeter 0
MasterChannelMeterRight MasterTrackOutputMeter 1
MasterFaderTouch MasterTrackTouch
MasterFaderTouch MasterTrackUniqueSelect

VUMeter TrackOutputMeter 0
VUMeter TrackOutputMeter 1
DisplayUpper TrackNameDisplay
DisplayLower TrackSendTouchControlled TrackSendNameDisplay TrackSendVolumeDisplay
Fader TrackSendVolume
FaderTouch TrackTouch
FaderTouch TrackUniqueSelect
Rotary TrackSendPan 0
Select TrackUniqueSelect
Shift+Select TrackRangeSelect
Control+Select TrackSelect
Mute TrackSendMute
poetnprophet is offline   Reply With Quote
Old 12-15-2018, 09:56 AM   #2246
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by dixo View Post
I have added the line:

smpteBeats CycleTimeDisplayModes

to my QConPro.axt file, to cycle the mode of the time display by pressing the "SMPTE/Beats" button on the QCon. This works, but it does not clear the display before changing the contents. This leaves various digits lit where they were supposed to be blank (e.g. between bar, beat and beat fraction), making it almost unreadable. Not sure if this is QCon specific, or that the MCU has similar behaviour. I think it also happened with the Klinke extension, so it may be the QCon...

Geoff, would it be possible to clear the time display when changing the mode?
I also have a bug where the display freezes, I have not been able to figure out what's causing it. There's some other bugs, don't let it discourage you. The meters, not sure why those aren't working but look in my files, there may be a line in there you can use if you don't have.
poetnprophet is offline   Reply With Quote
Old 12-16-2018, 08:09 AM   #2247
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

Hi Poetnprophet,

Thanks very much for posting your config! I will go through the files for bits that I may want to add to my own config.

I have been messing around with my setup (re-installed the VC2017 redist, and the latest Reaper) and I managed to get CSI working on my main machine too. And magically, the VU meters on my QCon Pro and EX started working too!

So, I am very happy!

The 2 major things missing (but I will patiently wait for that ):
- Time Display is messy when switched to other modes
- Jog wheel not implemented yet

Pretty impressive for pre-alpha software!

Next task is to set up my BCR2000 for VST control...
dixo is online now   Reply With Quote
Old 12-16-2018, 10:34 AM   #2248
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

my pleasure, glad to hear you have it working. Now, you can pretty much make it how you want. I can see that since I've been using it and since I am looking at the files again, I feel like I should make some changes. Good for me to re-acquaint myself again anyway!

No the jog wheel doesn't yet work..not your fault

Funny, when I switch to send mode the time display works great...on any project. We haven't been able to narrow that down, though.
poetnprophet is offline   Reply With Quote
Old 12-18-2018, 08:33 PM   #2249
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by MixMonkey View Post
From Geoff:

"Just like you can use this syntax:

TrackOnSelection MapTrackAndFXToWidgets

you can now do the same for last focused FX:

TrackOnFocusedFX MapSingleFXToWidgetsForTrack"


So in my C4.axt I just swapped TrackOnSelection MapFX to Widgets for TrackOnFocusedFX MapSingleFXToWidgetsForTrack and now only the focussed (active window) FX maps to the surface.

C4 looks like this:
Code:
TrackOnFocusedFX MapSingleFXToWidgetsForTrack

SlotUp Reaper _S&M_WNONLY1
SlotDown Reaper _S&M_WNONLY2
TrackL Reaper _6e6967db562a45f3b499d3b9daaefd60
TrackR Reaper _172419af88f947d1b7205e75478aa4b7
SlotUp/Down is SWS/S&M: Float previous/next FX (and close others) for selected tracks

TrackL/R is a custom action comprising:

SWS/S&M: Close all floating FX windows + Track: Go to next track

This closes the floating fx windows opened by SlotUp/SlotDown, when you use the C4 TrackL/R buttons to move to a new track. Stops too many FX windows staying open and making a mess.

Big advantage of TrackOnFocusedFX MapSingleFXToWidgetsForTrack is no more collisions on the surface, as only one FX is mapped at a time and navigation is by slot, which is how most people conceptualise the FX chain. Also, on a C4, all but the biggest (most parameters) plugins can be mapped in full.

There does seem to be a bug in the latest build that causes the master fader to disappear from the surface- be good if you could try it out and see if you get the same results- might just be me
Following up, this has worked very well, thank you!
poetnprophet is offline   Reply With Quote
Old 12-19-2018, 09:00 AM   #2250
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 180
Default

Quote:
Originally Posted by poetnprophet View Post
Following up, this has worked very well, thank you!
You're welcome Does the master fader still appear on the surface?

BTW are you on Mac or Windows?
MixMonkey is offline   Reply With Quote
Old 12-19-2018, 10:44 AM   #2251
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Yes the master fader still works for me. Win10 64bit.
poetnprophet is offline   Reply With Quote
Old 12-21-2018, 12:20 PM   #2252
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Hey Geoff, happy holidays!

I wanted to post a couple of potential bugs, not to distract you but just to document. These are new for me and I think for the thread. Nothing detrimental really. I've been building FX maps for the C4, have about 30 now that I'm on focused FX, it's been great!

1. SYS Comp by HOFA. I am pretty sure I have the syntax all correct, but if this fxt file is in the folder, Reaper will not open. I have a few other sys plugs mapped no problem. I'm wondering if it's because of the file name? "SYS Comp"

2. Slate Digital FG-MU. Even when the channels are linked via the switch, the L/R parameters will not link when using the C4 to adjust.
poetnprophet is offline   Reply With Quote
Old 12-21-2018, 12:47 PM   #2253
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

couple more questions:

ReaDelay: has anyone gotten a parameter map to work for reaDelay, specifically the LENGTH parameters? There are two, one for musical the other for milliseconds, but they are both named the exact same, I can't find a way to separate and so can't really use and that's the most important one.

C4 knob resolution: is there a way to make finer adjustments? Some parameters just can't be used, in the above example the length parameter corresponds to the ms setting, and it jumps from 0 to 150ms in one increment.
poetnprophet is offline   Reply With Quote
Old 12-21-2018, 01:31 PM   #2254
tXShooter
Human being with feelings
 
tXShooter's Avatar
 
Join Date: Aug 2017
Posts: 249
Default 58 Pages, and I still don't know how to use this.

So, is there a video that shows how to set this thing up to get the active scene number from an X32 console?
__________________
"But be ye doers of the word, and not hearers only, deceiving your own selves."
tXShooter is offline   Reply With Quote
Old 12-21-2018, 06:39 PM   #2255
spoon
Human being with feelings
 
spoon's Avatar
 
Join Date: Jul 2007
Location: Chicago
Posts: 198
Default Mouse Follow, TrackBank & Action Commads

Hi Geoff.

Is there something I need to add to the .axt file (or other file) to have the Control Surface (X-Touch) follow the mouse? When I mouse-click the track is highlighted as selected but that selection does not flow thru to the Control Surface.

Related to following (sorta); when I press the RIGHT TrackBank button and it gets to the end of my tracks, it stops (which is expected/desired behavior). However, when I go left, the Surface will go "off the grid" so to speak and show nothing on the displays. Is there something I can add to prevent this?

(I re-read a post where someone else was experiencing something similar...I had two entries in the "Surfaces" section as I do not know what I am doing. )

And finally, I understand documentation is coming (in the grand scale) but I noticed there are custom commands I assumed you created, ie., "MapTrackToWidgets", "PinSelectionToTracks", etc.
Can you post some docs for them...as in code comments...something you can copy-paste into this thread?

This project is pretty awesome...if the Green Brothers didn't already have "The Project for Awesome" I would suggest it as a name. Thanks much for your efforts (and the many others contributing on this thread).

Cheers,
David
__________________
"I drank what?!?" - Socrates

Last edited by spoon; 12-21-2018 at 09:25 PM.
spoon is online now   Reply With Quote
Old 12-22-2018, 04:34 AM   #2256
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by poetnprophet View Post
Hey Geoff, happy holidays!

I wanted to post a couple of potential bugs, not to distract you but just to document. These are new for me and I think for the thread. Nothing detrimental really. I've been building FX maps for the C4, have about 30 now that I'm on focused FX, it's been great!

1. SYS Comp by HOFA. I am pretty sure I have the syntax all correct, but if this fxt file is in the folder, Reaper will not open. I have a few other sys plugs mapped no problem. I'm wondering if it's because of the file name? "SYS Comp"

2. Slate Digital FG-MU. Even when the channels are linked via the switch, the L/R parameters will not link when using the C4 to adjust.

1) Sounds like a buggy plugin, but Reaper should open without the buggy plugin mapped.
Could you please post the .fxt file contents, thanks for the bug report.

2) I have often found Slate's VST implementations incomplete.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-22-2018, 04:42 AM   #2257
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by poetnprophet View Post
C4 knob resolution: is there a way to make finer adjustments? Some parameters just can't be used, in the above example the length parameter corresponds to the ms setting, and it jumps from 0 to 150ms in one increment.
Yup, IMHO customizable acceleration is the way to go and is planned.

It's very intuitive, slow for fine, getting coarser as you speed up.

Implementation TBD but likely includes an .rst and .axt component, .rst to be able to "tune" overall widget acceleration as well as balance multiple surfaces "feel", and .axt for action specific acceleration.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-22-2018, 04:46 AM   #2258
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by spoon View Post
Hi Geoff.

Is there something I need to add to the .axt file (or other file) to have the Control Surface (X-Touch) follow the mouse? When I mouse-click the track is highlighted as selected but that selection does not flow thru to the Control Surface.

Related to following (sorta); when I press the RIGHT TrackBank button and it gets to the end of my tracks, it stops (which is expected/desired behavior). However, when I go left, the Surface will go "off the grid" so to speak and show nothing on the displays. Is there something I can add to prevent this?

(I re-read a post where someone else was experiencing something similar...I had two entries in the "Surfaces" section as I do not know what I am doing. )

And finally, I understand documentation is coming (in the grand scale) but I noticed there are custom commands I assumed you created, ie., "MapTrackToWidgets", "PinSelectionToTracks", etc.
Can you post some docs for them...as in code comments...something you can copy-paste into this thread?

This project is pretty awesome...if the Green Brothers didn't already have "The Project for Awesome" I would suggest it as a name. Thanks much for your efforts (and the many others contributing on this thread).

Cheers,
David
Yeah, things are getting stable enough -- famous last words -- that a pre alpha set of docs is probably a good idea, I'll play around over the holidays.

Also, a reminder of an upcoming breaking change -- .rst (real surface template) files will now be named .mst (Midi surface template) -- shouldn't be too intrusive, there aren't a lot of them
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-22-2018, 06:04 PM   #2259
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by Geoff Waddington View Post
1) Sounds like a buggy plugin, but Reaper should open without the buggy plugin mapped.
Could you please post the .fxt file contents, thanks for the bug report.

2) I have often found Slate's VST implementations incomplete.
Hey, no worries, its not the end of the world and I'm really happy to have so much working so far. Yes some of Slate's stuff isn't easy, I have no idea what to do with the VMR but it is what it is. I have to say, the new AirEQ Premium sits perfectly on the C4 and works great.

Here's the fxt lines:

VST3: SYS Comp (HOFA)

DisplayUpperA1 " " TrackFXParamNameDisplay "Comp"
DisplayLowerA1 "MasterBypass" TrackFXParamValueDisplay
Toggle+RotaryPushA1 "MasterBypass"


DisplayUpperD1 "Threshold" TrackFXParamNameDisplay "Thr"
DisplayLowerD1 "Threshold" TrackFXParamValueDisplay
RotaryD1 "Threshold"

DisplayUpperD2 "Attack" TrackFXParamNameDisplay "Atk"
DisplayLowerD2 "Attack" TrackFXParamValueDisplay
RotaryD2 "Attack"

DisplayUpperD3 "Release" TrackFXParamNameDisplay "Rel"
DisplayLowerD3 "Release" TrackFXParamValueDisplay
RotaryD3 "Release"

DisplayUpperD4 "Out" TrackFXParamNameDisplay "Out"
DisplayLowerD4 "Out" TrackFXParamValueDisplay
RotaryD4 "Out"


DisplayUpperC1 "Ratio" TrackFXParamNameDisplay "Ratio"
DisplayLowerC1 "Ratio" TrackFXParamValueDisplay
RotaryC1 "Ratio"
poetnprophet is offline   Reply With Quote
Old 12-22-2018, 06:05 PM   #2260
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yup, IMHO customizable acceleration is the way to go and is planned.

It's very intuitive, slow for fine, getting coarser as you speed up.

Implementation TBD but likely includes an .rst and .axt component, .rst to be able to "tune" overall widget acceleration as well as balance multiple surfaces "feel", and .axt for action specific acceleration.
Woohoo, as always you've done us all a great service and thank you, and look forward.

Cheers and happy holidays
poetnprophet is offline   Reply With Quote
Old 12-24-2018, 02:14 AM   #2261
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 18,049
Default

Happy Holidays, Geoff: Still lurking, but following the thread with great interest.

Your massive amount of work is much appreciated. Once it gets to the poiunt where a dummy like me can work it, I will be sending you some beer tokens.
__________________
Why can`t we just all get along? Because the moneyed elite dont want us to.
ivansc is offline   Reply With Quote
Old 12-24-2018, 05:16 PM   #2262
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yup, IMHO customizable acceleration is the way to go and is planned.

It's very intuitive, slow for fine, getting coarser as you speed up.

Implementation TBD but likely includes an .rst and .axt component, .rst to be able to "tune" overall widget acceleration as well as balance multiple surfaces "feel", and .axt for action specific acceleration.
Hi, I am pretty new in this thread, but I am slowly reading through it to get a better understanding of how this works. So far I have my QCon Pro and EX working quite well with CSI, using the MCU config files with only very minor tweaks required.
I am now cautiously dipping my toes in the VST waters... My first try is to create a new page that maps ReaComp and/or ReaEQ to the surfaces. This is working pretty well, but I notice that the control of some ReaComp parameters (e.g. threshold) via the faders is not very convenient: most of the action happens at the bottom end of the fader. I can imagine that other plugins also may have controls that are not linear, so would it be possible to set a curve or something for fader control? (Obviously, 'acceleration' doesn't really mean anything for faders)

I have not finished reading the thread completely, but do I understand correctly that there is already a system in place to map and unmap VST parameters to widgets in a page (e.g. my main mixing page)? So I don't have to create a separate page for VST control? Or am I talking nonsense now?

Last edited by dixo; 12-25-2018 at 03:39 AM.
dixo is online now   Reply With Quote
Old 12-27-2018, 02:28 PM   #2263
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Chelmsford
Posts: 108
Default

Greetings Geoff and all the contributors and participants!

All basically working well here, very excited about the potential, and very grateful for the hard work. Need to get busy understanding where exactly we are and how to configure this thing. I take it it's a closed source project?

Coming from using Klinke's csurf, I'm interested in how I would achieve something made possible with that extension.

Klinke implements a load of actions in the extension which trigger MCU events, meaning you can assign CC or note data from another device to fill gaps in your HW interface with other devices. I was using a nanopad2 with a scene mapping pads to MCU modifier keys (alt,shift, etc to botton row of pads), and then using the top row as track buttons. This way I could map tons of actions to button combos on the nanopad2 (alt + 1 to mute etc) So the nanopad plus an x-touch midi could do basically everything except shuttle.
jamesd256 is offline   Reply With Quote
Old 12-28-2018, 09:43 AM   #2264
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by dixo View Post
Hi, I am pretty new in this thread, but I am slowly reading through it to get a better understanding of how this works. So far I have my QCon Pro and EX working quite well with CSI, using the MCU config files with only very minor tweaks required.
I am now cautiously dipping my toes in the VST waters... My first try is to create a new page that maps ReaComp and/or ReaEQ to the surfaces. This is working pretty well, but I notice that the control of some ReaComp parameters (e.g. threshold) via the faders is not very convenient: most of the action happens at the bottom end of the fader. I can imagine that other plugins also may have controls that are not linear, so would it be possible to set a curve or something for fader control? (Obviously, 'acceleration' doesn't really mean anything for faders)

I have not finished reading the thread completely, but do I understand correctly that there is already a system in place to map and unmap VST parameters to widgets in a page (e.g. my main mixing page)? So I don't have to create a separate page for VST control? Or am I talking nonsense now?
Hey Dixo, correct you can map vst parameters within your existing page but ON A SEPARATE SURFACE. I believe you said you have a bcr? There is an example above...actually two that you can use to start setting up. The first is where I quoted Mixmonkey who provided his C4 AXT file. This is where you assign basic function. Also you'll have to make sure the RST file has all the right midi addresses. C4 users are lucky that Geoff provided a full RST for those, so you'll have to modify that for yours.

Then you can setup FXT files, I have an example for a plugin, the basic syntax is there, you just need to apply to your surface and vst(s). You need on FXT file for each plug, this is what takes the longest. Its probably taken me 8-10 hours to map about 30 plugs so far. You will need to have the plug open to get the exact parameter names, but you can't test your new maps until you close and reopen Reaper. Also pay attention to the file name, and the heading within the file lines. It has to be exact.

So you should have 3 surfaces for your current page: Qcon, EX, and BCR. in each setup it will ask where FXT files are. For the Qcon and EX it doesn't matter since you likely wont use those for fx (just point to empty folders like the default). But the bcr should have it's own fxt folder for all your vst mapped files.
poetnprophet is offline   Reply With Quote
Old 12-29-2018, 05:24 AM   #2265
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by jamesd256 View Post
Greetings Geoff and all the contributors and participants!

All basically working well here, very excited about the potential, and very grateful for the hard work. Need to get busy understanding where exactly we are and how to configure this thing. I take it it's a closed source project?

Coming from using Klinke's csurf, I'm interested in how I would achieve something made possible with that extension.

Klinke implements a load of actions in the extension which trigger MCU events, meaning you can assign CC or note data from another device to fill gaps in your HW interface with other devices. I was using a nanopad2 with a scene mapping pads to MCU modifier keys (alt,shift, etc to botton row of pads), and then using the top row as track buttons. This way I could map tons of actions to button combos on the nanopad2 (alt + 1 to mute etc) So the nanopad plus an x-touch midi could do basically everything except shuttle.
If I understand you, that's exactly what this project is all about, being able to map arbitrary surface controls to Reaper behaviour.

Yes, it closed source -- for now at least.

Things are stable enough that I'm now going to write a "How it Works" document that describes all this, should be a couple of days or so, stay tuned...
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-29-2018, 05:29 AM   #2266
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by poetnprophet View Post
Hey Dixo, correct you can map vst parameters within your existing page but ON A SEPARATE SURFACE. I believe you said you have a bcr? There is an example above...actually two that you can use to start setting up. The first is where I quoted Mixmonkey who provided his C4 AXT file. This is where you assign basic function. Also you'll have to make sure the RST file has all the right midi addresses. C4 users are lucky that Geoff provided a full RST for those, so you'll have to modify that for yours.

Then you can setup FXT files, I have an example for a plugin, the basic syntax is there, you just need to apply to your surface and vst(s). You need on FXT file for each plug, this is what takes the longest. Its probably taken me 8-10 hours to map about 30 plugs so far. You will need to have the plug open to get the exact parameter names, but you can't test your new maps until you close and reopen Reaper. Also pay attention to the file name, and the heading within the file lines. It has to be exact.

So you should have 3 surfaces for your current page: Qcon, EX, and BCR. in each setup it will ask where FXT files are. For the Qcon and EX it doesn't matter since you likely wont use those for fx (just point to empty folders like the default). But the bcr should have it's own fxt folder for all your vst mapped files.
Thanks @poetnprophet, excellent explanation, would just make one slight correction, you do not have to map VST's to separate surfaces, you can map them to the rotaries at the top of the MCU, for example.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-29-2018, 07:10 AM   #2267
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

New file is up: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

There is a very quick and dirty "How it Works" pdf, let me know if it is helpful in understanding CSI, and how to expand it / make it better.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-29-2018, 08:37 AM   #2268
spoon
Human being with feelings
 
spoon's Avatar
 
Join Date: Jul 2007
Location: Chicago
Posts: 198
Default

Quote:
Originally Posted by Geoff Waddington View Post
New file is up: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

There is a very quick and dirty "How it Works" pdf, let me know if it is helpful in understanding CSI, and how to expand it / make it better.
Awesome "How it Works". Is that the only change with this build...ie., no changes to the libs?

Also, how do I activate/use the job wheel?
__________________
"I drank what?!?" - Socrates
spoon is online now   Reply With Quote
Old 12-29-2018, 09:53 AM   #2269
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Germany
Posts: 6,338
Default

Quote:
Originally Posted by Geoff Waddington View Post
There is a very quick and dirty "How it Works" pdf, let me know if it is helpful in understanding CSI,
Yep. Now I know my way around all these hurdles.

-Michael
__________________
www.boa-sorte.de
mschnell is online now   Reply With Quote
Old 12-29-2018, 10:49 AM   #2270
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 381
Default

Quote:
Originally Posted by Geoff Waddington View Post
New file is up: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

There is a very quick and dirty "How it Works" pdf, let me know if it is helpful in understanding CSI, and how to expand it / make it better.
Hi Geoff, any other changes in this update?
poetnprophet is offline   Reply With Quote
Old 12-30-2018, 04:33 AM   #2271
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by spoon View Post
Awesome "How it Works". Is that the only change with this build...ie., no changes to the libs?

Also, how do I activate/use the job wheel?
No other changes in that version, but I will be back at coding in the New Year.

Jog wheel is TBD.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-31-2018, 08:47 AM   #2272
spoon
Human being with feelings
 
spoon's Avatar
 
Join Date: Jul 2007
Location: Chicago
Posts: 198
Default

Quote:
Originally Posted by Geoff Waddington View Post
No other changes in that version, but I will be back at coding in the New Year.

Jog wheel is TBD.

Geoff, trying to expand my understanding here.
So we define a button (rst) and add an action to it (axt).
Most of the actions are Reaper <some number> and others are defined by you (living in that dylib, for Macs, I assume). So far, so good?

Ok, if that holds, I also assume a "PressFB" button allows you to define additional logic based on current state of that button/action?

And if _that_ holds, since there exists a "Pause" Reaper action, creating a nuanced "Pause/Play" using the RST Play button would need to be a custom function (dylib/dll) relying on "PressFB" checking whether we are currently "playing" and either "pausing" if we are in play mode or "playing" if stopped/paused...does that hold true?

All the best in any NYE celebrations you may have.

Cheers,
David
__________________
"I drank what?!?" - Socrates
spoon is online now   Reply With Quote
Old 12-31-2018, 09:54 AM   #2273
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

New build is up: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

Updated the ReadMe.

@dixo -- please check and see if the time display is better when switching modes.

@mixmonkey -- been playing around with both the Master fader problem, which I can reproduce here, still haven't solved, and ditto for the Windows reset problem. I will continue to work these, but will have to split some time to getting at OSC in the new year, can't wait any longer
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-31-2018, 10:17 AM   #2274
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by spoon View Post
Geoff, trying to expand my understanding here.
So we define a button (rst) and add an action to it (axt).
Most of the actions are Reaper <some number> and others are defined by you (living in that dylib, for Macs, I assume). So far, so good?
Yup, spot on !

Quote:
Originally Posted by spoon View Post
Ok, if that holds, I also assume a "PressFB" button allows you to define additional logic based on current state of that button/action?
Sort of... probably should do another how it works... on the widget types, the "FB" designator means the widget requests feedback, in this case to switch the surface Play light on or off depending on Reaper's state. Widgets without "FB" opt out of feedback and therefore save resources, since they don't respond to messages sent from Reaper we don't bother sending any

Quote:
Originally Posted by spoon View Post
And if _that_ holds, since there exists a "Pause" Reaper action, creating a nuanced "Pause/Play" using the RST Play button would need to be a custom function (dylib/dll) relying on "PressFB" checking whether we are currently "playing" and either "pausing" if we are in play mode or "playing" if stopped/paused...does that hold true?
I see where you are going theoretically here, but first let me say the Play action in CSI already does exactly what you describe, so there is no need for a custom action.
Code-wise it's a snap, since the Reaper behaviour already does this. Here is the actual source code for the Play action, RequestUpdate provides the feedback to the light and Do is executed when the Play button is pressed:

Code:
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
class Play : public Action
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
{
public:
    void RequestUpdate(Page* page, ActionContext* actionContext, Widget* widget) override
    {
        int playState = DAW::GetPlayState();
        if(playState == 1 || playState == 2 || playState == 5 || playState == 6) // playing or paused or recording or paused whilst recording
            playState = 1;
        else playState = 0;
        actionContext->SetWidgetValue(widget, 0, playState);
    }
    
    void Do(Page* page, double value) override
    {
        DAW::CSurf_OnPlay();
    }
};
You can also make "compound" Reaper Actions and call them (some users are already doing this).

Also planned is the ability to call scripts via button press... you see where this is going... gets pretty flexible.


Quote:
Originally Posted by spoon View Post
All the best in any NYE celebrations you may have.

Cheers,
David
Thanks -- you as well.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 12-31-2018, 01:36 PM   #2275
dixo
Human being with feelings
 
dixo's Avatar
 
Join Date: May 2011
Posts: 73
Default

Hi Poetnprophet, Geoff,

Thanks very much for your replies! I really appreciate you (and many others) spending all this time helping everybody out.

I realized that my questions may have been quite random and unclear, possibly caused by my very incomplete understanding of how CSI is set up, and which parts are not implemented yet. I have spent the last couple of days reading the entire thread again, and much has become clearer now. I also realized that I did not really understand what workflow I actually wanted to implement, so I sat down and figured out how I ideally would like to use my control surfaces (QCon Pro + Ex) with Reaper.
And I hope that you can give me pointers on how to set this up using CSI.

So, what would I ideally like to have:
- A tracking/mixing page that controls all mixer faders and pan knobs, and a transport. This is working great already.
- A page to control the sends for all tracks. This is working fine too, but optionally I would love to have a mode where I can control all sends of a single track on one page (similar to how Klinke does it).
- There are a small number of plugins that I include on almost every track (e.g. EQ, Compressor), and I would love to have separate pages to control these, using all widgets (faders, knobs, etc) and with the QCon LCD showing sensible info. These pages would ideally be accessible by a dedicated button on the QCon (e.g. one of the F1-F8 or the EQ button), but using NextPage is ok too for now. I am still very screen focused, so I would like the associated FX window to open on-screen when that page is selected, and close when the page is left. I have been experimenting to set this up, but so far it does not really work well, requiring mouse clicks in the FX list to open and select the FX to get the widgets to map. Maybe I don't understand the selection keywords (TrackOnSelection, MapTrackAndFXToWidgets, TrackOnFocusedFX, MapSingleFXToWidgetsForTrack) properly...
- For all other VSTs I would like to be able to map the parameters to the rotaries, and have two buttons to navigate through the FX list of the selected track, with its VST window opening on-screen when selected and the QCon LCD indicating the parameters controlled the knobs below, and maybe the name of the plugin too. The other widgets (e.g. faders etc.) should keep behaving as in the main mixer page, so this would be more like an overlay on the mixer page than a separate page.
There was some point in the thread where this was discussed, but I believe it was put on the backburner, is that right?
The way I set up most of my (recorded) tracks is with an EQ on top that does basic clean-up of the signal (e.g. high-pass to remove the extreme low-end). Later in the FX chain I will have another EQ to really shape the tone. If I use different EQ VSTs for that there is no problem with the .fxt mapping, but how can I handle for instance 2 ReaEQ's on the same track? Which one will be mapped, or is it random?

I also have a BCR2000, that I may want to use to map the most common VSTs to, but at the moment my desk is too small to conveniently place it, the QCon and EX already take all the space. So I would love to have everything available on the QCon and have the BCR as an add-on extra later.

So, would this be possible to achieve with the final CSI (I guess the answer is going to be 'yes' ), and how much is already possible?

Geoff: the new version you put up today behaves much nicer on the QCon w.r.t. the Time Display. All modes are now clearly readable and all 'stale' digits are cleared. Thank you so much!

A small feature request: how hard is it to create a 'JumpToPage <page name>' command in addition to the NextPage command?
I know that there has been talk that this should ideally be combined with the radio button mode, but even without that, and no LEDs to indicate the selected page I think it would already be very useful to have.

Thanks for all the great stuff so far, can't wait to see what else you have in store for us...

And: all the best for the new year!

Cheers,
Paul

Last edited by dixo; 01-01-2019 at 05:42 AM.
dixo is online now   Reply With Quote
Old 01-01-2019, 07:03 AM   #2276
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 2,628
Default

Quote:
Originally Posted by dixo View Post
Hi Poetnprophet, Geoff,

Thanks very much for your replies! I really appreciate you (and many others) spending all this time helping everybody out.

I realized that my questions may have been quite random and unclear, possibly caused by my very incomplete understanding of how CSI is set up, and which parts are not implemented yet. I have spent the last couple of days reading the entire thread again, and much has become clearer now. I also realized that I did not really understand what workflow I actually wanted to implement, so I sat down and figured out how I ideally would like to use my control surfaces (QCon Pro + Ex) with Reaper.
And I hope that you can give me pointers on how to set this up using CSI.

So, what would I ideally like to have:
- A tracking/mixing page that controls all mixer faders and pan knobs, and a transport. This is working great already.
- A page to control the sends for all tracks. This is working fine too, but optionally I would love to have a mode where I can control all sends of a single track on one page (similar to how Klinke does it).
Yes, the Klinke approach is frequently requested, and on the to do list.


Quote:
Originally Posted by dixo View Post
There are a small number of plugins that I include on almost every track (e.g. EQ, Compressor), and I would love to have separate pages to control these, using all widgets (faders, knobs, etc) and with the QCon LCD showing sensible info. These pages would ideally be accessible by a dedicated button on the QCon (e.g. one of the F1-F8 or the EQ button), but using NextPage is ok too for now. I am still very screen focused, so I would like the associated FX window to open on-screen when that page is selected, and close when the page is left. I have been experimenting to set this up, but so far it does not really work well, requiring mouse clicks in the FX list to open and select the FX to get the widgets to map. Maybe I don't understand the selection keywords (TrackOnSelection, MapTrackAndFXToWidgets, TrackOnFocusedFX, MapSingleFXToWidgetsForTrack) properly...
You need a button mapped to SetShowFXWindows -- see Console1.axt for example.

You will also still need a way to select the FX of interest, but this will get you part way there.

Quote:
Originally Posted by dixo View Post
For all other VSTs I would like to be able to map the parameters to the rotaries, and have two buttons to navigate through the FX list of the selected track, with its VST window opening on-screen when selected and the QCon LCD indicating the parameters controlled the knobs below, and maybe the name of the plugin too. The other widgets (e.g. faders etc.) should keep behaving as in the main mixer page, so this would be more like an overlay on the mixer page than a separate page.
There was some point in the thread where this was discussed, but I believe it was put on the backburner, is that right?
You can do that now -- would suggest using TrackOnSelection, see Console1.axt for a starting point.

Quote:
Originally Posted by dixo View Post
The way I set up most of my (recorded) tracks is with an EQ on top that does basic clean-up of the signal (e.g. high-pass to remove the extreme low-end). Later in the FX chain I will have another EQ to really shape the tone. If I use different EQ VSTs for that there is no problem with the .fxt mapping, but how can I handle for instance 2 ReaEQ's on the same track? Which one will be mapped, or is it random?
This is the one that's on the back burner -- we're talking matrix layout/navigation, and it was decided to wait until we can do a really good job, loads of forum discussion/design work needed.

Quote:
Originally Posted by dixo View Post
I also have a BCR2000, that I may want to use to map the most common VSTs to, but at the moment my desk is too small to conveniently place it, the QCon and EX already take all the space. So I would love to have everything available on the QCon and have the BCR as an add-on extra later.

So, would this be possible to achieve with the final CSI (I guess the answer is going to be 'yes' ), and how much is already possible?

Geoff: the new version you put up today behaves much nicer on the QCon w.r.t. the Time Display. All modes are now clearly readable and all 'stale' digits are cleared. Thank you so much!

A small feature request: how hard is it to create a 'JumpToPage <page name>' command in addition to the NextPage command?
I know that there has been talk that this should ideally be combined with the radio button mode, but even without that, and no LEDs to indicate the selected page I think it would already be very useful to have.

Thanks for all the great stuff so far, can't wait to see what else you have in store for us...
JumpToPage is planned, except it will be more like go to named page, so that you can do something like this in you .axt -- using the F buttons as an example:

F1 GoPage Track
F2 GoPage Sends
F3 GoPage EQ
...


Quote:
Originally Posted by dixo View Post
And: all the best for the new year!

Cheers,
Paul
Thanks -- you as well.
__________________
Groove is the subtle control of chaos -- Control Surface Integrator -- You can donate here: geoffwaddington.ca -- Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143 -- Pre alpha software: https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip
Geoff Waddington is online now   Reply With Quote
Old 01-01-2019, 07:59 AM   #2277
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 180
Default

Hi Geoff, Happy New Year! thanks for all your hard work over the old year- CSI is coming along great!

Thanks for confirming the master fader bug, I can stop scouring the setup files looking for errors now. As PoetandProphet doesn't seem to be affected by this, could it be something to do with the creation of new projects from scratch?

I've completed a lot of .fxt files now and they're working great (once i'd corrected all the mistakes )

Here's a few notes I made as I went along:

In Waves, most multi-position switches won't work with a rotary controller, although a switch will select the first and last positions.

In u-he DIVA and Repro, three position switches won't work with a rotary controller but 2,4 and greater are fine.

In Slate VCC and Trigger, out of range values from the controller crashes Reaper.

In Slate VBC, out of range values causes the on screen control to disappear (non-fatal).

Regarding stereo linking in VBC, this from the manual small print: "When Stereo Link is engaged, each control has its own automation lane. The Stereo Link only links control changes that are coming from the VBC GUI. The automation is managed by the host, and the plugin can't override it without any undefined side-effects." So it's definitely Slate, not CSI.

It's easy to miss if a plugin has a parameter name with a space at the end (Dynamic Spectrum Mapper , this means you!) This results in:-

Getting the parameter name wrong in the rotary assignment usually results in the wrong (random) parameter being controlled.

Forgetting to close the quotation marks on your alias name means the original name will be used.

Syntax errors in the .fxt can prevent Reaper from starting (ie crash on launch) or causing an error message regarding the odd termination of a C++ library (forgetting to close the quotation marks on a rotary parameter name with spaces causes this)

Flickering displays is a sure sign you have more than one widget assigned to the same parameter.

It is essential to comment out (/) any lines in the .fxt that aren't being used or chaos will ensue. I also comment out the blank lines I use to make the .fxt more readable.

I've been experimenting with using Pages to allow more than one C4 worth of parameters to be used (a ridiculously ambitious plan to map the u-he DIVA synth)

Essentially this involves creating a copy of the current Page, but changing the .fxt assignment to point to a different folder of .fxt files. These files contain the additional parameters for any given plugin.

This works, up to a point. It can take a bit of channel switching back and forth to get the second Page parameters to load, but once this happens you can switch between the two parameter sets easily.

I tried more than two pages but had problems with the Pages loading on NextPage press. On the button press the parameters wouldn't load to the surface and a further press would move on to the next Page's parameters. With 4 Pages, nothing I did would cause Page3 to load, so I stuck to 2)

It can get confused quite easily (and so can you) meaning a parameter set from a previous fx slot gets loaded instead of the one you were expecting. I think it needs a kind of "Synch Pages" fix but for FX slots rather than channels.

Obviously all this becomes unnecessary when we have layer navigation for the FX assignment.

+1 for direct Page navigation

All the best MM
MixMonkey is offline   Reply With Quote
Old 01-01-2019, 08:16 AM   #2278
spoon
Human being with feelings
 
spoon's Avatar
 
Join Date: Jul 2007
Location: Chicago
Posts: 198
Default

Quote:
Originally Posted by MixMonkey View Post
Hi Geoff, Happy New Year! thanks for all your hard work over the old year- CSI is coming along great!

Thanks for confirming the master fader bug, I can stop scouring the setup files looking for errors now. As PoetandProphet doesn't seem to be affected by this, could it be something to do with the creation of new projects from scratch?

<SNIP>
This is a great summary. Thanks for that.
Are you using a straight MCU or do you have other controllers you are mapping your FX to?
__________________
"I drank what?!?" - Socrates
spoon is online now   Reply With Quote
Old 01-01-2019, 08:18 AM   #2279
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 180
Default

Quote:
Originally Posted by spoon View Post
This is a great summary. Thanks for that.
Are you using a straight MCU or do you have other controllers you are mapping your FX to?
Thanks, mapping to a Mackie C4Pro.
MixMonkey is offline   Reply With Quote
Old 01-01-2019, 08:32 AM   #2280
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 180
Default

Oh, I nearly forgot.

If you want cross-platform compatibility for your .fxt files, make sure you use the Unix (LF) syntax for a new line, not the Windows (CRLF). This is more an issue for Windows to Mac, as Windows understands the Mac (Unix) LF, but Mac doesn't understand CRLF.

In short, if you create .fxt files in macOS Text Edit in plain text (not .rtf) it will work on Windows, but unless you select Unix for new line in Notepad++ (my preferred Win text editor) it won't be recognised on Mac.

Fortunately, Notepad++ lets you search and replace special characters, so you can batch process the whole lot
MixMonkey is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:07 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.