Sorry everyone, for keeping the thread hanging... I was away from my system for a few days, and just got back. @J.E.B Wow! That looks like a rather comprehensive list. Will try each suggestion, perform the stress test, and get back to you. @Lee Interesting idea. If memory serves me right, restarting only fluidsynth doesn't solve the problem, but I have to confirm this. Will do so soon... Cheers, Guru Lee Revell wrote: > On Mon, Nov 2, 2009 at 3:03 AM, Guru Prasad B. R. <prasadbrg@xxxxxxxxx> wrote: > >> Hello everyone, >> So I've been trying out AVLinux. By the looks of it, quite impressive >> - but I soon ran into a rather serious issue, but I doubt whether it has >> anything to do with AVLinux or not. I need your help in this knowing for >> sure. >> >> My usual setup involves a piano sample on Linuxsampler and a strings >> soundfont on qsynth. I had an unusual gig last week that required no >> piano sounds, but instead use of multiple layered samples. I therefore >> used only qsynth, with 3 engines running concurrently. So in my brand >> new AVLinux setup, I loaded up my samples, and had sooperlooper running >> 2-3 loops concurrently, all on a core2-duo macbook. >> > > If it only happens when you run more than 1 fluidsynth app at once, a > locking bug in the fluidsynth shared library would explain those > symptoms. Is it supposed to be thread safe? > > Does the problem go away if you leave JACK running but restart all the > fluidsynth apps? > > Lee > > _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
