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

Reply
 
Thread Tools Display Modes
Old 02-28-2020, 05:16 AM   #7081
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by WaveTrans View Post
What is actually missing/not working/wrong with the
FocusedFXNavigator?
Not sure, please try it out and let us know

Seriously, Focused FX is tricky, a WIP...
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-28-2020, 05:50 AM   #7082
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,686
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yes, but control surface language is not Midi.

Although there is no control language standard, Mackie Control Protocol is very often used.
Yep. But those devices that communicate via a Midi OS device and don't adhere to some variant of MCI very likely will adhere to the Midi standard. E.g. the XTouch devices (if not set to MC mode) use plain old Midi Note and CC messages. And the A&H obviously uses the more recent standards NRPM and high resolution CC. I recon that there will be more more devices of such kind now and/or in future.


Quote:
Originally Posted by Geoff Waddington View Post
I would say that support for all these new Midi features will be tepid at best in the controller world -- OSC is the up and coming new kid in town, certainly not Midi 2.0
I do agree (while IMHO the most obvious extension would be high res CC - which by the way already is perfectly supported by Reaper itself - seems not a great problem).

But stuff like NRMP (e.g. for this A&H device) and Midi 2.0 seems more demanding and obviously OSC is the more needed feature.

As a workaround we (e.g. me) can do scripts for OSCIIBot to convert such Midi implementations to OSC, when OSC is perfectly supported by CSI.

-Michael

Last edited by mschnell; 02-28-2020 at 06:14 AM.
mschnell is online now   Reply With Quote
Old 02-28-2020, 05:57 AM   #7083
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by Geoff Waddington View Post
Not sure, please try it out and let us know

Seriously, Focused FX is tricky, a WIP...

I´ll look more closely into it.

So far, only a tendency to interrupt contact between Reaper and the controller
was to be noticed;
most notably after clicking away from the focused FX or toggled Focused FX Menu.

Less so when focused fX Menu is appropriately un-toggled
WaveTrans is offline   Reply With Quote
Old 02-28-2020, 06:00 AM   #7084
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,686
Default

Quote:
Originally Posted by Geoff Waddington View Post
they use 12 bytes to deliver a payload of.. wait for it... 7 bits -- yup, the ninth byte is of range 0-7f -- that's the fader level.
But at least they adhere to the Midi standard .
That is extremely weird, especially as it's known that 7 bits is not really a decent resolution for a fader. Their protocol does provide for more bits in CC#38 (high resolution Midi standard), so maybe it's planned for a future release of the device.

-Michael

Last edited by mschnell; 02-28-2020 at 06:13 AM.
mschnell is online now   Reply With Quote
Old 02-28-2020, 07:49 AM   #7085
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 998
Default

Faderport classic update:

Switched it to live mode (which does denote MCU in some documentation)

Used the mcu mst and zon files and stuff started to work. Transport functions mainly.

In csi learn, it looks to be very mcu-like

touching the fader yields a fadertouch1 and using the over arrow and then touching the fader yields a fadertouch2. I'm expecting to see a bunch of values as I'm moving the fader up and down but I don't. Just touch and release messages.

I then tried to use the touch1 message data for the fader in the mst but I haven't succeeded in getting the fader talking to csi yet.

The pan knob also doesn't register any value in csi learn.

Does that give anyone any clues?
cjewellstudios is offline   Reply With Quote
Old 02-28-2020, 07:55 AM   #7086
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 998
Default

Focusedfxnavigator issue:

-Instantiate plugin, plugin gets mapped with feedback.

- click on a track, knobs go back to controlling volume.

-re-focus the same plugin, nothing happens

-instantiate another instance of plugin and its mapped correctly

@funkybot I noticed you used a toggle focused fx that I havent set up yet. Is that something i have to do? My goal would be to have it map the plugin whenever its focused but thats not how its behaving currently
cjewellstudios is offline   Reply With Quote
Old 02-28-2020, 09:00 AM   #7087
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by cjewellstudios View Post
touching the fader yields a fadertouch1 and using the over arrow and then touching the fader yields a fadertouch2. I'm expecting to see a bunch of values as I'm moving the fader up and down but I don't. Just touch and release messages.
Yeah, I'm expecting you to see a bunch of values when you move a fader too.

Quote:
Originally Posted by cjewellstudios View Post
I then tried to use the touch1 message data for the fader in the mst but I haven't succeeded in getting the fader talking to csi yet.

The pan knob also doesn't register any value in csi learn.
FaderTouch isn't going to move the fader. I'd undo those .mst changes.

Do you have any other apps that allow you to monitor messages? If it were me, I'd open Bome, I'd open the MIDI input port, open the Log, then start moving stuff to see what kind of messages are being transmitted, then try the various modes out and experiment from there.

If you can get a log, move the fader, make note of the messages and post here. Move to the next channel on the surface and do the same. Move the pan knob and do the same. If you're not getting messages, try to experiment with different modes.

Anyone with a Faderport around who can help?
Funkybot is offline   Reply With Quote
Old 02-28-2020, 09:07 AM   #7088
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 998
Default

Quote:
Originally Posted by Funkybot View Post
Yeah, I'm expecting you to see a bunch of values when you move a fader too.



FaderTouch isn't going to move the fader. I'd undo those .mst changes.

Do you have any other apps that allow you to monitor messages? If it were me, I'd open Bome, I'd open the MIDI input port, open the Log, then start moving stuff to see what kind of messages are being transmitted, then try the various modes out and experiment from there.

If you can get a log, move the fader, make note of the messages and post here. Move to the next channel on the surface and do the same. Move the pan knob and do the same. If you're not getting messages, try to experiment with different modes.

Anyone with a Faderport around who can help?
I was just working off of mcu mst and zon. The change came as a last ditch effort.

Yeah I thought the same thing;

I opened up midi ox, experimented with different modes and its the same story there.

I did see the term Mackie HUI not in the official docs but somewhere else. So maybe that's why?
cjewellstudios is offline   Reply With Quote
Old 02-28-2020, 09:11 AM   #7089
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by cjewellstudios View Post
Focusedfxnavigator issue:

-Instantiate plugin, plugin gets mapped with feedback.

- click on a track, knobs go back to controlling volume.

-re-focus the same plugin, nothing happens

-instantiate another instance of plugin and its mapped correctly

@funkybot I noticed you used a toggle focused fx that I havent set up yet. Is that something i have to do? My goal would be to have it map the plugin whenever its focused but thats not how its behaving currently
You know how Geoff keeps saying FocusedFXNavigator is a work in progress?

For the most part, it works very well here. But my setup is quite different than yours. When the MFTwister is controlling volume, it's doing it in Bank C. My FX are all mapped on Bank A.

So over here, it works like this:

-Instantiate plugin, plugin gets mapped with feedback.

-Click on a track in the MCP, move a fader or whatever, plugin is still mapped with feedback

-re-focus the same plugin, plugin is still mapped with feedback

-Hey, I need to use one of the buttons on the MFTwister assigned to the same page as the plugin...hit the Bank1 button - this turns off FocusedFX

Code:
	Bank1 ToggleMapFocusedFX
-Now I need to go back to the plugin. Hit Bank1 again.

Also, my FX.zon files use NoAction for all parameters on the MFTwister bank not mapped to the plugins. So when the plugin is in focus, it's the only thing happening on that device. I didn't need to set them up this way, but I didn't want some things controlling the plugin and other things controlling the track so it's a hard takeover.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 09:13 AM   #7090
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by cjewellstudios View Post
I opened up midi ox, experimented with different modes and its the same story there.

I did see the term Mackie HUI not in the official docs but somewhere else. So maybe that's why?

I know Geoff has experience with the Faderport so hopefully he can add some insight. Dumb question: you have the 9v outlet plugged into the unit right? You're not trying to power it straight off of USB? I briefly saw in the manual that the fader will only work when plugged into the wall outlet.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 09:51 AM   #7091
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 998
Default

Quote:
Originally Posted by Funkybot View Post
You know how Geoff keeps saying FocusedFXNavigator is a work in progress?
I missed that actually I've only been heavily following for a couple weeks or so

Quote:
For the most part, it works very well here. But my setup is quite different than yours.
Yeah for sure. I do like your setup. I just wanted to embrace the csi way and try not banking the twisters at all. I do like that mindset. I can use the toggle focused fx for now though if thats the workaround I need to use.

...

and to consolidate and answer about the faderport. Yes its plugged in
cjewellstudios is offline   Reply With Quote
Old 02-28-2020, 09:56 AM   #7092
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Likely bug: F1 and F2 exist in SelectedTrackNavigator. Shift, Shift+F1, and Shift+F2 exist as "global buttons" and don't have a navigator.

Result: F1 and F2 do no longer work on the selected track. F3-F5 work as expected. I think having Shift+F1 and Shift+F2 in a non-navigator, or different navigator, is somehow interfering with the non-modified buttons on the SelectedTrackNavigator.

Here's the .zon:
Code:
Zone "SelChannelButtons|"
	SelectedTrackNavigator
	F1 				TrackAutoMode 1 	//Read
	F2 				TrackAutoMode 3 	//Write
	F3 				TrackAutoMode 0 	//Trim
	F4 				TrackAutoMode 2 	//touch
	F5				TrackAutoMode 4 	//Latch

ZoneEnd

Zone "GlobalButtons|"
	Zoom				Shift	
	Shift+F1			GoZone Home
	Shift+F2			GoZone FocusedFXParam
ZoneEnd
EDIT
Just want to clarify that the CSI Learn mode registers the standalone F1 or F2 presses. But the automation mode doesn't change on the selected track for those buttons.

Last edited by Funkybot; 02-28-2020 at 01:19 PM.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 11:15 AM   #7093
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
Default

Quote:
Originally Posted by Funkybot View Post
Likely bug: F1 and F2 exist in SelectedTrackNavigator. Shift, Shift+F1, and Shift+F2 exist as "global buttons" and don't have a navigator.

Result: F1 and F2 do no longer work on the selected track. F3-F5 work as expected. I think having Shift+F1 and Shift+F2 in a non-navigator, or different navigator, is somehow interfering with the non-modified buttons on the SelectedTrackNavigator.

Here's the .zon:
Code:
Zone "SelChannelButtons|"
	SelectedTrackNavigator
	F1 				TrackAutoMode 1 	//Read
	F2 				TrackAutoMode 3 	//Write
	F3 				TrackAutoMode 0 	//Trim
	F4 				TrackAutoMode 2 	//touch
	F5				TrackAutoMode 4 	//Latch

ZoneEnd

Zone "GlobalButtons|"
	Zoom				Shift	
	Shift+F1			GoZone Home
	Shift+F2			GoZone FocusedFXParam
ZoneEnd
Shift (and other modifiers) are global, affecting all surfaces and all Zones.
MixMonkey is offline   Reply With Quote
Old 02-28-2020, 11:18 AM   #7094
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by MixMonkey View Post
Shift (and other modifiers) are global, affecting all surfaces and all Zones.
Right, but why would F1 and F2 stop working in the above? Having a shift+widget modifier shouldn't prevent the standalone widget from working.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 11:22 AM   #7095
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
Default

Quote:
Originally Posted by Funkybot View Post
Right, but why would F1 and F2 stop working in the above?
Yes, fair point, although I've found that modifiers tend to be a law unto themselves regarding their 'reach' and predicted behaviour can be a little, well, uncertain
MixMonkey is offline   Reply With Quote
Old 02-28-2020, 11:29 AM   #7096
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Ok, so sorry for being such a newb first of all.

I have a question, that's real basic and perhaps quite stupid. I wonder if the Console1.mst and the accompanying *.zon files that are included in the beta are up to date? By up to date I mean, are they supposed to work ok?

The Console1.mst file looks like this, I guess that one is probably still OK:

Code:
Widget Preset
	AnyPress b0 3a 7f 
	FB_TwoState b0 3a 7f b0 3a 00
WidgetEnd

Widget Mode
	AnyPress b0 68 7f b0 68 00
	FB_TwoState b0 68 7f b0 68 00
WidgetEnd

Widget ChannelLeft
	AnyPress b0 61 7f b0 61 00
	FB_TwoState b0 61 7f b0 61 00
WidgetEnd

Widget ChannelRight
	AnyPress b0 60 7f b0 60 00
	FB_TwoState b0 60 7f b0 60 00
WidgetEnd

Widget DisplayFX
	AnyPress b0 66 7f
	FB_TwoState b0 66 7f b0 66 00
WidgetEnd

Widget Order
	AnyPress b0 0e 7f b0 0e 00
	FB_TwoState b0 0e 7f b0 0e 00
WidgetEnd

Widget ExternalSidechain
	AnyPress b0 11 7f b0 11 00
	FB_TwoState b0 11 7f b0 11 00
WidgetEnd

Widget FiltersToComAnyPressor
	AnyPress b0 3d 7f b0 3d 00
	FB_TwoState b0 3d 7f b0 3d 00
WidgetEnd

Widget HiCut
	Fader7Bit b0 69 7f
	FB_Fader7Bit b0 69 7f
WidgetEnd

Widget LoCut
	Fader7Bit b0 67 7f
	FB_Fader7Bit b0 67 7f
WidgetEnd

Widget PhaseInvert
	AnyPress b0 6c 7f b0 6c 00
	FB_TwoState b0 6c 7f b0 6c 00
WidgetEnd

Widget Shape
	AnyPress b0 35 7f
	FB_TwoState b0 35 7f b0 35 00
WidgetEnd

Widget HardGate
	AnyPress b0 3b 7f b0 3b 00
	FB_TwoState b0 3b 7f b0 3b 00
WidgetEnd

Widget Equalizer
	AnyPress b0 50 7f b0 50 00
	FB_TwoState b0 50 7f b0 50 00
WidgetEnd

Widget LoCurve
	AnyPress b0 5d 7f b0 5d 00
	FB_TwoState b0 5d 7f b0 5d 00
WidgetEnd

Widget HiCurve
	AnyPress b0 41 7f b0 41 00
	FB_TwoState b0 41 7f b0 41 00
WidgetEnd

Widget HiGain
	Fader7Bit b0 52 7f
	FB_Fader7Bit b0 52 7f
WidgetEnd

Widget HiFrequency
	Fader7Bit b0 53 7f
	FB_Fader7Bit b0 53 7f
WidgetEnd

Widget HiMidGain
	Fader7Bit b0 55 7f
	FB_Fader7Bit b0 55 7f
WidgetEnd

Widget HiMidFrequency
	Fader7Bit b0 56 7f
	FB_Fader7Bit b0 56 7f
WidgetEnd

Widget HiMidQ
	Fader7Bit b0 57 7f
	FB_Fader7Bit b0 57 7f
WidgetEnd

Widget LoMidGain
	Fader7Bit b0 58 7f
	FB_Fader7Bit b0 58 7f
WidgetEnd

Widget LoMidFrequency
	Fader7Bit b0 59 7f
	FB_Fader7Bit b0 59 7f
WidgetEnd

Widget LoMidQ
	Fader7Bit b0 5a 7f
	FB_Fader7Bit b0 5a 7f
WidgetEnd

Widget LoGain
	Fader7Bit b0 5b 7f
	FB_Fader7Bit b0 5b 7f
WidgetEnd

Widget LoFrequency
	Fader7Bit b0 5c 7f
	FB_Fader7Bit b0 5c 7f
WidgetEnd

Widget ComAnyPressor
	AnyPress b0 2e 7f b0 2e 00
	FB_TwoState b0 2e 7f b0 2e 00
WidgetEnd

Widget Threshold
	Fader7Bit b0 2f 7f
	FB_Fader7Bit b0 2f 7f
WidgetEnd

Widget Release
	Fader7Bit b0 30 7f
	FB_Fader7Bit b0 30 7f
WidgetEnd

Widget Ratio
	Fader7Bit b0 31 7f
	FB_Fader7Bit b0 31 7f
WidgetEnd

Widget Parallel
	Fader7Bit b0 32 7f
	FB_Fader7Bit b0 32 7f
WidgetEnd

Widget Attack
	Fader7Bit b0 33 7f
	FB_Fader7Bit b0 33 7f
WidgetEnd

Widget Drive
	Fader7Bit b0 0f 7f
	FB_Fader7Bit b0 0f 7f
WidgetEnd

Widget Character
	Fader7Bit b0 12 7f
	FB_Fader7Bit b0 12 7f
WidgetEnd

Widget ComAnyPressorMeter
	FB_GainReductionMeter b0 73 00
WidgetEnd

Widget InputMeterLeft
	FB_VUMeter b0 6e 00
WidgetEnd

Widget InputMeterRight
	FB_VUMeter b0 6f 00
WidgetEnd

Widget OutputMeterLeft
	FB_VUMeter b0 70 00
WidgetEnd

Widget OutputMeterRight
	FB_VUMeter b0 71 00
WidgetEnd

Widget Volume
	Fader7Bit b0 07 7f
	FB_Fader7Bit b0 07 7f
WidgetEnd

Widget Pan
	Fader7Bit b0 0a 7f
	FB_Fader7Bit b0 0a 7f
WidgetEnd

Widget Mute
	AnyPress b0 0c 7f
	FB_TwoState b0 0c 7f b0 0c 00
WidgetEnd

Widget Solo
	AnyPress b0 0d 7f 
	FB_TwoState b0 0d 7f b0 0d 00
WidgetEnd
...and the two *.zon files I'm most interested in so far looks like this:

Code:
Zone "Home"
	OnTrackSelection	GoZone "Channel"
	OnTrackSelection 	MapSelectedTrackFXToWidgets
	DisplayFX 		SetShowFXWindows
	Mode 			ToggleMapSelectedTrackFX
	Preset 			GoZone "Home"
	ChannelLeft 		TrackBank "-1"
	ChannelRight 		TrackBank "1"
	Shape 			ToggleLearnMode
ZoneEnd

Zone "Channel"
	SelectedTrackNavigator
	InputMeterLeft 		TrackOutputMeter "0"
	InputMeterRight		TrackOutputMeter "1"
	OutputMeterLeft 	TrackOutputMeter "0"
	OutputMeterRight	TrackOutputMeter "1"
	Volume 			TrackVolume
	Control+Volume 		TrackPanWidth	"1"
	Shift+Volume 		TrackPan 	"0"
	Mute 			TrackMute
	Solo 			TrackSolo
ZoneEnd
Code:
Zone "VST: ReaComp (Cockos)" "ReaComp"
	SelectedTrackNavigator
	Threshold 	FXParam "0" "Thresh"
	Attack 		FXParam "2" "Attack"
	Release 	FXParam "3" "Release"
	Ratio 		FXParam "1" "Ratio"
	Compressor 	FXParam "19" "Bypass"
	Parallel 	FXParam "20" "Wet"
	CompressorMeter	FXParam "GainReductionDB"
ZoneEnd
ramses is offline   Reply With Quote
Old 02-28-2020, 12:03 PM   #7097
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by ramses View Post
Ok, so sorry for being such a newb first of all.

I have a question, that's real basic and perhaps quite stupid. I wonder if the Console1.mst and the accompanying *.zon files that are included in the beta are up to date? By up to date I mean, are they supposed to work ok?
Did you try them? Are they not working? If not, what exactly? Does anything work? Do you have the Console1 MIDI Ports disabled in Reaper's preferences and the VC Runtime installed as linked to here:

https://github.com/malcolmgroves/rea...i/Installation
Funkybot is offline   Reply With Quote
Old 02-28-2020, 12:08 PM   #7098
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Updated the Wiki just not to show how to update stepped parameters to Encoders:

https://github.com/malcolmgroves/rea...rs-to-encoders

Also included an fx.zon example in the MFTwister where the button color changes from green (active) to red (bypassed). There was a color chart added to the bottom of that page also.

https://github.com/malcolmgroves/rea...iki/FB_MFT_RGB
Funkybot is offline   Reply With Quote
Old 02-28-2020, 12:12 PM   #7099
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Quote:
Originally Posted by Funkybot View Post
Did you try them? Are they not working? If not, what exactly? Does anything work? Do you have the Console1 MIDI Ports disabled in Reaper's preferences and the VC Runtime installed as linked to here:

https://github.com/malcolmgroves/rea...i/Installation
I can get the C1 output Volume encoder to control Reaper selected track fader setting, and reverse (moving the fader in Reaper changes C1 Vol encoder led position). Mute + Solo works as well. So that's something.

Can't get stuff like track selection, polarity/phase, pan or banking to work so far.

>>EDIT<< Oh, the input/output led meters work as well >>END EDIT<<

Last edited by ramses; 02-28-2020 at 12:20 PM.
ramses is offline   Reply With Quote
Old 02-28-2020, 12:21 PM   #7100
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by ramses View Post
I can get the C1 output Volume encoder to control Reaper selected track fader setting, and reverse (moving the fader in Reaper changes C1 Vol encoder led position). Mute + Solo works as well. So that's something.

Can't get stuff like track selection, polarity/phase, pan or banking to work so far.
Ok, that's helpful! Let's take a look at the zone file...

Code:
Zone "Home"
	OnTrackSelection	GoZone "Channel"
	OnTrackSelection 	MapSelectedTrackFXToWidgets
	DisplayFX 		SetShowFXWindows
	Mode 			ToggleMapSelectedTrackFX
	Preset 			GoZone "Home"
	ChannelLeft 		TrackBank "-1"
	ChannelRight 		TrackBank "1"
	Shape 			ToggleLearnMode
ZoneEnd

Zone "Channel"
	SelectedTrackNavigator
	InputMeterLeft 		TrackOutputMeter "0"
	InputMeterRight		TrackOutputMeter "1"
	OutputMeterLeft 	TrackOutputMeter "0"
	OutputMeterRight	TrackOutputMeter "1"
	Volume 			TrackVolume
	Control+Volume 		TrackPanWidth	"1"
	Shift+Volume 		TrackPan 	"0"
	Mute 			TrackMute
	Solo 			TrackSolo
ZoneEnd
...TrackPan is currently assigned to shift+volume. Does the unit have a Shift button? If yes, hold it down while you move the volume fader. Does it move the pan? If yes, that means it's working. Now...is that what you want? Might not be.

If the surface has a dedicated pan control and you would prefer to use that, we have to update some of the instructions in the .zon file. So let's say you want the dedicated Pan control on the surface to control TrackPan in Reaper, and Shift+Pan to control TrackPanWidth. That would be easy to modify and work into the Channel section of the .zon file. See what I did below?

Code:
Zone "Channel"
	SelectedTrackNavigator
	InputMeterLeft 		TrackOutputMeter "0"
	InputMeterRight		TrackOutputMeter "1"
	OutputMeterLeft 	TrackOutputMeter "0"
	OutputMeterRight	TrackOutputMeter "1"
	Volume 			TrackVolume
	Pan     		TrackPan 	"0"
	Shift+Pan 		TrackPanWidth	"1"
	Mute 			TrackMute
	Solo 			TrackSolo
ZoneEnd
...Note: I don't actually have a Console1.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 12:35 PM   #7101
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 1,231
Default

Quote:
Originally Posted by Funkybot View Post
If the surface has a dedicated pan control and you would prefer to use that, we have to update some of the instructions in the .zon file. So let's say you want the dedicated Pan control on the surface to control TrackPan in Reaper, and Shift+Pan to control TrackPanWidth. That would be easy to modify and work into the Channel section of the .zon file. See what I did below?
Cool, it works! Thanks for the pointers, I'll go ahead and try to get the rest of the controls working.
ramses is offline   Reply With Quote
Old 02-28-2020, 12:39 PM   #7102
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by ramses View Post
Cool, it works! Thanks for the pointers, I'll go ahead and try to get the rest of the controls working.
Glad you got it! Post back if you need more help. Maybe even share your .zon file after you make the updates.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 02:09 PM   #7103
KroniK907
Human being with feelings
 
Join Date: Mar 2017
Posts: 11
Default

Quote:
Originally Posted by Geoff Waddington View Post
Incorrect, look more carefully at the spec -- they use 12 bytes to deliver a payload of.. wait for it... 7 bits -- yup, the ninth byte is of range 0-7f -- that's the fader level.

All of that work decoding 4 3 byte messages to get a 7 bit result -- nope we won't be doing that one -- unless it gets VERY popular.

On a side note, I've used A&H since the 70's -- great sounding, well thought out kit

This Midi implementation -- not so much
That's disappointing, but understandable. I guess I'll just stick with 16 faders and no knobs

I do really like the sound of A&H boards, and they are very easy to understand and use, so I'm happy with my purchase for live gigs. Just wish it could also be better at integrating with my DAW
KroniK907 is offline   Reply With Quote
Old 02-28-2020, 02:13 PM   #7104
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Feature request if possible: have a "Refresh Parser" button on the CSI Learn screen or maybe a "Refresh CSI Parser" action. The idea being that [hopefully] we could modify one or more .zon files and refresh CSI so we didn't need to close and relaunch Reaper.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 02:15 PM   #7105
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
Default

Quote:
Originally Posted by Funkybot View Post
Feature request if possible: have a "Refresh Parser" button on the CSI Learn screen or maybe a "Refresh CSI Parser" action. The idea being that [hopefully] we could modify one or more .zon files and refresh CSI so we didn't need to close and relaunch Reaper.
Just open the CSI prefs + hit ok twice.
MixMonkey is offline   Reply With Quote
Old 02-28-2020, 02:35 PM   #7106
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,988
Default

Quote:
Originally Posted by MixMonkey View Post
Just open the CSI prefs + hit ok twice.
Never occurred to me to try it that way but it works very well. Thanks! I'd still like a dedicated action to make it even faster, but this is so much better than what I was doing before.

The only thing to watch out for is if you're testing an FX.zon mapping, you'll have to unload and reload the effect.
Funkybot is offline   Reply With Quote
Old 02-28-2020, 02:38 PM   #7107
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,869
Default

Quote:
Originally Posted by Funkybot View Post
The only thing to watch out for is if you're testing an FX.zon mapping, you'll have to unload and reload the effect.
That doesn't seem to happen here, I have to reselect the track, then the FX from the FX menu, but that's it.
MixMonkey is offline   Reply With Quote
Old 02-28-2020, 03:11 PM   #7108
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by Geoff Waddington View Post
Not sure, please try it out and let us know
Seriously, Focused FX is tricky, a WIP...
Ok, did some clicking, I mean testing
-Toggling Focused FX Navigator(FFXN) works well.
-Params are shown and it is possible to switch between plugins with mouse or reaper action. Display is updated accordingly.
-if FFXN is left by un-toggling the FFXN by dedicated button, everything works fine and without observable clitches.

Issues appear, if the FFXN is focused and one works "outside" of the FX Menu or closes the FX menu by mouse while it is focused (which is a frequenct event on my side).
If one notices soon enough that FFXN is still in focus in the background (indicated by Param display etc) one may re-focus the FXMenu and leave it by untoggling.
Everything is then back to normal.

However, selecting a couple of tracks and opening/closing a couple of FX menues while the Navigator is toggled crashes it after some clicking around.
Other functions of CSI appear unaffected by this.
I guess it´s impossible for CSI to simply block any clicks which are directed outside the FXMenu while FFXN is toggled-on?
Automatic focus/unfocus sort of thing maybe?
WaveTrans is offline   Reply With Quote
Old 02-28-2020, 04:49 PM   #7109
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by cjewellstudios View Post
and to consolidate and answer about the faderport. Yes its plugged in
You only need the power supply for the Fader motor - aka - if you want Reaper to be able to move it.

I wrote the original driver software for Sanewave/Presounus around 2006, my first control surface software gig

I seem to recall it was easy to brick/semi-brick these way back then -- have you tried various firmware versions ?

It should put out a steady stream as you move the fader -- bracketed by touch on/off messages -- maybe just a bad fader ? happens reasonably often -- probably the most common failure industry wide across all control surface brands
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-28-2020, 04:55 PM   #7110
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by Funkybot View Post
Likely bug: F1 and F2 exist in SelectedTrackNavigator. Shift, Shift+F1, and Shift+F2 exist as "global buttons" and don't have a navigator.

Result: F1 and F2 do no longer work on the selected track. F3-F5 work as expected. I think having Shift+F1 and Shift+F2 in a non-navigator, or different navigator, is somehow interfering with the non-modified buttons on the SelectedTrackNavigator.

Here's the .zon:
Code:
Zone "SelChannelButtons|"
	SelectedTrackNavigator
	F1 				TrackAutoMode 1 	//Read
	F2 				TrackAutoMode 3 	//Write
	F3 				TrackAutoMode 0 	//Trim
	F4 				TrackAutoMode 2 	//touch
	F5				TrackAutoMode 4 	//Latch

ZoneEnd

Zone "GlobalButtons|"
	Zoom				Shift	
	Shift+F1			GoZone Home
	Shift+F2			GoZone FocusedFXParam
ZoneEnd
EDIT
Just want to clarify that the CSI Learn mode registers the standalone F1 or F2 presses. But the automation mode doesn't change on the selected track for those buttons.
Those are both template Zones.

If they are both included (instantiated) in the same enclosing Zone and "GlobalButtons|" comes second, it will clobber the "SelChannelButtons|" F1/F2 definitions.

You can't do it additively like that, you just need to rearrange some definjtions.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-28-2020, 04:57 PM   #7111
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by KroniK907 View Post
That's disappointing, but understandable. I guess I'll just stick with 16 faders and no knobs

I do really like the sound of A&H boards, and they are very easy to understand and use, so I'm happy with my purchase for live gigs. Just wish it could also be better at integrating with my DAW
I know, I've loved using their stuff for years, that's why this is so surprising, go figure...
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-28-2020, 04:59 PM   #7112
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by WaveTrans View Post
However, selecting a couple of tracks and opening/closing a couple of FX menues while the Navigator is toggled crashes it after some clicking around.
Whooaa, do you mean Reaper crashes ?

That should NEVER happen, please enumerate steps to reproduce.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-28-2020, 05:46 PM   #7113
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 998
Default

Quote:
Originally Posted by Geoff Waddington View Post
You only need the power supply for the Fader motor - aka - if you want Reaper to be able to move it.

I wrote the original driver software for Sanewave/Presounus around 2006, my first control surface software gig

I seem to recall it was easy to brick/semi-brick these way back then -- have you tried various firmware versions ?

It should put out a steady stream as you move the fader -- bracketed by touch on/off messages -- maybe just a bad fader ? happens reasonably often -- probably the most common failure industry wide across all control surface brands

That's awesome!

No the fader is fine. It works completely fine with the faderport xt drivers from the forum here. So I guess if all else fails I'd go back to that. But I definitely wanted to try the the last touched parameter thing (sorry forgot what you called it ) as well as using some of the buttons as modifiers for csi.

There is a firmware update but its very hard to accomplish so I gave up there.
cjewellstudios is offline   Reply With Quote
Old 02-29-2020, 02:31 AM   #7114
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by Geoff Waddington View Post
Whooaa, do you mean Reaper crashes ?

That should NEVER happen, please enumerate steps to reproduce.
Sorry for causing alarm.
No, Reaper does not crash.

Last night, it looked like FXnavigator crashes when I clicked outside the focused FX Menu.

Tried again this morning.
Nothing crashes, appears very robust and stable actually.

FFXN seems work well. As long as it is toggled one can click between FX menus, open them with the mouse etc and the controller responds.

Very nice.

Once in a while, display information is lost completely, so for tracks as well as fx, from clicking wildly but this is not easy to reproduce.

may be caused by more or less severe lags in updating Display information when switching between FX menus and tracks,

since re-selecting plugins or tracks usually brings the focus back.

So seems fine by me
WaveTrans is offline   Reply With Quote
Old 02-29-2020, 03:56 AM   #7115
MalcolmG
Human being with feelings
 
MalcolmG's Avatar
 
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
Default

I've started doing more with OSC using Lemur on iOS. So far it's relatively straightforward but one thing I'd like to be able to do is to change the Lemur interface (what they call the screen layout) automatically as the zones change.

Lemur lets you change interfaces using an OSC message. I've been trying to trick the CSI FB_Processor into sending the right OSC message for me, but nothing useful so far.

So Geoff, given you've already figured out how to send OSC messages, is it possible to get an Action we can use to send an arbitrary message? The trick is I'd probably want to invoke it from a different surface than the one receiving it, which might complicate matters.

Is there more complexity in this than I appreciate?
__________________
Filter Theory | CSI Notes wiki
MalcolmG is offline   Reply With Quote
Old 02-29-2020, 05:17 AM   #7116
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by WaveTrans View Post
Sorry for causing alarm.
No, Reaper does not crash.

Last night, it looked like FXnavigator crashes when I clicked outside the focused FX Menu.

Tried again this morning.
Nothing crashes, appears very robust and stable actually.

FFXN seems work well. As long as it is toggled one can click between FX menus, open them with the mouse etc and the controller responds.

Very nice.

Once in a while, display information is lost completely, so for tracks as well as fx, from clicking wildly but this is not easy to reproduce.

may be caused by more or less severe lags in updating Display information when switching between FX menus and tracks,

since re-selecting plugins or tracks usually brings the focus back.

So seems fine by me
Cool, thanks
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-29-2020, 05:49 AM   #7117
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by MalcolmG View Post
I've started doing more with OSC using Lemur on iOS. So far it's relatively straightforward but one thing I'd like to be able to do is to change the Lemur interface (what they call the screen layout) automatically as the zones change.

Lemur lets you change interfaces using an OSC message. I've been trying to trick the CSI FB_Processor into sending the right OSC message for me, but nothing useful so far.

So Geoff, given you've already figured out how to send OSC messages, is it possible to get an Action we can use to send an arbitrary message? The trick is I'd probably want to invoke it from a different surface than the one receiving it, which might complicate matters.

Is there more complexity in this than I appreciate?
Depends on the tools at your disposal with Lemur

TouchOSC has a free editor available.

TouchOSC Layouts are used for different Surfaces.

Within Layouts there are Pages to which can be ascribed a name property.

Then you can do this - from the docs page:

"The name of a page is used when constructing the automatic OSC address of a control and can be used to remotely make TouchOSC switch to the page by sending an OSC message to the device with the OSC address: /<pagename>"

It was then a simple matter of setting the Page's name property to the name of the Zone/VST (with risky chars changed to underscores) and coding CSI to send the Zone/VST name on each Zone change.

This is the output - the first 2 lines switch the iOS devices to the proper GUIs -- if Lemur has something like this you are good to go.

Let me know if you can/can't do this.

Probably the 2 most popular apps are TouchOSC and Lemur, so, we should support both if possible


Code:
OUT -> iPhone /VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__ 
OUT -> iPad /VST__UAD_Lexicon_224__Universal_Audio__Inc__ 
OUT -> iPhone /Ch2UlHi  1.000000  
OUT -> iPhone /Ch2Vol  0.500000  
OUT -> iPhone /Ch2Tr  0.500000  
OUT -> iPhone /Ch2Bass  0.740656  
OUT -> iPad /Program  0.625000  
OUT -> iPad /BASS  0.500000  
OUT -> iPad /MID  0.343750  
OUT -> iPad /CROSSOVER  0.156250  
OUT -> iPad /TREBLEDECAY  0.875000  
OUT -> iPad /DEPTH  0.332001  
OUT -> iPad /Mode_Enh  1.000000  
OUT -> iPad /Decay_Opt  1.000000  
OUT -> iPad /Wet_Solo  1.000000  
OUT -> iPad /DiffusionInc  0.500000  
OUT -> iPad /DiffusionDec  -1.000000  
OUT -> EuCon Select1  0.000000  
OUT -> EuCon Select2  1.000000
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-29-2020, 01:46 PM   #7118
MalcolmG
Human being with feelings
 
MalcolmG's Avatar
 
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
Default

Quote:
Originally Posted by Geoff Waddington View Post
"The name of a page is used when constructing the automatic OSC address of a control and can be used to remotely make TouchOSC switch to the page by sending an OSC message to the device with the OSC address: /<pagename>"


Yeah, it s similar, except the message is /Interface PageName


Officially they support spaces in the page name (wrap it in quotes if so) , but even if we took the same restrictions as above, that would be fine.

Relevant docs are here https://liine.net/assets/files/lemur...User-Guide.pdf Page 68, 3rd paragraph from the bottom.

Quote:
Originally Posted by Geoff Waddington View Post
It was then a simple matter of setting the Page's name property to the name of the Zone/VST (with risky chars changed to underscores) and coding CSI to send the Zone/VST name on each Zone change.


That would be perfect.
__________________
Filter Theory | CSI Notes wiki

Last edited by MalcolmG; 02-29-2020 at 03:00 PM.
MalcolmG is offline   Reply With Quote
Old 02-29-2020, 05:05 PM   #7119
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

New build is up.

It now outputs both TouchOSC style and Lemur style Page/Layout changes.

TouchOSC is not bothered by the superfluous messages, we'll see about Lemur

Code:
OUT -> iPhone /Home 
OUT -> iPhone /Interface Home 
OUT -> iPad /Home
OUT -> iPad /Interface Home
OUT -> iPhone /VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__ 
OUT -> iPhone /Interface VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__ 
OUT -> iPad /VST__UAD_Lexicon_224__Universal_Audio__Inc__ 
OUT -> iPad /Interface VST__UAD_Lexicon_224__Universal_Audio__Inc__
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
Geoff Waddington is offline   Reply With Quote
Old 02-29-2020, 05:56 PM   #7120
MalcolmG
Human being with feelings
 
MalcolmG's Avatar
 
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
Default

Quote:
Originally Posted by Geoff Waddington View Post
New build is up.

It now outputs both TouchOSC style and Lemur style Page/Layout changes.

TouchOSC is not bothered by the superfluous messages, we'll see about Lemur

Code:
OUT -> iPhone /Home 
OUT -> iPhone /Interface Home 
OUT -> iPad /Home
OUT -> iPad /Interface Home
OUT -> iPhone /VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__ 
OUT -> iPhone /Interface VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__ 
OUT -> iPad /VST__UAD_Lexicon_224__Universal_Audio__Inc__ 
OUT -> iPad /Interface VST__UAD_Lexicon_224__Universal_Audio__Inc__

That was quick thanks, I'll test it out tonight
__________________
Filter Theory | CSI Notes wiki
MalcolmG 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 02:15 AM.


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