I’m in a detached garage, and my wife enjoys listening to me practice, so I’m planning to implement some sort of way for her to listen to whatever I’m doing musically, if she so desires. Probably a video feed too.
I setup tailscale a couple weeks ago and I’ve been rearranging my whole outlook as regards accessing things around that as well.
Using a control end and a render end for zynthian over wired Ethernet opens up all kinds of interesting possibilities, not so impressed with wireless but it was a couple of years ago when I last tried it.
In our house it’s wired the other way.
My wife makes sure I don’t escape into the wild…
Is there a good primer on this networked midi stuff? It’s clear enough conceptually, but I have the ability to be astoundingly dense when approaching anything for the first time.
(plans exist to climb up into the insulation above this summer and run more cables, ethernet and HDMI for sure, but was also considering putting in some midi lines in the walls…)
I added +1 and -1 for each zynpot starting at E1, by the way - there’s 9 in a row there so they can all be grouped.
Welp, I seem to have wrangled the Teensy into shape, and I have a midi monitor window showing all the right notes on the correct channel. I also see M activity on the main screen of the zynthian when I twiddle and press the encoders, so the Teensy is definitely talking to the Zynth properly, but there is no corresponding activity, that I can see, it doesn’t react in any way to them other than acknowledging the incoming midi.
I am on testing and have updated multiple times, everything else seems fine. Master channel is enabled in the webconf. I wish I could stay and spend the rest of the afternoon pushing this over the finish line, but I have to go to rehearsal now. Boo.
Anyways, the controller is doing what I believe it’s supposed to do, but I can do a more detailed writeup of where I’m at later this evening or tomorrow morning.
I like the keyboard navigation on the GUI, but how does one get to the Mixer? and I’m getting no response from Enter…
Mar 13 12:25:39 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SWITCH_SELECT'
Mar 13 12:25:46 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SWITCH_SELECT'
Seem to be getting errors of both a qwerty keyboard and my encoder box…
Mar 13 12:20:42 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SNAPSHOT_UP'
Mar 13 12:20:43 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SNAPSHOT_UP'
Mar 13 12:20:44 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SNAPSHOT_DOWN'
Mar 13 12:20:45 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SNAPSHOT_DOWN'
Mar 13 12:20:45 zynthian-rack startx[463]: ERROR:zynthian_gui.callable_ui_action: Unknown CUIA 'SNAPSHOT_DOWN'
Keybinding is currently broken. Our man in Catalonia is working on it…
But he said enjoy!
I’m just obeying orders sir!
Very heavy, sir! Very humble…
But change is occuring…
We fear change…
Not really, it all came about with the inevitable division between various commercial organisations.
A Bit got written…
https://wiki.zynthian.org/index.php/MIDI_Network
I can’t remember where I first encounted qmidinet but it was implemented on the zynth way back with RTP-MIDI following on behind. It allows you to pick up alsa or jack pipes at any host within the local subnet and present it as a MIDI stream. It simply extends your 16 channels of MIDI on a zynthian to any connected machine.
Make a noise near you at pretty much the same time as you make it over there…
It means you don’t need audio on stage for MIDI instruments.
I’ve never used RTP-MIDI so don’t know much about it.
Long sleepless nights on google and a lot of studying.
In my case:
Raspberry Pi with runing Bome Network (based on rtpmidi), over it is connected Bome Box. On the Bome Box are connected 6 midi controllers and 8 synths via USB (and one Blokas MidiHub). A Translator file is uploaded to the Bome Box, which is controlled using OSC via the Open Stage Control server, which also runs on the mentioned RPi. On RPi is also installed McLaren rtpmidi networking utility over is Zynthian connected.
And these network midi devices, they respond at acceptable latencies? It’s hard to conceive, though also far from impossible I know, if the network is not congested.
It should work now, at less the default mapping. Webconf’s keybinding panel doesn’t work yet.
Regards
If you’re referring to testing, I did some keybinds yesterday while finishing up my box, which is fully functional now. So… dunno what to tell ya, worked for me. :>
edit: my piano player is extremely excited. :>
Emotionally, there is nothing to know. I didn’t measure it exactly, apparently network midi would be faster than via usb. I use it on my home network, everything is wired, no wifi.
One of my combinations is Akai EWI USB → WIDI Uhost --(over BLE midi)–> WIDI Bud Pro → USB host → second USB host → Bome Box (translator manipulation, change of midi channels) → second USB host → MIDIHUB Blokas → XO-mini Dynasample synth and it works. In the Bome Box, there is possible a split (better copy) of the signal and the path also can be Bome Box → Bome Network → Raspberry Pi → saving to a midi file.
According to the creators of Bome Box, Bome Network should access usb ports directly. There is now a bug in the RPi version, direct access to input ports is not possible when Bome Box Translator is running. However, the signal to the output ports can be sent, so midi or sequencer playback on the hardware synths works.
Last time I’ve used the network for controlling Zynthian was for testing this music pattern generator:
it has work like a breeze and was very fun.
What wonderful instruments… they were the ones that the Greats had and we “little ones” had to settle for Crumar keyboards… my god 
Did anybody try the 57: SELECT?
I am using the drumpads of my Akai.
Other mappings work, but I don’t get the select to work.
If it’s a bug, I will open an issue.
Cheers,
Markus
Hi Markus!
Check the updated CUIA list:
https://wiki.zynthian.org/index.php/Accessing_Zynthian_from_your_computer
Some CUIA need parameters. SELECT, for instance, need the list index to select. I don’t think is a good idea to map it to a midi note.
If you want to emulate the select switch action, you should use ZYSWITCH CUIA, passing 3 as parameter. If you do so, you will get full switch emulation, including short/bold/long action. You can do the same with all the zynswitches (0-3).
Regards