fluid-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Running more than 1 fluidsynth


From: Julien Claassen
Subject: Re: [fluid-dev] Running more than 1 fluidsynth
Date: Mon, 20 Oct 2008 22:08:02 +0200 (CEST)

Evening Joshua!
Just what I asked a mail ago. The problem is: Fluidsynth just has one Client_name "fluidsynth". So if another fluidsynth tries to get its client-name setup, JACK is annoyed. Reason: There already is a client named "fluidsynth". Workarounds: Use qsynth. Qsynth can start more than one fluidsynth engine in the background. This should give you the flexibility you need. I'm not sure, I can't use any graphical application, for being blind. Second way: Start one fluidsynth as a JACK client and the second as an ALSA client. Wait! This will work! Then you edit your ~/.asoundrc, to contain this:
*** ~/.asoundrc ***
pcm.!default
{
  type plug
  slave
  {
    pcm "myjack"
  }
}

pcm.myjack
{
  type jack
  playback_ports
  {
    0 system:playback_1
    1 system:playback_2
  }
  capture_ports
  {
    0 sstem:capture_1
    1 system:capture_2
  }
}
*** End excerpt from ~/.asoundrc ***
If you already have a line saying "pcm.!default" rename "!default" to whatever you like "old_default". Now a second fluidsynth should start as an alsa audio client, which by secret alsa magic still comes through to JACK. I believe, this way you could start more than two fluidsynths, but I'm not sure.
  Hope that helps!
  Kindest regards
          Julien

--------
Music was my first love and it will be my last (John Miles)

======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de




reply via email to

[Prev in Thread] Current Thread [Next in Thread]