>From the output of those commands it seems clear that Portable Ubuntu
doesn't have any direct access to the hardware. I should probably have
guessed this or looked it up, but it may well explain why things aren't
as straightforward as they would normally be. In particular, sound is
done via PulseAudio which I think works like a proxy. I'm not all that
familiar with PulseAudio, so if I have time I'll try Portable Ubuntu
myself to see if I can get it to work, but for now two ideas are:
a) Follow the 'ALSA Configuration' section from here:
https://wiki.ubuntu.com/PulseAudio assuming it doesn't appear to have
been done already. (Things may need restarting for it to take effect).
This might make Audacity able to use the normal ALSA interface.
b) If that doesn't work, try launching Audacity with "padsp ./audacity"
which might allow it to use the OSS interface.
See also the 'audacity' section here:
And a few somewhat relevant threads:
On Mon, May 04, 2009 at 12:08:32AM +0100, Martyn Shaw wrote:
> Hi Dan
> Sorry to hear you've been under the weather, but glad you are on the
> mend. I tried your suggestions (see below)...
> Dan Horgan wrote:
> > Hi, sorry about the delayed response; I've been a bit ill. Fairly sure
> > it's not swine flu though, and I'm mostly feeling better now!
> > I can't think of any obvious reason why this isn't working... I can
> > suggest running commands to try to work out for sure whether the right
> > devices are properly available to Audacity. The complication is that I
> > don't know precisely how linux-within-windows differs from
> > linux-not-within-windows with regards to device stuff. With Ubuntu
> > things ought to just work, so when they don't it can be a pain to
> > determine why.
> > As a start, the "lspci" command should usually produce an entry for a
> > device of some sort. (You can search the output with "lspci | grep
> pubuntu@...$ lspci
> pcilib: Cannot open /proc/bus/pci
> lspci: Cannot find any working access method.
> > There are two linux sound systems - OSS and ALSA. OSS is basically
> > obsolete now, but still supported generally, and works via device files
> > in /dev on the filesystem. ALSA is what you want to get working if it
> > isn't already. Try running "alsamixer"
> ┌─────────────────────────────────────[AlsaMixer v1.0.16 (Press Escape
> to quit)]──────────────────────────────────────┐
> │ Card: PulseAudio │
> │ Chip: PulseAudio │
> │ View: [Playback] Capture All
> │ Item: Master
> then a single 'fader' called 'Master' which would go up and down with
> arrow keys.
> and/or "amixer" to check that a
> > device shows up there.
> pubuntu@...$ amixer
> Simple mixer control 'Master',0
> Capabilities: pvolume pswitch pswitch-joined
> Playback channels: Front Left - Front Right
> Limits: Playback 0 - 65536
> Front Left: Playback 52611 [80%] [on]
> Front Right: Playback 52611 [80%] [on]
> Simple mixer control 'Capture',0
> Capabilities: cvolume cswitch cswitch-joined
> Capture channels: Front Left - Front Right
> Limits: Capture 0 - 65536
> Front Left: Capture 65536 [100%] [on]
> Front Right: Capture 65536 [100%] [on]
> You could also check that there are sound kernel
> > modules loaded by running "lsmod | grep snd".
> pubuntu@...$ lsmod
> Module Size Used by
> ipv6 265188 10
> iptable_filter 3072 0
> ip_tables 12616 1 iptable_filter
> x_tables 15876 1 ip_tables
> fuse 47508 3
> Is this useful?
> Will continue to look at this, with my 'baffled' face on.
> > I suspect these things *are* set up properly given that you got
> > rhythmbox to make sound, but it might help to narrow it down and
> > more details about what devices are actually available.
> > Dan
> > On Sat, May 02, 2009 at 01:38:02AM +0100, Martyn Shaw wrote:
> >> OK, so my knowledge of Linux is increasing, but so is my frustration.
> >> can't see why I get no devices found in Audacity. I have been
> >> through PortAudio1.9, which appears to iterate through devices but
> then I
> >> get
> >> Getting supported playback rates for device 0
> >> Could not get device info!
> >> from AudioIO. Any idea where to go next?
> >> I've tried with and without PulseAudio installed.
> >> TTFN
> >> Martyn
> >> Martyn Shaw wrote:
> >>> Dan Horgan wrote:
> >>>> On Mon, Apr 27, 2009 at 12:34:51AM +0100, Martyn Shaw wrote:
> >>> ...
> >>>>> Unfortunately it doesn't play audio, giving an 'Error while
> >>>>> sound device...' message, and calling up Prefs causes a
> >>>>> 'segmentation fault'. Probably things I've done wrong/not
> >>>>> completed.
> >>>> I'd check whether other Linux audio apps work if you haven't
> >>>> I'd guess that the segmentation fault is "P2 Crash opening
> >>>> with no audio devices present." although I haven't checked that this
> >>>> occurs on Linux.
> >>> This is not a good story.
> >>> I got sound from Rhythmbox by using 'mount' and then browsing to an
> >>> arbitrary .wav on my C:.
> >>> I wondered if the pulseaudio thing was causing me problems and found
> >>> http://ubuntuforums.org/showthread.php?t=789578 which promised to
> >>> that for ubuntu hardy (which is what I have), but after 30 minutes or
> >>> more of downloads, installs, reconfiguring and making audacity, I
> >>> haven't got any further. Still no sound devices found. Baffled I
> >>> Ideas?
> >>> And I've managed to break ./configure for sbsms, and I've no idea
> >>> Maybe this wasn't a good plan.
> >>> TTFN
> >>> Martyn