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

Reply
 
Thread Tools Display Modes
Old Today, 05:16 AM   #7081
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 4,233
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...
__________________
CSI - You can donate here: geoffwaddington.ca
Beta software: https://stash.reaper.fm/v/38349/CSI%20beta.zip
EuCon software:
https://stash.reaper.fm/v/37947/reaper_csurf_EuCon.zip
Geoff Waddington is offline   Reply With Quote
Old Today, 05:50 AM   #7082
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 8,507
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; Today at 06:14 AM.
mschnell is offline   Reply With Quote
Old Today, 05:57 AM   #7083
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Posts: 123
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 Today, 06:00 AM   #7084
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 8,507
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; Today at 06:13 AM.
mschnell is offline   Reply With Quote
Old Today, 07:49 AM   #7085
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 294
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 online now   Reply With Quote
Old Today, 07:55 AM   #7086
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 294
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 online now   Reply With Quote
Old Today, 09:00 AM   #7087
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 678
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 online now   Reply With Quote
Old Today, 09:07 AM   #7088
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 294
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 online now   Reply With Quote
Old Today, 09:11 AM   #7089
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 678
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 online now   Reply With Quote
Old Today, 09:13 AM   #7090
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 678
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 online now   Reply With Quote
Old Today, 09:51 AM   #7091
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 294
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 online now   Reply With Quote
Old Today, 09:56 AM   #7092
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 678
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
Funkybot is online now   Reply With Quote
Old Today, 11:15 AM   #7093
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,100
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 online now   Reply With Quote
Old Today, 11:18 AM   #7094
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 678
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 online now   Reply With Quote
Old Today, 11:22 AM   #7095
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,100
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 online now   Reply With Quote
Old Today, 11:29 AM   #7096
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 649
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 online now   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 11:38 AM.


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