|
|
| Reporter | ppqn | Assigned To | | |
|---|
| Priority | normal | Severity | major | Reproducibility | random |
|---|
| Status | new | Resolution | open | |
|---|
| Platform | 6.19.14-108.fc42.x86_64 #1 SMP P | OS | Fedora Linux Workstation | OS Version | 42 |
|---|
| Product Version | 9.7 | |
|---|
|
|
| Summary | 0010394: Pipewire/Jack Inter-app MIDI/Audio Routing with internal Audio issues |
|---|
| Description | Multiple configurations of routing and engine parameters yield crashes/held notes/connection blocking.
I am trying to play MIDI imported from a custom file, route that to QSynth/FluidSynth and route back audio to master.
Ardour is set to JACK/Pipewire.
With QSynth/FS MIDI engine set to "jack", ambiguous latency is reported. This is somewhat stable, but
it excludes the possibility of internal audio routing. This manifests as Ardour MIDI/VST tracks do not allow
routing (the green circle disappears on connecting to Master).
With QSynth/FS MIDI engine set to "alsa_seq", the ambiguous latency seems resolved, but introduces held-notes issue
(hiccups/xruns introduce note-off misses)
With QSynth/FS AUDIO engine set to pipewire (it's either-or) and MIDI to alsa_seq (I guess if audio is pipewire, MIDI
should NOT be jack) the situation is somewhat stable with regards to audio.
All in all, results in several issues to drive an external "module" routing back to Master in Pipewire mode. |
|---|
| Steps To Reproduce | 1. Set FluidSynth to audio: jack, midi: jack
2. Set Ardour to JACK/Pipewire
3. Route 16 MIDI tracks to External - QSynth (subengine for soundfonts)
4. Ambigous latency/no internal audio
1. Set FluidSynth to audio: pipewire, midi: alsa_seq
2. Set Ardour to JACK/Pipewire
3. Route 16 MIDI tracks to internal MIDI bus, route that bus to QSynth MIDIBridge input
4. Route FluidSynth output (back) to Ardour Master In
5. Internal Audio works but glitchy and a lot of note-off misses (held notes) |
|---|
| Tags | No tags attached. |
|---|
|
|
