Closed ToFFmashines closed 9 months ago
Sorry, i can't reproduce the issue in stable branch. I loaded your snapshot and MIDI from the "OMNI" device doesn't reach chain 2, only chain 1.
Please can you try this: Channel #1 - selected OMNI controler 1,
Sorry, i can't reproduce the issue in stable branch. I loaded your snapshot and MIDI from the "OMNI" device doesn't reach chain 2, only chain 1.
Describe the bug Zynthian is set with:
Engine Sfizz on midi channel 1 with select MULTI- Network MIDI-IN and unselect OMNI - Widi Bud Pro Midi
Engine Sfizz on midi channel 2 with unselect MULTI- Network MIDI-IN and select OMNI - Widi Bud Pro Midi
Issue is in that midi signal from Widi Bud Pro Midi is going to channel 1, where is unselect and where it has nothing to do. Is visible by ZynMidi route ch#1 in Midi Log.
To Reproduce Connections: Zynthian is conntroled by Bespoke from PC over rtp-midi WIDI BUD Pro is connected over USB Setting of Midi in for ch#1 Setting of Midi in for ch#2
Expected behavior The midi signal from the Widi Bud Pro will only go to channel 2
Setup: HARDWARE Raspberry Pi 400 Rev 1.1 Audio: Behringer UMC404HD Display: WaveShare 7 HDMI+USB 1024x600 Wiring: DUMMIES I2C: Not detected Profile: SYSTEM Raspbian GNU/Linux 10 (buster) Build Date: 2023-08-25 Memory: 6% (246M/3839M) SD Card: 65% (37G/59G) Temperature: 45.7ºC Overclock: None SOFTWARE zyncoder: testing (c452d2b) zynthian-ui: testing (f19f78c) zynthian-sys: testing (77b48c1) zynthian-data: testing (44a652c) zynthian-webconf: testing (6b74794)
Additional context Snapshots 018-example-widi.zip