-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] sf3 support #607
Comments
This needs new fluidsynth version. |
That is right that a lot of sf3 are available as well as sf2. This is because of its purpose I guess : "same as an sf2, but lighter weight because it's OGG and not WAV". Promise, if I find one, I'll tell you! (PS: I've got a working 1.1.8-1 version build for stretch which i giving me the ability to load SF3 in a few software) |
I believe carla should support this now. |
@trebmuh ping :) |
ftp://ftp.osuosl.org/pub/musescore/soundfont/MuseScore_General/MuseScore_General.sf3 Loads and make piano sounds for me, though I turned all the reverb/chorus dials up and it didn't sound different. |
I see in the kxstudio builds at least, sf3 is not supported. PS: regarding the chorus and reverb, these are soundfont specific, and also something that fluidsynth does internally. carla only tells fluidsynth to activate the parameters. |
@falkTX I've rebuild a carla from GIT fcc1597 and the SF3 is working. Thanks! I've spotted a small buggish thingy: while it reads the SF3, the "type column" is set to SF2. That's not a big deal but it did confuses me for a few minutes while I was searching for a SF3 with the help of the "type" column. Please, let me know if you prefer a new issue to be open or if you're fine with being here. Once again, thanks! |
yeah, not something I am going to "fix" right now. If it is something you really care about, open a new bug report for it. |
Done here: #739 . |
Since SF3 is now supported within fluidsynth, it is now possible to support SF3 in software depending on fluidsynth which Carla is.
See LMMS/lmms#3895 and LMMS/lmms#3286 .
The text was updated successfully, but these errors were encountered: