Build a ZynSeq with RPI3

[Wapata]

Hi !
I was playing with a friend with a Korg Kross and he have seen how great ZynSeq was.
If I make him a Zynthian with a raspberry pi 3 and nothing else than a touch screen (no sound card) will it be okay to handle midi and ZynSeq only ?
His keyboard will be USB-Midi and I will ask him to take an APC MK2.

[wyleu]

@Wapata

will it be okay to handle midi and ZynSeq only

Yep.

[Wapata]

thank you for the confirmation.
I will try to burn an mSD as soon as possible then !
Midi clock and transport goes thru Ethernet rtp-midi between two Zynthian?

[wyleu]

@Wapata

Midi clock and transport goes thru Ethernet rtp-midi between two Zynthian?

Don’t know about rtp-midi but it certainly works over qmidinet.

[Wapata]

Crap… My old gears are raspberry pi 2 model B and not RPI3
I will try to burn Ann SD anyway and see ?

[wyleu]

@Wapata

I will try to burn Ann SD anyway and see ?

I don’t think I ever tried that…

[Wapata]

If we don’t look at the “at minimum” paragraph… It’s okay
https://wiki.zynthian.org/index.php?title=No_Hardware_Build&mobileaction=toggle_view_desktop

[Wapata]

So, two rpi2 tested (and also two uSD) no sign of life via HDMI or Ethernet.
Rpi3 is okay.
But taking the uSD from rpi3 to rpi2 doesn’t work

You have made a wonderful job. A raspberry, mouse, keyboard and tv and you are able to test Zynthian. Wonderful.

[Wapata]

So… It seems that it’s not as easy.
RTP-Midi and QmidiNet are agree to be active together but there is no midi exchange between the two Zynthian.
NetUMP Midi 2.0 desactivate itself after reboot… Annd there is no midi exchange too.

Maybe we need a midi router between the units…

[Wapata]

I there !
So. Reading this : MIDI Network - ZynthianWiki it seem that QmidiNet should magically work.
But it doesn’t.
And for both Zynthian, i do not have access to the Midi Devices page from webconf.
A windows with midi and Zynthian logo pop and disappear 2 seconds later.
Midi Log set to QmidiNet is empty and still empty on both devices.

I’m in the last Oram. Does someone else have the same behavior?

EDIT : Inside a chain, if I look out at the "capture midi from /!QmidiNet bold click configuration, the name port is Net:qmidi_out_1
… It should be In and not Out I guess

[riban]

Input and output are often confusing in the jack graph. A module that receives MIDI over the network will present that MIDI to the jack graph from its output, so you may consider this as an input to zynthian, it is actually an output from the net module.

[Wapata]

Reading old posts, it seem that my non working test can be due to the fact I’ve played with midi without adding a new chain :

Help with 2 Zynthian with Qmidinet

@wyleu mentioned an issue with autorouting that he thought was fixed but I have found that the route to / from qmidinet is not made automatically and needs a nudge, e.g. add/remove an synth chain. I understand the reason for this but don’t have a solution in my head yet. The routing graph is updated when configuration changes, e.g. add/remove a chain and there is a background check for change of MIDI interfaces that triggers an update of the routing graph but if qmidinet is enabled there is no c…

[Wapata]

So it’s a fail on my side. No QmidiNet, no NetUMP by Ethernet, direct link or via router.

[jtode]

If I recall correctly, Pi2 is 32 bit, I think. Either way, I remember when Pi3 came out, it was a wow moment because the CPU performance got a seriously large boost, as well as the wiffy…

I still have a working original Pi here, I guess that’s almost ready to sit next to the vintage 8 bits. :>

[riban]

@jtode

Pi2 is 32 bit

It depends. Initial release was 32-bit but revision 1.2 was 64-bit, same SoC as RPi3.

If you have a RPi2 < 1.2 then it won’t run Oram. We stopped supporting RPi2 many years ago.

[Wapata]

Oh gosh… We need to add a MIDI chain set to ALL MIDI CHANNELS and output to QmidiNet

For now it send notes from my devices channel thru the Ethernet, but not from the active channel. I did not have time to search more but in the end I want from ZynSeq to QmidiNet so… It’s should be okay, I’ve seen the label.

And it work both directions!