So, before the end, I will try to do a small recap of what's been going on for the last month or so.
First step: when installing, or enabling, ttymidi over the serial /dev/ttyAMA0 it's possible to use the raspberry Pi more or less
similarly to what can be done with it's smaller sibling, the Pico or the W. It is possible to run python scripts, and Midi in and out
signals are present on the GPIOs. Alsa Midi is not covered here. This is really basic Serial communication.
Second step: when working inside Raspios, Midi can be made available systemwide, but only with python scripts, which
can talk and listen directly to and from the serial. The passages to get to step two might not be as minimalistic as portrayed, but it can be done. I did it on a Pi4B, and on a Pi5B it might be slightly different. It could entirely be possible that using an old Raspbian OS too it could be possible to get here, to the dawless Pi step, which works with MIDO python3 (this is installed automatically) scripts and Thonny. This is advanced Serial communication.
Third step: Some midi bridges, tries to use ttymidi to their advantage, I'm referring to bento_ttymidi but it could be Zita Alsa-midi bridge.
This Midi bridge, appears alongside Midi ports 128:0.1 that ttymidi-sysex also creates.
The problem here, is that untill now, I wasn't able to get any Midi in or out from the
serial to the ttymidi ports and wasn't sure that the GPIO pins were actually active and doing their work.
Who's upper in the tree now, so others know where to look? Is it raw midi?
In presence of both ttymidi and aconnect GUI, where does serial midi sits?
The overall picture remains almost un-altered so that the final product, i.e. alsa connect gui, or other programs, still can't access Midi.
This is the final boss.
A huge positive step has been accomplished today. So I want to thanks all the gui's connected!!
First step: when installing, or enabling, ttymidi over the serial /dev/ttyAMA0 it's possible to use the raspberry Pi more or less
similarly to what can be done with it's smaller sibling, the Pico or the W. It is possible to run python scripts, and Midi in and out
signals are present on the GPIOs. Alsa Midi is not covered here. This is really basic Serial communication.
Second step: when working inside Raspios, Midi can be made available systemwide, but only with python scripts, which
can talk and listen directly to and from the serial. The passages to get to step two might not be as minimalistic as portrayed, but it can be done. I did it on a Pi4B, and on a Pi5B it might be slightly different. It could entirely be possible that using an old Raspbian OS too it could be possible to get here, to the dawless Pi step, which works with MIDO python3 (this is installed automatically) scripts and Thonny. This is advanced Serial communication.
Third step: Some midi bridges, tries to use ttymidi to their advantage, I'm referring to bento_ttymidi but it could be Zita Alsa-midi bridge.
This Midi bridge, appears alongside Midi ports 128:0.1 that ttymidi-sysex also creates.
The problem here, is that untill now, I wasn't able to get any Midi in or out from the
serial to the ttymidi ports and wasn't sure that the GPIO pins were actually active and doing their work.
Who's upper in the tree now, so others know where to look? Is it raw midi?
In presence of both ttymidi and aconnect GUI, where does serial midi sits?
The overall picture remains almost un-altered so that the final product, i.e. alsa connect gui, or other programs, still can't access Midi.
This is the final boss.
A huge positive step has been accomplished today. So I want to thanks all the gui's connected!!
Statistics: Posted by Zool64Pi — Mon Jul 07, 2025 10:51 pm