I can't help but join in to outline a thing or two regarding LMMS and JACK.
>From the very beginning (when I started to use LMMS), connecting to JACK
didn't prove to be a wise choice. As such, I've been using bare ALSA and
things are as expected, yes.
My situation may be a little different, though. No matter which
Linux/Gnu platform I'm using, on startup LMMS will cause an xrun. When I
play anything, be it one track + one instrument/vst/sample or multiples of
either, I'd get cracks and pops similar to a system where the audio
subsystem is not optimized to handle such tasks. Soon, the xruns will
increase to an extent the application is no longer usable and would
ultimately crash if a track is playing for more than a minute or two.
The strange thing starts there. If I run a program like Hydrogen via ALSA
only, and before starting up LMMS in particular, I'd get those same
distortion - badly. If I quit the program, initiate LMMS and _play_
something, then go on to start Hydrogen again, the drum tracks are crystal
clear. It's as if LMMS changes some ALSA settings, and when JACK comes in to
the equation, it just so happens that there is some sort of a conflict. Is
there any code in particular that might provide a hint on this issue? I
believe that'd be the key to pin-point where these LMMS + JACK issues stem
P.S: LMMS + ALSA, JACK + Hydrogen + Ardour is my current _working_ setup -
and it's perfectly fine. It's just that any synth-based (LMMS) work need to
be carried out in a separate ALSA-only session before I export the tracks
for mixing/further processing in the JACK environment.
On 08/04/2008, Nathan Coulson <conathan@...> wrote:
> > What happens with a non-JACK audio device?
> > -Paul
> (Sorry about the delay, wasn't on the lmms list)
> Using alsa for audio works exactly as expected. I let my brother
> loose on it, who had about 15 different instruments (Many were vst's).
> It plays, it loads (Crashed the odd time when I moved stuff around
> while moving, but that's another story).
> Using jack, it works for a while (fails when I load the above
> project). I believe the trigger is when a xrun occures on jackd,
> since I see xrun's when I see the thread go zombie on lmms. Loading
> complicated lmms files is one trigger I have found.
> Nathan Coulson (conathan)
> conathan at gmail com
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> Monday, April 7! Use priority code J8TLD2.
> LMMS-devel mailing list