@ltignis it sounds like you don’t have Multitimbral selected for your MIDI input.
1 Like
ohhhh found it! thanks a lot for the help!
1 Like
Please post a snapshot.
found it, still trying to get used to new user interface and controls of this device
3 Likes
Hello .
I have now integrated my Zynthian in the studio and control it via the Akai Force. I wrote above that there is no error in connection with the Force. It does with the Deluge.
Unfortunately this is not correct, even with the Akai Force this behaviour occurs as soon as I add a third midi track with the Linux sampler (drumkit). In addition, there are note hangs, which leads me to believe that Note Off messages are also ignored.
Everything is fine via USB Midi.
Somewhere in the Din Midi in and the
assignment of the midi tracks in multimode something is wrong.
It is now the second sequencer (Akai Force) that shows the same behaviour.
I have tried the Deluge on the Blofeld = multimode and on the Access Virus = multimode and there were no problems.
Greetings Ron
Then, it could be an issue with the mod-ttymidi service. Do you know if the sequencers you tested with are using “MIDI running status”? If so, perhaps it could be disabled just to check?
Regards,
I am happy to test this, but what is meant by ‘MIDI running status’?
Midi Clock ?
It’s part of MIDI specification, although i think it was not a core feature from the very beginning:
http://midi.teragonaudio.com/tech/midispec/run.htm
Devices using it, normally explain about it somewhere in their manuals. And some/most devices allow disabling it.
Regards,
I think running status has always been in MIDI 1.0. The purpose is to reduce the data flow by removing the command byte for consecutive, similar messages. This improved latency and data rate. Basically, if a command is the same type as the previous command, e.g. NOTE-ON then the command byte is not sent. The receiver remembers the last command and assumes the data payload relates to it.
It may be useful to capture some MIDI that causes this issue so that we can reproduce it. I wonder if you have a mechanism for capturing the MIDI, e.g. recording it to a standard MIDI file (.mid)?
If I get a chance, I will try to reproduce but am rather busy this week.
But i fear the issue is inside mod-ttymidi. Look at the logs sent by @highsiderr:
This is the raw MIDI stream coming out the mod-ttymidi and as you can see, there is no “note-on” messages in MIDI channel 3. Just “note-off” messages in this channel.
This is the data flow:
sequencer -> MIDI cable ->
-> MIDI IN circuit (opto-coupler) -> RBPi serial port ->
-> kernel driver -> mod-ttymidi -> zynthian router
From my POV, the issue is too reproducible to be a hardware issue. It smells like a software issue and MIDI-protocol related. IMHO mod-ttymidi is the shady guy.
Regards,
1 Like
Which is why it would be advantageous to have the raw MIDI stream so that we can play it in and debug.
No stress, I am now using USB Midi for the time being.
There are certainly more important things to do than to find this error here.
As you have built the Zynthian very well there is no noise in the audio when using USB.
By the way, all my synths hum when I use usb midi but not the Zynthian.
Very good work.
1 Like
If I can find out how I can record and send the midi stream.
This is an important issue. If the MIDI-IN port is flawed in such a way, we should solve it ASAP.
The curious is that mod-ttymidi is a very stable piece of software. It has not been updated in the last 4 years, so if there is a bug, it’s there from a long time ago and nobody noted until now.
@highsiderr, I will send you a script to get debug logs from ttymidi, OK?
Regards
1 Like
With pleasure.
Please send me instructions on what to do.
I hope it’s not due to my setup after all.
The Deluge was connected directly to the Zynthian.
Maybe there is someone here in the forum who has an Akai Force or MPC live.
He could load my snapshot, set up the midi channels in the Force/MPC and see if he has similar errors.
First, please could you try different combinations of channels? For instance if you put the linuxsampler in channel 4 or 5, is it the same? What if you use another synth instead of linuxsampler? Etc.
To get useful debug output from ttymidi, you have to follow these exact steps:
cd /zynthian/zynthian-sw
git clone https://github.com/moddevices/mod-ttymidi.git
cd mod-tty-midi
make debug
Now you have a debug version of ttymidi. Let’s start the debug session:
systemctl stop mod-ttymidi
cd /zynthian/zynthian-sw/mod-ttymidi
- Connect the sequencer to zynthian MIDI-IN. You must have prepared the sequence that produce the error, but keep it stopped.
- Run this command:
./ttymidi -p -s /dev/ttyAMA0 -b 38400
- Play the sequence that cause the error. Just one loop if possible. Not less.
- Copy-paste the output. This is the raw serial port data input. Ctrl-C to end.
- Run this command:
./ttymidi -v -s /dev/ttyAMA0 -b 38400
- Play the sequence that cause the error. Just one loop if possible. Not less.
- Copy-paste the output. This is the processed MIDI stream. . Ctrl-C to end.
Send both logs and let’s see if ttymidi if something is lost in translation.
You can restore normal zynthian behavior:
systemctl start mod-ttymidi
Thanks a lot for helping with this!!
just connected the Force directly to the Zynthian again, so no other synths in between.
The same as described above .
Linux sampler (Drumkit) replaced by FluidSampler (Drumkit) .
The track with the pad disappears see video.
Loaded other plug-ins and the same thing happens.
After make debug stop this…
root@zynthian:/zynthian/zynthian-sw# make debug
make: *** No rule to make target ‘debug’. Stop.
root@zynthian:/zynthian/zynthian-sw/mod-ttymidi# ./ttymidi -p -s /dev/ttyAMA0 -b
38400
bash: ./ttymidi: No such file or directory
Got it working make debug had to be executed in the folder .
here are the two streams as .txt files.
midi2.txt (1.9 KB)
midi1.txt (2.0 KB)
003-midi fai;.zss (31.5 KB)