Repository navigation
How launching freetribe over sysex should work #60
|
Hello everyone ! I've discovered recently that beyond the Hacktribe there was this project. I've been interested for a while by audio programmation, groovebox and custom firmware stuff. So I would like to test to code some programs for Freetribe. Since I'm not into soldering stuff to my electribe I would like to run stuff through the sysex transfer. So I follow the documentation I could find to do so, I did upgrade my hacktribe to the last on I could find on github, I downloaded freetribe repo and used docker to build the demo. Then using the execute_freetribe.py and my usb/midi interface got the bin file to start the transfer. The screen of the electribe turns a kind of yellow and the terminal says it starts the transfer. However it doesn't seems to end nothing is happening on the electribe or the terminal after a while. Is there somehing I'm missing ? I'll paste the output I got from the script :
If anyone as some experience with it I would be glad to have a bit of help with that ! |
Replies: 5 comments 5 replies
|
Hi!🕷 I think that your electribe MIDI settings are already fine, you already have a properly established sysex connection. My first thought is: which binary are you trying to run? |
|
I tried the demo app and monosynth app. Those you find on the main branch of freetribe repo. |
|
Well, I just tested it out and I've got the same exact behaviour. If I eventually installed a version of the hacktribe that doesn't support that feature would it still have the screen going yellow using the script to launch freetribe ? It seems odd to me since I pulled hacktribe from the last dev branch commit yesterday... Maybe I should compile the application using dev branch for the freetribe repo ? |
|
Yes that is that, it's stuck at : DEBUG:root:Sending data |
|
https://docs.google.com/document/d/e/2PACX-1vQ9rHYMmyfvMqh5t-i0FRRobpI8y0Y_QJKlAwxeBxmQs8t5wWfINZ0F_Tawjj3LGm9Cp0LBRnTAvgGj/pub |
So in e2sysex.py, in write_cpu_ram()
can you check whether it gets stuck sending in
self.outport.send(msg)?I suggest changing the mido MIDI backend to portMIDI if it was previously RtMidi and vice-versa.
if it hangs waiting for a response in
response = sysex_response()then you may also try to use other programs to test the sysex message sequence manually.