I do not know how many of you who have this piece of hardware, but i’ve gotten one now. Hopefully it deserves it’s own thread, if so - here it is.
From @Riban in this thread
”APC40 is currently the most feature rich / complete implementation of mixer, launcher and GUI control and feedback”
I’ve been looking at the driver (which is my baby step towards learning about the driver stuff) and i think i understand that this driver has only one mode?
If so, my next thought is to look into @oscaracena’s driver for Akai APC Key25 MK2 (which has several modes) and try to find out if i’m able to copy-paste-adapt my way to a device mode for APC40, so that i do not need my Romoral key-encoder set-up for my main Zynthian Machine.
Alternatively - there actually is a “Device Mode” for the APC40 already, and i just need to know how to activate it?
There is also the possibility (i gather it is quite high:) that “someone” is already developing something for the APC40. If so, i can choose my usual (and with Zynthian often quite successful) approach to problem solving, which is: sit on the fence. Or maybe i could even dream of contributing to the development of the driver. In that case i feel that i would need some more self study beforehand, just to feel “not too much of dilettante” before entering the ring with some one in a weight class high above mine….
The apckey25 driver(s) aren’t ready yet for zynbleton. That said, the only mode of the base driver which did not need any porting so far is device mode. In fact one the first things I did was make device mode the default, cause the padmatrix and stepseq modes need much changes (still not all done).
There will probably be some changes in device mode regarding feedback having to do with new Alt capabilities just introduced.
I do not know whether @riban or @jofemodo already has plans for including this in apc40. Only about putting the step sequencer in a separate class. To let that be used by other drivers too.
Thx. I forgot that Apckey25 was still not ready for zynbleton. But if the device mode is good to go - then i guess my next step would be to se if i could get 2 modes working on the apc40, and then try to get the device mode from key25 adapted to apc40.
Or maybe something else depending on whatever Riban&Jofemodo are coming up with!
And of course as you mention - if/when the step sequencer mode is abstracted or made it’s own class or something (i’m not familiar with termonology) then that would be great for APC40. I also remember that @Riban has allready mentioned this, probably in the zynbleton thread.
I want to see step sequencer abstracted to it’s own class that can be implemented in any other (suitable) device.
I’m not sure what, “device mode” is. APC40 has 8 dedicated encoders that may be MIDI learned and it has 8 channel strip encoders that may be switched between pan, device and send with the device mode acting on the favourite controllers of each chain. (You can select which of the first 8 favourite controllers these control, similar to being able to select which of the first 8 sends are controlled.)
Left, right, up & down are always available via the APC40’s arrow buttons. Select and back are mapped to buttons above. There are dedicated buttons for tempo and record. I’m not sure how beneficial it is to mimic all the V5 buttons.
I can see you might be right, and it could be that i’m just to familiar with the button/encoder layout from the V5. Often i come to understand that i can solve my challenges by changing me, rather than by changing the world around me I will know better when i’ve used the APC40 more i guess.
Hey @core.east there’s an ongoing driver chat thread here. You should post in there so others who have been working on (or interested in) driver development will see the discussion.
I’ve also been working on the apc 25 driver trying to adapt it to the launchpad pro (mk2) for Oram. I got 70% of the way but the sequencer ‘notepad’ input functions never worked. The Launchpad doesn’t have any keys, only buttons (similar to apc40) so there’s something in there that needs to change to allow it to work.
But as discussed, an abstracted sequencer class avoids having to reinvent the wheel for every device.
I know that thread but in a moment i thought it better to make a new one. It is surely hard to decide on what kind of tree-level one should be. And i must admit that i did not search for any guidance on that. I’m very fond of branched communication, but often it gets muddied by stray thoughts or off topic stuff. On the other hand if “there can be only one” topic, everything fits in there. “the Ultimate Topic of Life, the Universe, and Everything”.
EDIT2; IGNORE POST - for now it seems like my unit is faulty
EDIT3; And now it’s working, i opened it up and yelled at it, put it back together. Seems like some kind of magic.
My scene launch buttons on the APC40 do not launch the scenes on my Zynthian
i must admit i do not recall if they did earlier (it is on and off with my focus on music these days, and my memory is faulty)
Is this a bug?
Or some button that needs to be pressed in order to activate the functionality?
EDIT: I see now there is no m lighting up on the Zynthian when i press the scene launchers (and the “stop all clips” and the master button) - evrything else seems to send MIDI signal
I will know better when i’ve used the APC40 more i guess.