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 is to use patchbay so
that your routes are restored as needed when the player plays a song.
Always keeping the gstreamer jacksink element in the 'playing' state,
although possible, would be too complicated, and still the routes
wouldn't survive the shutdown of gmb (unlike with patchbay).
So I'll close this as WON'T FIX ("invalid"). Though if someone find an
example of a player that does this, mention it here or by email, and I
will take a look to see if it can be done in gmb too.
Also, looking at the doc for the jack gstreamer element
(http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-jackaudiosink.html)
there is a potentially interesting property: port-pattern,
I couldn't test it as it is new in gstreamer 1.6, but maybe it could help, it
is a text pattern that is used to choose which port it should connect to. I can
easily add this option in gmb if it could be useful, let me know.
** Changed in: gmusicbrowser (Ubuntu)
Status: New => Invalid
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmusicbrowser/+bug/1499987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
