-
|
Using fluidsynth 2.4.5 API under windows; downloaded the prebuilt version fluidsynth-2.4.5-win10-x64.zip . In my scenario, for performance reasons, to have the minimum latency possible, we use WASAPI driver with exclusive mode ON. If I shrink the channels to the default number of 16, no problems occurs. Is this eligible to open a new issue as a BUG? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You know it, because you're running an audio driver for that synth instance. Hence if you still call Fluidsynth's MIDI player has not been designed for your use-case. What you want to do is using a MIDI parsing library, so that your application takes care of handling those "various MIDI realtime midi sources", syncing them somehow and then create There will be a single synth, configured for more than 16 MIDI channels. |
Beta Was this translation helpful? Give feedback.
You know it, because you're running an audio driver for that synth instance. Hence if you still call
delete_fluid_playeryou're causing it to crash. It's your bug.Fluidsynth's MIDI player has not been designed for your use-case. What you want to do is using a MIDI parsing library, so that your application takes care of handling those "various MIDI realtime midi sources", syncing them somehow and then create
fluid_event_ts from it that you dispatch to the MIDI sequencer.There will be a single synth, configured for more than 16 MIDI channels.
There will be single sequencer, with that syn…