Skip to content
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

Add Support for SF2 SoundFont files as instruments #29

Open
tim-janik opened this issue Nov 22, 2023 · 3 comments
Open

Add Support for SF2 SoundFont files as instruments #29

tim-janik opened this issue Nov 22, 2023 · 3 comments
Assignees
Milestone

Comments

@tim-janik
Copy link
Owner

While hunting for links to recommend as downloadable sample collections, I found that lots of people are confusing SF2 with SFZ files, often just referring to them as "sound font" files.

I'm working on merging LiquidSFZ (#7) atm, it'd be really nice to have similar support for SF2 files.

Ideally, we'd integrate SF2 rendering in a manner similar to LiquidSFZ, based on FluidSynth, here's the integration code created by Stefan from Beast:

https://github.com/tim-janik/beast/blob/master/bse/bsesoundfont.cc

Stefan, is that something you can look into for Anklang?

@swesterfeld
Copy link
Collaborator

Stefan, is that something you can look into for Anklang?

Sure, I'll implement a FluidSynth device, similar to the LiquidSFZ device.

@tim-janik tim-janik added this to the v0.4.0 milestone Jan 27, 2024
@swesterfeld
Copy link
Collaborator

FYI, this currently blocks on property rescanning. After loading the sf2 file, a new choice which contains all the presets of the soundfont should be created, to be able to select the instrument to be used. Its the same mechanism that is needed for supporting sfz file specific properties in the LiquidSFZ (#44).

@swesterfeld
Copy link
Collaborator

Or maybe one day we have some kind of device preset support, which also CLAP and LV2 have in some way, then depending on how it is implemented we could use it to select the sf2 preset

@tim-janik tim-janik modified the milestones: v0.4.0, vFuture Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants