To help make things a bit more organized I will set forth a plan for the
1.1.0 development cycle. This is not set in stone and is open for
input.
Development cycle will be 3 months, which means FluidSynth 1.1.0 will be
released around July 12th. Feature freeze will occur 2 weeks before.
June 28
jimmy escrigué:
It seems we are all looking forward to 2.0, while 1.0 is agreed as legacy code
base.
I don't know how far along the code refactoring (FS 2.0) is. Can we get a
status update, or current functions available. What's missing compare to 1.0.9?
I still haven't worked a lot on i
Hello Esben,
Yes indeed, its a problem. Its on the list for the next release.
Ticket #6 if you want to track it:
http://fluidsynth.resonance.org/trac/ticket/6
Cheers!
Josh
On Wed, 2009-04-15 at 03:03 +0200, Esben Stien wrote:
> Running fluidsynth-1.0.9, which is really nice, thanks;),
Running fluidsynth-1.0.9, which is really nice, thanks;), but it reports:
fluidsynth: warning: Jack sample rate mismatch, expect tuning issues
(synth.sample-rate=44100, jackd=96000)
I run with -r 96000 and it's fine, but why don't you just get the
sample rate from JACK?;).
--
Esben Stien is b
Hello Jimmy,
On Tue, 2009-04-14 at 15:56 -0700, jimmy wrote:
> It seems we are all looking forward to 2.0, while 1.0 is agreed as legacy
> code base.
>
> I don't know how far along the code refactoring (FS 2.0) is. Can we get a
> status update, or current functions available. What's missing c
It seems we are all looking forward to 2.0, while 1.0 is agreed as legacy code
base.
I don't know how far along the code refactoring (FS 2.0) is. Can we get a
status update, or current functions available. What's missing compare to 1.0.9?
It may be better if we put more efforts to work towar
Hello everyone,
My name is Zachary Northrup and I'm a 16 year old living in New York (the
state, not the city). I've been programming for about 6-7 years in the areas
of (listed chronologically): web development, VB, VB/C# .NET, C++, C,
robotics/embedded systems, electronics (of all kinds), an
Hi,
About the future versions, I agree with keeping compatibility in 1.1, adding
new functionality while avoiding breaking existing applications. But at the
same time, keep the 2.0 door open for changes that require incompatible
changes. When functions must be added or changed, it would be sens
Hello David,
On Tue, 2009-04-14 at 18:06 +0200, David Henningsson wrote:
> > With all this big changes and new plans, I'm wondering where does lie
> > the 2.0 branch? I could have done some work these holidays but I have
> > the feeling that we're diverging and I prefer to wait for the water to
>
Hello Bernat,
On Tue, 2009-04-14 at 11:00 +0200, Bernat Arlandis i Mañó wrote:
> First, I sent this message but it didn't get to my mailbox and it seems
> to be ignored by everyone so I guess it didn't reach your mailbox
> neither, I think it's interesting:
> http://lists.gnu.org/archive/html/fl
> Date: Saturday, April 11, 2009, 9:00 AM
> . . .
> Okay, I stand corrected. Judging from the design of the
> audio drivers
> and the player/sequencer, it seems like those parts were
> designed for
> live usage only (up to now).
Whatever changes made, please do keep in mind, and test the live u
Hello all,
rapid introduction:
I'm 47 and living in Paris, France. I'm both a programming consultant (www.schmittmachine.com
) and an artist (www.gratin.org/as/), using programming as a main
artistic material : things that act by themselves, programmed freedom,
things like this...
I starte
Bernat Arlandis i Mañó skrev:
> First, I sent this message but it didn't get to my mailbox and it seems
> to be ignored by everyone so I guess it didn't reach your mailbox
> neither, I think it's interesting:
> http://lists.gnu.org/archive/html/fluid-dev/2009-04/msg00044.html
I got it, read it, an
Josh Green escrigué:
Hello,
Its been really nice reading the introductions.. There are no specific
qualifications on this, so if anyone else feels inspired to introduce
themselves, please do. I know there are several other people on this
list who have been long time FluidSynth contributors and
14 matches
Mail list logo
