User Details

Username: aaarco
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Apr 14 2021
About aaarco:
(report this profile)

Devices by aaarco

No devices have been posted by this user.

Comments by aaarco


Hey there,
really great device, using the CPU version for a kind of hybrid arrangment and session view set im building.
Running into one issue though I dont know how to debug so posting it here:

I automate the rack the device is in on and off, and each time i turn it back on the device is slightly broken in that when i navigate to another slot the slot that was on while the device was deactivated stays on. Only if i navigate back to that slot and then navigate away again it turns off.
(Using "navigate" because the issue occurs with while, back and forth buttons as well as number-dial buttons)

This makes the device a bit hard to use for me always risking to accidently have two instances on so it would be a blast to have fixed.

There is also some bugs with outmating the selector wheel since it instantly deactivates automation when a value is changed but since thats way less relevant for me ill not go into detail here.


Sweet, works perfectly!

Thanks so much! :)

Alright, i couldnt figure out an exact pattern as of now.

Probably gonna work with my workaround for now.
Your plugin is nevertheless a gamechanger for me, totally awesome!

So thanks for that ;)

Oh, thanks for the quick reply!

Yea i figured that that would be difficult to fix.

The workaround with Automation should work fine for me, but i run into different problems there.
Cant quite put my finger on it, but sometimes when i automate the program change the wheel will jump to the correct position in the plugin but the minilogue will (i think) be one program down from that. (So wheel at 17 and minilogue at 16 for example).
When i then click through the programs via the arrows in the plugin it behaves really strangely and jumps say 3 programs ahead or something like that.

I will experiment a bit more and write again, but maybe you can find a problem with that description already?

A slightly annoying workaround for me right now is to create a different track that sends midi to the ext instrument track and handle program change on that. You have to send directly to the ext Instrument instance though, not just Track In.

Hey, great work on the device, planning on using it in a big live set for my minilogue.
Im running into one problem though. When i use the standard program change implemented in my ableton midi track it changes the program in the plugin but not on my minilogue.
There are some workarounds with multiple tracks(which would be a bit clunky) but maybe im doing something wrong in the first place? Or is it a bug you are aware of?