Quote:
Originally Posted by BScout
Eucon can already do that. It is free for plugin developers to implement. Up to the plugin developers to implement it. (They don't want to because it will cut their hardware sales.) Take it up with the plugin developers.
Why would Avid support other companies so they can sell hardware when they already have hardware that does these things? This development time costs money to Avid.
|
No, it can't. There is no Eucon hardware control that provides a drum machine with loading/chopping samples and one-shots like Maschine. There is no Eucon hardware that is a competitor to Kontorl with integrated VI control and preset/plugin browsing...Or even a channel strip like console 1 or even something like the app for omnisphere. Nothing in Eucon land does any of that, and none of that crosses over into eucon land. Have you ever opened omnisphere on a eucon surface? Completely useless.
I'm not asking Avid for full console 1 support, or NKS support and so on. It's perfectly understandable that they aren't going to rewrite the daw for every hardware/software product on the market- and they aren't going to provide hooks to the hardware to control PT faders, sends, macros etc. Completely fair that they maintain that you need a eucon surface for *that*.
But this is different, it's simply a request to setup the AAX protocol so that plugins can tell which window is open in PT, and if there are multiple instances, to enumerate them from first track to last track.
The most important factor here is this works WITH eucon. I can have machine/kontrol/console 1/etc track follow, and still use the eucon surface for faders, sends, mutes, macros, xmon, audiosuite, on and on.