[pulseaudio-tickets] [PulseAudio] #392: pulse audio prevents sound capture from working on thinkpad x300

PulseAudio trac-noreply at tango.0pointer.de
Thu Nov 13 10:46:13 PST 2008


#392: pulse audio prevents sound capture from working on thinkpad x300
---------------------+------------------------------------------------------
  Reporter:  dvstin  |       Owner:  lennart 
      Type:  defect  |      Status:  reopened
  Priority:  normal  |   Milestone:          
 Component:  daemon  |    Severity:  normal  
Resolution:          |    Keywords:          
---------------------+------------------------------------------------------
Comment (by coling):

 minholi, this is almost certainly a different problem. Please open a new
 bug if you feel it is a real problem, but please also be aware that it's
 more likely that some pulse is not releasing the sound device for your
 exclusive use via OSS.

 I also find it very hard to believe that istanbul (which makes extensive
 use of GST) is using OSS for recording. I'd be very surprised if it is not
 using gst for which there exists a pulse source which would be
 recommended.

 If you have more info, such as a backtrace or a log and can confirm that
 this is the same bug, please reopen. If you have such info and realise
 it's a new bug then please open a new one. Start by making sure that parec
 works, then arecord and then move on to testing oss recording.

 For me the easiest way to do this was via:
 {{{
 export AUDIODEV=/dev/dsp
 export AUDIODRIVER=oss
 padsp rec something.wav
 }}}

 This operated correctly but didn't really work very well in terms of the
 timing information. Certainly no lockups tho'. arecord looked to work fine
 too.

 I'm pretty sure my laptop has totally broken recording at the moment
 anyway as alsa just records nothing... this could be something to do with
 smoke coming out of it a while ago :p

 These tests were just the theory of operation rather than any actual data.


 But without any additional info from you, i'm not sure if we can keep the
 bug open. It really does sound like a config issue rather than a bug, and
 even if it is a bug, I strongly suspect it's not the same as this one,
 even if it looks the same on the surface.

-- 
Ticket URL: <http://www.pulseaudio.org/ticket/392#comment:9>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server


More information about the pulseaudio-bugs mailing list