Software synthesizer based on the SoundFont 2 specifications
Find a file
Tom M 75db4f31b3
WinXP compatible CI builds (#419)
attempt to remain windows xp compatibility for AppVeyor CI builds and statically link MSVC's C Run-Time Library
2018-08-08 20:12:37 +02:00
.github Update issue_template.md 2018-02-22 20:21:24 +01:00
cmake_admin make cmake report install prefix 2018-06-07 14:15:06 +02:00
doc extend documentation on multi-channel rendering 2018-07-16 12:10:07 +02:00
include add fluid_synth_count_effects_groups() 2018-07-12 10:34:02 +02:00
sf2 Add VintageDreamsWaves-v2 in SF3 format and some tests for sf3 loading 2018-04-18 09:14:55 +02:00
src remove unused midi driver status functions 2018-07-21 10:43:38 +02:00
test enforce coding style guide 2018-06-24 13:13:18 +02:00
.appveyor-vcpkg.yml WinXP compatible CI builds (#419) 2018-08-08 20:12:37 +02:00
.appveyor.yml WinXP compatible CI builds (#419) 2018-08-08 20:12:37 +02:00
.clang-format cmake: setup formatting targets 2018-06-24 12:59:46 +02:00
.clang-tidy fix build for clang-tidy >= 5.0 2018-03-22 21:51:46 +01:00
.gitignore
.travis.yml travis CI: build audio drivers with clang3.9 2018-05-27 08:28:51 +02:00
AUTHORS
ChangeLog
CMakeLists.txt WinXP compatible CI builds (#419) 2018-08-08 20:12:37 +02:00
CONTRIBUTING.md add style guide related notes to CONTRIBUTING.md 2018-03-24 14:35:52 +01:00
fluidsynth.conf.in add systemd service files 2018-02-20 21:31:35 +01:00
fluidsynth.pc.in
fluidsynth.service.in add systemd service files 2018-02-20 21:31:35 +01:00
fluidsynth.spec.in
LICENSE
NEWS
README-OSX update READMEs 2018-06-15 18:38:21 +02:00
README.cmake.md Update and rename README.cmake to README.cmake.md 2018-06-15 17:47:12 +02:00
README.md update READMEs 2018-06-15 18:38:21 +02:00
THANKS
TODO

FluidSynth

Build Status glib < 2.30 glib >= 2.30
Linux/MacOSX n.a. Build Status Travis
Windows Build status Appveyor Build status

FluidSynth is a software real-time synthesizer based on the Soundfont 2 specifications.

OHLOH Project Stats

FluidSynth reads and handles MIDI events from the MIDI input device. It is the software analogue of a MIDI synthesizer. FluidSynth can also play midifiles using a Soundfont.

Information on the web

The place to look if you are looking for the latest information on FluidSynth is the web site at http://www.fluidsynth.org/.

For documentation, please see the links below.

For information on how to build FluidSynth from source, please see our wiki page.

Why did we do it

The synthesizer grew out of a project, started by Samuel Bianchini and Peter Hanappe, and later joined by Johnathan Lee, that aimed at developing a networked multi-user game.

Sound (and music) was considered a very important part of the game. In addition, users had to be able to extend the game with their own sounds and images. Johnathan Lee proposed to use the Soundfont standard combined with an intelligent use of midifiles. The arguments were:

  • Wave table synthesis is low on CPU usage, it is intuitive and it can produce rich sounds

  • Hardware acceleration is possible if the user owns a Soundfont compatible soundcard (important for games!)

  • MIDI files are small and Soundfont2 files can be made small thru the intelligent use of loops and wavetables. Together, they are easier to downloaded than MP3 or audio files.

  • Graphical editors are available for both file format: various Soundfont editors are available on PC and on Linux (Smurf!), and MIDI sequencers are available on all platforms.

It seemed like a good combination to use for an (online) game.

In order to make Soundfonts available on all platforms (Linux, Mac, and Windows) and for all sound cards, we needed a software Soundfont synthesizer. That is why we developed FluidSynth.

Design decisions

The synthesizer was designed to be as self-contained as possible for several reasons:

  • It had to be multi-platform (Linux, MacOS, Win32). It was therefore important that the code didn't rely on any platform specific library.

  • It had to be easy to integrate the synthesizer modules in various environements, as a plugin or as a dynamically loadable object. I wanted to make the synthesizer available as a plugin (jMax, LADSPA, Xmms, WinAmp, Director, ...); develop language bindings (Python, Java, Perl, ...); and integrate it into (game) frameworks (Crystal Space, SDL, ...). For these reasons I've decided it would be easiest if the project stayed very focussed on it's goal (a Soundfont synthesizer), stayed small (ideally one file) and didn't dependent on external code.

Home Page

Documentation

Software SoundFont Synthesizers:

Soundfont Editors

Conversion Tools

Soundfont Databases