(redacteddddddddddddd)
3 Likes
very happy to see this! always loved my push 1 but never really got into ableton for full tunes. look forward to grabbing the WIP and seeing how it develops.
this project completely slipped my mind but i just tried to dive in and fell at the first hurdle…
what’s the setup procedure? which mode does the push need to be in?
i see your good vibrations and raise you a campachoochoo
thanks for the tip! you were bang on the money - in windows 10 the device name is simply “Ableton Push” and setting the ‘Push.device_name’ worked a treat. well, to a point!
once that was sorted my LCD pipes up with “Track 01 un-named Length:64” which is full of eastern promise - the un-named string even updates with the name of the current intrument but that seems to be the limit of it. no other lights or reponse from the play/note/session button. or pads for that matter. i’ll see if i can commandeer my other halfs swanky MBP and see what the story is on OSX, my appetite has been whetted now!
Hello again, thanks for looking into this for me! I’d say all Windowsers, but looks like it might be just us? Anyway… Yes I get the MIDIIN2 (Ableton Push) port showing as a MIDI input in the Renoise preferences, bang on again. Setting the device name to this in your tool gives a Push not found error, however if I set it as a midi input in the Renoise prefs I can get the pads to send notes, which is nice! Is there more I can do at this end or does it require some tweaks in the code to accommodate this other port?
ah you champ! appreciate the hand-holding there 
sadly the auto detect is a no go on my machine though, behaviour is the same as the first version i tried before manually entering the device name - terminal throws up the cannot find push error
im gonna have a go on a mac n see what im missing tonight anyway!
ey up! good news and bad news. good news is - the mac version is great so far, the pad grid fits with the Renoise columns really well n it’s a tidy little sequencer!
bad news is - you guessed it - no dice with windows. tbh now i’ve got a taste i’ll probably just pinch the macbook when i fancy using the push sequencer - please don’t squander any time wrestling with windows on my behalf! i’m sure there’s some considerably more exciting features you’re keen to work on…
I did a little bit of digging and, on my PC at least, the problem seems to be that the push midi input and output have different names “(MIDIIN2 (Ableton Push)” and “MIDIOUT2 (Ableton Push)”, and your code tries to use a single variable Push:device_name to open both midi ports.
I could make it work by pasting the proper name into the code, but there’d need to do some refactoring or platform dependent string magic to make it work properly.
Really nice tool btw 
Hi! Yeah, those were the exact names. There is actually a midi in and out just called “Ableton Push”, but oddly you have to use the other ones I named above 
It actually was set to sysex checking, but on my computer it barfed when it tried to open the built in Microsoft GM synth, so I switched to finding by name instead.
1 Like
Great, I’ll check it out
Hi @cupcake
My machine runs on a linux based distro prepared for audio and video editing. (AVL) Now you have a linux guy who will test your script. 
I’ll do it today and will head back with a reply.
Greetings!
1 Like
Thank you anyway. I hoped that the script will activate the LEDs but it wasn’t able to get installed in the first place. The guy who sold be the push told me that it has an open structure and could be configurated via sysex. I did not investigate yet but my first impression is that most of the folks who are digging in this realm are using Max4Live & Mac.
Would it be possible to translate some of these capabilities with the existing tools you’ve created to maybe integrate a Push 2 atleast somewhat with Renoise?
I suspect this will be even more highly desired with the release of the Push 3 (including Standalone); a lot of folks - like me - will have a Push 2 “just sitting around.”