Forget it, just the wrong cable connected :S
It was too late xD.
Works fine now
Here on amazon more quick https://www.amazon.es/3-1-Tipo-USB-C-macho-teléfono-celular/dp/B01LAV03KE
But itâs pretty clear!! The power and the data from the 2xA is for the type C ⊠what else?
Anyway, the Y-connector you linked is quite interesting too
Regards,
I have a USB hub with on/off switches. When I turn off the power on the one going to my Casio Keyboard . It still works since only the power line is interrupted and the Casio supplies its own power , so it only uses D+ and D- data lines. Since the PI 4âs Connector Isnât standard USB C Spec, Only Power and USB 2.0 routed from the SOC.
A Y with only power on one and data on the other would be perfect. But youâd have to make your own cable as no one seems makes one.
You may have USB 3.0 ports on your PC which can deliver 900mA each so the splitter jofemodo found could plug into both and get 1.8A @ 5v Still under the 2.5A-3A that weâd prefer
Is there a USB audio capability in the latest software, or was that a nonstarter? Iâm using the 4.1 Kit, HiFiBerry DAC+ ADC Stage and can see the Zynthian midi ports in MacOS. I also found where to disable OTG in the Web Configuration tool, and I glean from the interwebs and this thread that there is a theoretical Raspberry Pi 4B USB C audio capability, although HiFiBerry generated maybe not so much. Iâm otherwise pretty clueless where to cast my gaze in hope of catching a glimpse of the fabled creature. Will the new soundcard help?
Hi @AndyV
Currently only MIDI is supported over OTG. I think this thread went quiet when people realised the awkwardness of getting sufficient power into the Zynthian with this configuration, i.e. USB from host computer to Zynthian power inlet. Although it may be possible I am not aware of anyone progressing the interface to support audio.
This also works via a USB hub. I have a 4A power supply on the hub. That should be enough power.
Iâve got a RPi5 board with a hifiberry, and I do have a powered usb hub (Prodjuser), which I hooked up to the RPi5. It works. My DAW recognizes Zynthian as a MIDI device, and I can send MIDI from the DAW to Zynthian.
However⊠I do get this nagging little startup message from Zynthian OS saying it detects undervoltage, which probably has everything to do with RPi5 increased power requirements. So I felt I needed another solution.
I bought an arduino leonardo and an arduino MIDI shield, so I could route serial MIDI from my audio interface to the arduino, which would then convert it to USB-MIDI and send it to Zynthian. This way, my RPi5 can be juiced by its own power adapter, and Zynthian can still receive MIDI from my DAW.
Now, not every arduino is suitable for this. Hereâs a handy chart that tells you which board sends MIDI over USB:
https://tttapa.github.io/Control-Surface-doc/Doxygen/d8/d4a/md_pages_MIDI-over-USB.html
You should use the control surface library here:
and the Sketch here:
https://tttapa.github.io/Control-Surface-doc/Doxygen/d0/dc4/MIDI_Pipes-Routing_8ino-example.html
I fully support this recommensation for the control-surface project⊠for me it was soooo easy to make a USB to BLE MIDI interface⊠.
A few lines of code and a cheap pico W. (also a ESP32-S3 works fine)
That certainly addresses the USB controller Midi problem, and looks incredibly mature.
During the development stage you also want to upload new code and doing this over USB can be done, if at a little configuration⊠The Maple library and VSC seem to allow this to be populated over the single USB connection With the composite USB library which allows QWERTY and mouse interaction.
Hopefully we can build a couple of approaches to address the increasingly impressive and bizarre ways people will find to abuse and use this stuffâŠ
Good ainât itâŠ?
I have experienced a lot of strange behaviors when using USB devices wich are self powered (I mean, with their own power supply) and are connected to my Zbox, wich Iâm powering with official RBPi PSU.
These pbs are like âa synchro process error bugâ when the power rail of an USB device (audio/midi/or touchscreen device via USB) is not the same as the RBPi main power rail. Kernel messages complains a lot (use dmesg command from command line to see whatâs happens)
I believe all these exotic behaviors (eg: my RBPi wonât really do a true âpoweroffâ because it is still feeded in, via some third party USB plugged in and self powered device) are mostly HW design (of your RBPi, your USB midi control surface / keyboard, or USB audio gear)
Nice solution.
I would just like to mention the neglected possibility of connecting PC/DAW and Zynthian via RTP-Midi.
Weâve come full circle since August 2020!