I have moved my soundcard to a new computer, and wanted to have it on
a high priority interrupt. The mobo is ASUS P4P800.
lspci tells me something like "pin A routed to IRQ 23" (or similar)
I do not know anything about interrupt priority with these new irq's.
Pointers, informations or help highly appreciated.
Robert Epprecht
hi,
i don't know much about professional audio-applications for linux but i want to try using VST-Instruments with linux-applications. which applications can i tra/use? is it possible to get low or almost no tatency with the new kernel 2.6?
thany
mike
______________________________________________________________________________
Nachrichten, Musik und Spiele schnell und einfach per Quickstart im
WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110
Guess what?
...*chirp*...*chirp*...
Right, well... Specimen is midi controlled audio sampler for GNU/Linux
systems, and this is a new release of it. I'm justifying this on the
inclusion of velocity sensitivity, cuts, and proof-of-concept (read:
crappy) pitch scaling.
You can download the newest tarball, check out the new screenshot, and
listen to the _fearsome_might_ of Specimen at www.gazuga.net.
[pb]
I've read some of these discussions and cannot offer much, except that I
have been trying to use the SATA driver in "enhanced" mode with an ASUS
board with Intel ICH5R chipset. This is impossible to do for very long.
Eventually accessing the hard drives causes the machine to lock up.
If the mouse is moved while a process that has extensive disk activity
is running, erratic behaviour results, such as pasting of text into
xterms. I've also observed that it is impossible to run e2fsck on a large
drive without it halting. Hitting keys, especially Ctl-Alt-Del, will
restart e2fsck, this must be done repeatedly (dozens of times for checking
3 PATA's and one SATA).
What does this have to do with jack?
I come down on the side of a very serious bug in the kernel, scheduler,
something of that nature --- not jack or the SATA driver. I believe that
other demanding drivers must be also having problems.
Now I am running a P4/800 in APIC mode for 2.6.1 with low-latency selected.
I have not tried jack yet (not that far along). I'm also running Slackware
9.1 (uses devfs).
I think we'll all be very happy with this new kernel once this gets worked
out. It has a lot of good features. I like the build process better, too,
and gconfig.
Dave.
I'm in the process of trying to rebuild my audio box, after thoroughly
mangling my previous setup. I started with a fresh install of Slackware 9.1.
I then built the following software:
Vanilla 2.6.1 kernel (with 2-line capabilities patch)
ALSA-lib 1.0.0rc1
Jack 0.94.0 (configured with --enable-capabilities)
libcap 1.10
Hydrogen 0.8.1
When I tried to start Hydrogen, however, the application locked up when
it connected to Jack. Any other program interacting with Hydrogen (e.g.
"killall -9 hydrogen", "ps -A", "top") also locked up. Jack continued
running smoothly, as did the rest of the environment.
This problem does not happen when I run as root, nor does it happen when
I run Jack without realtime scheduling. It happens only when I use jackstart
as a normal user.
I would like to test some of my other favorite Jack applications, but
sourceforge.net's CVS servers seem to be down right now, and some of the
library dependencies don't seem available by any other means. The only other
Jack client I'm aware of on my machine is jackrec. I successfully used
jackrec to capture 5 seconds of audio, with no lockup.
Originally, the output of dmesg contained "Debug: sleeping function
called from invalid context at include/asm/semaphore.h:119" statements each
time there was a lockup. A visit with Google turned up this message:
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg10203.html
The call trace from my dmesg output was essentially identical, and so I
applied the patch contained in the message. This silenced the complaints,
but the lockups persisted.
I was able to get a fresh CVS copy of Hydrogen (right before CVS went
down), but the result is the same as with 0.8.1. I was unable to build
0.8.0, due to backward-compatibility problems with Jack.
Originally, I had Jack configured with --enable-optimize and
--enable-posix-shm, but I have since rebuilt (make uninstall, make clean,
./configure, make, make install) with only --enable-capabilities. No effect.
If I use strace to launch Hydrogen, I get output which consistently
terminates with the following lines:
sched_get_priority_max(0x1) = 99
sched_get_priority_min(0x1) = 1
mlockall(MCL_CURRENT|MCL_FUTURE
If I use strace to launch jackrec, the output continues past the mlockall
call:
sched_get_priority_max(0x1) = 99
sched_get_priority_min(0x1) = 1
mlockall(MCL_CURRENT|MCL_FUTURE) = 0
rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0
write(7, "\240\360\n@\0\0\0\0 M\5\10\31o\7@P\260\4\10\0\0\0\200\0"..., 148) =
148
rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0
(Plus another screen or so of additional output.)
If there's any other info I should provide, please let me know. I'm out
of my league here. I don't know whether the issue is the kernel, ALSA, Jack,
libcap, or Hydrogen. Can anyone point me in the right direction?
|)
|)enji
Thanks to all who replied to my earlier posting
about available apps for linux audio in comparison
to Window$/Mac apps. Now that I know there is an
abundant supply of apps... What would be your
recommendations to help a Linux newbie make the
transition and begin using a Linux DAW? In other
words how do you make music using your Linux DAW?
Next, sound card recommendations? A friend may
donate a Delta66 with Omni I/O breakout box to me.
I may also purchase a SB Live! (EMU10K) card for
using soundfonts. What cards work well? Good
driver support. Low latency. Good D/A chips.
Low noice. Etc.
Finally, is there a preference to Intel or AMD
CPUs and chipsets? Does one seem to work better
than another? VIA chipset? nVidia? Intel?
Sorry for asking what probably seems mundane to
you. But, I'm new and want to get educated before
making the switch. But I am dedicated to making
the switch from Window$ to Linux.
--
===========================================================
Richard K. Ingalls
Director of Information Technology
Glenwood R-8 School District
West Plains, MO
email..ringalls(a)glenwood.k12.mo.us
web....glenwood.k12.mo.us
ph.....417.256.4849
fax....417.257.2567
"Glenwood R-8: home of the mustangs!"
===========================================================
Hi,
1) I'm using alsa 1.0.1 with the latest version of jackd on a via kt400
mobo (VT8377) and a VT8233 audio controller. I have the low-latency/premp
kernel patches as well as the capabilities patch applied to a 2.4.22
kernel. I get xruns like crazy that average around 0.09 msecs when running
jackd in duplex mode. These disapear when running in either capture or
playback mode. I had seen that there may be some issues with the via82xx
chipset and jackd on the alsa list, but no solutions or description of
what the actual problems were. Am I stuck in a duplex-free zone or is
there a way to work around this? Will this affect my ability to use ardour
as multitracking device using the mic/line-in, or will it only cripple my
ability to use other programs as jack slaves?
2) Even with the capabilities patch, I get the following error when
running jack as a normal user:
JACK: unable to mlock() port buffers: Operation not permitted
cannot set thread to real-time priority (FIFO/20) (1: Operation not
permitted)
cannot use real-time scheduling (FIFO/10) (1: Operation not permitted)
Any ideas?
Thanks!
Keith
Delta 66 is good (and well supported). I use AMD and VIA with few problems. Of course, it can take a while to get everything the way you want it. Tuning the system is probably the most time consuming part.
Jan
-----Original Message-----
From: "linux-audio-user-bounces(a)music.columbia.edu" <linux-audio-user-bounces(a)music.columbia.edu> on behalf of "Richard K. Ingalls" <ringalls(a)glenwood.k12.mo.us>
Sent: Wed, 21 Jan 2004 12:25:43 -0600
To: "A list for linux audio users" <linux-audio-user(a)music.columbia.edu>
Subject: [linux-audio-user] Recommendations for the newbie?
Thanks to all who replied to my earlier posting
about available apps for linux audio in comparison
to Window$/Mac apps. Now that I know there is an
abundant supply of apps... What would be your
recommendations to help a Linux newbie make the
transition and begin using a Linux DAW? In other
words how do you make music using your Linux DAW?
Next, sound card recommendations? A friend may
donate a Delta66 with Omni I/O breakout box to me.
I may also purchase a SB Live! (EMU10K) card for
using soundfonts. What cards work well? Good
driver support. Low latency. Good D/A chips.
Low noice. Etc.
Finally, is there a preference to Intel or AMD
CPUs and chipsets? Does one seem to work better
than another? VIA chipset? nVidia? Intel?
Sorry for asking what probably seems mundane to
you. But, I'm new and want to get educated before
making the switch. But I am dedicated to making
the switch from Window$ to Linux.
--
===========================================================
Richard K. Ingalls
Director of Information Technology
Glenwood R-8 School District
West Plains, MO
email..ringalls(a)glenwood.k12.mo.us
web....glenwood.k12.mo.us
ph.....417.256.4849
fax....417.257.2567
"Glenwood R-8: home of the mustangs!"
===========================================================