For anyone else getting this message, also make sure you do not have any
other sound applications open. I was trying to launch Audacity after
killing esd, but it was still failing because Rhythmbox was open on
another workspace.
** Summary changed:
- Can't find sound devices
+ Error message
This is probably due to other apps using your sound system.Close your
programs that use sound, like amarok and try again.
+ Upon launching audacity, the following message appears in a dialog box:
There was an error initializing the audio i/o layer. You will not be able
to play or record audio.
is it possible to compile + package it with alsa support? see
http://audacityteam.org/forum/post/966;?unb553sess=5587e4a7b69bcd3a9b157e980fb71fe7
--
Can't find sound devices
https://launchpad.net/bugs/337
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
I am using a HP Pavillion computer with no sound card--- audacity
complained about no i/o so I plugged in a new sound card just now and
the complaints about no i/o disappeared !!!
--
Can't find sound devices
https://launchpad.net/bugs/337
--
universe-bugs mailing list
** Changed in: audacity (Ubuntu)
Status: Unconfirmed = Confirmed
--
Can't find sound devices
https://launchpad.net/bugs/337
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
on Dapper still the same problem.
Can't that really be handled another way?
It's really not user-friendly this way
--
Can't find sound devices
https://launchpad.net/bugs/337
--
universe-bugs mailing list
universe-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/universe-bugs
It's generally a poor idea to try to record whilst also using software
mixing. Furthermore, many onboard sound modules are half-duplex, in
that whatever is being recorded will also be played, and vice-versa,
possibly causing unwanted noise in the recording. esound
0.2.36-3ubuntu3 changed the