Ableton Push controlling Axoloti

#12

This is fantastic, and one of the primary reasons I ended up buy the Axoloti today! So much potential. Do you have a github I could help contribute to? or are you just going to go solo?

#13

which are you interested in Push 1, or Push 2?

Push 1, I have to decide what to do with, as I don't have a Push 1 anymore ( I traded it in for the Push 2), so won't be able to take it further, as I don't have a way to test changes. I guess I could put whats there on my github, will need to check what state it was in when I left it (as far as I remember its got parameters, patch loading, scales), can then be picked up by others if they desire.

Push 2, initially I'll do the dev/testing 'solo' (as you put it), then once its got to a reasonable stage decide how best to release it. (its going to be part of a bigger project, but should I guess be useable outside of it)

#14

I have a push 1, and will most likely not be upgrading anytime soon. I can not commit to anything (don't even have my board yet, just ordered) but your project is very interesting to me. A stand alone push, driving midi, and down the road, cv-able gear, through the axoloti is exactly what I would like to be doing. I'm pretty new to hardware hacking, so I have a feeling I am pretty far off from meaningful contributions, was mostly looking to do code clean up and bug fixes to get my head around it all.

Thanks for your response!

#15

the Push 1 is perfect for controlling 1 axoloti board... I did seriously considered not trading mine in, and just getting a Push 2 (which is awesome in a different way) but thought Id probably not use it enough to really justify it....

I'll see what I can do about the code, pretty busy at the moment, trying to sort out a few things before the holidays... but I suspect this code, is not the first thing you will want to dig into when you get your Axoloti :smile:

#16

You suspect right! No rush at all.

#17

@fma the code is now contained in the community library , which you can access when you upgrade to 1.0.7 (in testing now).
note: as i said above, I can't quite remember its current state... but I believe it was working ok last time I used it ... shout if you need any help.

#18

Thank you sir! I'll be grabbing 1.07 this evening!

#19

Hi,

I am interested in the control of Axoloti with Push too. I just wanted to know if it is usable right now, and whether or not purchsing a Push 2 is worth it regardig the same task, especially since thetechnobear seems to suggest that Axoloti is somehow incompatible with Axoloti.

Thanks in advance!

Best

Matthieu

#20

The Push 2 is not compatible with Axoloti , since it uses USB 2.0 high speed.

My plan, is I'm going to run a PI2 that will host axolotis (4 :smile: ) and the Push 2, and other controllers on a USB hub...
and the Push 2 will control the axoloti in a similar way to what you see above with the Push 1.

i.e. rather than Push -> Axoloti , I have Push2-> PI2 -> Axoloti(4)

If you want direct control, which I admit was really nice, then go for a Push 1...
the Push 1 was slightly better for this as well, because when running on USB power it was very much still useable, not really the case with the Push2 as it requires alot more power.

I was quite tempted to keep my Push 1 for this, but frankly thought I wouldn't use it enough to justify it. also I figured over time, the cost for a used Push 1 is going to drop, so might pick one up then :smile:

#21

Hey have you seen this?http://createdigitalmusic.com/2016/03/ableton-just-released-every-last-detail-of-how-push-2-works/

#22

yup, but old news, we were doing this within a few weeks of release :wink:
http://www.kvraudio.com/forum/viewtopic.php?f=102&t=450494&p=6303105

but it is nice to have it official, I had asked Ableton, but Im still surprised they have done it.

as an aside, I actually have the Push 2 talking to my Raspberry PI 2

#23

Any tips on how to get started with Push 1 and Axoloti?
I saw the patch in the community lib but it does not do anything so far. Is it just a prototype?

#24

as far as I know, it should be working...

I used to put this in a controller object (subpatch), but for testing purposes you can just place it on the patch.

in the console when you connect the push, you should see it also recognised as a midi device;

you then need to set the device input and output, from memory this is 'usb host port 2' (but try 1)
... as you will know, this is due to the Push having 2 midi ports, 'user' and 'live', and axoloti has to talk to the right one.
(you'll know immediately, as the pad and display will do things)

Note: these are attributes, so you have to 'restart' the patch, to take effect.

sorry, I know, Im using works like 'should' and 'from memory', but unfortunately, I traded in my Push 1 for a Push 2, so I can't test it here.

Im pretty sure it was working fine last time I used it, but stupidly before I packed up he Push1 to go to ableton, I didn't do a final test.

what I might be able to do, is to do a test with an Push 1 emulator on the Push 2... though this can only be via a PC.

well it works, and it was further on than shown in the video -but yes, its not as far as I was going to take it... and I wont be taking it further (unless I convince myself to get another P1 :smile: )

it would be reasonably easier for someone to take it over.

#25

Now i can connect and play on the keyboard, in the video you had assigned the encoders and even given graphical output back to push. Are these features avialable by GUI programming or shall i dive in the code and build a new object?

I am so excited about this, it is really awesome!!

EDIT: Okay, i figured it out, i hadn't used subpatch programming so far. It works great. Wow, i fell like a whole new world is opening up to me. Now i can take my axoloti to band practice on Thuesday :smiley:

#26

awesome, glad you got it working...
(I was miffed with myself for not doing final testing before I traded in the Push)

I think most things were working, like browsing and loading from the SD card... scales, parameters...
(you can add more scales in axo_push_scale.h )

I agree it does open up Axoloti a lot, I actually miss having it around, it was great that it could be powered directly from axoloti.

#27

Can't wait to see the progress!!!!

#28

The stuff that is implemented works perfectly.

I am now thinking about making some improvements. Maybe you can help me to get started. I would really like to be able to make some kind of selection of control dials that are accessible from Push. Right now all control dials throughout all subpatch levels are used. The obvious approach would be to restrict the selection to the controls avialable in the top level, i.e. the main patch. Any tips on how to get started there.

#29

Your wish may be coming true... I just picked up a used Push 1 for $180! Can't wait to try it w/ the axoloti. Is there a way to control two of them without a Pi? Thanks for your great work on this!

#30

sorry guys busy on other projects at the moment.

@Hugo its a while since i read the code. I think this will be problematic, since the parameter table it uses, I dont think knows anything about the hierarchy of objects/patches.
there are 2 changes probably for the future:
a) parameter need to have more meta data/stucture
b) custom objects for push, to allow the UI to be 'explicitly' designed.

(a) is need for axoloti control , so is likely to happen, then the Push object will need updating.
(b) could be done now, and could be done in a similar way to the way I use axocontrol.
the latter is more flexible, since a completely custom display could be made, the disadvantage is you probably have to add 'patching code' to each patch you use... but you can consider this is 'building its UI'
... its probably what I would do for now, and I was going to do this for a sequencer, as its the only way to make a decent UI.

@Shrigg yeah, I'm keeping an eye out still ... prices are still about 50% more over in Europe...
Im pretty close to have a Push 1 emulator for the Push 2 running on a rasperry PI, but as always this is competing with other things Im doing :slight_smile:

connecting 2 axo in series and combining the parameters to display on the push wont work (without dev effort).
the issue is axoloti has no way currently of sharing parameters across boards.
with a bit of dev, you could possibly 'hack it' by forwarding push midi messages , by creating an 'intelligent' switch... but thats not trivial to make it work well.. (the push object 'optimises' the display sysex messages to keep 'load' lower)

seeing a 'world view' of parameters/objects, might also be something thats valuable for axoloti control.

(my intention for using with a 'PI hub' was to rewrite this, and basically get the Axoloti to push parameter data to the hub, and then the PI would render to the Push)

generally, the axoloti firmware needs a bit of development to help more elaborate controllers have a good UI, but as mentioned above, this effort is also a requirement for axoloti control.

Arturia Minilab / Beatstep
#31

Hi, i have a push just laying around, got it for about 120$ here in sweden, they are dirt cheap atm :smiley: been thinking that it would be a perfect controller for axoloti, or even using the euxaloti to create a cv sequncer, but im getting ahead of myself. I dont now any coding but i really want to use the push without a pc!

One problem i stumbled upon using the push object is that the encoders send midi notes when you touch them, very anying!
anyone know why?

anyway, great work getting this started, just wish someone would continue working on this :slight_smile: