Don’t be discourteous.
Raspberry Pi foundation build single board computers for education and other uses. They don’t make MIDI controllers. If someone wants to misconfigure the standard, fully working serial port to interface with MIDI then they (or anyone else) should not blame Raspberry Pi Foundation for not making that misconfiguration work. It is the very fact that they are so open about their product that allows us to stretch it to work in such varied configurations. We now have DIN MIDI working on RPi5 in Zynthian within months of us porting to RPi5. This is a great outcome and not one to be critisised but instead to be commended. Well done to everyone who worked to make that work for the wider community.
USB MIDI is a standard and, any USB MIDI compliant device now works on zynthian, out of the box. We have built a mechanism for hot plugging devices (and USB audio - which is more challenging) and presenting the devies in a consistent way - with the ability to auto allocate single instances or tie multiple instances to each physical port. The latency issues of USB MIDI are historical and mostly resolved. There used to be an issue with large and multiple buffers but this was resolved a few years ago and now latency is low. Zynthian has had some issues with MIDI jitter (both USB and DIN) but that is also mostly resolved (by more careful handling of timing in our core MIDI router module and in plugins… although we don’t have control of most plugins).
So I challenge the critisim voiced here for is validity and its clarity. I don’t really understand what is being complained about. There are hundreds of zynthian users who use USB and or DIN MIDI successfully without complaint.
I would also like to point out that this thread relates to issues with DIN MIDI on RPi5 which is now resolved. We should avoid being off topic.
Sorry Baggy, I’m in a bit of burnout, I didn’t mean to.
I have the NiftYCase from Cre8Audio, it has both Usb and Midi in interface, it converts
Usb Midi or DIn Midi to gates, Cv and Clock.
The problem is the usb drivers don’t work on the Raspberry. They Work on a
Windows 10 laptop.
And I have a limited amount of Usb ports anyway on the Pi.
So it would be really useful to me to be able to use DIN midi for the NiftyCase-Eurorack
I also have a Kenton Usb to Midi box, other Active Kenton Midi Splitter…
My hope was to being able to use the Hybrid Pi for doing all these things.
Once I got the Midi Din IN and out working, is just a matter of adding a hex schmitt
to make an active Midi out splitter so I get 5 Midi out…
I quick internet search reveals Cre8Audio released a firmware update last year to make the device Class Compliant. https://www.youtube.com/watch?v=Kn87Sf1PCuA This should work on a pi.
Or have, like me, bought a USB-MIDI-cable in a well trained reflex. Too many classic devices do not listen well to modern 3.3 Volts MIDI. Good to see the V5.1 has real 5 Volts MIDI and now it works.
I have just updated it with my Mac.
My Mac don’t even sees it, nevermind trying with the Pi…
The frimware updater worked the first time, then there is a multichip updater, that i had to connect
chips and cells on by one otherwise wouldnt work. connect them directly with miniusb
the mac dont even sees them.
It seemed everything has been updated, but it still refuses to be seen on both Sonoma ad sequoia.
I could try with my win 10 laptop.
Also my my Pi sees the Roland Octacapture as second sub sound card with midi in out,
but now refuses to see the chinese usb soundcard that before I installed the hifiberry dac worked, and it had a line input also…
It also has a bluetooth module.
NOTE: SORRY FOR CONFUSION THIS WAS RELATED NOT TO ZYNTHIAN VANGELIS OS RATHER STANDARD BOOKWORM - MY BAD!
I have this in config also
dtparam=uart0_clkrate=3000000
I opened a support ticket with NiftyCASE cre8Audio months ago and I haven’t yet recived an answr… btw the MIDI DIN input of the NiftyCase is the only thing that works…
EDIT… lsusb
Midiplus co, ltd Cre8audioNiftycase!!!
It sees it!!! Miracle! Now let see if I can do anything with it…!| Tnx Baggy for your positivty!!
This should not be required for ttyMIDI and is irrelevant for USB MIDI.
Try amidi -l
to see if it is detected as a USB MIDI device.
amidi -l YES!
Just Cardinal Idk how to select it…
I tried with Alsa seq to do the connection but it didnt work
Carla Patchbay instead I could choose one or both midi devices,
and it worked! Huge success!!!
(I STILL HAVE A DEAD SLIM MIDI hat, but I’m going to open a bottle of wine and suppose it’s ALL GOOD!! At least for tonight… :):):)
I need to try Midi next, lots of stuff to do
So, USB MIDI works on zynthian (and always has!). Your issues with how to use MIDI with Cardinal are not relevant to this forum. You should read the Cardinal docs and engage with the Cardinal community for that. I am glad that a few simple, wise words from @Baggypants led to you updating your Niftycase to make it USB class compliant so that it will work on any OS without requiring a driver, particularly on linux and hence zynthian. I hope your celebratory glass (or bottle) of wine was as satisfying as resolving an issue.
But again… may I remind you that this is rather off-topic for this thread? You have updated the firmware in another bit of kit to make its USB MIDI work which has nothing to do with the DIN MIDI problems with RPi5 that is now resolved in testing (vangelis) branch and, very soon to be released new stable build.
BTW I was able to see DIN MIDI messages from my RPi5 on a scope last night for the first time so I too can confirm the fix has worked.
UH, I just noticed I made a bit of confusion here yesterday.
At one point I switched to Bookworm and didn’t realize.
I’ll be testing again in Vangelis today. tnx.