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

[Antoine Schmitt]

The fluidXtra (http://www.schmittmachine.com/fluidXtra.html) uses the  
sequencer extensively. And the fluidXtra has many users in the Adobe  
Director world, as it is the only free multipurpose sound engine  
available.

There is a IMHO bit complex API around the sequencer because we (Peter  
Hanappe and myself) initially designed it to be independent of the  
synth (it does not depend on fluid_synth.h), so that it could be  
usable outside of fluidsynth someday. This led to the seqbind.h file  
and the notion of sequencer 'client'. I think that as the sequencer  
will be made to depend on the slave timer, itself being dependent on  
the fluid synth, then we should simplify this sequencer API quite a  
bit. But we should not remove the fluid_sequencer_register_client  
function, as indeed it is important that other clients than the  
synthesizer may use the sequencer feature (the fluidXtra uses it for  
callbacks synchronized to the audio for example).

Le 21 mars 09 à 12:42, David Henningsson a écrit :
> Bernat Arlandis i Mañó skrev:
> > 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.
>
> There is no call to new_fluid_sequencer() anywhere in the source code,
> so it is merely a library function. I don't know which other programs
> that actually use the sequencer interface.
>
> // David
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fluid-dev

++ as