
By Metatron72
Mon Apr 01, 2013 11:02 pm
coolderb wrote:JazzyDrewProductions wrote:I guess I can only speak for myself but I've done that many times only to be given very political corporate answers from akai and retronyms. Akai is purposely holding back. And due to the fact that they left it very disabled leads me to believe that it won't gain ground on bm2 ever. Just my opinion. When I first got it I was a big advocat for it but now. I'm not holding my breath
Their "strategy" is really baffling.I can see them not being enthusiastic about having the Fly work with BM2,but the iMPC app. which works well with the Fly standalone is crippled within their own Tabletop environment.Retronyms says they are working to fix it,but what were they doing for the last 15 months since they announced the Fly and demoed the iMPC app?You would think that they would have had it all working by now.It seems as if the Akai/Retronyms partnership is shakey.They keep pointing the finger at each other and the right hand doesn't know what the left is doing:)
Baffling, exactly. I had mentioned in another thread how I saw a Retronyms rep on their Facebook page answering questions this past summer. As soon as I asked them to elaborate on how iMPC was going to handle Core MIDI and by extension what could they tell me about the Fly as far as Core MIDI. No answer, straight crickets. I knew then this would play out like it has.
Fair enough that the two firms primary focus is their own apps but "most" apps in the spec sheet referencing Core MIDI turned out to be the catch. From the posted video you can see that the Fly's default MIDI doesn't follow any accepted MIDI mapping. At first I thought it was a standard MIDI GM Drum mapping, which is somewhat random numbers and not in chromatic order. but it's not, it's just totally random. Almost looks like it was done on purpose to ruin your day if you want to actually utilize the advertised Core MIDI support, and again that whole "most apps" thing.
So little needed to happen to avoid all this. First why did they make a MIDI controller that can only send 16 out of 127 note values? Bank switches or octave transpose buttons would have helped.(although it would have been 4banks at most and only covered 64 MIDI note values).
The solution to that could have been so simple. They could have made a free app that let's you map the Fly and have that app capable of writing the mappings to the Fly. Even if it was still just the one bank of 16 pads you could quickly switch over to the map app and load a different one and go back to your music app. We're all used to swapping between apps at this point anyway. This would be a way around how Apple has made the devices so closed and that a desktop app for mapping isn't as feasible. Plus obviously you'd prefer to handle mappings on the device itself.




