FluidR6 GoblinSynth sound is causing polyphony overflow in the Fluid Synth (Windows)
Keyboard synthesizer standard soundfont will crash, thus failing to play the rest of the piece.
Attachment | Size |
---|---|
Goblin Synth Playback.mscz | 1.97 KB |
Keyboard synthesizer standard soundfont will crash, thus failing to play the rest of the piece.
Attachment | Size |
---|---|
Goblin Synth Playback.mscz | 1.97 KB |
Comments
Could you be more specific about the steps to reproduce this? Which "keyboard synthesizer soundfont" are you using, and what makes you think the crash has something to do with this?
I used the "Goblins Synthesizer" in MuseScore 2.0; the program itself does not crash, but the MIDI playback does whenever I try to play sustained notes. I'm not sure if it is because of my laptop's processing power (it does not crash in MuseScore 1.3).
Goblin Synth is one of the instruments in instruments.xml
I manage to play the full score using beta1 on Mac OSX. We need more info.
Which operating system are you using? Can you monitor CPU and Memory usage? Which hardware do you use?
Will look into this when I get home.
I ran it on Windows 7 (64 bit); 4 GB ram, Intel Pentium Processor (2.20 GHz); ASUS. At measure 1, CPU usage remained normal(14-17 percent) and MIDI playback proceeded normally. Halfway through measure 2, MIDI playback crashes (skips and continues to skip even after stopping playback) and CPU usage spikes to ~45-50 percent and climbs to ~55-60 percent, even after stopping. CPU usage decreases down to 14-17 percent (normal) after about a minute. Closing that file (Goblin Synth playback.mscz) or a file related to it does not change these figures.
I tried closing Goblin Synth playback.mscz and running a different file (does not matter which one), but playback failed for them as well until CPU usage returns to normal. These figures only change when I kill musescore 2.0 entirely (CPU usage immediately returns to normal).
Done a bit of testing on this.
The behaviour is the same with the original FluidR6 soundfont.
I think the problem is that the sound is so complex that it is flooding Fluid's polyphony.
I've checked in Viena, and the sound has a very slow attack and a slow release. What is happening is that somehow Fluid is insisting on maintaining the sustain phase due to the long notes, so consequently the release phase is not over when the next sound is beginning. Consequently Fluid's audio engine quickly gets flooded if the processor isn't up to handling the amount of polyphony required.
Remedy is to change the Goblin Synth sound completely.
I'll look into that.
I'm now on it.
May be a while before I find a suitable replacement sound.
Upon further investigation it seems that this may be a Windows only problem connected with Fluidsynth.
1. The score also crashes Fluidsynth audio in MuseScore 1.3 on my Windows 8.1 system.
2. The crash is unrelated to synth and reverb (Zita1) settings, still occurring with volume turned right down and Zita1 set to 100% dry signal.
3. The score plays fine in my Virtual box installation of Ubuntu Studio
4. The score plays fine when converted to an SMF in SynthFont
Lasconic has no problem playing the score on his Macbook.
Guess it's Windows only - title amended accordingly
Worked it out sooner than expected. All that was needed was to attenuate one element of the Goblin instrument.
Replacement Soundfont files available from my Dropbox account.......
FluidR3Mono_GM.sf3
https://www.dropbox.com/s/urc6kn4lam96zcs/FluidR3Mono_GM.zip?dl=0
FluidR3Mono_GM.sf2 and updated licence
https://www.dropbox.com/s/8ouh3jyjtgsisra/FluidR3Mono_GM2-8.zip?dl=0
Bump :)
Please will you mark this as fixed once you have the edited soundfont and updated licence please Nicolas :)
Bump :)
It would be cool if we could have assorted fixes in the soundfont instead of small incremental fixes... the git repo is growing 13MB every time we pull the soundfont. Or we need a better solution to get the soundfont in the final package...
Well I'm happy for people to grab it from Dropbox.
Or I could set up a Google Drive account specifically for access to the latest version of the Soundfonts.
The only other solution would be to hold them somewhere on the MuseScore server and give me upload access.
Automatically closed -- issue fixed for 2 weeks with no activity.