Playback of SF3 features loud pops
Using Windows, GIT commit: 34a4d6d
1) load attached score
2) play
I hear very loud pops on about half the notes (always the same ones in this example - first two, last five). As far as I know, all synth settings are default. In particular, using FluidR3-GM2-2.sf3
| Attachment | Size |
|---|---|
| bass_pop.mscz | 1.4 KB |
Comments
I've just checked the sample set, and there is an audible click at the start of each sample caused by the close miking of the instrument when it was recorded. That is picking up the transient attack of the note.
Sometimes this is deliberately accentuated by plucking the string in vertical plane from the fingerboard rather than horizontal, in which case the string hits the fingerboard before vibrating normal, so it is possible that the samples were recorded in this way.
It would seem that the Fluid engine is picking up this transient and amplifying it, possibly due to the attack phase of the amplitude envelope.
I will run the same test with the sf2 version to see whether conversion to Ogg is responsible.
Running the test with the SF2 version of the Fluid soundfont confirms that it is the sf3 version itself which is at fault, possibly due to the conversion to Ogg?
Git Commit -faf83ee (not sure this is accurate may be my working branch commit number)
See http://musescore.org/en/node/22086 for more info
It's not just acoustic bass, so maybe the title should be updated to reflect this.
After investigation here, http://musescore.org/en/node/22086 we are waiting for libsndfile 1.0.26 to be released. It should happen in the next weeks, see http://comments.gmane.org/gmane.comp.audio.libsndfile.devel/420
Hope the title is better?
can't we just take libsndfile from https://github.com/erikd/libsndfile?
Take libsndfile as it is not that easy. The build process requires on a number of tools (autogen, autoconf, automake etc...) which makes the integration harder. However, there is light since libsndfile creator is working on a Cmake based build. https://github.com/erikd/libsndfile/issues/71
This has been fixed in https://github.com/musescore/MuseScore/commit/3ddcfc16d4ecd2803ede28046…
by adding the attenuated soundfont from here to the codebase
http://musescore.org/en/node/22086#comment-83529
A proper fix when libsndfile is ok.
FWIW, I've been using the attenuated soundfont for a long time now. I'm sure an audiophile listening very carefully could hear the difference between it and the full version, but it's still so much better than the old TimGM6mb that people will be wowed when upgrading from 1.3 even if we don't ever get a libsndfile fix to allow the full FuildR3.
Automatically closed -- issue fixed for 2 weeks with no activity.