e project by letting us know
> about them :) Best regards,
> Josh
>
>
> On Thu, 2007-12-13 at 20:27 -0800, Ken Restivo wrote:
> > I've noticed an alarming tendency lately for fluidsynth to "go stealth"
> > sometimes.
> >
> > Basic
ou could give the latest release a test though, that would be great!
> You could always revert to your CVS version, if you find there are any
> other issues. But you could also help the project by letting us know
> about them :) Best regards,
> Josh
>
>
> On Th
I've noticed an alarming tendency lately for fluidsynth to "go stealth"
sometimes.
Basically I'll start up a couple fluidsynth instances, like I've been doing
every day for almost a year now. But, once in a while, and increasingly
frequently, the instances will NOT show up in JACK, nor will the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 07, 2007 at 03:02:10PM -0700, Nathaniel Gray wrote:
> Hi fluid-devs,
>
> I'm doing a VST/AU/etc embedding of FluidSynth and I've had a lot of
> success so far, but there's one issue I'm not sure about. As usual
> in audio plugin archi
to FluidSynth one time using liblo and it was
> pretty straightforward (I'll see if I can find the code). I meant to
> submit the patch, but then I realized that liblo is GPL licensed while
> FluidSynth is LGPL. I never got around to figuring out if there was a
> way to resolv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 20, 2007 at 08:55:28PM +0200, Josh Green wrote:
> On Fri, 2007-04-20 at 19:42 +0200, Miguel Lobo wrote:
> > Hi Josh,
> >
> > Glad to hear you like the idea!
> >
>
Another thing to add to the list: OSC support, at least for the kind of
On Fri, Apr 27, 2007 at 08:46:43PM +0200, Josh Green wrote:
> On Fri, 2007-04-27 at 11:12 -0700, Ken Restivo wrote:
> > On Fri, Apr 27, 2007 at 07:54:32PM +0200, Josh Green wrote:
> > > I believe that functionality is already available:
> > > fluidsynth -f configfile.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 27, 2007 at 07:54:32PM +0200, Josh Green wrote:
> I believe that functionality is already available:
> fluidsynth -f configfile.txt
>
> The config file just contains commands like you would type at the
> command prompt.
>
> fluidsynth --h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 27, 2007 at 12:24:09PM +0200, Miguel Lobo wrote:
> HI Ken,
>
> There are some uses of FluidSynth I'm not familiar with and I would like to
> know more about these use cases.
>
> For me, as a pretty heavy user of fluidsynth (it's my main i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Apr 21, 2007 at 04:45:48PM +0200, Josh Green wrote:
> On Sat, 2007-04-21 at 12:29 +0300, Mihail Zenkov wrote:
> > Why we hear it only in 16 bits?
> >
>
> FluidSynth currently only has support for 16 bit samples. Swami uses
> the SoundFont lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I built debian packages of the latest CVS of fluidsynth for AMD4 (Core 2 Duo),
and put them here:
http://www.restivo.org/projects/debian/various-etch-audio-backports/
- -ken
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGJa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Feb 21, 2007 at 01:04:56PM -0700, Dave Serls wrote:
> On Wed, 21 Feb 2007 11:17:06 -0800
> Ken Restivo <[EMAIL PROTECTED]> wrote:
>
> > Attached is a MIDI file that causes fluidsynth to segfault on my machine
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Feb 21, 2007 at 01:04:56PM -0700, Dave Serls wrote:
> On Wed, 21 Feb 2007 11:17:06 -0800
> Ken Restivo <[EMAIL PROTECTED]> wrote:
>
> > Attached is a MIDI file that causes fluidsynth to segfault on my machine
> >
Attached is a MIDI file that causes fluidsynth to segfault on my machine (Core
Duo 1.66Ghz 2GM RAM, linux 2.8.19-rt15), jackd 102.20-1, fluidsynth
1.0.8.2006.12.24-2-SVN)
This is with no softsynths running except one fluidsynth instance, using the
Steinway Grand soundfont (the 80MB one with all
ut it'd be
nice if there were a way to identify the MIDI-handling thread so I could bump
that thread to *higher* than JACK, which is what is recommended by the guide I
linked to.
>
> Perhaps that should be permanently done, so that things are setup in an
> ideal manner for all use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This guide says: locate the MIDI threads of your softsynths, and give them a
higher rtprio than JACK.
http://tapas.affenbande.org/wordpress/?page_id=40
OK, I have chrt, and a full RT system, and I have most of the priorities set up
the way this gui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On an SMP system (Intel Core Duo), does fluidsynth spawn off child
threads/processes for each midi channel active?
Right now I have multiple fluidsynth instances, one for each MIDI instrument,
and I patch them using qjackctl. I suppose I could also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 01, 2007 at 12:28:03PM -0700, Dave Serls wrote:
>
> I haven't seen this message, but I'm more of a recidivist. Having found a
> combination that mostly works and is only moderately annoying, I kept it.
> I would suggest a sound card
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 02, 2007 at 08:32:00AM -, Rui Nuno Capela wrote:
> On Tue, January 2, 2007 02:35, Ken Restivo wrote:
> >
> >
> > Thanks. I have ordered an FA-66, which should arrive later this week.
> >
>
> Firewire?
gt; with Jack and very bad audio output (I don't get continuous xrun errors,
> > > but it sounds like the effect of lots and lots of xruns, clicks/pops
> > > etc). I believe I got things working in the past by messing with the
> > > frames and period sizes. I just
Maybe that helps? If not, I would look into other things, like make
> sure jackd is using the hw:0 device (that is the default, so not sure
> why it wouldn't be). Best regards,
> Josh
>
>
> On Thu, 2006-12-28 at 02:41 -0800, Ken Restivo wrote:
> > -BEGIN PG
mes without problems, as long as it is set to 3
> periods. You can do this by starting jack like so:
>
> jackd -d alsa -n 3 -p 512
>
> Maybe that helps? If not, I would look into other things, like make
> sure jackd is using the hw:0 device (that is the default, so not sure
> why
-ken
- --
On Thu, Dec 28, 2006 at 06:02:14PM +0100, Florian Schmidt wrote:
> On Thursday 28 December 2006 11:41, Ken Restivo wrote:
> > I don't expect any answer to this, but it's making me very sad.
> >
> > Advanced Linux Sound Architecture Driver Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't expect any answer to this, but it's making me very sad.
Advanced Linux Sound Architecture Driver Version 1.0.14rc1.
Compiled on Dec 28 2006 for kernel 2.6.19.1-rt15-1-ingo (SMP).
And an ugly hda-intel sound card, on a Mac Mini.
jackd starts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've run into the problem outlined in
http://lists.nongnu.org/archive/html/fluid-dev/2006-11/msg00041.html and I've
bought 2GB RAM for my machine as a "solution" for now. Yay, it works.
I have a separate, unrelated question too. I'm running 2.6.17 D
25 matches
Mail list logo
