2 May
2015
2 May
'15
11:50 p.m.
Hi everyone!
To launch jack I run:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D -Chw:5,1 -Phw:5,0
This is what I have in my .jackdrc.
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl, I get this in the
message window:
creating alsa driver ...
hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
The 5.0 output becomes 5.1. I don't understand why.
Does anyone have an idea of what happen ?
Sound card: Fast Track Pro
OS: Ubuntu 12.04
Jack: jackdmp 1.9.8
QjackCtl: 0.3.8
pulseaudio-module-jack installed and Fast Track Pro disabled in PulseAudio
Anton Curl
3 May
3 May
12:06 a.m.
On Sat, 02 May 2015 23:51:22 +0200, Anton Curl wrote:
This is what I have in my .jackdrc.
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl
Do you use this settings, or do you expect that QjackCtl does use the
settings stored in ~/.jackdrc?
QjackCtl does not use the settings stored in ~/.jackdrc, it does use
the settings stored in ~/.config/rncbc.org/QjackCtl.conf .
Regards,
Ralf
2:06 a.m.
On Sat, May 2, 2015 4:51 pm, Anton Curl wrote:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq
-D -Chw:5,1
-Phw:5,0
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl, I get this in the
message window:
creating alsa driver ...
hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
The 5.0 output becomes 5.1. I don't understand why.
In the QJackControl setup dialog, did you select different input and
output hardware device?
--
Chris Caudle
7:09 a.m.
On 03/05/2015 00:06, Ralf Mardorf wrote:
On Sat, 02 May 2015 23:51:22 +0200, Anton Curl wrote:
Yes, but QJackCtl wrote
this file, not me. So if I run this command, I
run the same command that QJackCtl uses to start jackd.
On 03/05/2015 02:05, Chris Caudle wrote:
This is what I have in my .jackdrc.
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl
Do you use this settings, or
do you expect that QjackCtl does use the
settings stored in ~/.jackdrc?
QjackCtl does not use the settings stored in ~/.jackdrc, it does use
the settings stored in ~/.config/rncbc.org/QjackCtl.conf . On Sat, May 2, 2015 4:51 pm, Anton Curl wrote:
Yes,
Input: hw:5.1
Output: hw:5.0
And duplex is also set.
Anton Curl
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2
-Xseq -D -Chw:5,1
-Phw:5,0
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl, I get this in the
message window:
creating alsa driver ...
hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
The 5.0 output becomes 5.1. I don't understand why.
In the QJackControl setup dialog, did you select different input and
output hardware device?
4:08 p.m.
Some news:
I reinstalled jackd1 instead of jackd2. QJackCtl now runs jack without
error. But ladiconf depends on jackd2. So I can't use Gladish, which is
very annoying for me.
Furthermore, Puleaudio sink and source are no more created automatically
in Jack. I have to add supplementary lines in /etc/pulse/default.pa,
then kill Pulseaudio, and when it restarts, it appears in jackd
connections. It's also not very practical.
On 02/05/2015 23:51, Anton Curl wrote:
Hi everyone!
To launch jack I run:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D -Chw:5,1
-Phw:5,0
This is what I have in my .jackdrc.
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl, I get this in
the message window:
creating alsa driver ...
hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
The 5.0 output becomes 5.1. I don't understand why.
Does anyone have an idea of what happen ?
Sound card: Fast Track Pro
OS: Ubuntu 12.04
Jack: jackdmp 1.9.8
QjackCtl: 0.3.8
pulseaudio-module-jack installed and Fast Track Pro disabled in PulseAudio
Anton Curl
10:48 p.m.
On Sun, 3 May 2015, Anton Curl wrote:
Some news:
I reinstalled jackd1 instead of jackd2. QJackCtl now runs jack without error. But
ladiconf depends on jackd2. So I can't use Gladish, which is very annoying for
me.
Furthermore, Puleaudio sink and source are no more created automatically in Jack.
I have to add supplementary lines in /etc/pulse/default.pa, then kill Pulseaudio,
and when it restarts, it appears in jackd connections. It's also not very
practical.
With jack2, I have found chmod -x /usr/bin/jackd helps. jackd does not do
auto-pulse or gladish either anyway. What that leaves is jackdbus which is
what qjackctl starts.
You can also play with jack_control for trouble shooting.
jack_control ds alsa dps capture hw:5,1 dps playback hw:5,0 dps \
rate 44100 dps period 256 dps nperiods 2 dps midi-driver seq \
ep realtime-priority 80 start
Should give you the same thing as the command below... but run jackdbus
instead.
On 02/05/2015 23:51, Anton Curl wrote:
Hi everyone!
To launch jack I run:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D
-Chw:5,1 -Phw:5,0
Ya, I know that is a long command line :)
Personally, I would remove the dps midi-driver seq (-Xseq) and add the
command:
a2j_control ehw start
But that is personal preference. You may have a better idea than I why you
want seq.
--
Len Ovens
www.ovenwerks.net
4 May
4 May
12:08 a.m.
On 03/05/2015 22:45, Len Ovens wrote:
It was a mistake, I don't know why I had this -Xseq option.
Oh! Now it works again...
I don't know what I've changed but jackd starts on hw:5,0 as playback
and hw:5,1 as capture with QJackCtl and Gladish.
I'm very confused. I just hope it will keep working when I'll reboot.
Anton Curl
On Sun, 3 May 2015, Anton Curl wrote:
Is there other differences between runing jackd with
command line and
with QJackCtl ?
Some news:
I reinstalled jackd1 instead of jackd2. QJackCtl now runs jack
without error. But
ladiconf depends on jackd2. So I can't use Gladish, which is very
annoying for
me.
Furthermore, Puleaudio sink and source are no more created
automatically in Jack.
I have to add supplementary lines in /etc/pulse/default.pa, then kill
Pulseaudio,
and when it restarts, it appears in jackd connections. It's also not
very
practical.
With jack2, I have found chmod -x /usr/bin/jackd helps. jackd does not
do auto-pulse or gladish either anyway. What that leaves is jackdbus
which is what qjackctl starts.
You can also play with jack_control for trouble shooting.
jack_control ds alsa dps capture hw:5,1 dps playback hw:5,0 dps \
rate 44100 dps period 256 dps nperiods 2 dps midi-driver seq \
ep realtime-priority 80 start
Should give you the same thing as the command below... but run
jackdbus instead.
With this command it's like with QJackCtl. jackd starts with
hw:5,1 for
capture and playback.
On 02/05/2015 23:51, Anton Curl wrote:
Hi everyone!
To launch jack I run:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D
-Chw:5,1 -Phw:5,0
Ya, I know that is a long command line :)
Personally, I would remove the dps midi-driver seq (-Xseq) and add the
command:
a2j_control ehw start
But that is personal preference. You may have a better idea than I why
you want seq.
12:23 a.m.
On Mon, 4 May 2015, Anton Curl wrote:
That sounds like a bug in the jack2 dbus interface to me. I have never
used anything more than first digit devices so I can't even test it. In
fact I have not used different input to output devices.
On 03/05/2015 22:45, Len Ovens wrote:
It depends :) Qjackctl can be set up to run either jackd or jackdbus. In
debian/ubuntu the default action is to run jackdbus. Switch to jackd on
the last tab in setup (Misc) with the "Enable D-Bus interface" checkbox.
With Dbus disabled jackd is what is run and the action is the same as
running jackd from the command line.
With jack2, I have found chmod -x /usr/bin/jackd
helps. jackd does not do
auto-pulse or gladish either anyway. What that leaves is jackdbus which is
what qjackctl starts.
Is there other differences between runing jackd with command
line and with
QJackCtl ? You can also
play with jack_control for trouble shooting.
jack_control ds alsa dps capture hw:5,1 dps playback hw:5,0 dps \
rate 44100 dps period 256 dps nperiods 2 dps midi-driver seq \
ep realtime-priority 80 start
Should give you the same thing as the command below... but run jackdbus
instead.
With this command it's like with QJackCtl. jackd starts with hw:5,1
for
capture and playback. Oh! Now it works again...
I don't know what I've changed but jackd starts on hw:5,0 as playback and
hw:5,1 as capture with QJackCtl and Gladish.
I'm very confused. I just hope it will keep working when I'll reboot.
From a terminal, you may wish to find out if it is
jackd or jackdbus you
are using. But if Gladish (and I presume Jacksink in pulse)
are working,
it sounds like it does work.
--
Len Ovens
www.ovenwerks.net
1:14 a.m.
On Sun, 3 May 2015, Len Ovens wrote:
I meant to add another line or two...
ps x |grep jack
should show something like this:
13401 ? SLl 7:19 /usr/bin/qjackctl
15503 ? SLsl 1:47 /usr/bin/jackdbus auto
17396 pts/1 S+ 0:00 grep --color=auto jack
If there is also a jackd... qjackctl is probably not controlling that one.
You may have to killall -9 jackd to get rid of it. Jack_control exit
should get rid of the jackdbus. (killall of course will work there too)
--
Len Ovens
www.ovenwerks.net
From a
terminal, you may wish to find out if it is jackd or jackdbus you
are using. But
if Gladish (and I presume Jacksink in pulse) are working, it
sounds like it does work.
9:47 a.m.
Hi,
I would like to see 3 screenshots from QjackCtl.
1. Setup... > Settings
2. Setup... > Options
3. Setup... > Misc
Use http://picpaste.com/ or whatever you like and only send the links
of the screenshots too the list.
It might be worth to repeat that QjackCtl can store jackd settings
to ~/.jackdrc, but QjackCtl does start jackd with the settings stored in
~/.config/rncbc.org/QjackCtl.conf .
Regards,
Ralf
10:10 a.m.
> jackd starts on hw:5,0 as playback and
> hw:5,1 as capture withQJackCtl and Gladish.
JFTR what kind of device is hw:5?
Why do you need to use it that way?
Not really important is what hw:0, hw:1, hw:2, hw:3, hw:4 and perhaps
hw:6 to hw:n are, anyway, please show the outputs of
$ aplay -l
$ arecord -l
$ amidi -l
it might be or might not be helpful to get an idea of the setup you're
using, but it doesn't harm.
6 May
6 May
11:36 p.m.
On 04/05/2015 10:10, Ralf Mardorf wrote:
It's a Fast Track Pro
All is explained here:
http://joegiampaoli.blogspot.fr/2011/06/m-audio-fast-track-pro-for-debian-l…
> jackd
starts on hw:5,0 as playback and
> hw:5,1 as capture withQJackCtl and Gladish.
JFTR what kind of
device is hw:5?
Why do you need to use it that way?
Not really important is what hw:0, hw:1, hw:2, hw:3, hw:4 and perhaps
hw:6 to hw:n are, anyway, please show the outputs of
$ aplay -l
$ arecord -l
$ amidi -l
it might be or might not be helpful to get an idea of the setup you're
using, but it doesn't harm.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3493
days inactive
3497
days old
linux-audio-user@lists.linuxaudio.org
11 comments
4 participants
participants (4)
-
Anton Curl -
Chris Caudle -
Len Ovens -
Ralf Mardorf