26 Aug
2009
26 Aug
'09
10:35 p.m.
Hello all,
I'm using jackd and jamin at work to help the sound in cheap
headphones in such a way:
# xine -A jack *.ogg
Then I route the signal from xine to jamin and use jamin's bass boost
for instance.
xine disconnects from jamin at the end of each song. I have to
manually reconnect it using qjackctl's switch panel. I run a rather
'old' version of xine/jackd/jamin (Fedora 8). Is this a problem with
such versions ? Or, is there an option to be given somehow to tell
xine to maintain the connection until all songs are played ?
Cheers.
27 Aug
27 Aug
6:23 a.m.
On Wed, 26 Aug 2009 20:44:02 -0400
lanas <lanas(a)securenet.net> wrote:
Hello all,
I'm using jackd and jamin at work to help the sound in cheap
headphones in such a way:
# xine -A jack *.ogg
Then I route the signal from xine to jamin and use jamin's bass
boost for instance.
xine disconnects from jamin at the end of each song. I have to
manually reconnect it using qjackctl's switch panel. I run a rather
'old' version of xine/jackd/jamin (Fedora 8). Is this a problem with
such versions ? Or, is there an option to be given somehow to tell
xine to maintain the connection until all songs are played ?
Cheers.
It's just a somewhat wrong implementation of jack in xine. I just
checked for you with a very recent version of xine and it still behaves
this way.
Sadly, many media players connect to the first two outputs they can
find at the beginning of every new song/video, and obviously this is
very very wrong.
I don't know if there is an option in xine to disable autoconnect, I
somewhat doubt it.
One possible solution for you would be qjackctls patchbay where you
could set up a persistent connection from xine to jamin. I haven't
tried it but it could work good enough.
Regards,
Philipp
9:23 p.m.
Le Jeudi, 27 Août 2009 10:23:29 +0200,
<hollunder(a)gmx.at> a écrit :
One possible solution for you would be qjackctls
patchbay where you
could set up a persistent connection from xine to jamin. I haven't
tried it but it could work good enough.
Thanks, this works good, as it establishes automatically the xine ->
jamin connection at every song. That works. On the other hand,
xine always conencts to the system sound at every song so there are two
conenctions. The automatic one configured with qjackctl's patchbay,
and xine's own. So at the start of each song I have to disconnect the
conenction xine made to leave the one configured by the patchbay alone.
Is there a way with qjackctl to prevent a connection to be made ? If
it does, the user interface is not that intuitive about it.
Cheers.
9:40 p.m.
lanas wrote:
Le Jeudi, 27 Août 2009 10:23:29 +0200,
<hollunder(a)gmx.at> a écrit :
while in qjackctl patchbay, try the "exclusive" flag at the xine side.
as designed, any other connections will get shutdown and only the ones
defined (in your case xine->jamin) will be kept, again and again. thus
the said "exclusive" semantics
seeya
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
One possible solution for you would be qjackctls
patchbay where you
could set up a persistent connection from xine to jamin. I haven't
tried it but it could work good enough.
Thanks, this works good, as it establishes automatically the xine ->
jamin connection at every song. That works. On the other hand,
xine always conencts to the system sound at every song so there are two
conenctions. The automatic one configured with qjackctl's patchbay,
and xine's own. So at the start of each song I have to disconnect the
conenction xine made to leave the one configured by the patchbay alone.
Is there a way with qjackctl to prevent a connection to be made ? If
it does, the user interface is not that intuitive about it.
5365
days inactive
5366
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
hollunder＠gmx.at -
lanas -
Rui Nuno Capela