Re: problems using JACK
On Monday 19 July 2004 10:54 am, Raphaël Berbain wrote: > rich lott <[EMAIL PROTECTED]> writes: > > then some comments seemed to hint otherwise. It certainly doesn't seem to > > work that way. > > http://alsa.opensrc.org/index.php?page=AlsaSharing basically says that > ALSA allows sound mixing, with more or less setup involved depending It does look encouraging, doesn't it? Until you get to the bit about how to set it up. Gah. But it might just work. Come to think of it, I used to have to shut down JACK before running things like mplayer, but I can mostly just leave JACK running and do whatever. Except run arts and things that depend on arts (which is nothing I can't live without having sound, really.) I have no idea how the guts work, but something somewhere is more conveniently interoperable than it used to be, though things becoming ALSA-aware, or through some other magic. -- Michael McIntyre Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/
Re: problems using JACK
rich lott <[EMAIL PROTECTED]> writes: > related question, ALSA : can 2+ apps play through it at once? I understand the > answer is no, that's what you need jack/arts/esd for, but then some comments > seemed to hint otherwise. It certainly doesn't seem to work that way. http://alsa.opensrc.org/index.php?page=AlsaSharing basically says that ALSA allows sound mixing, with more or less setup involved depending on wether h/w supports mixing, apps use the ALSA or OSS api, a sound server is involved... Disclaimer: It's been a long time since I toyed with sound, which means I didn't try any sound-related stunts recently. One can hope the link is accurate: The page's history says it was created on July 16th. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems using JACK
Thanks for responses. I had seen the Jack page, which as you say, was easy to find. But I'd been having problems with clients connecting to it when not run as root, rather than difficulties with realtime. Bizarely these seem to have vanished and it now works...for the mo! related question, ALSA : can 2+ apps play through it at once? I understand the answer is no, that's what you need jack/arts/esd for, but then some comments seemed to hint otherwise. It certainly doesn't seem to work that way. also, please excuse me mentioning audacity: I've NOT got it working with jack, I was listing it simply to get across the type of app I wanted to run. I'm not new to linux but new to sound on linux, and am used to the joys of cool edit pro and fruityloops. audacity was all I found that worked when I was previously using mdk9. I'm now on debian, so will probably revisit the others (ardour etc). Again, thanks for the comments, they've all helped me understand stuff a bit more! rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems using JACK
On Fri, 16 Jul 2004 18:33:10 +0100 rich lott <[EMAIL PROTECTED]> wrote: > > First, is it right that you pretty much have to run jack (and therefore > all audio apps) as root? I can't get it started as any other user - it > starts but the clients can't find it. http://lists.debian.org/debian-user/2004/05/msg03172.html (see the second and third parts of my response in particular) > Second, is there anyway to get Arts to use Jack? (and then, any way to > get ESD to use it?) Not that I'm aware of at this time. It's important to note, however, that jackd was not intended to be a general, all-purpose audio server. > Call me radical, but I thought it would be really good if all my apps > which make sounds could...well, make sounds, without interfering > with/blocking eachother. I like jack because I play with hydrogen and > audacity and so I appreciate the low latency. When did audacity become a jackd client? Anyway, jackd running should not prevent esd from sending sound to the soundcard via ALSA. If it is, there's an issue to be resolved. However, if you are running jackd because you do pro-audio stuff, you want to get rid of esd and aRts if you can, because they increase latencies. > There doesn't seem to be much on the net about jack, perhaps it's too > young yet? There's lots about JACK on the net; you simply have to poke around. Google is your friend. -c -- Chris Metzler [EMAIL PROTECTED] (remove "snip-me." to email) "As a child I understood how to give; I have forgotten this grace since I have become civilized." - Chief Luther Standing Bear pgp1wHIKC31DT.pgp Description: PGP signature
Re: problems using JACK
On Friday 16 July 2004 01:33 pm, rich lott wrote: > First, is it right that you pretty much have to run jack (and therefore all > audio apps) as root? I can't get it started as any other user - it starts > but the clients can't find it. No, you don't *have* to. If you don't run it in realtime mode, you can run everything out of userland. That will impair your performance. You have to decide what's most important to you. I run everything in userland, and live with what I get, because I can't be bothered to become a Linux audio expert. To get more, I'd have to do far more research than it's worth to me. > Second, is there anyway to get Arts to use Jack? (and then, any way to get > ESD to use it?) I don't think so, no. > Call me radical, but I thought it would be really good if all my apps which > make sounds could...well, make sounds, without interfering with/blocking > eachother. It would be nice if everything supported JACK. Perhaps that will be the case someday. > I like jack because I play with hydrogen and audacity and so I > appreciate the low latency. Do you actually have that working somehow? Audacity hasn't worked with JACK in ages, and it isn't working here now. I've had to start using sweep and rezound for audio editing, since I need JACK running. > There doesn't seem to be much on the net about jack, perhaps it's too young > yet? Exactly. If there are any easy, simple answers out there, google is doing a good job of keeping them from me, as well. There's amazing work being done, but you really still have to be a Linux audio insider to understand most of the discussion. Latency scheduling capabilities blmphf realtime blrfl xruns blah, wake me up when stupid people can use it too. :) -- Michael McIntyre Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problems using JACK
On July 16, 2004 10:33, rich lott wrote: > First, is it right that you pretty much have to run jack (and therefore all > audio apps) as root? I can't get it started as any other user - it starts > but the clients can't find it. > > Second, is there anyway to get Arts to use Jack? (and then, any way to get > ESD to use it?) > > Call me radical, but I thought it would be really good if all my apps which > make sounds could...well, make sounds, without interfering with/blocking > eachother. I like jack because I play with hydrogen and audacity and so I > appreciate the low latency. > > There doesn't seem to be much on the net about jack, perhaps it's too young > yet? > For non-root applications to connect to jackd you will have to patch your 2.4 kernel (adds some security risk). The file "include/linux/capability.h" requires a small change. If you are using a 2.6 kernel you can use the new Linux Realtime Security module. This is all explained in the jack faq http://jackit.sourceforge.net/docs/faq.php -- not very hard to find RJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problems using JACK
First, is it right that you pretty much have to run jack (and therefore all audio apps) as root? I can't get it started as any other user - it starts but the clients can't find it. Second, is there anyway to get Arts to use Jack? (and then, any way to get ESD to use it?) Call me radical, but I thought it would be really good if all my apps which make sounds could...well, make sounds, without interfering with/blocking eachother. I like jack because I play with hydrogen and audacity and so I appreciate the low latency. There doesn't seem to be much on the net about jack, perhaps it's too young yet? thanks, rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
