The push2 interface will not work with the push1… as yes, the protocol is completely different for the display - if someone wanted to do it, they could probably do it relatively easily…
funny, ive been trying to get my hands on a cheap push 1 ever since i traded it in for a push2,
they are really neat for this kind of thing.
(though honestly, they’d be a bit more suitable if they were a little smaller!)
Thanks for the answer ! I ll save up for a push 2 then !
Take care
Is external sound input possible ? Eg guitar in …clouds out?
Yes! I think is possible, In each chain have an input gain, by default is off.
Great thanks. I’ll review the input and output gain issues later
@thetechnobear I updated to beta 2 and now I noticed a strange thing in that my patch (the one I used in the video) don’t work anymore… has the CC handling changed? I tried to midi learn again and the difference is that I get a higher number in the params.json file, e.g. what was
"7": ["r-chout-gain-1"]
in the original (beta 1) patch, is now
"2039": ["r-chout-gain-1"]
when I re-learn the same CC.
I checked and the MIDI controller sends CC 7 correctly.
If this is expected, what is the logic behind it? To speed up patching I wrote many of the CC directly in the params.json instead of manually midi learn them. But there was a 1:1 correspondence between the number in the json file and the controller number, now it seems to be different, is there a formula to apply?
Thanks
Yes , this now includes the midi channel number - so that our can use the same cc on different midi channels
Most obvious use case is mod wheel.
Say you have 3 synths in different chains, and happen to use ch 1-3 (default)
You can now assign the mod wheel to each of these synths.
Also very handy when your using a controller ( eg synth) and it has markings for parameters - so you can use your decay knob in different synth modules.
It should be 128 x midi ch+ cc#
(But your example looks like I incorrectly used 127 - so I’ll fix that ;)))
Sure, this makes a lot of sense!
Ok so I’ll better wait the next release to convert the patch… I guess 
Thanks Mark
here I am, sorry I’ve been busy doing much more tedious things lately and I haven’t had time to improve the patch (though, I’ve been looking into Orac code and now I’m certain that I’m trying to solve the puzzle the wrong way)… still. Here’s what I’ve done so far.
There’s a pd patch and a python script. hope it will help you to do something nicer.
@martindunne @languidlost @fpgaona @Pranciskus @Makrotulpa
cheers
https://drive.google.com/drive/folders/1O-B34_NaHTeU1JQ_7xDTS3Cb2BwAaCnC?usp=sharing
thanks for this. so the py patch runs on the teensy?
No everything runs on the pi.
The oled is connected by i2c
I thank you for that work(sorry for english, im french). I did every thing during the entire week-end, and i stil cant show the gui on mine (rasp). There is alway the demo patch, i dont know how To show the interface, my Bluetooth doesnt work too ! Help me please, this drum loop is making me crazy !
thanks for this makes sense. are osc_connect and shell in the pd script custon extensions as i cant seem to find them? 
osc_connect is part of the externals included with orac2 (Orac/OscClients/pd at master · TheTechnobear/Orac · GitHub) ,
as for “shell” it’s an external to run shell scripts within pd, you can install it via del external library manager of pd. (I use shell just to execute the python script)
@fpa the “gui” is the remote control app you can download here: https://patchstorage.com/orac-remote-control-patches/ for pd or lemur.
You can use the pd patch on a computer on the same network by inserting the IP of the raspi where it says “edit hostname here”. You should be able to use it also on the raspi itself in graphical mode, in that case you should use “localhost” or “127.0.0.1” (not tried myself, but it should work)
I have more or less the prototype and the design for the box. To say that I do not have any Arduino experience and it’s my first project, that’s why I think that anyone can do it. It is a midi usb controller with 4 banks, one for the three chains and one for the post effects. It can also be used with other software but I have focused it on Orac. Cheers.
thanks for all the help. i think im getting somewhere.
do i replace python /home/patch/testosc.py with home/patch/oscScript.py
also whats going on inside your osc connect, i repaced it with Ttb orac object pd connect but it only has 2 inlets your obect has 3. 
Ok, thank you emilio, now i realy can say that its awesome!!!
Is it normal that there is no sound if my rasp boot on console? I feel that Since i use the remote control ap on localhost, i have to start the grafical mode to have sound (the sound appears just when the desktop is arrived)
no, graphics mode is not required - I only use console mode ( as mentioned in the video)
Have you got beta 2 installed?
(ie done an update since original beta. )
beta 1 has a blank default rack so made no sound, this was changed in beta 2 as mentioned in the getting started video.
