Also, I forgot to mention another work-around: use the pulse-audio
output and use a pulse-audio plugin to connect to JACK :
http://www.penguinproducer.com/Blog/2011/09/using-jack-with-different-
non-jack-programs/
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Pulseaudio and jack don't seem to play nicely together, because it gives
horrible crunching distortion. I suspect someone somewhere is making a
faulty assumption about scaling.
The patchbay thing works well enough to solve the immediate issue.
--
You received this bug notification because you
Bad news, using the 'ready' state instead of 'null' doesn't solve your
problem. When playing with the gapless option, the state is kept to
'playing' so that's why it worked.
After looking a bit, it seems that's how most players work (as opposed
to 'pro'/creation audio software), the work-around
I must admit I don't know much about jackd. From my simple test playing
on alsa (jackd -d alsa), it seems to work fine. So it'd be nice if you
could explain how I could see the problem for myself.
I _think_ the problem is that gmb set the gstreamer the playbin to the 'null'
state rather than the
Just tried it - it doesn't "hop" between songs but it does if you select
a new song.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1499987
Title:
Jack output fundamentally broken
To manage
I'll try that - perhaps gapless playback will solve the problem.
An app should never disconnect from jack unless it's told to (possibly
by exiting). If it's disconnecting because the output is set to null,
then doing that after a minute will cause the problem to occur if you
pause the music for
