zdoom
/
fluidsynth
mirror of https://github.com/ZDoom/fluidsynth.git
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Software synthesizer based on the SoundFont 2 specifications
2,014 Commits 10 Branches 46 Tags 9.2 MiB
C 92.2%
CMake 5.6%
C++ 1.1%
Shell 0.9%
Go to file
Foster McLane 19eacc6b60 Fix undefined behaviour in get_num_outputs in CoreAudio driver (#594) 
See discussion in #591 for details. Basically an incorrect size was
being allocated for the CoreAudio buffer list for a device. It was being
allocated by a VLA (which already did not quite fit the semantics of the
list) and the length calculated could be 0 (instead of the size of the
struct with no buffers elements) causing undefined behaviour.

This corrects it to allocate the amount of memory required by the
CoreAudio framework function and adds a check for the size retrieval and
for the dynamic allocation. This change passed UBSan in my test where
before the change it did not.

Fixes #591
 		2019-11-13 22:13:54 +02:00
.circleci Android CircleCI Build (#574) 2019-10-20 23:09:23 +02:00
.github Update default issue template 2019-08-15 14:31:21 +02:00
cmake_admin Remove unused macros from config.h (#588) 2019-11-04 16:44:32 +01:00
doc Deprecate fluid_synth_set_sample_rate() 2019-10-31 09:29:55 +01:00
include Make Fine Tune destination of default modulator Pitch-Wheel-To-pitch (#590) 2019-11-08 21:26:07 +01:00
sf2 remove VintageDreamsWaves-v2.sf3 2019-03-24 17:25:57 +01:00
src Fix undefined behaviour in get_num_outputs in CoreAudio driver (#594) 2019-11-13 22:13:54 +02:00
test Add a unit test for fluid_synth_write_float 2019-10-22 16:08:41 +02:00
.appveyor-vcpkg.yml Import CI build scripts from master 2019-08-08 21:57:20 +02:00
.azure-pipelines-mac.yml Split Mac and Windows CI build badges 2019-10-21 13:23:44 +02:00
.azure-pipelines.yml Split Mac and Windows CI build badges 2019-10-21 13:23:44 +02:00
.cirrus.yml Add more Cirrus FreeBSD CI builds 2019-10-07 13:25:12 +02:00
.clang-format cmake: setup formatting targets 2018-06-24 12:59:46 +02:00
.clang-tidy Silence clang-tidy's unsafe string operations 2019-07-11 10:16:22 +02:00
.gitignore add gitignore 2017-09-23 18:17:40 +02:00
.travis.yml TravisCI: add ppc64 and arm64 builds 2019-10-23 16:24:07 +02:00
AUTHORS Support Loading DLS Files (#493) 2019-05-11 05:31:56 +02:00
CMakeLists.txt Remove unused macros from config.h (#588) 2019-11-04 16:44:32 +01:00
CONTRIBUTING.md update CONTRIBUTING.md 2019-03-10 10:20:34 +01:00
ChangeLog remove fop-level "fluidsynth" directory node 2017-09-03 13:30:26 +02:00
LICENSE move README and LICENSE to top-level dir 2017-07-27 12:11:26 +02:00
README.cmake.md Update and rename README.cmake to README.cmake.md 2018-06-15 17:47:12 +02:00
README.md Change Android build badge 2019-10-21 14:21:09 +02:00
THANKS remove fop-level "fluidsynth" directory node 2017-09-03 13:30:26 +02:00
TODO Revise README (#566) 2019-10-13 10:56:24 +02:00
fluidsynth.conf.in add systemd service files 2018-02-20 21:31:35 +01:00
fluidsynth.pc.in remove fop-level "fluidsynth" directory node 2017-09-03 13:30:26 +02:00
fluidsynth.service.in Improve systemd integration 2019-03-02 10:18:32 +01:00
fluidsynth.spec.in remove fop-level "fluidsynth" directory node 2017-09-03 13:30:26 +02:00

README.md

FluidSynth

Build Status glib < 2.30 glib >= 2.30
Linux n.a. Build Status Travis
FreeBSD n.a. Build Status
Windows Build Status Build status
MacOSX n.a. Build Status
Android n.a. CircleCI

FluidSynth is a cross-platform, real-time software synthesizer based on the Soundfont 2 specification.

FluidSynth generates audio by reading and handling MIDI events from MIDI input devices by using a SoundFont. It is the software analogue of a MIDI synthesizer. FluidSynth can also play MIDI files.

OHLOH Project Stats

Documentation

The central place for documentation and further links is our wiki here at GitHub:

https://github.com/FluidSynth/fluidsynth/wiki

If you are missing parts of the documentation, let us know by writing to our mailing list. Of course, you are welcome to edit and improve the wiki yourself. All you need is an account at GitHub. Alternatively, you may send an EMail to our mailing list along with your suggested changes. Further information about the mailing list is available in the wiki as well.

Latest information about FluidSynth is also available on the web site at http://www.fluidsynth.org/.

License

The source code for FluidSynth is distributed under the terms of the GNU Lesser General Public License, see the LICENSE file. To better understand the conditions how FluidSynth can be used in e.g. commercial or closed-source projects, please refer to the LicensingFAQ in our wiki.

Building from source

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

Links

Historical background

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 intelligent use of midifiles. The arguments were:

  • Wavetable 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 environments, 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 its goal (a Soundfont synthesizer), stayed small (ideally one file) and didn't dependent on external code.