[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Patch for bad MIDI timing (with large buffer sizes)

From: Bernat Arlandis i Mañó
Subject: Re: [fluid-dev] Patch for bad MIDI timing (with large buffer sizes)
Date: Sat, 21 Mar 2009 13:45:17 +0100
User-agent: Mozilla-Thunderbird (X11/20090103)

Pedro Lopez-Cabanillas escrigué:
Bernat Arlandis i Mañó wrote:
Pedro Lopez-Cabanillas escrigué:
For the record: the MIDI file player and the MIDI sequencer are two
different interfaces of FluidSynth. They are implemented independently,
though the player could be reworked to use the sequencer as a backend
(some day). But anyway, both functions need to play MIDI events on
Where is the MIDI sequencer interface used?  It looks like something
that belongs to the Jack MIDI server.

fluidXtra, by Antoine Schmitt is using this interface

fluidXtra is listed in our applications page

there was a thread on January about this matter

About your question: yes, Jack MIDI provides some sequencer functionality, but it requires Jack audio daemon running, because it uses the Jack audio buffers sample count for timing. Another available MIDI sequencer for Linux is the ALSA Sequencer. There are some more sequencer engines for Linux and other platforms.

Having a platform independent sequencer integrated in FluidSynth has obvious advantages. It is a decision of the application developers to use it, or something else.
Sure, I guess it's practical having everything together, I'm not implying this is good or bad, but further developing of FS is hard since it's a mixture of libraries (data types, logging, sequencer, soundfont management, etc.), a lo more than just a synthesizer. I might left some libraries unattended for my branch since I won't be able to keep up with everything, until someone takes care of them, but this doesn't imply that I'm against them.

Bernat Arlandis i Mañó

reply via email to

[Prev in Thread] Current Thread [Next in Thread]