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

Reply
 
Thread Tools Display Modes
Old 03-20-2020, 10:08 AM   #7601
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by Funkybot View Post
Agree that splitting it up can make sense. Even if it's just two tabs of one window (Edit tab, Create tab). Don't be afraid to make the screen bigger too. Even on my laptop, the current screen can be comfortably expanded in size.
+1 for two tabs, Edit and Create. Resizable window, if it's not a nightmare.

Quote:
Would personally love it if you could implement a more traditional "Learn" type mode for FX [at least] where I could open a plugin, click Learn, move an FX, move a parameter on a surface, add any modifiers, repeat as necessary, then hit Save to create FX zones.
From where we are at the moment, turning a surface control will select the control on the screen. Modifiers should be recognised and shown in simple check boxes. FX parameter would be selected from a list (if the naming is obscure, Reaper's FX window shows 'last touched control'- you can get the name there). Rinse and repeat, hit save when done.

Quote:
Editing surface .zon files seems like it could be accomplished easily (select the widget, assign an action - worked for a bit in a prior build of the current Edit window).
I agree. People will have their own priorities for what Actions should be assigned to what buttons.

This, and FX.zon creation should be the most easily operable bits of the window.

Quote:
But I almost see creating surface .zon files as a nightmare for most users, but maybe you're envisioning a way to make it simple and foolproof. If there's no way to avoid the nightmare, maybe leave that text only for now and we just all work together to help you make sure we've got a wide list of available surfaces.
Agree. I'd leave out creation of surface.zon files, at least initially. We have a pretty good base of surface.zon and surface.mst files. The more adventurous user can study these in a text editor to see how they're put together.

Having lots of examples and clear guidance for what mode a surface shoud be placed in to use existing .mst and/or .zon files are key here.

Quote:
Last thought: I can see a common use-case where users have some random MIDI controller box that they want to map and there's no .mst. Asking a complete newb to create an .mst for each random surface may be a bit much. Would it make sense to create a "General_MIDI_Device.mst" that captures the general MIDI data outputs for CC's 0-127 across channels 1-16? Or is a "Device Learn" also going to be added? Studio One has a window where you hit Learn, move a knob, fader, or press a button, and it creates a surface device for any controller. Then you can assign that device to any plugin, etc. Maybe something similar. Just trying to think of the use-case of "I've got something obscure and I'm not technical" and how to deal with that.
Lovely idea, later maybe?
MixMonkey is offline   Reply With Quote
Old 03-20-2020, 10:18 AM   #7602
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
Default

Quote:
Originally Posted by MixMonkey View Post
Parameter FX lists aren't working at the moment.
"Show Params When FX Inserted" is working. That's what I meant.
Funkybot is offline   Reply With Quote
Old 03-20-2020, 10:26 AM   #7603
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by WaveTrans View Post
The Nano has 4 modes, MCP, LogicPro, HUT and user defined.
It works with CSI in MCP and LogicPro mode, HUT and UserDefined did not respond.

However, LogicPro did not behave differently when it comes to Tracking and Banking. Same as MCP.

[/Code]
IN <- nano 90 18 7f
IN <- nano 90 18 00
IN <- nano 90 19 7f
IN <- nano 90 19 00
IN <- nano 90 18 7f
IN <- nano 90 18 00
IN <- nano 90 18 7f
IN <- nano 90 18 00
IN <- nano 90 19 7f
IN <- nano 90 19 00
IN <- nano 90 1a 7f
IN <- nano 90 1a 00
IN <- nano 90 1b 7f
IN <- nano 90 1b 00
IN <- nano 90 1c 7f
IN <- nano 90 1c 00
IN <- nano 90 1d 7f
IN <- nano 90 1d 00
IN <- nano 90 1e 7f
IN <- nano 90 1e 00
IN <- nano 90 1f 7f
IN <- nano 90 1f 00
[code]
I think you misunderstood me. It isn't the MIDI output generated by the Channel L/R buttons that's the issue, rather whether pressing these buttons alters the message sent by the fader (and the other channel controls.

The way manufacturers have 'stretched' a single channel surface into an eight channel protocol (Mackie) is by internally changing the surface output messages to address each of the eight channels individually. The Channel L/R buttons do this.

Take the fader for instance:

When addressing channel one the message needed is:
Code:
e0 7f 7f
Channel two:
Code:
e1 7f 7f
Channel three:
Code:
e2 7f 7f
See what message the fader is sending and then press the channel L or R buttons and see if the fader message changes to confirm if this is what is happening on the Nano.
MixMonkey is offline   Reply With Quote
Old 03-20-2020, 10:27 AM   #7604
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by Funkybot View Post
"Show Params When FX Inserted" is working. That's what I meant.
Ah yes, quite right
MixMonkey is offline   Reply With Quote
Old 03-20-2020, 12:30 PM   #7605
TVbene
Human being with feelings
 
Join Date: Oct 2017
Posts: 42
Default

Quote:
Originally Posted by Geoff Waddington View Post
Not currently, this is kind of a radio button thing -- we decided not to do radio buttons when we added GoZone -- this looks like a reason to think about radio buttons again
To me it sounds like an important feature if you want to include the 8x8 pad controllers for example - because their layout is very abstract, so LEDs help a lot.

I made a short video that shows how I use a script for Launchpad Mini with Bitwig, I think it's similar to the implementation with Ableton Live:
https://youtu.be/wrcKjqzMilk

You have the right hand side column for selecting the modes (volume, pan, and send 1, 2, 3 and 4). The LEDs show which mode is selected. Not for precise mixing but I love it for live stuff where its often about turning things on/off.
TVbene is offline   Reply With Quote
Old 03-20-2020, 03:14 PM   #7606
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by TVbene View Post
To me it sounds like an important feature if you want to include the 8x8 pad controllers for example - because their layout is very abstract, so LEDs help a lot.

I made a short video that shows how I use a script for Launchpad Mini with Bitwig, I think it's similar to the implementation with Ableton Live:
https://youtu.be/wrcKjqzMilk

You have the right hand side column for selecting the modes (volume, pan, and send 1, 2, 3 and 4). The LEDs show which mode is selected. Not for precise mixing but I love it for live stuff where its often about turning things on/off.
That video illustrates your use case perfectly !

Yup, radio buttons of one sort or another are back on the feature to-do list :}
__________________
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 03-20-2020, 03:20 PM   #7607
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Thanks for the Edit Mode input folks.

As far as size, one user already complained it was too big, that's how it got to where it is now

That might not matter -- I think it should be broken up anyway.

What I'm hearing most, and I concur, is the use case for quickly setting up FX Zones.

Secondly, tweaking existing Surface .zon files.

Perhaps that is enough to get out of the gate.

I'm envisioning the current window being used for monitoring (as it is now) with the addition of some buttons to launch other non-modal windows such as the FX generator and the Surface tweaker, something along those lines...
__________________
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 03-20-2020, 04:00 PM   #7608
Funkybot
Human being with feelings
 
Funkybot's Avatar
 
Join Date: Jul 2007
Location: New Joisey
Posts: 5,973
Default

Quote:
Originally Posted by Geoff Waddington View Post
Thanks for the Edit Mode input folks.

As far as size, one user already complained it was too big, that's how it got to where it is now

That might not matter -- I think it should be broken up anyway.

What I'm hearing most, and I concur, is the use case for quickly setting up FX Zones.

Secondly, tweaking existing Surface .zon files.

Perhaps that is enough to get out of the gate.

I'm envisioning the current window being used for monitoring (as it is now) with the addition of some buttons to launch other non-modal windows such as the FX generator and the Surface tweaker, something along those lines...
Sounds good!
Funkybot is offline   Reply With Quote
Old 03-20-2020, 05:05 PM   #7609
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
I'm envisioning the current window being used for monitoring (as it is now) with the addition of some buttons to launch other non-modal windows such as the FX generator and the Surface tweaker, something along those lines...
Given you mentioned monitoring, how hard would it be add an option to output mst/zon parser errors to the log?

This would help a lot in those cases where a change isn’t being picked up, and after 15 minutes of tweaks/staring at it/swearing you realise you forgot the quotes, or duplicated a msg, or similar.

Assuming the parser throws an exception of some sort when it barfs on something, outputting that could help a lot.
__________________
Filter Theory | CSI Notes wiki
MalcolmG is offline   Reply With Quote
Old 03-20-2020, 11:34 PM   #7610
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Awright !!

Guess I should follow my own rules about quotes

Now that it is working, props to @inertia who supplied the FP code he had to the CSI project, thanks @inertia
Awesome that it worked. Did you get the track colouring working as well?

I'd be more than happy to stop developing my controller and work with you on Faderport modifications and do the coding for it. I see no reason to invest so much time working away from the CSI now there is significant headway for Fadeport support.
inertia is offline   Reply With Quote
Old 03-21-2020, 01:58 AM   #7611
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,814
Default

I have FX control to implement now. The current Faderport 16 support is working well, but is in part customized for my own needs of course. I'll be putting in comments to make this all easy to grasp at a glance I hope.

Panning is not working right now with the small and large encoders. There is just one of each on the controller. Could someone check whether I'm doing this correctly ?

How the encoders work:
Turn -> b0 3c xx or b0 10 xx
left -> 41 - 7f (slowest to fastest)
right -> 01 - 3f (slowest to fastest)
MST
Code:
Widget RotarySmall
	Encoder b0 10 7f
WidgetEnd
Widget RotaryBig 
    Encoder b0 3c 7f
WidgetEnd
ZON (PanPrimary included in Home Zone)
Code:
Zone "PanPrimary"
	SelectedTrackNavigator
	RotarySmall 		TrackPan "0"
	RotarySmallPush		GoZone PanWidth
ZoneEnd

Zone "PanWidth"
	SelectedTrackNavigator
	RotarySmall 	TrackPanWidth "1"
	RotarySmallPush	GoZone PanPrimary
ZoneEnd
None of the controls in Reaper are reacting thus far. If I can't get this to work, I'll switch to zoning out the faders to do the panning.
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom
airon is offline   Reply With Quote
Old 03-21-2020, 03:09 AM   #7612
schoko
Human being with feelings
 
Join Date: Jul 2018
Posts: 20
Default

Quote:
Originally Posted by Geoff Waddington View Post
Hmmm... don't see anything obvious.
Thanks for taking a look, but i don't know how to debug this problem.
Reascript console sends out the message.
But on the other side in the open stage control debug window no input is shown.
I tried OSCII-BOT to Monitor OSC Messages (show-io.txt just shows an empty black window).

Any Ideas to analyze this (Preferences//Control/OSC/Web is configured like described in the wiki page)

thanks
schoko is offline   Reply With Quote
Old 03-21-2020, 03:53 AM   #7613
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Yes, I obviously misunderstood, sorry.
Not shure if I got it right this time, but I tried .

I hit the ChannelLeft button and then moved the fader and checked for the code.

CSI console shows Fader 2, hit CL button again, Fader is designated Fader 3 and so on until Fader 8.

With hitting the ChannelRight button it goes backwards Fader 8 to Fader 1.

As soon as Fader1 is indicated, the surface is working again.

Is this what you meant?
Does this make sense?

Sorry for being a bit slow.
Quote:
Originally Posted by MixMonkey View Post
I think you misunderstood me. It isn't the MIDI output generated by the Channel L/R buttons that's the issue, rather whether pressing these buttons alters the message sent by the fader (and the other channel controls.

The way manufacturers have 'stretched' a single channel surface into an eight channel protocol (Mackie) is by internally changing the surface output messages to address each of the eight channels individually. The Channel L/R buttons do this.

Take the fader for instance:

When addressing channel one the message needed is:
Code:
e0 7f 7f


Channel two:
Code:
e1 7f 7f
Channel three:
Code:
e2 7f 7f
See what message the fader is sending and then press the channel L or R buttons and see if the fader message changes to confirm if this is what is happening on the Nano.
WaveTrans is offline   Reply With Quote
Old 03-21-2020, 04:10 AM   #7614
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by MalcolmG View Post
Given you mentioned monitoring, how hard would it be add an option to output mst/zon parser errors to the log?

This would help a lot in those cases where a change isn’t being picked up, and after 15 minutes of tweaks/staring at it/swearing you realise you forgot the quotes, or duplicated a msg, or similar.

Assuming the parser throws an exception of some sort when it barfs on something, outputting that could help a lot.
Yeah, the never ending parsing battle...

Good points all, will put on to-do list.
__________________
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 03-21-2020, 04:13 AM   #7615
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
Awesome that it worked. Did you get the track colouring working as well?
Thanks for reminding me, see build post below

Quote:
Originally Posted by inertia View Post
I'd be more than happy to stop developing my controller and work with you on Faderport modifications and do the coding for it. I see no reason to invest so much time working away from the CSI now there is significant headway for Fadeport support.
Thanks again for the code, from me and the whole CSI community !!

Thanks as well for the offer to help, that sure will come in handy testing FP stuff

Don't really need any help coding right now, but thanks again for the offer.
__________________
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

Last edited by Geoff Waddington; 03-21-2020 at 04:21 AM.
Geoff Waddington is offline   Reply With Quote
Old 03-21-2020, 04:20 AM   #7616
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

New build is up.

Added Track colour support.

These are made up values, replace with real ones, notice the new syntax for Track colour:

Code:
Widget Select1
        Press 90 05 7f
        FB_FaderportRGB7Bit 90 05 7f
WidgetEnd

Zone "Channel|"
        Select| TrackUniqueSelect { Track }
ZoneEnd
__________________
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 03-21-2020, 05:14 AM   #7617
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Thanks for reminding me, see build post below



Thanks again for the code, from me and the whole CSI community !!

Thanks as well for the offer to help, that sure will come in handy testing FP stuff

Don't really need any help coding right now, but thanks again for the offer.
No problem.

I do have some issues when I tested the stuff this morning.

I have trouble open existing projects and the Faderport doesn't initialise. It works perfectly ok with a new project though.

Another question I have : How can the Clear Solo and Clear Mute buttons be implemented? I had to write code to sort this out in my controller.

And one more thing...is it possible to set up exclusivity modes for some buttons like Channel and Bank? They shouldn't be turned on at the same time.
inertia is offline   Reply With Quote
Old 03-21-2020, 06:23 AM   #7618
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
No problem.

I do have some issues when I tested the stuff this morning.

I have trouble open existing projects and the Faderport doesn't initialise. It works perfectly ok with a new project though.
Yeah, there are some initialization issues, best to launch by double clicking .rpp files for now.

Quote:
Originally Posted by inertia View Post
Another question I have : How can the Clear Solo and Clear Mute buttons be implemented? I had to write code to sort this out in my controller.
Had a quick look in Reaper/SWS actions, didn't see anything, will have to write something.

Quote:
Originally Posted by inertia View Post
And one more thing...is it possible to set up exclusivity modes for some buttons like Channel and Bank? They shouldn't be turned on at the same time.
Why shouldn't they be turned on (active) at the same time ?
__________________
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 03-21-2020, 06:53 AM   #7619
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yeah, there are some initialization issues, best to launch by double clicking .rpp files for now.



Had a quick look in Reaper/SWS actions, didn't see anything, will have to write something.



Why shouldn't they be turned on (active) at the same time ?
The bank button is supposed to enable paging back and forth in banks of 8 or 16 while channel moves the page by 1. There's other buttons that require this kind of relationship. I can list them if you like. Maybe in the widget setup we would need to list buttons and their opposite states. Either channel or bank must lit, both can't be off or on at the same time.
inertia is offline   Reply With Quote
Old 03-21-2020, 07:49 AM   #7620
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
The bank button is supposed to enable paging back and forth in banks of 8 or 16 while channel moves the page by 1. There's other buttons that require this kind of relationship. I can list them if you like. Maybe in the widget setup we would need to list buttons and their opposite states. Either channel or bank must lit, both can't be off or on at the same time.
Ah, just had a look at the FP panel, the banking setup for FP is very different from MCU.

CSI does not currently have support for Channel and Bank mode buttons.

The banking support is for the MCU style, 4 button approach.

Will have to think about how to approach this kind of thing, and yes, as you say, it involves radio button behaviour

Man, seems like each time I learn something new about the FP8 and FP16, I see where they cut yet another corner or two
__________________
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 03-21-2020, 08:00 AM   #7621
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Ah, just had a look at the FP panel, the banking setup for FP is very different from MCU.

CSI does not currently have support for Channel and Bank mode buttons.

The banking support is for the MCU style, 4 button approach.

Will have to think about how to approach this kind of thing, and yes, as you say, it involves radio button behaviour

Man, seems like each time I learn something new about the FP8 and FP16, I see where they cut yet another corner or two
I have no experience with other controllers so can't say. I guess their mcu behavior is translated in the firmware so not sure how cutting corners helps them haha.

But yeah, there is a fair bit to do that is more than just adding buttons and adding an action which is why I offered hands on coding help 😊
inertia is offline   Reply With Quote
Old 03-21-2020, 08:04 AM   #7622
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by WaveTrans View Post
Yes, I obviously misunderstood, sorry.
Not shure if I got it right this time, but I tried .

I hit the ChannelLeft button and then moved the fader and checked for the code.

CSI console shows Fader 2, hit CL button again, Fader is designated Fader 3 and so on until Fader 8.

With hitting the ChannelRight button it goes backwards Fader 8 to Fader 1.

As soon as Fader1 is indicated, the surface is working again.

Is this what you meant?
Does this make sense?

Sorry for being a bit slow.
Hey, no probs The concept is pretty obscure. The results you've provided confirm that the nano does indeed change its output messages to control 8 channels.

What we need to determine now is whether the 'User Defined' mode behaves in the same way. Switch the unit to 'User Defined' mode and do the same thing again. See what message is sent by the fader and then push the Channel L or R button and check the fader message again.
MixMonkey is offline   Reply With Quote
Old 03-21-2020, 08:21 AM   #7623
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
I have no experience with other controllers so can't say. I guess their mcu behavior is translated in the firmware so not sure how cutting corners helps them haha.
I'm talking about the actual control count.

From looking at the panel I assume the Channel/Bank movement is caused by pressing Prev and Next, correct ?

If that is correct, the FP has:
Prev
Next
Channel
Zoom
Scroll
Bank

whilst the MCU has:
Left
Right
Up
Down
Scrub
Zoom
ChannelLeft
ChannelRight
BankLeft
BankRight

That's what I mean by cutting corners.

You have to set the surface to Bank mode , then press Prev or Next for an operation to occur.

If you want to move by one Channel, you have to set the surface to Channel mode , then press Prev or Next for an operation to occur.

All this mode switching starts defeating the very purpose of having a Surface -- fast, intuitive, uncluttered operation.

I fully realize this is always a tradeoff, but they have really dropped a lot of functionality compared to an MCU, heck, they don't have separate Record Arm buttons or even an encoder for each Channel -- that's some pretty big corners to cut
__________________
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 03-21-2020, 08:32 AM   #7624
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
I'm talking about the actual control count.

From looking at the panel I assume the Channel/Bank movement is caused by pressing Prev and Next, correct ?

If that is correct, the FP has:
Prev
Next
Channel
Zoom
Scroll
Bank

whilst the MCU has:
Left
Right
Up
Down
Scrub
Zoom
ChannelLeft
ChannelRight
BankLeft
BankRight

That's what I mean by cutting corners.

You have to set the surface to Bank mode , then press Prev or Next for an operation to occur.

If you want to move by one Channel, you have to set the surface to Channel mode , then press Prev or Next for an operation to occur.

All this mode switching starts defeating the very purpose of having a Surface -- fast, intuitive, uncluttered operation.

I fully realize this is always a tradeoff, but they have really dropped a lot of functionality compared to an MCU, heck, they don't have separate Record Arm buttons or even an encoder for each Channel -- that's some pretty big corners to cut
Yes that it is correct. And you're right.. It is not as fast as just hitting buttons for each operation. On the other hand, we have several buttons that have no function in Reaper that could be mapped instead now native mode is working.
inertia is offline   Reply With Quote
Old 03-21-2020, 08:59 AM   #7625
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
On the other hand, we have several buttons that have no function in Reaper that could be mapped instead now native mode is working.
Do those buttons not send anything at all in MCU mode ?

And don't get me wrong on Presonus, I think they generally do great products, and I'm sure this integrates perfectly with Studio One, just a bit disappointed in its general purpose control surface behaviour, that's all
__________________
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 03-21-2020, 09:12 AM   #7626
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Do those buttons not send anything at all in MCU mode ?

And don't get me wrong on Presonus, I think they generally do great products, and I'm sure this integrates perfectly with Studio One, just a bit disappointed in its general purpose control surface behaviour, that's all
There's a fair few buttons that do nothing in MCU mode at all because they are Studio One specific and don't send out midi codes in MCU mode.

It also integrates very well with Mixbus but they have written a native controller for it.

I am very happy with the controllers for my use. They can't replace the mouse and keyboard for me, but I am unsure I would ever be comfortable or willing to give up fine control of using a DAW with just a controller. I just find the mixing process much more comfortable with real faders.
inertia is offline   Reply With Quote
Old 03-21-2020, 09:34 AM   #7627
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
There's a fair few buttons that do nothing in MCU mode at all because they are Studio One specific and don't send out midi codes in MCU mode.

It also integrates very well with Mixbus but they have written a native controller for it.

I am very happy with the controllers for my use. They can't replace the mouse and keyboard for me, but I am unsure I would ever be comfortable or willing to give up fine control of using a DAW with just a controller. I just find the mixing process much more comfortable with real faders.
Definitely, there are a lot of things that are just fine mousey/keyboardy, and others that are just SO much better on a surface.

As far as integration, CSI doesn't support the original Faderport either, since it has a 2 midi message protocol (6 bytes).

You might want to revisit writing your own support, it isn't that bad, and I can clearly see from the code you kindly shared that you get what's going on here, glad to help in any way I can.

Meanwhile, it looks more and more like CSI radio buttons are inevitable, pondering...
__________________
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 03-21-2020, 11:52 PM   #7628
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
Definitely, there are a lot of things that are just fine mousey/keyboardy, and others that are just SO much better on a surface.

As far as integration, CSI doesn't support the original Faderport either, since it has a 2 midi message protocol (6 bytes).

You might want to revisit writing your own support, it isn't that bad, and I can clearly see from the code you kindly shared that you get what's going on here, glad to help in any way I can.

Meanwhile, it looks more and more like CSI radio buttons are inevitable, pondering...
We will see if I get back to it hehe

I can dig up the code I had for Mute/Solo clear.
inertia is offline   Reply With Quote
Old 03-22-2020, 04:27 AM   #7629
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
We will see if I get back to it hehe

I can dig up the code I had for Mute/Solo clear.
No worries on the code.

I'm wondering if you might want to write a lua script tied to a Reaper action to do the clear functions and just use something like this:

Code:
Zone "Buttons|"
       ClearMute Reaper "EzD54f" // someCrazyStringReaperNamesTheCustomAction
       ClearSolo Reaper "GrtY4f" // SomeCrazyStringReaperNamesTheCustomAction


ZoneEnd
__________________
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 03-22-2020, 09:13 AM   #7630
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by MixMonkey View Post
Hey, no probs The concept is pretty obscure. The results you've provided confirm that the nano does indeed change its output messages to control 8 channels.

What we need to determine now is whether the 'User Defined' mode behaves in the same way. Switch the unit to 'User Defined' mode and do the same thing again. See what message is sent by the fader and then push the Channel L or R button and check the fader message again.
Ok, I set the Nano to user-def mode upon startup and wondered if that is all it takes

When I run the litte test, it turned out that the behaviour in user defined mode is exactly the same as in MCP mode (also in LogicPro mode; HUI mode makes only funny numbers).

ChannelRight->Faders1-8
ChannelLeft->Faders8-1

Again the surface is out of order if faders2-8 are indicated.
Only when fader1 is on, the Nano is working.

Any idea why the Nano behaves so?

I checked in the user-def app which is provided for changing the layout of the Nano. The Channel and Bank keys are not available for changes (greyed out). So I guess there´s something hardwired going on regardless of the mode.


Anything I can do about it?
Or any workaround via CSI?

Last edited by WaveTrans; 03-22-2020 at 09:36 AM.
WaveTrans is offline   Reply With Quote
Old 03-22-2020, 09:47 AM   #7631
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by WaveTrans View Post
Any idea why the Nano behaves so?
Yep, that's how they've made it possible for a single fader surface to cover eight channels (see my previous posts)

Quote:
I checked in the user-def app which is provided for changing the layout of the Nano. The Channel and Bank keys are not available for changes (greyed out).
Are they greyed out when you set both the 'Control Protocol' and 'Control Mode' to User Define?
Quote:
So I guess there´s something hardwired going on regardless of the mode.
Yes, there is something hardwired. The Channel buttons change the messages that the unit sends out, so it can address different channels.

Quote:
Anything I can do about it?
Or any workaround via CSI?
Well, you could just try accepting the way they've gone about things and change your surface.zon to be eight channels instead of one. Then you would step through the channels using Channel L/R (the messages will be changed internally, not via CSI) I'm not entirely clear how the banking groups of eight will work, you'll have to experiment. Note: DON'T assign the Channel L/R buttons to anything in CSI, they are only used to switch the Nano messages internally.

Alternatively, you could set the Nano to Channel one using the Channel L/R buttons, never touch them again and carry on as you are. Again. don't assign the Channel L/R buttons to anything in CSI.
MixMonkey is offline   Reply With Quote
Old 03-22-2020, 10:55 AM   #7632
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by MixMonkey View Post
Yep, that's how they've made it possible for a single fader surface to cover eight channels (see my previous posts)
I really wonder why they forced this 8 channel banking scheme onto a single channel surface; seems rather counter-intuitive to me.


Quote:
Originally Posted by MixMonkey View Post
Are they greyed out when you set both the 'Control Protocol' and 'Control Mode' to User Define?
Under Control protocol there is only MCP and HUI to chose from

Quote:
Originally Posted by MixMonkey View Post
Yes, there is something hardwired. The Channel buttons change the messages that the unit sends out, so it can address different channels.
As mentioned above, it would be more intuitive without this 8 channel banking scheme.

Quote:
Originally Posted by MixMonkey View Post
Well, you could just try accepting the way they've gone about things and change your surface.zon to be eight channels instead of one. Then you would step through the channels using Channel L/R (the messages will be changed internally, not via CSI) I'm not entirely clear how the banking groups of eight will work, you'll have to experiment. Note: DON'T assign the Channel L/R buttons to anything in CSI, they are only used to switch the Nano messages internally.
In the beginning, when I used only marginally adapted CSI MCU files banking and channel switching worked like on an 8 channel surface. If you got to channel 8 and wanted to move to channel 9 you had to press Bankright to get to channel16, then move back to channel 9.

So I got used early to chose tracks with the mouse and won´t miss banking and channeling much

It´s just the fact that the surface stops working when hitting the channel keys that motivated me to look into this.

Quote:
Originally Posted by MixMonkey View Post
Alternatively, you could set the Nano to Channel one using the Channel L/R buttons, never touch them again and carry on as you are. Again. don't assign the Channel L/R buttons to anything in CSI.
I guess the Banking widgets are also obsolete in this sense?

Thanks for pointing things out so clearly (and patiently)

Last edited by WaveTrans; 03-22-2020 at 11:01 AM.
WaveTrans is offline   Reply With Quote
Old 03-22-2020, 12:00 PM   #7633
timothys_monster
Human being with feelings
 
timothys_monster's Avatar
 
Join Date: Jan 2012
Location: Germany
Posts: 1,130
Default

Hey WaveTrans and MixMonkey,

thanks for dealing with this weirdo controller. I would also LOVE to see a proper track selection happening. Let me know if I can be of help testing anything related to it.

@WaveTrans: have you been successful untying the two first encoders via iMap?
timothys_monster is offline   Reply With Quote
Old 03-22-2020, 01:17 PM   #7634
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
No worries on the code.

I'm wondering if you might want to write a lua script tied to a Reaper action to do the clear functions and just use something like this:

Code:
Zone "Buttons|"
       ClearMute Reaper "EzD54f" // someCrazyStringReaperNamesTheCustomAction
       ClearSolo Reaper "GrtY4f" // SomeCrazyStringReaperNamesTheCustomAction


ZoneEnd
It's easier than that. The api has "SoloAllTracks(0)" and that clears the solo button and "MuteAllTracks(0).
inertia is offline   Reply With Quote
Old 03-22-2020, 01:42 PM   #7635
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 4,835
Default

Quote:
Originally Posted by WaveTrans View Post
I really wonder why they forced this 8 channel banking scheme onto a single channel surface; seems rather counter-intuitive to me.
That's because all the DAWs have a Mackie mode and that mode is 8 channel. They had no choice but to play along or write their own driver for every DAW they wanted to support.

Quote:
Under Control protocol there is only MCP and HUI to chose from
That's a shame. On Page 31 of the manual, the table makes it look like there's a 'User Define' Control Protocol too.

Quote:
As mentioned above, it would be more intuitive without this 8 channel banking scheme.
I quite agree btw what does the 'Lock' button do? I don't suppose it disables the Channel L/R buttons, does it?


Quote:
In the beginning, when I used only marginally adapted CSI MCU files banking and channel switching worked like on an 8 channel surface. If you got to channel 8 and wanted to move to channel 9 you had to press Bankright to get to channel16, then move back to channel 9.
That's exactly how Icon want you to use it
Quote:
I guess the Banking widgets are also obsolete in this sense?
Not necessarily. The Channel L/R buttons change the Nano internally. The Bank buttons issue commands to the DAW- 'move along 8 channels' This is analogous to CSI's TrackBank Action.
Quote:
Thanks for pointing things out so clearly (and patiently)
You're welcome I'm sorry we haven't found a way to better tie it in with CSI. What we're looking for is a way to prevent the Channel L/R buttons changing the messages that the Nano sends, preferably allowing those buttons to be freed up to work with CSI.

If that 'Lock' button stops them changing the messages internally, but the buttons themselves still output a MIDI message, we'd be onto a winner!
MixMonkey is offline   Reply With Quote
Old 03-22-2020, 03:18 PM   #7636
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,150
Default

Quote:
Originally Posted by inertia View Post
It's easier than that. The api has "SoloAllTracks(0)" and that clears the solo button and "MuteAllTracks(0).
I feel like we are on slightly different pages here

You can write a lua script that calls "SoloAllTrscks(0)".

You can then save the script as a custom action -- Reaper will assign a string -- e.g. "Csfe47RGdsv".

Then you can assign any surface widget to that action :
Code:
soloWidget Reaper  "Csfe47RGdsv"
This is all doable by you right now, you can have this behaviour today with no changes to CSI at all.

Did I misinterpret what you are saying ?
__________________
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

Last edited by Geoff Waddington; 03-22-2020 at 03:32 PM.
Geoff Waddington is offline   Reply With Quote
Old 03-22-2020, 10:14 PM   #7637
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,814
Default

Don’t those codes change for every user ?

I’m on my way to my workstation. I do remember having something in the Faderport 16 Zone file for solo and mute clearing.Will report right back.
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom
airon is offline   Reply With Quote
Old 03-22-2020, 11:39 PM   #7638
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 800
Default

Quote:
Originally Posted by Geoff Waddington View Post
I feel like we are on slightly different pages here

You can write a lua script that calls "SoloAllTrscks(0)".

You can then save the script as a custom action -- Reaper will assign a string -- e.g. "Csfe47RGdsv".

Then you can assign any surface widget to that action :
Code:
soloWidget Reaper  "Csfe47RGdsv"
This is all doable by you right now, you can have this behaviour today with no changes to CSI at all.

Did I misinterpret what you are saying ?
Ok, I get you.

It's ok as a solution but ultimately the CSI should do as much as it can without the user having to write extra scripts or setup actions, I think.
inertia is offline   Reply With Quote
Old 03-23-2020, 12:23 AM   #7639
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 11,814
Default

Quote:
Originally Posted by airon View Post
Don’t those codes change for every user ?

I’m on my way to my workstation. I do remember having something in the Faderport 16 Zone file for solo and mute clearing.Will report right back.
Here are the actions, built in to Reaper. I have unsolo all tracks on one of the buttons on my X-Mini because I use it all the time.

SoloClear Reaper "40340" /Track: Unsolo all tracks
MuteClear Reaper "40339" /Track: Unmute all tracks
__________________
Using Latch Preview (Video) - Faderport 16 setup for CSI 1.1 , CSI 3.10
Website
"My ego comes pre-shrunk" - Randy Thom
airon is offline   Reply With Quote
Old 03-23-2020, 01:01 AM   #7640
WaveTrans
Human being with feelings
 
Join Date: Aug 2019
Location: Forest City
Posts: 336
Default

Quote:
Originally Posted by MixMonkey View Post
That's because all the DAWs have a Mackie mode and that mode is 8 channel. They had no choice but to play along or write their own driver for every DAW they wanted to support.
Well, they missed an opportunity here, no mistake

By the way, isn´t the "original" MCP code for channel leftRight 90 30 7f or 90 31 7f; the channel buttons send 90 18 7f or 90 1f 7f

And one more question: Why does it work for switching between sends with the channel keys?

Quote:
Originally Posted by MixMonkey View Post
That's a shame. On Page 31 of the manual, the table makes it look like there's a 'User Define' Control Protocol too.
There´s just the choice between MCP and HUI.

Quote:
Originally Posted by MixMonkey View Post
Not necessarily. The Channel L/R buttons change the Nano internally. The Bank buttons issue commands to the DAW- 'move along 8 channels' This is analogous to CSI's TrackBank Action.
The reaction of the Nano to the Bank buttons is the same as to the Channel buttons. Hitting Bank right takes it "out of order" until one presses bankLeft.

Quote:
Originally Posted by MixMonkey View Post
I quite agree btw what does the 'Lock' button do? I don't suppose it disables the Channel L/R buttons, does it?
Quote:
Originally Posted by MixMonkey View Post
If that 'Lock' button stops them changing the messages internally, but the buttons themselves still output a MIDI message, we'd be onto a winner!
Ah, the Lock Button. Another mysterious part of the Nano.
I couldn´t find anything about it in the manual so I went for applying our simple test scenario with the lock button engaged.

Locking apparently represses sending of the fader movement code while faderTouch is still being sent.

Lock engaged: ChannelRight -> FaderTouch2-8 and backwards with channelLeft

Apparently, neither the channel button codes sent nor the awkward "out of order" behaviour of the Nano are influenced by engaging the lick button.

Quote:
Originally Posted by MixMonkey View Post
You're welcome I'm sorry we haven't found a way to better tie it in with CSI. What we're looking for is a way to prevent the Channel L/R buttons changing the messages that the Nano sends, preferably allowing those buttons to be freed up to work with CSI.
I can only emphasize how grateful I am.
Without your help I would have dumped the Nano already

Last edited by WaveTrans; 03-23-2020 at 02:29 AM.
WaveTrans 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 01:52 AM.


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