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
schedule.
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
http://www.schmittmachine.com/fluidXtra.html
fluidXtra is listed in our applications page
http://fluidsynth.resonance.org/trac/wiki/Applications
there was a thread on January about this matter
http://lists.gnu.org/archive/html/fluid-dev/2009-01/msg00066.html
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ñó
_______________________________________________
fluid-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/fluid-dev
