...that deal with pure data
You are not logged in.
hi,
i'm pretty new to Pd, having some trouble getting it running on suse 10.2. Pd launches, but is just very, very, very, slow. for example, if i try to open a patch, it's about half a minute before the window appears; and another 30 seconds before anything is drawn in it. the interface in the window is unresponsive, i can't get any audio, can't go into Edit mode, or anything.
- it's an athlon 64, running suse 10.2 x86_64.
- pd worked great on the exact same box under suse 9.3 64bit, and even better in ubuntu 6.10 edgy. so the fault is probably with suse, but what could be the difference? baffling.
- same issue whether installing from the repositories, or compiling from scratch
thanks,
--arky
Offline
Hi arky,
welcome! I'm on OpenSuse 10.2 (32 bits), athlon 2400+,
and PD is like a sweet...
No hints about 64 bits.. maybe the distro, maybe PD itself?
cheers
Alberto
Offline
thanks albertoz,
that gave me hope, and now i've .5 solved it. looking at it again, i noticed that at launch it also prints an error, "Pd: System call timed out". also the "Media" menu was blank.
some trial and error later, discovered that
pd -noadc
works. so that's good; but i guess that means i have no sound input?
so here's some more detailed info; there's probably numerous threads and resources for dealing with this, so i'll also go do some more hunting.
~> pd -oss
Pd: system call timed out
(windows are unresponsive, no Media menu, etc)
~> pd -alsa
no terminal errors; in Pd, it says "audio stuck: closing audio"
~> pd -jack
no errors, but no sound either.
Offline
SOLVED!
sudo chmod a+rw /dev/dsp*
sudo chmod a+rw /dev/audio*
stupid linux.
Offline
Thanks for posting back your results for this problem Arky.
Offline
Just to understand: Do you have an idea of why did you have to do like that?
I got:
alberto@linux:~> ls -l /dev/dsp
crw-rw----+ 1 root audio 14, 3 4 apr 20:32 /dev/dsp
Is that correct?
Maybe your user was not on audio group?
Alberto
Offline
Hello,
I have the same lag troubles under Edgy 2.6.17.11
My sound card is a "Intel Corporation 82801 (ICH7 Family) High Definition Audio Controller (rev01)" on my laptop (Dell Inspiron 9400)
I've got the same "Pd: system call timed out".
"ls -l /dev/dsp" gives me:
crw-rw----- 1 root audio 14, 3 4 apr 20:32 /dev/dsp
I did what arky suggested (chmod ...) but this is useless.
"pd -noadc" works perfectlly (with no sound of course)
"pd -alsa" gives me "audio I/O stuck... closing audio"
Need help !
Last edited by ourscoca (2007-04-19 11:03:12)
Offline
Derek gave us this starting point for setup problems
http://www.flossmanuals.net/PureData/TroubleShooting
Please let us know if you have any luck with this Ourscoca. There is also an active thread on pd-list right now with exactly this problem. There are a variety of causes for the "no sound" problem, sometimes ALSA is not set up, sometimes permissions as above, sometimes it's sample rates set up differently between ALAS, Jack, Pd etc.
Have you any other diagnostic info?
Do other sound apps work alright?
Offline
Thanks for answering, Source master...
I am not in cases pointed by Derek's list.
Others sound applications are working very well.
I've tried to resolve this problem upgrading my Edgy to a brand new Festy... useless.
If the trouble comes from ALSA setting up, I have no idea how to configurate it to avoid this problem.
Offline
Hello there.
I have no news yet that will definitely help. Both Edgy and Feisty have problems with certain combos of hardware and ALSA.
Things I have found out:
Sound on Ubuntu is dodgy and has a lot of bug reports filed.
Daniel T Chen - search for bug reports by him, he is assigned to this in Ubuntu
Also search generally for "Ubuntu no sound". "Ubuntu ALSA"
Use Jack - it is much better than ALSA
I have seen several weird solutions involving things like deleting and recreating the sound group,
moving or recreating asound.conf and/or ~/.asoundrc*, and sacrificing a chicken to the flying spaghetti monster. In other words, no coherent problem definition or solution from Ubuntu users yet.
re-running alsaconf , sudo alsaconf (in sudo ubuntu you sudo must put sudo before sudo everything)
http://ubuntuforums.org/showthread.php?t=413626
https://bugs.launchpad.net/ubuntu/+sour … +bug/81476
good luck, report back soon
Offline