Linux-audio-user May 2012

linux-audio-user@lists.linuxaudio.org

113 participants
106 discussions

Re: [LAU] What Focusright firewire interfaces are fully working and currently available?

by Yvonnick Noel

Hi Drew, I have been using a Focusrite Firewire Pro24 for a year now. Works like a charm under Tango Studio (Jeremie Jongepier helped me to configure some audio and priorities aspect) and the FFADO driver. I note but this minor problem: I have to launch Jack twice, as it first complains about a ressource to be busy (or something). Not too much of a problem, I got used to it. Once launched, everything is OK. HTH, Yvonnick Noel

12 years, 4 months

Re: [LAU] Issue with the priority of the sound cards using rtirq

by Ralf Mardorf

> Looks good to me, except for the two ohci_hcd and the nvidia threads. I > don't see those when you start rtirq but they are there when you query > rtirq's status. Weird. Same issue after a reboot? And this hdspm device, > is that an extension card (PCI, PCIe)? If so you might want to try > another slot because having it to share the same IRQ as your GPU isn't > ideal. And maybe you could post or pastebin your complete > /etc/default/rtirq file. > > Best, > > Jeremy Jeremy, the bad is, that I don't have another PCIe x1 slot :(. > In my experience, restarting the script tries to raise the priorities > of the threads in RTIRQ_NAME_LIST, but the ones which are already > raised aren't lowered even if you leave them out of the list. > > Try rebooting the computer. > > Cheers, Pablo *reboot* The reboot doesn't improve anything :(. I'll build my own kernel within the next days. Is there anything missing to work with boot option threadirqs? Usually I use self build kernel-rt and the nv driver. Since the nv driver is dropped, I'm using the proprietary and I have given up to edit the nvidia drivers header or to fake the license, since both never worked on my machine. spinymouse@precise:~$ cat /boot/config-* | grep PREEMPT CONFIG_TREE_PREEMPT_RCU=y CONFIG_PREEMPT_RCU=y CONFIG_PREEMPT_NOTIFIERS=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_COUNT=y # CONFIG_PREEMPT_TRACER is not set spinymouse@precise:~$ cat /boot/config-* | grep CONFIG_IRQ_FORCED_THREADING CONFIG_IRQ_FORCED_THREADING=y spinymouse@precise:~$ uname -a Linux precise 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11 02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux There's another issue, I've got 4GB RAM, but only 3.8GB are accessible, resp. shown. 256MB are missing. I've got this for another install too, while a PAE 32-bit kernel has no issue with the 4GB. No framebuffer, the graphics has got it's own RAM. CONFIG_PREEMPT_COUNT ??? Thanks and regards, Ralf

12 years, 4 months

Re: [LAU] new rtirq release

by Ralf Mardorf

Perhaps it comes through the list now. > > On Sat, 2012-05-05 at 03:20 +0200, Ralf Mardorf wrote: > > > rtirq - Revision 7, resp. $ wget [snip] --2012-05-05 03:09:00-- > > > > > > DEFAULT CONFIG: > > > $ sudo /etc/init.d/rtirq status > > > > > > PID CLS RTPRIO NI PRI %CPU STAT COMMAND > > > 92 FF 90 - 130 0.0 S irq/8-rtc0 > > > 663 FF 85 - 125 0.0 S irq/20-snd_ice1 > > > 671 FF 85 - 125 0.0 S irq/21-snd_ice1 > > > 628 FF 83 - 123 0.0 S irq/18-snd_hdsp > > > 1230 FF 82 - 122 0.9 S irq/18-nvidia > > > 79 FF 80 - 120 0.0 S irq/19-ehci_hcd > > > 81 FF 80 - 120 0.4 S irq/16-ohci_hcd > > > 83 FF 79 - 119 0.0 S irq/17-ohci_hcd > > > 85 FF 78 - 118 0.0 S irq/18-ohci_hcd > > > 87 FF 78 - 118 0.0 S irq/17-ohci_hcd > > > 89 FF 77 - 117 0.0 S irq/18-ohci_hcd > > > [snip] > > > > > > WHEN snd_hdsp IS HEAD OF THE CARDS: > > > > > > $ sudo /etc/init.d/rtirq status > > > > > > PID CLS RTPRIO NI PRI %CPU STAT COMMAND > > > 92 FF 90 - 130 0.0 S irq/8-rtc0 > > > 628 FF 85 - 125 0.0 S irq/18-snd_hdsp > > > 1230 FF 82 - 122 0.9 S irq/18-nvidia > > > 663 FF 80 - 120 0.0 S irq/20-snd_ice1 > > > 671 FF 80 - 120 0.0 S irq/21-snd_ice1 > > > 85 FF 78 - 118 0.0 S irq/18-ohci_hcd > > > 89 FF 77 - 117 0.0 S irq/18-ohci_hcd > > > 79 FF 75 - 115 0.0 S irq/19-ehci_hcd > > > 81 FF 75 - 115 0.3 S irq/16-ohci_hcd > > > 83 FF 74 - 114 0.0 S irq/17-ohci_hcd > > > 87 FF 73 - 113 0.0 S irq/17-ohci_hcd > > > 91 FF 70 - 110 0.0 S irq/1-i8042 > > > [snip] > > > $ grep RTIRQ_NAME_LIST /etc/default/rtirq > > > RTIRQ_NAME_LIST="rtc snd_hdsp snd usb i8042" > > > > > > :( > > > Ralf > > > > > > PS: At least the RME has got a higher prio than the graphics. The wanted > > > order still is snd_hdsp, snd_ice1, snd_ice1 as working or older kernels. ^^ for

12 years, 4 months

Re: [LAU] new rtirq release

by Ralf Mardorf

FWIW another version of RTIRQ_NAME_LIST: spinymouse@precise:~$ sudo /etc/init.d/rtirq stop spinymouse@precise:~$ sudo /etc/init.d/rtirq start Setting IRQ priorities: start [rtc] irq=8 pid=92 prio=90: OK. Setting IRQ priorities: start [snd_hdsp] irq=18 pid=628 prio=85: OK. Setting IRQ priorities: start [snd_ice1] irq=20 pid=663 prio=80: OK. Setting IRQ priorities: start [snd_ice1] irq=21 pid=671 prio=79: OK. Setting IRQ priorities: start [ohci_hcd] irq=16 pid=81 prio=70: OK. Setting IRQ priorities: start [ohci_hcd] irq=17 pid=83 prio=69: OK. Setting IRQ priorities: start [ohci_hcd] irq=17 pid=87 prio=68: OK. Setting IRQ priorities: start [ehci_hcd] irq=19 pid=79 prio=70: OK. Setting IRQ priorities: start [i8042] irq=1 pid=91 prio=65: OK. spinymouse@precise:~$ grep RTIRQ_NAME_LIST /etc/default/rtirq RTIRQ_NAME_LIST="rtc snd_hdsp snd_ice1 snd usb i8042" spinymouse@precise:~$ sudo /etc/init.d/rtirq status PID CLS RTPRIO NI PRI %CPU STAT COMMAND 92 FF 90 - 130 0.0 S irq/8-rtc0 628 FF 85 - 125 0.0 S irq/18-snd_hdsp 1230 FF 82 - 122 0.9 S irq/18-nvidia 663 FF 80 - 120 0.0 S irq/20-snd_ice1 671 FF 79 - 119 0.0 S irq/21-snd_ice1 85 FF 78 - 118 0.0 S irq/18-ohci_hcd 89 FF 77 - 117 0.0 S irq/18-ohci_hcd 79 FF 70 - 110 0.0 S irq/19-ehci_hcd 81 FF 70 - 110 0.4 S irq/16-ohci_hcd 83 FF 69 - 109 0.0 S irq/17-ohci_hcd 87 FF 68 - 108 0.0 S irq/17-ohci_hcd 91 FF 65 - 105 0.0 S irq/1-i8042 20 FF 50 - 90 0.0 S irq/9-acpi 68 FF 50 - 90 0.0 S irq/22-ahci 285 FF 50 - 90 0.0 S irq/14-pata_ati 286 FF 50 - 90 0.0 S irq/15-pata_ati 293 FF 50 - 90 0.0 S irq/22-firewire 537 FF 50 - 90 0.0 S irq/7-parport0 979 FF 50 - 90 0.0 S irq/43-eth0 3 TS - 0 19 0.3 S ksoftirqd/0 9 TS - 0 19 0.2 S ksoftirqd/1 spinymouse@precise:~$

12 years, 4 months

Re: [LAU] new rtirq release

by Ralf Mardorf

Doesn't came through the list again. On Sat, 2012-05-05 at 02:08 +0200, Ralf Mardorf wrote: > VERSION: > $ wget --no-check-certificate > https://www.rncbc.org/svn/rtirq/trunk/rtirq.conf > https://www.rncbc.org/svn/rtirq/trunk/rtirq.sh > --2012-05-05 01:52:06-- > > ISSUE: > $ sudo /etc/init.d/rtirq [snip] > /etc/init.d/rtirq: line 129: syntax error near unexpected token `fi' > /etc/init.d/rtirq: line 129: ` fi' > > I can't see the bug near line 129.

12 years, 4 months

Re: [LAU] Open Audio Programming Tutorials

by Harry van Haaren

On Fri, May 4, 2012 at 6:07 PM, Harry van Haaren <harryhaaren(a)gmail.com>wrote: > Announcing: Open Audio Programming Tutorials! > https://github.com/harryhaaren/openAudioProgrammingTutorials And the link too this time :) -Harry

12 years, 4 months

Re: [LAU] new rtirq release (was: Re: Issue with the priority of the sound cards using rtirq)

by Ralf Mardorf

On Fri, 2012-05-04 at 15:13 +0200, Ralf Mardorf wrote: > On Fri, 2012-05-04 at 13:39 +0100, Rui Nuno Capela wrote: > [snip] > > > > > > Rui: this addition/hack in rtirq takes care of snd_hda_intel in my > > > 3.2.16-rt27 system and will presumably do the right thing for any other > > > pci soundcards: > > > > > > ---- > > > # Special for kernel-rt >= 2.6.31, where one can > > > # prioritize shared IRQs by device driver (NAME2)... > > > # first try with irq names that start with snd_ > > > PIDS=`ps -eo pid,comm | egrep -i "IRQ.${IRQ}.snd_.*" | awk '{print $1}'` > > > if [ -n "${PIDS}" ] > > > then > > > RTIRQ_TRAIL=":${IRQ}${RTIRQ_TRAIL}" > > > else > > > # try with the name reported in /proc/asound/cards > > > PIDS=`ps -eo pid,comm | egrep -i "IRQ.${IRQ}.${NAME2:0:8}" | awk '{print > > > $1}'` > > > if [ -n "${PIDS}" ] > > > then > > > RTIRQ_TRAIL=":${IRQ}${RTIRQ_TRAIL}" > > > else > > > # Backward compability for older kernel-rt < 2.6.31... > > > PIDS=`ps -eo pid,comm | egrep -i "IRQ.${IRQ}" | awk '{print $1}'` > > > if [ -n "${PIDS}" ] > > > then > > > RTIRQ_TRAIL=":${IRQ}${RTIRQ_TRAIL}" > > > fi > > > fi > > > fi > > > ---- > > > > given that, which got slightly re-hacked somehow, a new rtirq release > > has bumped in: > > http://www.rncbc.org/jack#rtirq > > > > packages: > > http://www.rncbc.org/jack/rtirq-20120504.tar.gz > > http://www.rncbc.org/jack/rtirq-20120504-28.src.rpm > > http://www.rncbc.org/jack/rtirq-20120504-28.noarch.rpm > > > > svn trunk: > > https://www.rncbc.org/svn/rtirq/trunk > > > > cheers && thanks > > Thank you Rui and Fernando :), I'll forward this to Ubuntu Studio > mailing lists. - Ralf The archive "says" this mail didn't came through the list. It's important :): Thank you Rui and Fernando :)

12 years, 4 months

Re: [LAU] Issue with the priority of the sound cards using rtirq

by Ralf Mardorf

On Thu, 2012-05-03 at 23:24 +0200, somebody off-list wrote: > Come on Ralf, do your homework. Nando create THE first linux-audio > distro. his email address will give you a hint. *chuckle* @ccrma.Stanford.EDU Haven't noticed that.

12 years, 4 months

Re: [LAU] Estimating JACK latency

by Robin Gareus

On 05/03/2012 10:43 AM, Joel Roth wrote: > On Thu, May 03, 2012 at 10:21:16AM +0200, Robin Gareus wrote: >> Capture latency in above message is a wrong. It was reported a while >> back: check jack-devel archive Dec 2010: > > Thanks > >> with jack2, there's also the difference of sync (jackd --sync .. -d alsa >> ...) vs. async mode. The latter adds 1 period of output latency. > > I'll need to read about this. --sync is listed in --help, > but not in the man page. http://www.grame.fr/~letz/jackdmp.html > I hope the difference shows up in get_jack_port_latency_range()! It does. The output latency is one period longer in async mode. >> see also: >> http://wiki.linuxaudio.org/wiki/jack_latency_tests > > And again. This is very helpful. > This wiki-page is a bit outdated (it's from before the new latency API was introduced) but item (2) under http://wiki.linuxaudio.org/wiki/jack_latency_tests#interpretation_and_analy… describes the same bug that you stumbled over. (1) was actually solved: The additional latency for USB devices comes from ALSA's USB driver implementation. Clemens explained the details in the same thread on jack-devel "Re: Differences in latency between USB and internal audio interfaces" December 9, 2010. ciao, robin

12 years, 4 months

new articles up

by Dave Phillips

Greetings, The world turns, the times change, and I get a new gig writing for the Linux Weekly News. My first article is up, but it's for subcribers only : http://lwn.net/Articles/495612/ And at the same time my article on Pd has been published by the Linux Journal, also a subscriber-only selection. Bummer, I know, but IIRC I'll be able to put the article on-line myself after a waiting period. I'll check on that and let this list know about it. Best, dp

12 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user May 2012