Josh Green skrev:
> On Sat, 2009-04-25 at 21:30 +0200, David Henningsson wrote:
>> About the buffer, first I think it should be an additional component
>> between the "producer" and the synth. We don't want to introduce the
>> overhead of thread safety when we don't need it, e g when using fast
>>
On Sat, 2009-04-25 at 21:30 +0200, David Henningsson wrote:
> About the buffer, first I think it should be an additional component
> between the "producer" and the synth. We don't want to introduce the
> overhead of thread safety when we don't need it, e g when using fast
> midi-file rendering or i
Josh Green skrev:
> On Sat, 2009-04-25 at 10:18 +0200, David Henningsson wrote:
>> We will probably have more than one producer? If somebody plays MIDI on
>> his/her keyboard while another thread is a midi file player.
> Yeah, that is true. I hadn't really considered that. I wonder if
> having mu
On Sat, 2009-04-25 at 10:18 +0200, David Henningsson wrote:
> > On Mon, 2009-04-20 at 20:59 +0200, David Henningsson wrote:
> >> But I've recently come to think of a disadvantage as well. If we're
> >> low-latency, it's important that fluid_synth_one_block finishes as soon as
> >> possible. If we
> On Mon, 2009-04-20 at 20:59 +0200, David Henningsson wrote:
>> But I've recently come to think of a disadvantage as well. If we're
>> low-latency, it's important that fluid_synth_one_block finishes as soon as
>> possible. If we do more things, we risc a buffer underrun if one of these
>> calls
On Mon, 2009-04-20 at 20:59 +0200, David Henningsson wrote:
> The callback I'm talking about is mainly the same thing as the as the
> sample timer, i e the possibility to receive notification before/after
> fluid_synth_one_block, and from the "audio thread" (or more correctly -
> whatever thread wh
Josh Green skrev:
> As for using a callback for resolving the concurrency issues. That
> sounds to me like you may still end up with race conditions, it would
> just make them less likely to happen.
The callback I'm talking about is mainly the same thing as the as the
sample timer, i e the possi
On Fri, 2009-04-10 at 15:09 +0200, David Henningsson wrote:
> What first was a quick fix that took an hour or two to write, expanded
> to fix ticket #15, and should also be expanded to fix the sequencer. And
> now I'm about to suggest that timing should be a separate
> component/subsystem.
>
> Fir
Ebrahim Mayat skrev:
> On Fri, 2009-04-10 at 15:09 +0200, David Henningsson wrote:
> Fluidsynth was initially used as a rendering library for Linux
> sequencers. IIRC, it was in release 1.0.4 that the live MIDI controller
> triggering feature was introduced by Stephane Letz in response to a
> reque
What first was a quick fix that took an hour or two to write, expanded
to fix ticket #15, and should also be expanded to fix the sequencer. And
now I'm about to suggest that timing should be a separate
component/subsystem.
First some history (from someone who has only been around the project a
mon
10 matches
Mail list logo
