Uh, oh, *=K=*! I don't have the KDE stuff installed and in this slim system
I don't want it. Too bad. But thanks, anyway for the suggestion. The UI
looks very nice.
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on Life and Faith<http://www.lanelester.com/>
Thanks for all your help, guys.
It looks like QSynth is working OK, but I don't see any way to tell it what
file to play!
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on Life and Faith<http://www.lanelester.com/>
___
fluid-
ckd. So I
installed Jackd, and there's still a problem. Part of the output says that
device "hw:0" is in use and the application using it needs to be stopped.
I couldn't copy and paste the QSynth output, so here's a screenshot:
http://i.imgur.com/lqiXL.png
Lane
--
*Lane Les
-a alsa /usr/share/sounds/sf2/FluidR3_GM.sf2 At_The_Hop.mid
Would jack sound any better? The above sounds very good.
So, is FluidSynth a command line app? I'm not afraid of the terminal, but I
prefer GUI.
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on L
t I'm still curious about whether to stick with alsa or go with jack. What
do you think?
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on Life and Faith<http://www.lanelester.com/>
___
fluid-dev mailing list
fluid-dev@nongnu.o
[no]
--query-now, -Q do freedb query when starting
--rename, -R rename according to freedb file, eg. after editing it
--vbr, -v generate variable bitrate files [yes] +
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on Life and Fai
ver socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
fluidsynth: error: Failed to connect to Jack server.
Failed to create the audio driver
Lane
--
*Lane Lester*
Codger's Cogitations: Reflections on Life and Faith<http://
