Yes, XMMS is working fine. Actually, I'm not getting any sound from Alsaplayer, though XMMS is supposedly using the XMMS-JACK driver. The output I pasted is from qjackctl with verbose turned on, though when I run jackd I get the same output. I've tried messing around with various Jack settings, but nothing seems to make any difference. What's puzzling is that it appears to be working until it says "Could not connect to JACK server as client". Could it have something to do with Alsa not being configured properly?
I'm sure this is typical of the Linux world, but there seems to be a lot of obsolete information that comes up on Google searches. It would be nice if things came down after a few years... for instance, the mini Alsa HOWTO posted on the alsa wiki site alsa.opensrc.org is from 1999... I think probably a lot has changed in the last 7 years! I would like to contribute some time to keeping these things up to date, but I don't feel that I have the expertise just yet. Certainly once I can reimage a low-latency machine with jack & alsa working right away I'm going to be paying back for all the help I've received over the years!
On 2/5/06, John Harrison john.harrison@wichita.edu wrote:
Is XMMS with the JACK output driver working for you? That's my standard JACK test...but...if qjackctl isn't working...I doubt the problem is with Pd. Sounds more like a problem with jackd. When messing with JACK initially, I always find it easiest to run jackd or jackstart from qjackctl. Easier to debug what is going on.
Is the output below from jackd or qjackctl? Whatever it is...it isn't happy. That's the place to start.
-John
david golightly wrote:
Hello everyone!
Sorry to be a drag here, but I've been scratching my head on this for several days now. I'm trying to coordinate pd, alsa, and jack on ubuntu (actually demudi multimedia kernel 2.6.12 in ubuntu) and I've got a number of symptoms here, but I've not been able to diagnose what's going on:
- not getting any sound from pd; pd doesn't recognize any devices
- pd's Media menu lists 'OSS', 'ALSA', and 'Jack'
- compiled pd 0.39-2 with --enable-alsa --enable-jack
- alsa seems to be installed fine, alsamixer works, cds play in alsaplayer
- qjackctl will not connect to jack server as client - but jack appears to
start fine (?):
13:44:26.950 JACK was started with PID=6255 (0x186f). jackd 0.100.9 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 48000 creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 1024 frames, buffer = 2 periods Note: audio device hw:0 doesn't support a 32bit sample format so JACK will try a 24bit format instead Note: audio device hw:0 doesn't support a 24bit sample format so JACK will try a 16bit format instead nperiods = 2 for capture nperiods = 2 for playback 13:44:29.002 Could not connect to JACK server as client. 13:44:31.629 JACK is stopping...
So I was wondering, anyone have any pointers here? I'm stumped.
Thanks,
David
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
i never played with JACK, but im using ubuntu too.
have you tried to search/ask on these
http://www.ubuntuforums.org/ https://wiki.ubuntu.com/ #ubuntu on irc.freenode.net
terveisin -andre
On Sun, 2006-02-05 at 23:19 -0800, david golightly wrote:
Yes, XMMS is working fine. Actually, I'm not getting any sound from Alsaplayer, though XMMS is supposedly using the XMMS-JACK driver. The output I pasted is from qjackctl with verbose turned on, though when I run jackd I get the same output. I've tried messing around with various Jack settings, but nothing seems to make any difference. What's puzzling is that it appears to be working until it says "Could not connect to JACK server as client". Could it have something to do with Alsa not being configured properly?
I'm sure this is typical of the Linux world, but there seems to be a lot of obsolete information that comes up on Google searches. It would be nice if things came down after a few years... for instance, the mini Alsa HOWTO posted on the alsa wiki site alsa.opensrc.org is from 1999... I think probably a lot has changed in the last 7 years! I would like to contribute some time to keeping these things up to date, but I don't feel that I have the expertise just yet. Certainly once I can reimage a low-latency machine with jack & alsa working right away I'm going to be paying back for all the help I've received over the years!
On 2/5/06, John Harrison john.harrison@wichita.edu wrote: Is XMMS with the JACK output driver working for you? That's my standard JACK test...but...if qjackctl isn't working...I doubt the problem is with Pd. Sounds more like a problem with jackd. When messing with JACK initially, I always find it easiest to run jackd or jackstart from qjackctl. Easier to debug what is going on.
Is the output below from jackd or qjackctl? Whatever it is...it isn't happy. That's the place to start. -John david golightly wrote: > Hello everyone! > > Sorry to be a drag here, but I've been scratching my head on > this for several days now. I'm trying to coordinate pd, > alsa, and jack on ubuntu (actually demudi multimedia kernel > 2.6.12 in ubuntu) and I've got a number of symptoms here, > but I've not been able to diagnose what's going on: > > - not getting any sound from pd; pd doesn't recognize any > devices > - pd's Media menu lists 'OSS', 'ALSA', and 'Jack' > - compiled pd 0.39-2 with --enable-alsa --enable-jack > - alsa seems to be installed fine, alsamixer works, cds play > in alsaplayer > - qjackctl will not connect to jack server as client - but > jack appears to start fine (?): > > 13:44:26.950 JACK was started with PID=6255 (0x186f). > jackd 0.100.9 > Copyright 2001-2005 Paul Davis and others. > jackd comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute > it > under certain conditions; see the file COPYING for details > JACK compiled with System V SHM support. > loading driver .. > apparent rate = 48000 > creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon| > swmeter|-|32bit > control device hw:0 > configuring for 48000Hz, period = 1024 frames, buffer = 2 > periods > Note: audio device hw:0 doesn't support a 32bit sample > format so JACK will try a 24bit format instead > Note: audio device hw:0 doesn't support a 24bit sample > format so JACK will try a 16bit format instead > nperiods = 2 for capture > nperiods = 2 for playback > 13:44:29.002 Could not connect to JACK server as client. > 13:44:31.629 JACK is stopping... > > So I was wondering, anyone have any pointers here? I'm > stumped. > > Thanks, > > David > > > ____________________________________________________________ > > _______________________________________________ > PD-list@iem.at > mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
John/Andre -
Thanks for the help so far. Here's the steps I'm doing exactly:
~$ qjackctl &
(qjackctl starts)
(display readout changes from faded "Stopped" to lit "Starting...", message box displays previously posted activity, then readout changes back to "Stopped".)
running: ~$ jackd -v -d alsa
gets the exact same output as the message box in qjackctl
in XMMS I'm using the libjackout.so driver, though I suspect that XMMS is reverting to a non-JACK driver without saying so - in Options > Preferences it still says it's using the JACK driver. XMMS still makes sound whether jackd or qjackctl is "running" (which it doesn't) or not.
I'm suspecting that this problem may have something to do with permissions? As in, I installed something as root that I should have installed as a normal user? In any event this seems to be more of an ALSA/JACK problem than a PD problem (or an ubuntu problem for that matter). Maybe I'll take this question over to their mailing lists to see what they make of it.
Thanks again, David
On 2/6/06, Andre Schmidt huolong@arcor.de wrote:
i never played with JACK, but im using ubuntu too.
have you tried to search/ask on these
http://www.ubuntuforums.org/ https://wiki.ubuntu.com/ #ubuntu on irc.freenode.net
terveisin -andre
On Sun, 2006-02-05 at 23:19 -0800, david golightly wrote:
Yes, XMMS is working fine. Actually, I'm not getting any sound from Alsaplayer, though XMMS is supposedly using the XMMS-JACK driver. The output I pasted is from qjackctl with verbose turned on, though when I run jackd I get the same output. I've tried messing around with various Jack settings, but nothing seems to make any difference. What's puzzling is that it appears to be working until it says "Could not connect to JACK server as client". Could it have something to do with Alsa not being configured properly?
I'm sure this is typical of the Linux world, but there seems to be a lot of obsolete information that comes up on Google searches. It would be nice if things came down after a few years... for instance, the mini Alsa HOWTO posted on the alsa wiki site alsa.opensrc.org is from 1999... I think probably a lot has changed in the last 7 years! I would like to contribute some time to keeping these things up to date, but I don't feel that I have the expertise just yet. Certainly once I can reimage a low-latency machine with jack & alsa working right away I'm going to be paying back for all the help I've received over the years!
On 2/5/06, John Harrison < john.harrison@wichita.edu> wrote: Is XMMS with the JACK output driver working for you? That's my standard JACK test...but...if qjackctl isn't working...I doubt the problem is with Pd. Sounds more like a problem with jackd. When messing with JACK initially, I always find it easiest to run jackd or jackstart from qjackctl. Easier to debug what is going on.
Is the output below from jackd or qjackctl? Whatever it is...it isn't happy. That's the place to start. -John david golightly wrote: > Hello everyone! > > Sorry to be a drag here, but I've been scratching my head on > this for several days now. I'm trying to coordinate pd, > alsa, and jack on ubuntu (actually demudi multimedia kernel > 2.6.12 in ubuntu) and I've got a number of symptoms here, > but I've not been able to diagnose what's going on: > > - not getting any sound from pd; pd doesn't recognize any > devices > - pd's Media menu lists 'OSS', 'ALSA', and 'Jack' > - compiled pd 0.39-2 with --enable-alsa --enable-jack > - alsa seems to be installed fine, alsamixer works, cds play > in alsaplayer > - qjackctl will not connect to jack server as client - but > jack appears to start fine (?): > > 13:44:26.950 JACK was started with PID=6255 (0x186f). > jackd 0.100.9 > Copyright 2001-2005 Paul Davis and others. > jackd comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute > it > under certain conditions; see the file COPYING for details > JACK compiled with System V SHM support. > loading driver .. > apparent rate = 48000 > creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon| > swmeter|-|32bit > control device hw:0 > configuring for 48000Hz, period = 1024 frames, buffer = 2 > periods > Note: audio device hw:0 doesn't support a 32bit sample > format so JACK will try a 24bit format instead > Note: audio device hw:0 doesn't support a 24bit sample > format so JACK will try a 16bit format instead > nperiods = 2 for capture > nperiods = 2 for playback > 13:44:29.002 Could not connect to JACK server as client. > 13:44:31.629 JACK is stopping... > > So I was wondering, anyone have any pointers here? I'm > stumped. > > Thanks, > > David > > > ____________________________________________________________ > > _______________________________________________ > PD-list@iem.at > mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list