Session Box vs MPK249 + Feedback [with Images]

John and Community,

First of all, I appreciate and have a profound respect with this Remotify idea. It’s great to see this effort being unrolled. But I’m already almost quitting, ‘cus I’m not able to create a simple and effective Session Box. Let me explain…

I own a Akai MPK249 and plug it along my MB Pro with Ableton Live 9. This hardware come with a Factory Script that works very well for what it’s purpose to do. Everything they programmed works fine (Faders, Knobs, Switches and DAW Control). Ok, after researching a lot around internet and discovering this RemoteScript world, I found Remotify 2 month’s ago and only this week I have the courage to invest in this idea. I was trying to learn python programming – didn’t worked either.

My wish for the MPK249 behavior within Live is to work similar as APC40: with a Session Box to launch clips for live recording or playing samples. This is the most important for me. The rest is a plus.

And yes, I make it work, but I found this problems:

– When I arm a track, the hardware receives a “Midi Note On” and all the 3 Scenes turns Red. With “Remote” options On or Off, this happens anyway. I believe the MPK249 pads only works with 2 color leds per pad. (Image 1)

– If I unarm the same track, the Scenes with Clips appears the way it should (On for Scenes with Clips, Off without Clips). (Image 1)

– I’ve organized the 4×4 pads of the MPK as 3×4 Scene Launch and the bottom 1×4 as “Clip Stop Button”. The Stop buttons have a strange behavior with colors either. It functions well inside the program, but if I hold a little longer, the pad colours go Off, then I need to Hold again to go On. Isn’t a hardware problem, ‘cus I already mapped the stops buttons with another MPK Preset and it all works fine… Seems to be a MIDI Feedback issue. (Image 2)

– This problema above seems to be similar to the other topic I’ve opened (I’ve already gave up of that). When I create a “Arm” button from a Switch on the Hardware (yellow on/off, no coloured leds), I need to press 2 times to arm/unarm, instead of one.

What have worked of all my scripting:
– Faders as Volumes
– Transport Buttons

##

All of this is my present problems. It’s seems to me that Remotify is a great idea still being develop by one person only ( <3 developers). And I think it's a great idea that doesn't work for all controllers... Not everything can be mapped trough Remotify 'til now. Maybe trough Python coding it's all possible, but I don't have this skills... So, John, I will give you here some feedback of what I think of remotify so far, ok? Some things that I've missed:

– manual/tutorials with deep explanations.
– search engine on this forum (maybe a deep organization either)
– More MIDI languages as MMC, Sysex, Keystroke, etc… only CC and Notes it’s a pain sometimes.
– Save a draw of the last script being developed in the app. I’ve lost 2 or 3 script studies until I understand I couldn’t close Chrome without downloading the script.
– Organize mappings by Add order.
– Play Scenes independent of the Session Box – I’d like to play Scenes as a sequencer in my 4×4 pads.

##

I know It’s a lot and I hope there’s a way out to my problems. I take the opportunity to ask/suggest another thing:

– Is there a way to edit the Factory Script of my controller? It would be much easier to understand how does it work and “only” add the Session Box above it. I don’t know it this information can be grabbed from the .pyc file inside the folder.

For now thats it! Thanks for your attention!
RD