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

Reply
 
Thread Tools Display Modes
Old 02-08-2019, 12:15 PM   #2481
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 1,036
Default

Quote:
Originally Posted by Geoff Waddington View Post
You used the new CSI.ini and the new .axt files right ?
Yes, I replaced the CSI folder and .dll entirely. When I go to Pref>Cont/OSC/etc, CSI doesn't even show in the list.
__________________
https://www.kdubbproductions.com/
https://www.youtube.com/channel/UCpC...2dGA3qUWBKrXQQ
i7 8700k,4.9Ghz,Win10,Reaper 5,Motu 828es,MJE Hulk 990,GAP Pre73/EQ81
poetnprophet is offline   Reply With Quote
Old 02-08-2019, 12:49 PM   #2482
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by poetnprophet View Post
Yes, I replaced the CSI folder and .dll entirely. When I go to Pref>Cont/OSC/etc, CSI doesn't even show in the list.
You probably already did this, but... latest version of Reaper ?
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 12:53 PM   #2483
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 1,036
Default

I am on 5.94 or 5.95, I forget which exactly.
__________________
https://www.kdubbproductions.com/
https://www.youtube.com/channel/UCpC...2dGA3qUWBKrXQQ
i7 8700k,4.9Ghz,Win10,Reaper 5,Motu 828es,MJE Hulk 990,GAP Pre73/EQ81
poetnprophet is offline   Reply With Quote
Old 02-08-2019, 12:56 PM   #2484
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by poetnprophet View Post
I am on 5.94 or 5.95, I forget which exactly.
Try 5.965
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 03:05 PM   #2485
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Mostly working here

No displays on the 2 XTs (MCU is fine)

C4 plugin display and controls are muddled- all are shifted down by one row, with nothing showing on row A. Control mapping is scrambled.

Apart from these two things, all seems good. Channel functions, banking and transport all good.

Switching between Tracks and Sends Pages works fine and stays in sync. Stepping through Sends works fine. Haven't tried direct Page access yet, will report back when I have.

Master fader definition works, much better than pinning it.

Oh and my weird bank 1 right bug on MCU Rotary 1 has disappeared
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 03:23 PM   #2486
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Quote:
Originally Posted by MixMonkey View Post
There have been reports of failing/malfunctioning USB connections on the BCR2000, so you might end up on MIDI. It's a bit slower to send data when setting ip but doesn't seem to make any difference in actual use.
Ok, so back on topic, and after discovering my USB hub doesn't play nice with MIDI devices, I now understand all the resource files and also the BC Man config.

The FX mappings are working great, but for me the Channel mappings are not working as expected.

In the MIDI log I see the following when pressing button 1 on the top row:

IN -> r 90 08 00
IN -> r 90 08 7f

Seems that should be mapping to TrackSolo according to the .rst and .axt files, but it's not activating solo.

Looking really good though, thanks once again for all the hard work.

I don't know if any kind of automap functionality has been discussed for FX. Klinke's plugin does this of course, and it matches the order of params visible when you turn off the FX UI and just see faders.

Would be a nice way to tinker with those old VST synths with 100s of params straight out of the box.
jamesd256 is offline   Reply With Quote
Old 02-08-2019, 03:31 PM   #2487
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
Mostly working here
Great, that was a major refactor.

Quote:
Originally Posted by MixMonkey View Post
No displays on the 2 XTs (MCU is fine)
DOH, my bad, cut and paste error.

Change:

Code:
DisplayUpper1 MCUDisplayUpper 0
DisplayUpper2 MCUDisplayUpper 1
DisplayUpper3 MCUDisplayUpper 2
DisplayUpper4 MCUDisplayUpper 3
DisplayUpper5 MCUDisplayUpper 4
DisplayUpper6 MCUDisplayUpper 5
DisplayUpper7 MCUDisplayUpper 6
DisplayUpper8 MCUDisplayUpper 7

DisplayLower1 MCUDisplayLower 0
DisplayLower2 MCUDisplayLower 1
DisplayLower3 MCUDisplayLower 2
DisplayLower4 MCUDisplayLower 3
DisplayLower5 MCUDisplayLower 4
DisplayLower6 MCUDisplayLower 5
DisplayLower7 MCUDisplayLower 6
DisplayLower8 MCUDisplayLower 7

to:

Code:
DisplayUpper1 MCUXTDisplayUpper 0
DisplayUpper2 MCUXTDisplayUpper 1
DisplayUpper3 MCUXTDisplayUpper 2
DisplayUpper4 MCUXTDisplayUpper 3
DisplayUpper5 MCUXTDisplayUpper 4
DisplayUpper6 MCUXTDisplayUpper 5
DisplayUpper7 MCUXTDisplayUpper 6
DisplayUpper8 MCUXTDisplayUpper 7

DisplayLower1 MCUXTDisplayLower 0
DisplayLower2 MCUXTDisplayLower 1
DisplayLower3 MCUXTDisplayLower 2
DisplayLower4 MCUXTDisplayLower 3
DisplayLower5 MCUXTDisplayLower 4
DisplayLower6 MCUXTDisplayLower 5
DisplayLower7 MCUXTDisplayLower 6
DisplayLower8 MCUXTDisplayLower 7

Quote:
Originally Posted by MixMonkey View Post
C4 plugin display and controls are muddled- all are shifted down by one row, with nothing showing on row A. Control mapping is scrambled.
Try these lines instead:

Code:
DisplayUpperA1 	C4DisplayUpper 0 0
DisplayUpperA2 	C4DisplayUpper 0 1
DisplayUpperA3 	C4DisplayUpper 0 2
DisplayUpperA4 	C4DisplayUpper 0 3
DisplayUpperA5 	C4DisplayUpper 0 4
DisplayUpperA6 	C4DisplayUpper 0 5
DisplayUpperA7 	C4DisplayUpper 0 6
DisplayUpperA8 	C4DisplayUpper 0 7

DisplayLowerA1	C4DisplayLower 0 0
DisplayLowerA2	C4DisplayLower 0 1
DisplayLowerA3	C4DisplayLower 0 2
DisplayLowerA4	C4DisplayLower 0 3
DisplayLowerA5	C4DisplayLower 0 4
DisplayLowerA6	C4DisplayLower 0 5
DisplayLowerA7	C4DisplayLower 0 6
DisplayLowerA8	C4DisplayLower 0 7

DisplayUpperB1 	C4DisplayUpper 1 0
DisplayUpperB2 	C4DisplayUpper 1 1
DisplayUpperB3 	C4DisplayUpper 1 2
DisplayUpperB4 	C4DisplayUpper 1 3
DisplayUpperB5 	C4DisplayUpper 1 4
DisplayUpperB6 	C4DisplayUpper 1 5
DisplayUpperB7 	C4DisplayUpper 1 6
DisplayUpperB8 	C4DisplayUpper 1 7

DisplayLowerB1	C4DisplayLower 1 0
DisplayLowerB2	C4DisplayLower 1 1
DisplayLowerB3	C4DisplayLower 1 2
DisplayLowerB4	C4DisplayLower 1 3
DisplayLowerB5	C4DisplayLower 1 4
DisplayLowerB6	C4DisplayLower 1 5
DisplayLowerB7	C4DisplayLower 1 6
DisplayLowerB8	C4DisplayLower 1 7

DisplayUpperC1 	C4DisplayUpper 2 0
DisplayUpperC2 	C4DisplayUpper 2 1
DisplayUpperC3 	C4DisplayUpper 2 2
DisplayUpperC4 	C4DisplayUpper 2 3
DisplayUpperC5 	C4DisplayUpper 2 4
DisplayUpperC6 	C4DisplayUpper 2 5
DisplayUpperC7 	C4DisplayUpper 2 6
DisplayUpperC8 	C4DisplayUpper 2 7

DisplayLowerC1	C4DisplayLower 2 0
DisplayLowerC2	C4DisplayLower 2 1
DisplayLowerC3	C4DisplayLower 2 2
DisplayLowerC4	C4DisplayLower 2 3
DisplayLowerC5	C4DisplayLower 2 4
DisplayLowerC6	C4DisplayLower 2 5
DisplayLowerC7	C4DisplayLower 2 6
DisplayLowerC8	C4DisplayLower 2 7

DisplayUpperD1 	C4DisplayUpper 3 0
DisplayUpperD2 	C4DisplayUpper 3 1
DisplayUpperD3 	C4DisplayUpper 3 2
DisplayUpperD4 	C4DisplayUpper 3 3
DisplayUpperD5 	C4DisplayUpper 3 4
DisplayUpperD6 	C4DisplayUpper 3 5
DisplayUpperD7 	C4DisplayUpper 3 6
DisplayUpperD8 	C4DisplayUpper 3 7

DisplayLowerD1	C4DisplayLower 3 0
DisplayLowerD2	C4DisplayLower 3 1
DisplayLowerD3	C4DisplayLower 3 2
DisplayLowerD4	C4DisplayLower 3 3
DisplayLowerD5	C4DisplayLower 3 4
DisplayLowerD6	C4DisplayLower 3 5
DisplayLowerD7	C4DisplayLower 3 6
DisplayLowerD8	C4DisplayLower 3 7
Quote:
Originally Posted by MixMonkey View Post
Apart from these two things, all seems good. Channel functions, banking and transport all good.

Switching between Tracks and Sends Pages works fine and stays in sync. Stepping through Sends works fine. Haven't tried direct Page access yet, will report back when I have.

Master fader definition works, much better than pinning it.

Oh and my weird bank 1 right bug on MCU Rotary 1 has disappeared
All good, thanks for testing.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 03:42 PM   #2488
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Ok, so back on topic, and after discovering my USB hub doesn't play nice with MIDI devices, I now understand all the resource files and also the BC Man config.

The FX mappings are working great, but for me the Channel mappings are not working as expected.

In the MIDI log I see the following when pressing button 1 on the top row:

IN -> r 90 08 00
IN -> r 90 08 7f

Seems that should be mapping to TrackSolo according to the .rst and .axt files, but it's not activating solo.

Looking really good though, thanks once again for all the hard work.

I don't know if any kind of automap functionality has been discussed for FX. Klinke's plugin does this of course, and it matches the order of params visible when you turn off the FX UI and just see faders.

Would be a nice way to tinker with those old VST synths with 100s of params straight out of the box.
TrackSolo needs to be in a Channel/ChannelEnd block in the .rst:

Channel
TrackSolo PressFB 90 08 7f 90 08 00
ChannelEnd


If you have the software posted yesterday the channel concept has been moved to the .axt file.

BankableChannel
TrackSolo TrackSolo
BankableChannelEnd


Automap discussion has been touched upon, but as you say, it's most useful for tinkering around.

So, it's possible it will get done, but it's currently lower priority.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 03:45 PM   #2489
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

i'm pretty sure Jamesd256 is using the previous CSI build (hope so, I haven't had a chance to re-do the BCR Mapping yet )
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 04:13 PM   #2490
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
i'm pretty sure Jamesd256 is using the previous CSI build (hope so, I haven't had a chance to re-do the BCR Mapping yet )
Cool, did you try the XT and C4 corrections posted a couple back ?
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 04:20 PM   #2491
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Quote:
Originally Posted by Geoff Waddington View Post
TrackSolo needs to be in a Channel/ChannelEnd block in the .rst:

Channel
TrackSolo PressFB 90 08 7f 90 08 00
ChannelEnd


If you have the software posted yesterday the channel concept has been moved to the .axt file.

BankableChannel
TrackSolo TrackSolo
BankableChannelEnd


Automap discussion has been touched upon, but as you say, it's most useful for tinkering around.

So, it's possible it will get done, but it's currently lower priority.

Great to hear about automap down the road some time.

I'm working from MixMonkey's very generous effort to create a prototype BCR config, and against the previous release of CSI, which was current when the BCR stuff was done

Just the relevent bits

.rst has

Channel
...
Solo PressReleaseFB 90 08 7f 90 08 00
...
ChannelEnd

And the .axt has:

Solo TrackSolo

So it looks correct, and the controller addressing is matching what's displayed in the console log (I assume the label for the mapping in the .rst is freeform)
jamesd256 is offline   Reply With Quote
Old 02-08-2019, 04:26 PM   #2492
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Cool, did you try the XT and C4 corrections posted a couple back ?
Just finishing me pizza, then i'll be right on it
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 04:31 PM   #2493
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by jamesd256 View Post
I assume the label for the mapping in the .rst is freeform
It is, and after i'd finished it I wished I'd used generic names, which though less specific, would have made the CSI structure easier to understand.

After I've typed in Geoff's corrections, I'll get on with producing a version of the BCR map that'll work with the latest version (that WILL have generic names and will also have a new sysex to load)
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 04:56 PM   #2494
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Try these lines instead:
XT and C4 displays now working normally

C4 controls still messed up (all fxts), all Rotaries seem to control RotaryA1.

Also seem to have the MCU USB driver crash on Reaper quit, forcing a restart. Will try Mac to see if it's a Windows thing...
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 05:58 PM   #2495
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
XT and C4 displays now working normally
Excellent !!

Quote:
Originally Posted by MixMonkey View Post
Also seem to have the MCU USB driver crash on Reaper quit, forcing a restart. Will try Mac to see if it's a Windows thing...
Cool, let me know what you find.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143

Last edited by Geoff Waddington; 02-08-2019 at 06:23 PM.
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 06:22 PM   #2496
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
C4 controls still messed up (all fxts), all Rotaries seem to control RotaryA1.
Ah, yes, yet another mapping bug, try this:

Code:
RotaryA1 	EncoderFB b0 20 7f  b0 20 00
RotaryA2 	EncoderFB b0 21 7f  b0 21 00	
RotaryA3 	EncoderFB b0 22 7f  b0 22 00	
RotaryA4 	EncoderFB b0 23 7f  b0 23 00	
RotaryA5 	EncoderFB b0 24 7f  b0 24 00	
RotaryA6 	EncoderFB b0 25 7f  b0 25 00	
RotaryA7 	EncoderFB b0 26 7f  b0 26 00	
RotaryA8 	EncoderFB b0 27 7f  b0 27 00	

RotaryB1 	EncoderFB b0 28 7f  b0 28 00	
RotaryB2 	EncoderFB b0 29 7f  b0 29 00	
RotaryB3 	EncoderFB b0 2a 7f  b0 2a 00	
RotaryB4 	EncoderFB b0 2b 7f  b0 2b 00	
RotaryB5 	EncoderFB b0 2c 7f  b0 2c 00	
RotaryB6 	EncoderFB b0 2d 7f  b0 2d 00	
RotaryB7 	EncoderFB b0 2e 7f  b0 2e 00	
RotaryB8 	EncoderFB b0 2f 7f  b0 2f 00	

RotaryC1 	EncoderFB b0 30 7f  b0 30 00	
RotaryC2 	EncoderFB b0 31 7f  b0 31 00	
RotaryC3 	EncoderFB b0 32 7f  b0 32 00	
RotaryC4 	EncoderFB b0 33 7f  b0 33 00	
RotaryC5 	EncoderFB b0 34 7f  b0 34 00	
RotaryC6 	EncoderFB b0 35 7f  b0 35 00	
RotaryC7 	EncoderFB b0 36 7f  b0 36 00	
RotaryC8 	EncoderFB b0 37 7f  b0 37 00	

RotaryD1 	EncoderFB b0 38 7f  b0 38 00	
RotaryD2 	EncoderFB b0 39 7f  b0 39 00	
RotaryD3 	EncoderFB b0 3a 7f  b0 3a 00	
RotaryD4 	EncoderFB b0 3b 7f  b0 3b 00	
RotaryD5 	EncoderFB b0 3c 7f  b0 3c 00	
RotaryD6 	EncoderFB b0 3d 7f  b0 3d 00	
RotaryD7 	EncoderFB b0 3e 7f  b0 3e 00	
RotaryD8 	EncoderFB b0 3f 7f  b0 3f 00
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-08-2019, 07:01 PM   #2497
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Ah, yes, yet another mapping bug, try this:
No joy this time i'm afraid.

Original .rst:

RotaryA EncoderFB b0 00 7f b0 00 00
RotaryB EncoderFB b0 08 7f b0 08 00
RotaryC EncoderFB b0 10 7f b0 10 00
RotaryD EncoderFB b0 18 7f b0 18 00

So the original .mst looked right (to me)
MixMonkey is offline   Reply With Quote
Old 02-08-2019, 07:39 PM   #2498
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
No joy this time i'm afraid.

Original .rst:

RotaryA EncoderFB b0 00 7f b0 00 00
RotaryB EncoderFB b0 08 7f b0 08 00
RotaryC EncoderFB b0 10 7f b0 10 00
RotaryD EncoderFB b0 18 7f b0 18 00

So the original .mst looked right (to me)
Yup, my bad, the original is right, got fooled by the LED ring code, which is very similar, but is offset by 20 hex.

Confused as to why this doesn't work, the rotaries work fine on the MCU and XT's right ?

Do the C4 rotaries look right with midi in monitor on ?
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143

Last edited by Geoff Waddington; 02-09-2019 at 05:09 AM.
Geoff Waddington is offline   Reply With Quote
Old 02-09-2019, 06:55 AM   #2499
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Confused as to why this doesn't work, the rotaries work fine on the MCU and XT's right ?

Do the C4 rotaries look right with midi in monitor on ?
Rotaries on the MCU and XTs are fine (pan/width). C4 output in MIDI monitor corresponds with mst.

Have work to attend to today and tomorrow, back on the case on Monday
MixMonkey is offline   Reply With Quote
Old 02-09-2019, 07:00 AM   #2500
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

OK, preliminary thoughts re: Zones.

This is just Saturday morning rambling so feel free to say, "that's the stupidest thing I've ever heard of "

Currently we have in the .axt:

Code:
BankableChannel
VUMeter1 TrackOutputMeter 0
DisplayUpper1 TrackNameDisplay
DisplayLower1 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader1 TrackVolume
FaderTouch1 TrackTouch
Rotary1 TrackCycle RotaryPush1 "TrackPan 0" "TrackPanWidth 1"
Select1 TrackUniqueSelect
Shift+Select1 TrackRangeSelect
Control+Select1 TrackSelect
RecordArm1 TrackRecordArm
Mute1 TrackMute
Solo1 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter2 TrackOutputMeter 0
DisplayUpper2 TrackNameDisplay
DisplayLower2 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader2 TrackVolume
FaderTouch2 TrackTouch
Rotary2 TrackCycle RotaryPush2 "TrackPan 0" "TrackPanWidth 1"
Select2 TrackUniqueSelect
Shift+Select2 TrackRangeSelect
Control+Select2 TrackSelect
RecordArm2 TrackRecordArm
Mute2 TrackMute
Solo2 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter3 TrackOutputMeter 0
DisplayUpper3 TrackNameDisplay
DisplayLower3 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader3 TrackVolume
FaderTouch3 TrackTouch
Rotary3 TrackCycle RotaryPush3 "TrackPan 0" "TrackPanWidth 1"
Select3 TrackUniqueSelect
Shift+Select3 TrackRangeSelect
Control+Select3 TrackSelect
RecordArm3 TrackRecordArm
Mute3 TrackMute
Solo3 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter4 TrackOutputMeter 0
DisplayUpper4 TrackNameDisplay
DisplayLower4 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader4 TrackVolume
FaderTouch4 TrackTouch
Rotary4 TrackCycle RotaryPush4 "TrackPan 0" "TrackPanWidth 1"
Select4 TrackUniqueSelect
Shift+Select4 TrackRangeSelect
Control+Select4 TrackSelect
RecordArm4 TrackRecordArm
Mute4 TrackMute
Solo4 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter5 TrackOutputMeter 0
DisplayUpper5 TrackNameDisplay
DisplayLower5 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader5 TrackVolume
FaderTouch5 TrackTouch
Rotary5 TrackCycle RotaryPush5 "TrackPan 0" "TrackPanWidth 1"
Select5 TrackUniqueSelect
Shift+Select5 TrackRangeSelect
Control+Select5 TrackSelect
RecordArm5 TrackRecordArm
Mute5 TrackMute
Solo5 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter6 TrackOutputMeter 0
DisplayUpper6 TrackNameDisplay
DisplayLower6 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader6 TrackVolume
FaderTouch6 TrackTouch
Rotary6 TrackCycle RotaryPush6 "TrackPan 0" "TrackPanWidth 1"
Select6 TrackUniqueSelect
Shift+Select6 TrackRangeSelect
Control+Select6 TrackSelect
RecordArm6 TrackRecordArm
Mute6 TrackMute
Solo6 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter7 TrackOutputMeter 0
DisplayUpper7 TrackNameDisplay
DisplayLower7 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader7 TrackVolume
FaderTouch7 TrackTouch
Rotary7 TrackCycle RotaryPush7 "TrackPan 0" "TrackPanWidth 1"
Select7 TrackUniqueSelect
Shift+Select7 TrackRangeSelect
Control+Select7 TrackSelect
RecordArm7 TrackRecordArm
Mute7 TrackMute
Solo7 TrackSolo
BankableChannelEnd

BankableChannel
VUMeter8 TrackOutputMeter 0
DisplayUpper8 TrackNameDisplay
DisplayLower8 TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
Fader8 TrackVolume
FaderTouch8 TrackTouch
Rotary8 TrackCycle RotaryPush8 "TrackPan 0" "TrackPanWidth 1"
Select8 TrackUniqueSelect
Shift+Select8 TrackRangeSelect
Control+Select8 TrackSelect
RecordArm8 TrackRecordArm
Mute8 TrackMute
Solo8 TrackSolo
BankableChannelEnd
To me, this is confusing, because it is actually 3 concepts rolled into one:

Describes Widget -> Action
Describes which Widgets make up a given Channel
Implicitly describes the Channel count

Let's trade some verbosity for clarity, modularization, etc.

First the Widget -> Action:

Code:
ActionZone TrackOutputMeter 0
VUMeter1
VUMeter2
VUMeter3
VUMeter4
VUMeter5
VUMeter6
VUMeter7
VUMeter8
ActionZoneEnd

ActionZone TrackNameDisplay
DisplayUpper1
DisplayUpper2
DisplayUpper3
DisplayUpper4
DisplayUpper5
DisplayUpper6
DisplayUpper7
DisplayUpper8
ActionZoneEnd

ActionZone TrackTouchControlled TrackPanDisplay TrackVolumeDisplay
DisplayLower1
DisplayLower2
DisplayLower3
DisplayLower4
DisplayLower5
DisplayLower6
DisplayLower7
DisplayLower8
ActionZoneEnd

ActionZone TrackVolume
Fader1
Fader2
Fader3
Fader4
Fader5
Fader6
Fader7
Fader8
ActionZoneEnd

ActionZone TrackTouch
FaderTouch1
FaderTouch2
FaderTouch3
FaderTouch4
FaderTouch5
FaderTouch6
FaderTouch7
FaderTouch8
ActionZoneEnd

ActionZone TrackCycle "TrackPan 0" "TrackPanWidth 1"
Rotary1 RotaryPush1
Rotary2 RotaryPush2
Rotary3 RotaryPush3
Rotary4 RotaryPush4
Rotary5 RotaryPush5
Rotary6 RotaryPush6
Rotary7 RotaryPush7
Rotary8 RotaryPush8
ActionZoneEnd

ActionZone TrackUniqueSelect
Select1
Select2
Select3
Select4
Select5
Select6
Select7
Select8
ActionZoneEnd

ActionZone TrackRangeSelect
Shift+Select1
Shift+Select2
Shift+Select3
Shift+Select4
Shift+Select5
Shift+Select6
Shift+Select7
Shift+Select8
ActionZoneEnd

ActionZone TrackSelect
Control+Select1
Control+Select2
Control+Select3
Control+Select4
Control+Select5
Control+Select6
Control+Select7
Control+Select8
ActionZoneEnd

ActionZone TrackRecordArm
RecordArm1
RecordArm2
RecordArm3
RecordArm4
RecordArm5
RecordArm6
RecordArm7
RecordArm8
ActionZoneEnd

ActionZone TrackMute
Mute1
Mute2
Mute3
Mute4
Mute5
Mute6
Mute7
Mute8
ActionZoneEnd

ActionZone TrackSolo
Solo1
Solo2
Solo3
Solo4
Solo5
Solo6
Solo7
Solo8
ActionZoneEnd
Now we need to describe which Widgets make up a given Channel :

Code:
ChannelZone Channel1
VUMeter1
DisplayUpper1
DisplayLower1
Fader1
FaderTouch1
Rotary1
Select1
Shift+Select1
Control+Select1
RecordArm1
Mute1
Solo1
ChannelZoneEnd 

ChannelZone Channel2
VUMeter2
DisplayUpper2
DisplayLower2
Fader2
FaderTouch2
Rotary2
Select2
Shift+Select2
Control+Select2
RecordArm2
Mute2
Solo2
ChannelZoneEnd 

ChannelZone Channel3
VUMeter3
DisplayUpper3
DisplayLower3
Fader3
FaderTouch3
Rotary3
Select3
Shift+Select3
Control+Select3
RecordArm3
Mute3
Solo3
ChannelZoneEnd 

ChannelZone Channel4
VUMeter4
DisplayUpper4
DisplayLower4
Fader4
FaderTouch4
Rotary4
Select4
Shift+Select4
Control+Select4
RecordArm4
Mute4
Solo4
ChannelZoneEnd 

ChannelZone Channel5
VUMeter5
DisplayUpper5
DisplayLower5
Fader5
FaderTouch5
Rotary5
Select5
Shift+Select5
Control+Select5
RecordArm5
Mute5
Solo5
ChannelZoneEnd 

ChannelZone Channel6
VUMeter6
DisplayUpper6
DisplayLower6
Fader6
FaderTouch6
Rotary6
Select6
Shift+Select6
Control+Select6
RecordArm6
Mute6
Solo6
ChannelZoneEnd 

ChannelZone Channel7
VUMeter7
DisplayUpper7
DisplayLower7
Fader7
FaderTouch7
Rotary7
Select7
Shift+Select7
Control+Select7
RecordArm7
Mute7
Solo7
ChannelZoneEnd 

ChannelZone Channel8
VUMeter8
DisplayUpper8
DisplayLower8
Fader8
FaderTouch8
Rotary8
Select8
Shift+Select8
Control+Select8
RecordArm8
Mute8
Solo8
ChannelZoneEnd
Now let's put the Channels in a Track Navigation Zone:

Code:
NavigationZone Track
Channel1
Channel2
Channel3
Channel4
Channel5
Channel6
Channel7
Channel8
NavigationZoneEnd

Though more verbose, i think it is actually a lot easier to read and understand -- at least IMHO.

The modularity allows for very creative combing.

Since the Zones tend to be generic, they could be shared cross-control surface, likely with little or no modification.

Indeed, even locally, you probably will make a workflow, and use pieces over and over with cut and paste style ease of use.

What do you think ?
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-09-2019, 02:14 PM   #2501
poetnprophet
Human being with feelings
 
poetnprophet's Avatar
 
Join Date: Jan 2018
Posts: 1,036
Default

Quote:
Originally Posted by Geoff Waddington View Post
Try 5.965
well i updated and now lost sws and can't get it back, sheesh!
__________________
https://www.kdubbproductions.com/
https://www.youtube.com/channel/UCpC...2dGA3qUWBKrXQQ
i7 8700k,4.9Ghz,Win10,Reaper 5,Motu 828es,MJE Hulk 990,GAP Pre73/EQ81
poetnprophet is offline   Reply With Quote
Old 02-09-2019, 03:40 PM   #2502
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Have a portable instance now running 5.965 and the latest CSI download

My aim will be to contribute towards beta testing the releases here on. I have a BCF which is in MCU Sonar mode, and this banged up old BCR setup with MixMonkey's sysex/patch. I will happily take on maintenance of the BCR config started by Mix as I have the unit and am motivated to get it working.

The BCF/MCU is working out of the box with the latest release, however the midi log is
spewing messages like these pretty hard and non-stop:

OUT -> BCF d0 80000010 00
OUT -> BCF d0 80000010 00

Also when used alone, the BCR is working as before. I simply migrated the .rst to an .mst and left everything else the same.

The two don't play nice together. With both enabled, one or neither works.

Is there a log file I can read to help diagnose?

Edit: I say the BCR is working as before, and this includes not working on startup, working once then not even showing midi logging, then after re-adding, showing midi logging but not working.
Edit 2: and for the BCF, at this stage I'm calling it working if the track level and pan work correctly, haven't got anywhere near the other stuff

Last edited by jamesd256; 02-09-2019 at 03:49 PM.
jamesd256 is offline   Reply With Quote
Old 02-10-2019, 10:30 AM   #2503
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Have a portable instance now running 5.965 and the latest CSI download

My aim will be to contribute towards beta testing the releases here on. I have a BCF which is in MCU Sonar mode, and this banged up old BCR setup with MixMonkey's sysex/patch. I will happily take on maintenance of the BCR config started by Mix as I have the unit and am motivated to get it working.
Great news, welcome to the group !

Quote:
Originally Posted by jamesd256 View Post
The BCF/MCU is working out of the box with the latest release, however the midi log is
spewing messages like these pretty hard and non-stop:

OUT -> BCF d0 80000010 00
OUT -> BCF d0 80000010 00
Those are the VU meters, to disable them, In the .mst change these:

Code:
VUMeter1      MCUVUMeter 0
VUMeter2      MCUVUMeter 1
VUMeter3      MCUVUMeter 2
VUMeter4      MCUVUMeter 3
VUMeter5      MCUVUMeter 4
VUMeter6      MCUVUMeter 5
VUMeter7      MCUVUMeter 6
VUMeter8      MCUVUMeter 7
to:
Code:
/VUMeter1      MCUVUMeter 0
/VUMeter2      MCUVUMeter 1
/VUMeter3      MCUVUMeter 2
/VUMeter4      MCUVUMeter 3
/VUMeter5      MCUVUMeter 4
/VUMeter6      MCUVUMeter 5
/VUMeter7      MCUVUMeter 6
/VUMeter8      MCUVUMeter 7

Quote:
Originally Posted by jamesd256 View Post
Also when used alone, the BCR is working as before. I simply migrated the .rst to an .mst and left everything else the same.

The two don't play nice together. With both enabled, one or neither works.

Is there a log file I can read to help diagnose?

Edit: I say the BCR is working as before, and this includes not working on startup, working once then not even showing midi logging, then after re-adding, showing midi logging but not working.
Edit 2: and for the BCF, at this stage I'm calling it working if the track level and pan work correctly, haven't got anywhere near the other stuff
Please just post your CSI.ini file contents here, might be something we can catch by looking at that file.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-10-2019, 11:43 AM   #2504
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Thanks Geoff, I see about the VU data. I might see about how to use that on some encoder LEDS.

Everything is working on startup now. Seems the issue was changing stuff via preferences didn't leave CSI able to get the messages through, at least on the BCR.

Things seem ok when Reaper starts with the desired config.

FYI Right now I have this CSI.ini:

MidiInMonitor On
MidiOutMonitor On
VSTMonitor On

Page GreenPage FollowMCP NoSynchPages NoTrackColoring 75 255 166
MidiSurface BCR 1 2 BCR2000.mst BCR2000.axt BCR2000
MidiSurface BCF 0 1 MCU.mst MCU.axt MCU

Is there support for long press now or planned?

What are your thoughts on elegant track folder navigation? Klinke's folder mode is good but not perfect for me. I like that the CSI MCU follows the Mixer view, but showing only tracks in a folder and having a way to drill in and out would also be good (I can see mapping a button to 40080: "Mixer: Toggle show folder tracks in mixer" would be a start)

Edit: I spoke too soon. My test project has a ReaComp and a ReaEQ, and after some messing around for a bit, I found that again, ReaComp wasn't responding to the BCR when focused. But unlike before I had also enabled a ReaEQ, and found that this was still responding. Restarting Reaper doesn't change anything. In fact it's back to yesterday, where whatever I do, including removing the CSI instance, the ReaComp doesn't respond, even though I can see the correct controller data logged. At least now I know it's just ReaComp

Last edited by jamesd256; 02-10-2019 at 12:01 PM.
jamesd256 is offline   Reply With Quote
Old 02-10-2019, 02:01 PM   #2505
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Thanks Geoff, I see about the VU data. I might see about how to use that on some encoder LEDS.

Everything is working on startup now. Seems the issue was changing stuff via preferences didn't leave CSI able to get the messages through, at least on the BCR.

Things seem ok when Reaper starts with the desired config.

FYI Right now I have this CSI.ini:

MidiInMonitor On
MidiOutMonitor On
VSTMonitor On

Page GreenPage FollowMCP NoSynchPages NoTrackColoring 75 255 166
MidiSurface BCR 1 2 BCR2000.mst BCR2000.axt BCR2000
MidiSurface BCF 0 1 MCU.mst MCU.axt MCU
Midi/VST monitoring adversely affects performance, I would turn it off unless needed for debugging, or learning the names of VST params.


Quote:
Originally Posted by jamesd256 View Post
Is there support for long press now or planned?
Yup, just like you can use Shift+SomeButton, you can use Hold+Somebutton.

Quote:
Originally Posted by jamesd256 View Post
What are your thoughts on elegant track folder navigation? Klinke's folder mode is good but not perfect for me. I like that the CSI MCU follows the Mixer view, but showing only tracks in a folder and having a way to drill in and out would also be good (I can see mapping a button to 40080: "Mixer: Toggle show folder tracks in mixer" would be a start)
Definitely planned, but have not not much in depth thinking yet

CSI can follow Track or Mixer, it's set in the Page config -- more options planned for later.

For now, at least you can map that Reaper Action, it's a start
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 06:30 AM   #2506
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Quote:
Originally Posted by Geoff Waddington View Post
OK, preliminary thoughts re: Zones.

This is just Saturday morning rambling so feel free to say, "that's the stupidest thing I've ever heard of "

What do you think ?
Still getting up to speed with your new abstraction, but if I understand your comments about sharing, as things are today, this would be via copy/paste?

Any thoughts about having action file that could reference actions from multiple surface files? Let's say I want to use a padkontrol for the MCU modifier keys for example. Maybe a namespace prefix from whatever surface the widget lives on?

Incidentally, do you have support for modifier combinations, so;

shift+option+action

Is there a list of inbuilt actions somewhere?

The questions will reduce in frequency and become progressively less stupid as we go along.
jamesd256 is offline   Reply With Quote
Old 02-11-2019, 07:07 AM   #2507
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

New BCR2000 setup available for download:https://stash.reaper.fm/v/35379/BCR2000mk2.zip

Mk2 is compatible with the latest build of CSI.

If you are using the mk1 version, you should replace ALL the BCR2000 files within the CSI folder, as mk2 is in no way compatible with mk1!

A new sysex file is in the ZIP to setup your BCR2000 for the new version.
MixMonkey is offline   Reply With Quote
Old 02-11-2019, 07:37 AM   #2508
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
What do you think ?
I like this (I think..)

So now we have 3 separate definitions for the .axt: ActionZone, ChannelZone and NavigationZone.

Does the NavigationZone define which Channels are Bankable, Stepable or Drillable (X,Y,Z)?

I wonder whether the word 'Channel' is a bit specific. In your example it's completely appropriate, but conceivably it could represent a collection of widgets on a C4 surface that don't Bank or Step, but only Drill. When I read Channel, I immediately think 'vertical strip'.
MixMonkey is offline   Reply With Quote
Old 02-11-2019, 07:56 AM   #2509
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Just corrected a mistake in the BCR2000mk2.mst contained in the download.

I don't think it affected the functionality but if you downloaded mk2 already, you should probably do so again. Only BCR2000mk2.mst was affected. Sorry for the inconvenience
MixMonkey is offline   Reply With Quote
Old 02-11-2019, 08:05 AM   #2510
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Still getting up to speed with your new abstraction, but if I understand your comments about sharing, as things are today, this would be via copy/paste?
Yup.

Quote:
Originally Posted by jamesd256 View Post
Any thoughts about having action file that could reference actions from multiple surface files? Let's say I want to use a padkontrol for the MCU modifier keys for example. Maybe a namespace prefix from whatever surface the widget lives on?

Incidentally, do you have support for modifier combinations, so;

shift+option+action

Yeah, that turns out to be a tricky little design problem.

If you allow for a button on one surface to be used as a modifier on another via a prefix, as you say, this is possible.

However that introduces an unwanted dependency between files -- the prefix surface must exist, things fall apart if it doesn't.

Instead we opted for global modifiers, here are the ones currently available:

Shift
Option
Control
Alt

So in your .rst file you must designate some or all of the above, obviously the more buttons you can spare to allocate from the surface the more combinations you get, so let's say you can allocate all 4 buttons it will look something like this, although your midi numbers may be different:

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

Now you can use them like this in an .axt file:

Save Reaper 40026 // Save
Shift+Save Reaper 40022 // Save As

Select6 TrackUniqueSelect
Shift+Select6 TrackRangeSelect
Control+Select6 TrackSelect

etc.

You can use combos a la:

Shift+Control+Option+Alt+SomeButton SomeAction

etc., but note that Shift+Control is the same as Control+Shift


There are also some other modifiers:

Toggle - does opposite of last press

Invert - on is off and off is on -- e.g. Reaper EQ FX bypass On means control surface EQ Active light should be Off

Hold - 1 second long press


Quote:
Originally Posted by jamesd256 View Post
Is there a list of inbuilt actions somewhere?

The questions will reduce in frequency and become progressively less stupid as we go along.
It's actually the lack of documentation on this end that's the problem
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 08:07 AM   #2511
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
Just corrected a mistake in the BCR2000mk2.mst contained in the download.

I don't think it affected the functionality but if you downloaded mk2 already, you should probably do so again. Only BCR2000mk2.mst was affected. Sorry for the inconvenience
Thanks, as usual, for the great work !
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 08:14 AM   #2512
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yup, my bad, the original is right, got fooled by the LED ring code, which is very similar, but is offset by 20 hex.

Confused as to why this doesn't work, the rotaries work fine on the MCU and XT's right ?

Do the C4 rotaries look right with midi in monitor on ?
I think the refactoring may have introduced a bug that causes issues when b0 00 is used in the .mst definition.

This turned up when I was writing the BCR2000mk2.mst. When I started the Rotary controller codes from b0 00, the only rotary control that worked properly was b0 00 and all the other rotary controls were somehow mapped to the same action as the first (b0 00) control.

When I started the controller codes from b0 01 everything worked as expected.

I believe this to be the cause of the C4 problems. Its rotary controller codes begin from b0 00 as well.
MixMonkey is offline   Reply With Quote
Old 02-11-2019, 08:16 AM   #2513
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
I like this (I think..)

So now we have 3 separate definitions for the .axt: ActionZone, ChannelZone and NavigationZone.
Yes.

Quote:
Originally Posted by MixMonkey View Post
Does the NavigationZone define which Channels are Bankable, Stepable or Drillable (X,Y,Z)?

I wonder whether the word 'Channel' is a bit specific. In your example it's completely appropriate, but conceivably it could represent a collection of widgets on a C4 surface that don't Bank or Step, but only Drill. When I read Channel, I immediately think 'vertical strip'.
Good Point, let's rename ChannelZone to Zone

The fact the the NavigationZone is of type Track will sort out which direction, presumably we'll have:

NavigationZone Track
NavigationZone Slot
NavigationZone Dril

and perhaps others as well, still very preliminary thus far.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 09:16 AM   #2514
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Quote:
Originally Posted by MixMonkey View Post
Just corrected a mistake in the BCR2000mk2.mst contained in the download.
Thanks for the quick update, will try it out tomorrow night.

Quote:
Originally Posted by Geoff Waddington View Post
Instead we opted for global modifiers, here are the ones currently available:

Shift
Option
Control
Alt

So in your .rst file you must designate some or all of the above, obviously the more buttons you can spare to allocate from the surface the more combinations you get, so let's say you can allocate all 4 buttons it will look something like this, although your midi numbers may be different:

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
On the modifier example, the way you've implemented the 4 standard ones as global is great, and opens up exactly the kind of thing I was hoping for. By global, do you mean across all pages?

The icing on the cake would be if it would be possible to have a label show up in the MCU display indicating what the modifier combo was loaded with (Klinke again)

I have some other sketchy thoughts about having one one axt file reference multiple devices, but I will do the work of trying to achieve what I want with what's there first.

Another one; from the PDF in the distro:

"You can set up Actions to navigate instantly between Pages"

Is there an example of this somewhere?

Edit:In case it's useful to anyone, I have a little sketch pad going showing what's going on with my BCF. It's fw 1.10 and in NCso mode (MCU Sonar), and the buttons differ substantially to the initial docs from Behringer. I'll add in the numbers for the strip buttons when I get home. I got the MCU specification data tab from someone on these forums back in the day.

https://docs.google.com/spreadsheets...it?usp=sharing

Last edited by jamesd256; 02-11-2019 at 09:23 AM.
jamesd256 is offline   Reply With Quote
Old 02-11-2019, 09:19 AM   #2515
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by MixMonkey View Post
I think the refactoring may have introduced a bug that causes issues when b0 00 is used in the .mst definition.

This turned up when I was writing the BCR2000mk2.mst. When I started the Rotary controller codes from b0 00, the only rotary control that worked properly was b0 00 and all the other rotary controls were somehow mapped to the same action as the first (b0 00) control.

When I started the controller codes from b0 01 everything worked as expected.

I believe this to be the cause of the C4 problems. Its rotary controller codes begin from b0 00 as well.
Thanks for the great sleuthing, think I swatted it

New build is up, see link in sig below.

Let me know how it goes.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 09:26 AM   #2516
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
On the modifier example, the way you've implemented the 4 standard ones as global is great, and opens up exactly the kind of thing I was hoping for. By global, do you mean across all pages?
No, just on a page.

Quote:
Originally Posted by jamesd256 View Post
Another one; from the PDF in the distro:

"You can set up Actions to navigate instantly between Pages"

Is there an example of this somewhere?
In an .axt

SomeButton NextPage
OtherButton GoPage Track
AnotherButton GoPage Sends
YetAnotherButton GoPage SomePageName

NextPage cycles through, and GoPage goes to the Page whose name matches the 3rd param -- Track, Sends, etc.
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143

Last edited by Geoff Waddington; 02-11-2019 at 01:08 PM.
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 09:48 AM   #2517
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Edit:In case it's useful to anyone, I have a little sketch pad going showing what's going on with my BCF. It's fw 1.10 and in NCso mode (MCU Sonar), and the buttons differ substantially to the initial docs from Behringer. I'll add in the numbers for the strip buttons when I get home. I got the MCU specification data tab from someone on these forums back in the day.

https://docs.google.com/spreadsheets...it?usp=sharing
Great work, thanks !

Can I persuade you with a kind tone to think about how to express the notation for a second.

Earlier in the thread we chose hex notation for (what we believe) is a better way to express control surface concepts.

The Midi info doesn't represent notes, velocities or anything like that, it's been hijacked to represent entirely different concepts.

For instance, 0x90 is not note on, it's very commonly used for switches.

By using hex we intentionally hide the note/velocity/channel concept and it often actually makes for much cleaner reading files:

Code:
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
Once again, please don't think your work is unappreciated, but if we all use one notation things will go much easier
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 10:06 AM   #2518
jamesd256
Human being with feelings
 
jamesd256's Avatar
 
Join Date: Dec 2015
Location: Folkestone
Posts: 160
Default

Quote:
Originally Posted by Geoff Waddington View Post
Great work, thanks !

Can I persuade you with a kind tone to think about how to express the notation for a second.

Earlier in the thread we chose hex notation for (what we believe) is a better way to express control surface concepts.

The Midi info doesn't represent notes, velocities or anything like that, it's been hijacked to represent entirely different concepts.

For instance, 0x90 is not note on, it's very commonly used for switches.

By using hex we intentionally hide the note/velocity/channel concept and it often actually makes for much cleaner reading files:

Code:
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
Once again, please don't think your work is unappreciated, but if we all use one notation things will go much easier
Useful explanation of why hex, thanks.

So, my file:

The original data 'MCU Spec' tab is as it came, i.e; with note names and note numbers. I've added the other tabs. The BCF Layout tab is mine, and I've added a vlookup to translate the note name from the MCU spec to the action mapped on the BCF, and another vlookup to obtain the hex value for the button. I added the hex vlookup to help me setting up CSI as a matter of fact.

It wasn't clearly labelled, but I've now added a couple of headings to help in the BCF tab. I have no idea how useful this is to others. I would be happy to go back over the original MCU Spec tab and vlookup the hex values there too.
jamesd256 is offline   Reply With Quote
Old 02-11-2019, 11:32 AM   #2519
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 3,787
Default

Quote:
Originally Posted by jamesd256 View Post
Useful explanation of why hex, thanks.

So, my file:

The original data 'MCU Spec' tab is as it came, i.e; with note names and note numbers. I've added the other tabs. The BCF Layout tab is mine, and I've added a vlookup to translate the note name from the MCU spec to the action mapped on the BCF, and another vlookup to obtain the hex value for the button. I added the hex vlookup to help me setting up CSI as a matter of fact.

It wasn't clearly labelled, but I've now added a couple of headings to help in the BCF tab. I have no idea how useful this is to others. I would be happy to go back over the original MCU Spec tab and vlookup the hex values there too.
Cool, I didn't see the tabs originally, makes more sense now
__________________
CSI - You can donate here: geoffwaddington.ca
Alpha software: https://stash.reaper.fm/v/36903/CSI%20alpha.zip
Reaper forum thread: https://forum.cockos.com/showthread.php?t=183143
Geoff Waddington is offline   Reply With Quote
Old 02-11-2019, 11:42 AM   #2520
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 864
Default

Quote:
Originally Posted by Geoff Waddington View Post
Thanks for the great sleuthing, think I swatted it

New build is up, see link in sig below.

Let me know how it goes.
Yep, that swatted it C4 working normally now.

Regarding the MCU driver crashing, this seems to be Windows only. Works fine, stable, but doesn't exit very gracefully.

If you close the Reaper session and open another one (or even the same one) Reaper usually quits. Relaunching Reaper sometimes works, unless the MCU Driver has crashed (witnessed by the MCU not being seen in Device Manager) in which case a computer restart is needed.

Behaves fine on Mac
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 07:37 PM.


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