|
|
Post by lcr on Oct 16, 2018 7:05:56 GMT -6
What if, someone made a small desktop size controller similiar to Console 1 or faderport but maybe a few more knobs and buttons and instead of having labeled controls it had a bunch of led screens...
This product would use a plugin that is a plugin host. Once you load a plugin into the plugin, the user maps controls to the hardware control using the product plugins mapping parameters and not the DAWs. The led’s could be relabled by the user. User would save presets for plugins already mapped, or the product remembers mapped settings for each plugin. One drawback is the daw would have a bunch of inserts with the same name, so you wouldnt know what’s loaded in that insert slot looking at the mixer. Like a bunch of VMR’s for example. And I guess also have the ability to control generic DAW mixer settings also (level, pan, sends, mute, etc. ) Didnt Novation try and do something similiar but it didnt host the plugin to control? One can dream, This would be cool.
|
|
|
|
Post by lcr on Oct 16, 2018 7:10:45 GMT -6
Maybe this exists, if so please share!
|
|
ericn
Temp
Balance Engineer
Posts: 14,943 
|
Post by ericn on Oct 16, 2018 7:45:49 GMT -6
The problem is the only universal open control protocol is HUI, if AVID would open up EUCON to other hardware developers we would see some very cool stuff.
|
|
|
|
Post by lcr on Oct 16, 2018 9:23:44 GMT -6
What protocol does Console one use in PT?
|
|
|
|
Post by jdc on Oct 16, 2018 9:28:04 GMT -6
|
|
ericn
Temp
Balance Engineer
Posts: 14,943
|
Post by ericn on Oct 16, 2018 10:07:58 GMT -6
What protocol does Console one use in PT? I believe it’s there own and that’s the problem, if everybody uses there own the desktop gets crowded real fast. |
|
|
|
Post by sirthought on Oct 17, 2018 1:26:49 GMT -6
How is it that we're still stuck on HUI? Seems some smart folks could have developed something useful for those of us not using PT.
|
|
ericn
Temp
Balance Engineer
Posts: 14,943
|
Post by ericn on Oct 17, 2018 7:38:18 GMT -6
How is it that we're still stuck on HUI? Seems some smart folks could have developed something useful for those of us not using PT. We have EuConn, Euphonix was willing to license it to just about anybody, till AVID bought them and locked the door to other hardware vendors. That said, every controller designer I have talked to has explained that there is a love / hate relationship with plugin developers. To some extent you have to put some limitations on the plugin developers creativity to fit within the controller. |
|
|
|
Post by swurveman on Oct 17, 2018 9:32:24 GMT -6
The only plugin controller I would buy is if the controller had a screen on it that showed the plugin's controls, so that I wouldn't have to be looking at a computer screen anyway to check that I was turning the right nob.
|
|
|
|
Post by jdc on Oct 17, 2018 12:51:05 GMT -6
i've found in my short time with the softube console 1 setup that my muscle memory took over after the first day and i was only looking at the screen. the only exception to that is selecting the track that i'm working on, the font and led's at the top of the controller could be a bit bigger
|
|
|
|
Post by popmann on Oct 17, 2018 17:25:20 GMT -6
Cubase+AI knob. Most DAWs do mousewheel functional substitution(with a unit like my Griffin Powermate), albeit the scaling isn't always as smooth. Also, quick controls in Cubase (and I feel like Logic has a similar concept) can be mapped to basically any generic controller thing you have that will spit out CC or something.
What you're proposing sounds seriously flawed to me. That a USER maps all the buttons/knobs to various plug ins....remembers what they ARE....and has to have a layer of plug in wrapper to contend with for the ability to what? Do what the above does with a mouse in one hand and physical rotary in the other....plus the ability to turn two knobs at once--useful in a handful of vintage compressor emulations only really.
Here's what I'd also point out--as long as there have been DAWs, there have been people who HATE mouse+keyboard. Why do you think there's a solid solution that just hasn't been come up with? Pockets were once deeper...and more of the people BUYING DAWs were 100% trained on physical everything....and yet....with all that, what you have is what you have. Nearly everyone I know who buys a controller doesn't use it.
I've thought for a long time that the coolest thing would be for a DAW maker to implement an iPad app that whenever you open a plug in, it opens it's UI on the ipad. That seems like it would be one bit of code for the DAW maker....or technically the iOS app and then the one tweak of the host app....if they wanted to hit it out of the park, put an IPad dock ON a Presonus CS18, which controls Studio One on near "no need for a screen" levels....smartly developing a way to throw third party plug ins to a multitouch screen on it....takes care of that "issue" with first party controllers, which have always been good at driving the DAW itself, but less so third party anything.
|
|
|
|
Post by johneppstein on Oct 20, 2018 12:06:38 GMT -6
Cubase+AI knob. Most DAWs do mousewheel functional substitution(with a unit like my Griffin Powermate), albeit the scaling isn't always as smooth. Also, quick controls in Cubase (and I feel like Logic has a similar concept) can be mapped to basically any generic controller thing you have that will spit out CC or something. What you're proposing sounds seriously flawed to me. That a USER maps all the buttons/knobs to various plug ins....remembers what they ARE....and has to have a layer of plug in wrapper to contend with for the ability to what? Do what the above does with a mouse in one hand and physical rotary in the other....plus the ability to turn two knobs at once--useful in a handful of vintage compressor emulations only really. Here's what I'd also point out--as long as there have been DAWs, there have been people who HATE mouse+keyboard. Why do you think there's a solid solution that just hasn't been come up with? Pockets were once deeper...and more of the people BUYING DAWs were 100% trained on physical everything....and yet....with all that, what you have is what you have. Nearly everyone I know who buys a controller doesn't use it. I've thought for a long time that the coolest thing would be for a DAW maker to implement an iPad app that whenever you open a plug in, it opens it's UI on the ipad. That seems like it would be one bit of code for the DAW maker....or technically the iOS app and then the one tweak of the host app....if they wanted to hit it out of the park, put an IPad dock ON a Presonus CS18, which controls Studio One on near "no need for a screen" levels....smartly developing a way to throw third party plug ins to a multitouch screen on it....takes care of that "issue" with first party controllers, which have always been good at driving the DAW itself, but less so third party anything. I am one of those people who hates mouse-keyboard - to the point where I won't work on a DAW because the user interface drives me crazy, especially since there is little or no standardization. That being said, I have a couple of comments.
First, having tried a couple of controllers I think that one of the major factors impeding acceptance is that no controller I've seen (with one exception I'll get to) properly implements the controls in an intuitive manner. Most of them are just as annoying as mouse and keyboard and sometimes even more confusing and slow. Really, for me a controller would need to be a big as my console with an additional section for "outboard".
Second, there is one controller (which I have not personally used, but have observed in use) that does deal successfully with nearly all these problems successfully, and does get used all the time by people who own one. The reason that I said "nearly" is that it doesn't have physical controls, it's a touchscreen. That controller, or course, is the Slate Raven. Steven may come up with a lot of cockamamie ideas and his marketing style may bug the hell out of many people, but IMO the Raven is a stroke of genius.
|
|
|
|
Post by lcr on Oct 20, 2018 14:38:28 GMT -6
Cubase+AI knob. Most DAWs do mousewheel functional substitution(with a unit like my Griffin Powermate), albeit the scaling isn't always as smooth. Also, quick controls in Cubase (and I feel like Logic has a similar concept) can be mapped to basically any generic controller thing you have that will spit out CC or something. What you're proposing sounds seriously flawed to me. That a USER maps all the buttons/knobs to various plug ins....remembers what they ARE....and has to have a layer of plug in wrapper to contend with for the ability to what? Do what the above does with a mouse in one hand and physical rotary in the other....plus the ability to turn two knobs at once--useful in a handful of vintage compressor emulations only really. Here's what I'd also point out--as long as there have been DAWs, there have been people who HATE mouse+keyboard. Why do you think there's a solid solution that just hasn't been come up with? Pockets were once deeper...and more of the people BUYING DAWs were 100% trained on physical everything....and yet....with all that, what you have is what you have. Nearly everyone I know who buys a controller doesn't use it. I've thought for a long time that the coolest thing would be for a DAW maker to implement an iPad app that whenever you open a plug in, it opens it's UI on the ipad. That seems like it would be one bit of code for the DAW maker....or technically the iOS app and then the one tweak of the host app....if they wanted to hit it out of the park, put an IPad dock ON a Presonus CS18, which controls Studio One on near "no need for a screen" levels....smartly developing a way to throw third party plug ins to a multitouch screen on it....takes care of that "issue" with first party controllers, which have always been good at driving the DAW itself, but less so third party anything. Good to know you would def. buy my dream controller if it existed. |
|
