On Sat, 2009-04-25 at 23:04 +0200, David Henningsson wrote:
> Josh Green skrev:
> > On Mon, 2009-04-20 at 22:08 +0200, David Henningsson wrote:
> >>> I like the use of '-' to indicate stdout. That is common to many
> >>> applications and would save the user from accidentally getting a
> >>> termin
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 Mon, 2009-04-20 at 22:08 +0200, David Henningsson wrote:
>>> I like the use of '-' to indicate stdout. That is common to many
>>> applications and would save the user from accidentally getting a
>>> terminal full of seemingly endless junk.
>> Seems like a good idea. Hopefull
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
Now I have made a Debian package of 1.0.9, that has the non-DFSG files
removed. I've uploaded the Debian sid package to:
- URL: http://mentors.debian.net/debian/pool/main/f/fluidsynth
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors
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
