Sat Sep 15, 2018 11:49 am
@Peter,
I had already adressed the Loupedeck in a few other post , but here we go.
As far as i know (and i looked at it in my search for a new portable target controller after my apc40 project and when i ultimately decided to go for the beatstep), the loopdeck is NOT just a midi controller. Correct me if i am wrong, but it seemed to only work with a proprietary software . So for it to be usefull at all for treating it as a midi controller like i do and attach programming/logic etc to it , it needs to have some sort of dumb midi mode, sending out a (suitable !!) midi message for reach controller touched.
Separately and more to the specific hardware, you cant just randomly pick any midi controller as it needs to be "suitable" for the purpose of creating a logically laid out control surface and the physical features need to be suitable for dynamic changing controls of the type usefull for resolve. Just beeing able to map a few things means nothing without logic and user feedback. Ok for a buttons box (like i use a launchpad mini or for the popular other small button boxes around). And just that it sends out midi will also not mean the type of message or how (looped, endless , etc etc) wil be very usefull. Some are more usefull then others.
Hence i would have still chosen for the beatstep due to the perfect combinations of sufficient number of buttons and "endless" knobs, a useful midi implementation and super important programmable leds for feedback. For control itself, endless knobs is what you need the most ,but with buttons you can create logic and a user friendly controller. And with programmable lights you can program the all important user feedback absolutely required when mapping a thousand functions on a few knobs and buttons and still have it user friendly.
The loopdeck has been too much designed and layed out with lightroom in mind rather then a general layout but for that it is a beauty and well worth it, but i would not choose it for Resolve.
Ideally, but not absolutely required , a controller has bidirectional midi (so e.g. for the apc40, which has the most ideal midi implementation for this sort of stuff i found, i can set each button/knob status via midi . For the beatstep partly. )
And it has no features for user feedback at all.
So hardwarewise, even if it would get or has a dumb midi mode, it looks sweet but i see atm no future for it for Resolve but am happy to be proven wrong. The amount of effort you need to put into creating a full controller (rather then just random mapping a few features you need) has to be worth it so you better pick the best controller for the job and thats why i atm only cover 2 controllers (one large and one small portable.) with little reason to extend that.
Took me in total about 2-3 years the get to this level with zero financial benefits. Its pure love and passion project at such a small scale
In general it is of course a pitty we have no (free) access to the api, which would open up a next level of control without having to jump through hoops but i can live with it and understand it from BM's perspective and respect it. Their controllers are beautiful and if you have the money go for it. I target a different group which does not bite each other.
The few companies that do have access to the api reflect that in the price so for the by me targeted range this is unlikely to ever happen.
edit: took out a remark i made on the little faders in the center not beeing usefull as they looked just mini faders , but looking more closely these are little rotary knobs, so may or may not be usefull pending a proper midi implementation.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME