• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Now this is pretty cool....

I ordered the Console Compact and will see how I get along with it. I have the Console 1 but found it too large (and too mix focused) to justify the real-estate.
 
would have two (for switching hands) of the best encoders money can buy, endless, with haptic feedback and click function. But that's me :)

I might buy one of those, business opportunity anyone. :cool:

The MP Midi has a nice trick. They call it the Joker encoder. It controls any controllable part of the gui that you mouse over.

Best regards.
 
I ordered the Console Compact and will see how I get along with it. I have the Console 1 but found it too large (and too mix focused) to justify the real-estate.
Nice one.

Next item a bigger desk.

Best of regards
 
I might buy one of those, business opportunity anyone. :cool:

The MP Midi has a nice trick. They call it the Joker encoder. It controls any controllable part of the gui that you mouse over.

Best regards.
Yes, that's the idea :) Now it would be really interesting to know how many of the MP Midi users end up using only that Joker encoder after the novelty of having a new controller wears off ;)
 
Yes, that's the idea :) Now it would be really interesting to know how many of the MP Midi users end up using only that Joker encoder after the novelty of having a new controller wears off ;)
I wouldn't know about any other MP Midi user's that might fall into that demographic.
That sounds more like a character trait than a controller issue.
Myself, I have programmed which controls/coloured and positioned so I am familiar with what I need. It becomes second nature the more you use them.

Regards
 
I wouldn't know about any other MP Midi user's that might fall into that demographic.
That sounds more like a character trait than a controller issue.
Myself, I have programmed which controls/coloured and positioned so I am familiar with what I need. It becomes second nature the more you use them.

Regards
Fair enough. And of course it's a selective audience buying controllers like the MP Midi. But, not being critical or anything, there's also a good amount of folk in the music industry who will be running for the hills at the words "I have programmed...". The learning curve including the programming and the familiarising looks unnecessarily daunting. A 'Joker controller' on the other hand is instantly familiar and not testing the brain at all. So, as I said, interesting to know how many of the MP Midi users gravitate to that.:unsure:
 
Fair enough. And of course it's a selective audience buying controllers like the MP Midi. But, not being critical or anything, there's also a good amount of folk in the music industry who will be running for the hills at the words "."I have programmed... The learning curve including the programming and the familiarising looks unnecessarily daunting. A 'Joker controller' on the other hand is instantly familiar and not testing the brain at all. So, as I said, interesting to know how many of the MP Midi users gravitate to that.:unsure:
"I have programmed...
On the T/Screen there's a box/button called "Link" tap that-->touch a control --> twirl a H/Ware rotary, --> tap again choose a colour. 🤣
That's it, maybe programmed was not the best word to use. It makes me feel important tho'

Alternatively, maybe this is something you might like.


Made to order, cannot advise about cost, but a rumour I heard they are about $300

Best of regards.
 
I'm still struggling with the thought of having to translate, in my head, the GUI's knobs I see on the DAW's screen(s) to the layout of the knobs on the controller every time I switch from one plugin to the next. It means that I have to look thrice, first at the screen, then at the controller, and then back at the screen to start making changes. That can't be an efficient workflow. It's not like a mouse where hand movements are reflected by the cursor on the screen as positioning is completely disconnected. So for some plugins it may work because the layout of the controller matches the layout of the plugin selected, but then for all other plugins it won't. And I don't want to have to look at the controller knobs at all, for any reason. Who watches his/her mouse?

So rather than having to move my hands I would have one hand on the controller knob and the other hand selecting something on the screen (by touch or mouse), my eyes would be on the screen or anywhere else but not on my 'controller hand', and rather than 15 'OK' rotary encoders my controller would have two (for switching hands) of the best encoders money can buy, endless, with haptic feedback and click function. But that's me :)
Yeah I've tried em this is basically the issue with all the 'touch screen controls' controllers.

I mean they are useful if you are say, using an iPad for tracking REMOTE in another room and so forth.

But for mixing? Cant imagine using them for that purpose, like you say you're just constantly looking back and forth at it.
 
I don't think anyone is saying that T/Screens are the best option for mixing.

The range of controller's are hopefully giving a means to reaching certain outcomes in the process of making audio.
To each his own. I will leave it at that.

Kindest regards to all.
 
I don't think anyone is saying that T/Screens are the best option for mixing.

Never said they did, I'm just sharing my experience with the shortcomings.
The Slate Raven was pitched as a whole LCD mixing board kind of deal, I've always used it as a reference for the concept.
Steven still uses his to mix with afaik but I wonder how much of that is for show...
Not that all of his ideas fall flat mind you, VSX 5.0 is about as revolutionary of a product as you can get
 
I'm still struggling with the thought of having to translate, in my head, the GUI's knobs I see on the DAW's screen(s) to the layout of the knobs on the controller every time I switch from one plugin to the next. It means that I have to look thrice, first at the screen, then at the controller, and then back at the screen to start making changes. That can't be an efficient workflow. :)
As @TonalDynamics used this as an example, lets examine what is going on. In the hope it might clear up some confusion.
I believe this was in response to @TimC340 post ref, to "15 'OK' rotary encoders" nothing to do with T/Screens?
@SwitchBack can confirm if he so chooses?

MP Midi.
There is no need to look "thrice", as the Vst Gui is displayed on the screen, with the surrounding 32 H/Ware controls In my case... coloured for use.
Blue is for Filter Freq., Res., Release.
Red covers Envelopes. ADSR.
Green for Osc, Tune, Freq, Gain, offset. etc. and so on.
Maintaining the same scheme serves purpose as a visual colour filter. Simple but effective. This is all available on the MP Midi screen no need to look at the main screen.

It's not like a mouse where hand movements are reflected by the cursor on the screen as positioning is completely disconnected. So for some plugins it may work because the layout of the controller matches the layout of the plugin selected, but then for all other plugins it won't. And I don't want to have to look at the controller knobs at all, for any reason. Who watches his/her mouse?
There is no need to look at the mouse. See above, or below, regarding the MP Midi T/Screen

So rather than having to move my hands I would have one hand on the controller knob and the other hand selecting something on the screen (by touch or mouse), my eyes would be on the screen or anywhere else but not on my 'controller hand', and rather than 15 'OK' rotary encoders my controller would have two (for switching hands) of the best encoders money can buy, endless, with haptic feedback and click function. But that's me :)
This is where it becomes interesting in the Synth domain, you able to use the controls as you would a H/Ware Synth. No need to look at the main screen. If it were a hardware Synth would you keep looking at the main DAW Screen. I do not think folk do.
The same applies to outboard FX.

Not all T/Screen controllers are a Raven clone, so as a maxim it misses the point of how the MP Midi can be used.

Hope this helps
Kindest regards to all.
 
I think it’s worth saying that all of these controllers are intended to reduce reliance on the mouse/monitor combination. That might be an irrelevance to some, but if - like me - you’re prone to RSI from overuse of a mouse, and neck strain from imperfect monitor size or positioning, they can help to minimise these issues. I find the Flow Studio to be absolutely magic in this regard, as its own screen is large and hi-res enough to obviate any need to look at the main screen, and the feel of the encoders is smooth and with enough resistance to be a pleasure to use.

Of course this is a computer-based system and you’re never going to completely do without the mouse/monitor, but it’s helpful (for some at least) to try and reduce reliance on that combination.
IMG_9121.jpeg
 
@TimC340
You have yet to take the plastic screen protector off that screen 🙃

The RSI issue is a constant battle and having options that can address or help alleviate such problems make some of these controller's a worthwhile investment. To each his own.

Best of regards.
 
Haha - I always keep the screen protectors on. Dunno why, but I just leave them.

Edit: actually, with the amount of dust you can see on the device, maybe it's obvious why I leave them on!
 
Last edited:
Now I want to try Flow Studio, Nektar CS12, SSL UF1 and Console Compact.

Obviously I have a bad case of GAS and enjoy trying out different workflows (to the chagrin of my wallet).
 
As @TonalDynamics used this as an example, lets examine what is going on. In the hope it might clear up some confusion.
I believe this was in response to @TimC340 post ref, to "15 'OK' rotary encoders" nothing to do with T/Screens?
@SwitchBack can confirm if he so chooses?

MP Midi.
There is no need to look "thrice", as the Vst Gui is displayed on the screen, with the surrounding 32 H/Ware controls In my case... coloured for use.
Blue is for Filter Freq., Res., Release.
Red covers Envelopes. ADSR.
Green for Osc, Tune, Freq, Gain, offset. etc. and so on.
Maintaining the same scheme serves purpose as a visual colour filter. Simple but effective. This is all available on the MP Midi screen no need to look at the main screen.


There is no need to look at the mouse. See above, or below, regarding the MP Midi T/Screen


This is where it becomes interesting in the Synth domain, you able to use the controls as you would a H/Ware Synth. No need to look at the main screen. If it were a hardware Synth would you keep looking at the main DAW Screen. I do not think folk do.
The same applies to outboard FX.

Not all T/Screen controllers are a Raven clone, so as a maxim it misses the point of how the MP Midi can be used.

Hope this helps
Kindest regards to all.
The outset of this thread was @Vocalpoint asking to discuss the MP Midi as a controller for Studio One. Studio One as any DAW presents all its information on one or more screens, in the most basic setup controlled by mouse and keyboard.

Enter the MP Midi, what does it bring? In my view it brings 32 rotary encoders, in a different layout than what S1 shows on the screen. So the MP Midi relies on its own screen to show what's what, asking the user to take his/her eyes from the S1 screen(s) to look at a screen with a portion of what S1 is showing, adjust to the different layout, move hands to grab the appropriate encoders and then, I assume, focus on the main screen again to ensure that the correct parameters change in S1. And then move on to the next channel, with a different FX chain so with different controller needs, and repeat the process. And then have the Joker encoder to add what's missing, switching to the original screen-mouse workflow in some hybrid fashion.

So my comments were mainly directed at the ergonomics and workflow of the MP Midi for controlling S1 as a whole, and imho it introduces extra steps and thinking and memorising stuff and eye refocusing and hand movements compared to even the most basic setup with mouse and keyboard.

And then there's the price/quality tradeoff, because for the price of 32 encoders and a touchscreen 2 top quality encoders can be had, with haptic feedback for an even better workflow experience. And there's still a bank of proper faders missing (imho).

But, yeah, using the MP Midi for only one (e.g. remote) task with one layout, in combination with several other controllers each fulfilling another task could work for some. So peace.
 
Last edited:
take his/her eyes from the S1 screen(s) to look at a screen with a portion of what S1 is showing, adjust to the different layout, move hands to grab the appropriate encoders and then, I assume, focus on the main screen again to ensure that the correct parameters change in S1.

But, yeah, using the MP Midi for only one (e.g. remote) task with one layout, in combination with several other controllers each fulfilling another task could work for some. So peace.
This is the disconnect I see.
The GUI display is not on the main screen... it is being projected to the MP Midi screen. There is no other part of the Daw being projected to the MP screen. To me as a user of the MP Midi this is a major benefit, there is no need to look at the main Daw screen when adjusting controls.

Scenario use, whilst playing notes on a keyboard adjusting controls and listening to the output. Myself personally find this less distracting than fiddling with a mouse to locate a filter resonance then perhaps a cut-off frequency, then an envelope attack and so on, one control at a time in a linear fashion with the mouse.
If I have recorded material I can be adjusting 2 or more controls at once on the MPM or on any controller that displays the target GUI, on the controller H/Ware.

Also. with MP Midi...
A simple logical colour scheme plan unifies the use of a variety of Synths, so changing which Vst is in focus is less of problem.

Again, I am attempting to dispel what I see as misconceptions.

@SwitchBack I go in peace. Kindest regards for responding.
 
Last edited:
So my comments were mainly directed at the ergonomics and workflow of the MP Midi for controlling S1 as a whole
But that is exactly not what it's designed for. It's not a DAW on a touchscreen (which you can already have with the Remote Control app) nor is it a channel strip or mixing console. Although you can use it like that, particularly with the latest update.
It's primarily a plugin controller. You want to design a synth sound, let's say, then you bring up that synth on the internal screen, quite some of its controls are (automatically) mapped to the knobs, and the other non-knob elements can be operated via the touch screen.
In that sense, it's more akin to working with Komplete Kontrol rather than with FaderPort.
 
This is the disconnect I see.
The GUI display is not on the main screen... it is being projected to the MP Midi screen. There is no other part of the Daw being project to the MP screen. To me as a user of the MP Midi this is a major benefit, there is no need to look at the main Daw screen when adjusting controls.

Scenario use, whilst playing notes on a keyboard adjusting controls and listening to the output. Myself personally find this less distracting than fiddling with a mouse to locate a filter resonance then perhaps a cut-off frequency, then an envelope attack and so on, one control at a time in a linear fashion with the mouse.
If I have recorded material I can be adjusting 2 or more controls at once on the MPM or on any controller that displays the target GUI, on the controller H/Ware.

Also. with MP Midi...
A simple logical colour scheme plan unifies the use of a variety of Synths, so changing which Vst is in focus is less of problem.

Again, I am attempting to dispel what I see as misconceptions.

@SwitchBack I go in peace. Kindest regards for responding.

This all makes a lot of sense to me.
 
Back
Top