29 Mar
2013
29 Mar
'13
11:35 p.m.
On Fri, 29 Mar 2013 23:24:09 +0100, <jonetsu(a)teksavvy.com> wrote:
Actually, jackd (qjackctl) does not see the 1010LT
card.
lspci shows:
05:01.0 Multimedia audio controller: VIA Technologies
Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02)
Although qjackctl's message shows:
Fri Mar 29 18:12:41 2013: control device hw:0
I'm fairly sure your m-audio card is at hw:1 in this case. There's no
guarantee in which order the cards end up at each boot.
To make sure you always start your m-audio card, I usually always use the
name. Instead of hw:0 I would use hw:M66. You can get the name from
checking the file /proc/asound/cards as I do below
$ cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe300000 irq 16
1 [M66 ]: ICE1712 - M Audio Delta 66
M Audio Delta 66 at 0xd040, irq 21
2 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfe080000 irq 24
Fri Mar 29 18:12:41 2013: Acquired audio card Audio0
Fri Mar 29 18:12:41 2013: creating alsa driver
... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
Fri Mar 29 18:12:41 2013: ALSA: final selected sample format for
capture: 32bit integer little-endian
Fri Mar 29 18:12:41 2013: ALSA: use 2 periods for capture
Fri Mar 29 18:12:41 2013: ALSA: final selected sample format for
playback: 32bit integer little-endian
Fri Mar 29 18:12:41 2013: ALSA: use 2 periods for playback
Fri Mar 29 18:12:41 2013: ERROR: Cannot use real-time
scheduling (RR/10)(1: Operation not permitted)
This means you don't have realtime privilege. You need to do two things.
First, make sure you have a file called /etc/security/limits.d/audio.conf
with the contents (if you didn't enable realtime privilege during install,
the file will be named /etc/security/limits.d/audio.conf,disabled):
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd
@audio - rtprio 95
@audio - memlock unlimited
#@audio - nice -19
Second, add yourself to audio group. You can do this with the command:
sudo usermod -a -G audio $USER
Then, reboot for changes to take effect.
Fri Mar 29 18:12:41 2013: ERROR: AcquireSelfRealTime
error
Cannot lock down 82274202 byte memory area (Cannot allocate
memory)
And qjackctl ony has two capture inputs, instead of the ones from
the 1010LT card. The two errors in there made me look at a low
latency kernel. Now, I'm not sure if it would solve the problem.
So, these errors have nothing to do with the kernel. A realtime kernel
does not provide realtime privilege.
You accidentally sent this mail directly to me ;)
30 Mar
30 Mar
2:05 a.m.
Le 29-03-2013 18:35, Kaj Ailomaa a écrit :
I'm fairly sure your m-audio card is at hw:1 in
this case. There's no
guarantee in which order the cards end up at each boot.
To make sure you always start your m-audio card, I usually always use
the name.
This means you don't have realtime privilege. You
need to do two
things.
First, make sure you have a file called
/etc/security/limits.d/audio.conf with the contents (if you didn't
enable realtime privilege during install, the file will be named
/etc/security/limits.d/audio.conf,disabled):
The file was already as below. So I ran the dpkg-reconfigure command
in there. And I added my user name to the group file, and rebooted. Now
qjackctl shows all 1010LT ins and outs, so things are moving on. There
was no need to specify the card's name which is good in a sense, because
I do not know where to specify the name. qjackctl does not seemingly
take a card name as a parameter.
You accidentally sent this mail directly to me ;)
Sorry, I'm using the web interface mail thing from the ISP who did some
modifications to their email service and it's not that good - I should
get back to using sylpheed but haven't done it yet.
Well, thanks for the setup tips. It now works. So, if I notice
glitches and many xruns then I will know that I should use a low latency
kernel ? The machine is quad core with 16G RAM with a ASUS mobo that
has an new-improved-updated sata interface for the drives.
2:14 a.m.
On Sat, 30 Mar 2013 02:05:18 +0100, <jonetsu(a)teksavvy.com> wrote:
Le 29-03-2013 18:35, Kaj Ailomaa a écrit :
If the file already existed, there was no need to run the command.
I'm fairly sure your m-audio card is at hw:1
in this case. There's no
guarantee in which order the cards end up at each boot.
To make sure you always start your m-audio card, I usually always use
the name.
This means you don't have realtime privilege.
You need to do two things.
First, make sure you have a file called
/etc/security/limits.d/audio.conf with the contents (if you didn't
enable realtime privilege during install, the file will be named
/etc/security/limits.d/audio.conf,disabled):
The file was already as below. So I ran the dpkg-reconfigure command in there. And I added my user name to the group file,
and rebooted. Now
qjackctl shows all 1010LT ins and outs, so things are moving on. There
this is simply because after you rebooted, your LT1010 became hw:0 instead
of hw:1 as it was before.
As I said, the order in which the cards end up may be different at each
boot. You can check the order, and the names doing:
cat /proc/asound/cards
was no need to specify the card's name which is
good in a sense, because
I do not know where to specify the name. qjackctl does not seemingly
take a card name as a parameter.
You always need to specify which card you will run jack with. No matter
how you start jack, with or without qjackctl.
In qjackctl, you do this from Setup -> Interface. "default" is the same as
hw:0. I would change this to your card name, writing the name manually.
Again, the name can be gotten from doing: cat /proc/asound/cards
If my memory serves me correctly, your device is named simply LT1010, so,
in qjackctl, instead of "default", or "hw:0", you would write
"hw:LT1010".
2:21 a.m.
Le 29-03-2013 21:14, Kaj Ailomaa a écrit :
this is simply because after you rebooted, your LT1010
became hw:0
instead of hw:1 as it was before.
Indeed. The 1010LT is now card # 0. I would not have guessed that
adding my user name to the group file would do such a change.
You always need to specify which card you will run
jack with.
Well, hopefully the system will remain as is, stable as it is. So as
long as the 1010LT is # 0 it should be fine, and I'll save notes from
this thread in my audio notes, just in case an update to packages or
something changes the way the system behaves.
2:38 a.m.
New subject: Realtime Privilege, WAS:Re: OT: what is happening with RT kernel development?
On Fri, Mar 29, 2013 at 9:21 PM, <jonetsu(a)teksavvy.com> wrote:
Le 29-03-2013 21:14, Kaj Ailomaa a écrit :
this is simply because after you rebooted, your LT1010 became hw:0
it had nothing to do with the group thing.
the order of device discovery is not pinned down (by default). it could
change at every boot. or it might never change again.
you can specify which card ends up as zero and which one ends up as one,
but its much easier and better to simply use the *name*.
--p
instead of hw:1 as it was before.
Indeed. The 1010LT is now card # 0. I would not have guessed that adding
my user name to the group file would do such a change.
2:53 a.m.
On Sat, 30 Mar 2013 02:21:22 +0100, <jonetsu(a)teksavvy.com> wrote:
It is purely by chance that it is hw:0 now, and it will be each time you
reboot.
Le 29-03-2013 21:14, Kaj Ailomaa a écrit :
It didn't. Adding yourself to audio group let's you get realtime privilege
as it is given to the audio group.
You can see this in the file /etc/security/limits.d/audio.conf. This was
the only reason to become member of audio group.
this is simply because after you rebooted, your
LT1010 became hw:0
instead of hw:1 as it was before.
Indeed. The 1010LT is now card # 0. I would not have guessed that
adding my user name to the group file would do such a change.
You always
need to specify which card you will run jack with.
Well, hopefully the system will remain as is, stable as it is. So as
long as the 1010LT is # 0 it should be fine, and I'll save notes from
this thread in my audio notes, just in case an update to packages or
something changes the way the system behaves.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:59 p.m.
Le 29-03-2013 21:14, Kaj Ailomaa a écrit :
Again, the name can be gotten from doing: cat
/proc/asound/cards
If my memory serves me correctly, your device is named
simply LT1010,
so, in qjackctl, instead of "default", or "hw:0", you would write
"hw:LT1010".
I entered 'M1010LT' by error, which was from :
% cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7d10000 irq 53
1 [M1010LT ]: ICE1712 - M Audio Delta 1010LT
M Audio Delta 1010LT at 0xd040, irq 18
Forgot to prefix it with 'hw:'.
Now qjackctl does not fully start and has to be kill -9 to terminate.
I've looked in /etc/ but there's no jackd or qjackctl directories.
Where is this config stored so I can modify it to enable jack to
function normally ? - thanks.
10:09 p.m.
On Sat, 30 Mar 2013 21:59:03 +0100, <jonetsu(a)teksavvy.com> wrote:
Le 29-03-2013 21:14, Kaj Ailomaa a écrit :
Did you change it to hw:M1010LT ?
Again, the name can be gotten from doing: cat
/proc/asound/cards
If my memory serves me correctly, your device is
named simply LT1010,
so, in qjackctl, instead of "default", or "hw:0", you would write
"hw:LT1010".
I entered 'M1010LT' by error, which was from :
% cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xf7d10000 irq 53
1 [M1010LT ]: ICE1712 - M Audio Delta 1010LT
M Audio Delta 1010LT at 0xd040, irq 18
Forgot to prefix it with 'hw:'.
Now qjackctl does not fully start and has to be kill -9 to terminate.
Does not start, or crashes when you try to stop it (the latter is a bug in
jackd 1.9.8)?
I've looked in /etc/ but there's no jackd or
qjackctl directories.
/etc is for system wide configurations. When you set any kind of configs
as a user, they will be saved in your home directory.
The config file for qjackctl is at: ~/.config/rncbc.org/QjackCtl.conf
Where is this config stored so I can modify it to
enable jack to
function normally ? - thanks.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
10:16 p.m.
Le 30-03-2013 17:09, Kaj Ailomaa a écrit :
qjackctl draws the window, but with nothing inside. I presume it tries
to figure out what M1010LT is.
This is, I have changed the QjackCtl.conf so now it is:
Interface=hw:M1010LT
But same behaviour. Window frame, but nothing inside. KDE has to
terminate the app, eg. qjackctl not responding. Is it possible to reset
the whole thing ?
> Forgot to prefix it with 'hw:'.
Did you change it to hw:M1010LT ?
No, only to 'M1010LT'
Now qjackctl does not fully start and has to be kill -9 to
terminate.
Does not start, or crashes when you try to stop it (the latter is a
bug in jackd 1.9.8)?
10:18 p.m.
On Sat, 30 Mar 2013 22:16:03 +0100, <jonetsu(a)teksavvy.com> wrote:
Le 30-03-2013 17:09, Kaj Ailomaa a écrit :
qjackctl draws the window, but with nothing inside. I presume it tries
to figure out what M1010LT is.
This is, I have changed the QjackCtl.conf so now it is:
Interface=hw:M1010LT
Looks correct to me
> Forgot to prefix it with 'hw:'.
Did you change it to hw:M1010LT ?
No, only to 'M1010LT'
Now qjackctl does not fully start and has to be kill -9 to terminate.
Does not start, or crashes when you try to stop it (the latter is a
bug in jackd 1.9.8)?
But same behaviour. Window frame, but nothing inside. KDE has to
terminate the app, eg. qjackctl not responding. Is it possible to reset
the whole thing ?
To make things easier, if you suspect a problem with the config file, just
delete it. Next time you start qjackctl, a new one with default settings
will appear.
10:24 p.m.
Le 30-03-2013 17:18, Kaj Ailomaa a écrit :
To make things easier, if you suspect a problem with
the config file,
just delete it. Next time you start qjackctl, a new one with default
settings will appear.
Does not work. Deleted the config file and none is recreated.
qjackctl is jammed (no pun !) at drawing the window. Drats. And it was
so close have a working setup. qjackctl doe snto seem to have any debug
option to see what's going on, and it does not log to syslog. So no
idea what is wrong with this.
10:27 p.m.
On Sat, 30 Mar 2013 22:24:04 +0100, <jonetsu(a)teksavvy.com> wrote:
Le 30-03-2013 17:18, Kaj Ailomaa a écrit :
There's also ~/.jackdrc, all though, I doubt it has anything to do with
draing the qjackctl windoe.
Did you ever try restarting your session? It sounds to me there's
something else going on, rather than corrupted config files.
To make things easier, if you suspect a problem
with the config file,
just delete it. Next time you start qjackctl, a new one with default
settings will appear.
Does not work. Deleted the config file and none is recreated. qjackctl
is jammed (no pun !) at drawing the window. Drats. And it was so close
have a working setup. qjackctl doe snto seem to have any debug option
to see what's going on, and it does not log to syslog. So no idea what
is wrong with this.
10:36 p.m.
Le 30-03-2013 17:27, Kaj Ailomaa a écrit :
On Sat, 30 Mar 2013 22:24:04 +0100,
<jonetsu(a)teksavvy.com> wrote:
I removed that file too but it did not help.
Le 30-03-2013 17:18, Kaj Ailomaa a écrit :
There's also ~/.jackdrc, all though, I doubt it has anything to do
with draing the qjackctl windoe. To make things easier, if you suspect a problem
with the config
file,
just delete it. Next time you start qjackctl, a new one with
default
settings will appear.
Does not work. Deleted the config file and none is recreated.
qjackctl is jammed (no pun !) at drawing the window. Drats. And it
was so close have a working setup. qjackctl doe snto seem to have
any debug option to see what's going on, and it does not log to
syslog. So no idea what is wrong with this.
Did you ever try restarting your session? It sounds to
me there's
something else going on, rather than corrupted config files.
I rebooted and now it works OK. I've entered the name correctly this
time, and restarted qjackctl w/o any problem. I guess some temp file
was saved somewhere that a reboot has deleted.
Thanks for the info and help - much appreciated. Now instead of having
qjackctl jammed at start up, *I* can jam :-)
10:28 p.m.
Le 30-03-2013 17:24, jonetsu(a)teksavvy.com a écrit :
Does not work. Deleted the config file and none is
recreated.
qjackctl is jammed (no pun !) at drawing the window. Drats. And it
was so close have a working setup. qjackctl doe snto seem to have
any
debug option to see what's going on, and it does not log to syslog.
So no idea what is wrong with this.
I've also removed both qjackctl and jackd and re-installed them, but
the behaviour of qjackctl is still the same: will not start fully.
Arrrgh.
2:14 a.m.
New subject: Realtime Privilege, WAS:Re: OT: what is happening with RT kernel development?
On Fri, Mar 29, 2013 at 9:05 PM, <jonetsu(a)teksavvy.com> wrote:
Le 29-03-2013 18:35, Kaj Ailomaa a écrit :
I'm fairly sure your m-audio card is at hw:1 in this case. There's no
First, make sure you have a file called
> /etc/security/limits.d/audio.**conf with the contents (if you didn't
> enable realtime privilege during install, the file will be named
> /etc/security/limits.d/audio.**conf,disabled):
The file was already as below. So I ran the dpkg-reconfigure command in
there. And I added my user name to the group file, and rebooted. Now
qjackctl shows all 1010LT ins and outs, so things are moving on. There was
no need to specify the card's name which is good in a sense, because I do
not know where to specify the name. qjackctl does not seemingly take a
card name as a parameter.
just type hw:NAME into the device selector combo in the setup dialog of
qjackctl.
guarantee in which order the cards end up at each
boot.
To make sure you always start your m-audio card, I usually always use
the name.
This means you don't have realtime privilege. You need to do two things.
4331
days inactive
4332
days old
linux-audio-user@lists.linuxaudio.org
14 comments
3 participants
participants (3)
-
jonetsu＠teksavvy.com -
Kaj Ailomaa -
Paul Davis