I've been using a 2.4.2 kernel with Andrew Morton's patches and I got
jack to work very well. However, seeing 2.6 is the latest and greatest
I'd like to switch but am having no luck thus far.
Q. If anyone has got jack to work great with a 2.6(.1) kernel could you
share with me what version of the 2.6 kernel you used and what patches
At the moment I'm trying a 2.6.1 with an mm4 patch but I'm getting no
sound with my soundblaster live.
<*> Sound card support
and, under Advanced Linux Sound Architecture --->
<*> Advanced Linux Sound Architecture
<*> Sequencer support
<*> OSS API emulation
<*> OSS Mixer API
<*> OSS PCM (digital audio) API
<*> OSS Sequencer API
rebooted and install alsa-lib-1.0.1 and alsa-utils-1.0.1 as well but I
get these errors
root@upstairs glenn # aplay /usr/kde/3.2/share/sounds/pop.wav
ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed:
No such file or directory
aplay: main:502: audio open error: No such file or directory
glenn@upstairs glenn $ alsamixer
No mixer elems found
I'm at a loss but am interested at what type of kernel others are using.
I think my next best bet is to remove alsa from the kernel and install
I have recently bought the ice1712-based DSP2000 C-PORT from Hoontech and
I'm really satisfied with it. I only have a little problem: MIDI!
The card has 1 MIDI in and 2 MIDI out, and the 2 outs are working fine.
However, I can't get anything from MIDI in :-(
Anyone has that card and can confirm this problem or I have to check my
hardware? Maybe ALSA get confused? With aconnect I see 2 devices (0 and 32)
both as inputs and as outputs...
I've tried on the staudio.com forum and they suggest to test the card under
windows, but (ehm..) I don't have it...
| Emiliano Grilli |
| emillo(a)libero.it |
| Linux user #209089 |
| http://www.emillo.net |
I've been having some wierd problems with the stock drivers in CCRMA with
the quattro, I get sound in just fine, but no sound out, when I switch it
correctly its just distorted hiss, what version of alsa are people using
to get both input and output working from their quattro, and can you get
full duplex, and if you guys don't mine sharing how you did it, I'd
I have jack installed and working now. So, now I'm trying to get
AlsaModularSynth compiled and running. Has anyone else accomplished this
in debian stable (woody)?
I installed libqt3-mt (along w/everything it depended upon), fftw-dev,
fftw2, sfftw-dev, sfftw2 and ladspa-sdk to get ladspa.h. I've tried to
edit the top of make_ams to agree with the location of the qt3 libs, bin
and include directories on my system as best as I could figure ... but
I'm not sure I got it right:
it seems to compile OK when I do:
make -f make_ams
though there are a lot of warnings about comparing signed to unsigned
and other warnings that flew by. Are these benign?
Anyway. I end up with an executable ams. When I run ./ams I get this:
./ams: error while loading shared libraries: libjack.so.0: cannot open
shared object file: No such file or directory
I have that in /usr/local/lib/libjack.so.0 so creating this link appears
box1:/usr/lib# ln -s /usr/local/lib/libjack.so.0 libjack.so.0
Is that the correct sollution?
ams: cannot connect to X server
I assume this is because X is running as me (eric) and not as root. I'll
try getting out of X and starting it as root as soon as I finish writing
this message. But, is there a way to let root connect to the X server
that's running as eric?
I was sort of ok (well, not really, but I'm giving it a try) with the
idea of running jackd and its clients as root ... but, running X as
root, too? that makes me more nervous, somehow... maybe I shouldn't be
nervous about that ... I'm not sure.
anyway. i'll give it a shot with a root X session.
I'm thinking that maybe I should patch and recompile the kernel and
recompile jack to enable capabilities so I don't have to run as root.
Do those of you running jackd as root also run your X session as root?
Thanks for listening,
PS If all of this has been covered before and my questions are annoying
you, feel free to send me to the archives. I try to follow jackit-devel,
but most of it seemed to go over my head before I actually started to
try it. So, re-reading the past couple months would probably do me some
good now that I have the real thing in front of me. -edrz
Anyone in here using a RME cardbus card in a laptop ?
I'm considering going that route and it would be nice to
be able to use that interface in Linux.
I was planning to go the powerbook way, but as I have to
develop for XP and Linux in the first place, I will probably
go for a Thinkpad (who seem to have great battery life).
Any info is appreciated,
PS: I noticed that the Multiface is listed as supported on the
ALSA site, but I don't know if that means the cardbus card too,
or only the PCI card + multiface.
On the GNU/Linux Centre stand at Sounds Expo 2004 (London, 10-12 Feb)
I'm planning to take along a laptop with some DJ software, and I was
going to take my typical DJ set music with me. But - I thought - why
not take some 'Made with Linux' music instead!
Apart from our own stuff, I'd like to take along as much music made by
the community as possible. So please send me links for your oggs and
mp3s, offlist if you like - any genre is fine.
Note: I'm moving this thread to linux-audio-user,
because I think that's where this particular discussion belongs
since the intention is to serve linux audio users.
The topic is: a site to replace Dave Phillips' venerable,
labor-intensive, hand-maintained sound applications page.
It must allow visitors to easily add, update, and correct
entries for linux audio/music apps.
Probably also user reviews & commentary on applications.
This site may or may not end up affiliated with the
emerging linuxaudio.org website(s), it's too early to say.
So it doesn't seem appropriate to keep this discussion
on the consortium_p list.
On Sat, Jan 31, 2004 at 04:34:14PM +0100, Andrea Glorioso wrote:
> Paul Winkler <pw_lists(a)slinkp.com> writes:
> > We discussed some requirements a long time ago on LAD and/or LAU,
> > I forget. I put up a quick mockup on my website and have done nothing
> > since then.
> Paul, did the server wake up?
yes, I had exceeded my disk quota. Upgraded my account and all's well.
summary and links:
Rough mock-up of a typical page:
> I'm curious to see the current state of
> affairs (so that we can direct people who visit the "applications"
> page at www.agnula.org to this site :) and of course help where we
Help at this point would consist of:
1. Refining the requirements for an app-listing site,
in terms of features and user interface.
2. Suggestions for a name for the site
3. Improved visual design. This should come after
the requirements are worked out.
4. Improved app categorization.
There were some comments suggesting that Dave's old
categories can be improved.
This can always evolve, but it would be nice to
have a good starting point.
To keep this discussion from getting confused, I will follow up with
separate messages targeting points 1 and 2.
Look! Up in the sky! It's SUPERVISOR SPARK!
(random hero from isometric.spaceninja.com)
It seems that I get quite stable performance by starting jack like this
on my P4 2.4Ghz laptop with onboard i810:
jackstart -R -v -d alsa -n 3 -p 256 -zt
But what exactly does this translate to in terms of latency? Should I
expect more? I get almost the same performance under 2.4.23 with Andrew
Morton's low-latency patched and 2.6.2 with or without the mm-patch.
peace, love & harmony
With all the new releases of audio software of late and all the shift
that's taking place among distros, I'm trying to devise a good
upgrade path for my DAW.
As it stands I'm running RedHat 9 with a patched kernel. I've
installed all the audio software I use by building from scratch --
downloading, compiling, and installing individual packages. At this
point, it has taken so much work to get my system where it is that
I'm loathe to upgrade it. Yet, with new versions of Rosegarden,
Muse, Ardour, and Jack coming out lately, I'd really like to take
advantage of those new features. OTOH, I'm worried that an upgrade
can cause problems with work that is in progress.
An ideal world for me would be a fairly straightforward binary
install process for the OS and most packages, with the capability to
install "development" versions of those packages that I'm interested
in playing with or contributing to. For example, suppose I found a
bug in Ardour that I could patch. I'd like to be able to code,
install, and test my patch without screwing up my existing system.
I'd also like to be able to upgrade individual packages and back out
the upgrade if it breaks something. It would be *really* cool to
have something like a virtual machine where I could have a test
environment and production enviornment on the same machine. Then I
could get things running in the test environment and push them to
production when I'm sure they are stable. Another issue is that I'm
thinking of moving from RedHat, but I don't know where to move to. I
tried Planet CCRMA for a while, but my dial-up made that prohibitive.
I'm about to upgrade to broadband, so I may revisit that.
So, anyway, how are you guys handling these issues? Do you install
from scratch? Do you install audio on top of an existing distro?
Which one? RedHat, Mandrake, Debian, SuSE, Gentoo, etc? Does Planet
CCRMA work well for you? What about Agnula? How do you upgrade
individual packages? How do you back out the upgrade if there's a
problem? Do you manage a separate "test" environment to keep from
bringing down your DAW?
I know there's no single answer to these questions, and eventually,
I'll just have to pick from all the equally viable choices. But I'd
also like to learn from the wisdom of folks who have more experience
with this -- find out what the pitfalls are with each choice. So I
would be greatly appreciative of any suggestions you guys might have.
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes