Funny things happening: I am working on this, have something working but on certain cases I receive segfaults with fluidsynth-dssi (this is btw. my favorite as it shares sf2 fur multiple plugin-instances).
The segfault can be reproduced in qtractor by:
* Open Track-add dialog on an empty session
* Select Midi track
* add fluidsynth-dssi / remove it / add it again -> crash
I installed all the debuginfo stuff on my PC, debugged and found out, that it is caused fluidsynth-dssi using memory already deleted. OK check fluidsynth-dssi git and what do I find?:
commit d62316e8330d8824d4c3939de85656987348f1a8
Author: Sean Bolton
Date: Sat Mar 24 21:40:23 2012 +0000
* fsd_cleanup() bugfix from Rui Nuno Capela
* MIDI sysex patch from Albert Graef
* Use reentrant strtok_r()
Funny things happening: I am working on this, have something working but on certain cases I receive segfaults with fluidsynth-dssi (this is btw. my favorite as it shares sf2 fur multiple plugin-instances).
The segfault can be reproduced in qtractor by:
* Open Track-add dialog on an empty session
* Select Midi track
* add fluidsynth-dssi / remove it / add it again -> crash
I installed all the debuginfo stuff on my PC, debugged and found out, that it is caused fluidsynth-dssi using memory already deleted. OK check fluidsynth-dssi git and what do I find?:
commit d62316e8330d8824d4c3939de85656987348f1a8
Author: Sean Bolton
Date: Sat Mar 24 21:40:23 2012 +0000
* fsd_cleanup() bugfix from Rui Nuno Capela
* MIDI sysex patch from Albert Graef
* Use reentrant strtok_r()
LOL