Unkown Message - ZynMidiRouter: Bad chan number (65535)

Using Zynthian
1

About 10 seconds after succesfully booting I see this message in the debug logging - “Jan 04 22:45:47 zynthian1 startx[1184]: ZynMidiRouter: Bad chan number (65535).” The message does not re-occur. The system seems to be functioning normally. What, if anything, should I be concerned about here?

Harry

zyncoder: oram (af61613)
zynthian-ui: oram (0dc082a)
zynthian-sys: oram (93b16fb)
zynthian-data: oram (e4e24b8)
zynthian-webconf: oram (1c1b855)

Raspberry Pi 5 Model B Rev 1.0
Audio: Behringer UCA222
Display: WaveShare 7 HDMI+USB 800x480
Wiring: TOUCH_ONLY
I2C: Not detected
Profile: v5

2

This is used to indicate a chain has ALL MIDI CHANNELS selected so probably relates to your snapshot. It would be useful to see the context of this message, i.e. the surrounding log messages which might give a clue to where in the code the error occurs.

3

Yes -exactly. One chain was all midi out. Switched to a single midi channel on that chain and message did not re-appear.

Harry

4

It would still help us find the issue if you could provide the surrounding log entries.

5

Here’s the complete contents of the UI Log. Is info from the debug log also needed? If so I’ll have figure out the proper method for capturing it…

Jan 06 01:38:13 zynthian1 startx[1173]: /zynthian/config/img/fb_zynthian_boot.jpg is a 800x480 JPEG image, color space Grayscale, 1 comp, Huffman coding.
Jan 06 01:38:13 zynthian1 startx[1173]: Zooming image by 100%…done
Jan 06 01:38:13 zynthian1 startx[1173]: Merging…didn’t find evidence of prior run.
Jan 06 01:38:13 zynthian1 startx[1173]: done
Jan 06 01:38:13 zynthian1 startx[1173]: Building XImage…done
Jan 06 01:38:14 zynthian1 startx[1175]: Loaded libzynaudioplayer using libsndfile-1.2.0
Jan 06 01:38:15 zynthian1 startx[1175]: Started libzynmixer
Jan 06 01:38:15 zynthian1 startx[1175]: Started libzynseq
Jan 06 01:38:15 zynthian1 startx[1175]: Started libzynsmf
Jan 06 01:38:24 zynthian1 startx[1175]: ZynMidiRouter: Bad chan number (65535).

6

Thanks @harrylnorris. This error is reported by the low-level zynthian library that handles MIDI routing and filtering. Unfortunately, the same message may be issued from 3 places in the code, making it a bit more challenging to investigate. Some of these functions are only called from specific places in the Python code, e.g. from certain engines. Will you please tell us what engines are in use. Providing the snapshot may help.

7

Not quite fluid with snapshots yet but…

On the Zynthian that I sent the log from there are 5 chains ZynAddSubFX and 4 midi chains for just sending midi to a Eurorack Midi2CV converter. If I select “all” for midi chan for ZynAssSubFX, the error appears and if I deslect it it goes away. On a second Zynthian (both updated to latest Oram Staging) with only ZynAddSub FX the error also comes and goes away switching between “all” and a single midi channel.

Here is a UI log for the second Zynthian. Note there is a warning in this log not present in the first log.

Jan 05 01:29:41 zynthian0 startx[1054]: Zooming image by 100%…done
Jan 05 01:29:41 zynthian0 startx[1054]: Merging…didn’t find evidence of prior run.
Jan 05 01:29:41 zynthian0 startx[1054]: done
Jan 05 01:29:41 zynthian0 startx[1054]: Building XImage…done
Jan 05 01:29:42 zynthian0 startx[1056]: Loaded libzynaudioplayer using libsndfile-1.2.0
Jan 05 01:29:43 zynthian0 startx[1056]: Started libzynmixer
Jan 05 01:29:43 zynthian0 startx[1056]: Started libzynseq
Jan 05 01:29:43 zynthian0 startx[1056]: Started libzynsmf
Jan 05 01:29:54 zynthian0 startx[1056]: WARNING:zynthian_state_manager.update_thread: Command ‘[‘git’, ‘-C’, ‘//zynthian/zynthian-ui’, ‘ls-remote’, ‘origin’, ‘oram’]’ returned non-zero exit status 128.
Jan 06 14:32:36 zynthian0 startx[1056]: ZynMidiRouter: Bad chan number (65535).