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.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
Exclusive mode forces us to use a single synth.
We must support various MIDI realtime midi sources, mapped on channels >16 and a fluid_player mapped on first 16 channels.
The app seems to crash on the second or third fluid_player_stop / fluid_player_seek or new_fluid_player / fluid_player_add also if the realtime channels are not used currently.
To change the backing track we delete_fluid_player and create a new_fluid_player adding the new .mid to it, using the same synth instance reference.
I know about the red flag to not delete the player when the synth is processing, but how to know it?
And BTW the crashes occurs also on seek, not only when trying to create a new player....
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?
Please help,
Beta Was this translation helpful? Give feedback.
All reactions