#760 closed defect (fixed)
Record audio not working on SoaS
Reported by: | walter | Owned by: | alsroot |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
Component: | Sugar on a Stick (SoaS) | Version: | 0.84.x |
Severity: | Unspecified | Keywords: | |
Cc: | sdz | Distribution/OS: | Unspecified |
Bug Status: | Unconfirmed |
Description
Record-60 seems to work on SoaS (on a Classmate PC) except that the video and audio recordings are silent. Sample ogg files are attached. (Nothing of interest in the logs)
Attachments (2)
Change History (14)
Changed 14 years ago by walter
Changed 14 years ago by walter
comment:1 Changed 14 years ago by alsroot
- Component changed from sugar to Record
- Owner changed from tomeu to alsroot
- Status changed from new to assigned
comment:2 Changed 14 years ago by alsroot
- Resolution set to fixed
- Status changed from assigned to closed
comment:3 Changed 14 years ago by CarolineM
How do I do this?
check your alsamixer
or try Record-62
comment:4 Changed 14 years ago by walter
You can run alsamixer from Terminal
You can download Record-62 here:
http://activities.sugarlabs.org/en-US/sugar/downloads/latest/4081
comment:5 follow-up: ↓ 6 Changed 14 years ago by davidjim
i've already checked the alsamixer, and downloaded the last version of Record, and the problem still there, both, video and audio recordings are mute.
comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 14 years ago by alsroot
Replying to davidjim:
i've already checked the alsamixer, and downloaded the last version of Record, and the problem still there, both, video and audio recordings are mute.
could you post Record logs
and try this:
gst-launch-0.10 alsasrc ! queue ! wavenc ! filesink location=foo.wav
mute foo.wav should mean that its not Record problem but something in your environment
comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 14 years ago by davidjim
Replying to alsroot:
Replying to davidjim:
i've already checked the alsamixer, and downloaded the last version of Record, and the problem still there, both, video and audio recordings are mute.
could you post Record logs
and try this:
gst-launch-0.10 alsasrc ! queue ! wavenc ! filesink location=foo.wav
mute foo.wav should mean that its not Record problem but something in your environment
Indeed, i got a mute foo.wav file, so, where can i start looking for the problem?
comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 14 years ago by alsroot
Replying to davidjim:
Indeed, i got a mute foo.wav file, so, where can i start looking for the problem?
check alsamixer again:
$ alsamixer -V capture
if you are using pulseaudio(SoaS does it by default), use:
$ alsamixer -c 0 -V capture
and enable all channels(by <Space> key), maybe you'll have to switch to proper input sources for some channels(internal_mic/docking_station_mic/mix/etc)
and for example on my notebook with HDA Intel sound card I had to increase level of "Digital" channel
comment:9 in reply to: ↑ 8 ; follow-up: ↓ 10 Changed 14 years ago by davidjim
Replying to alsroot:
check alsamixer again:
$ alsamixer -V capture
if you are using pulseaudio(SoaS does it by default), use:
$ alsamixer -c 0 -V capture
and enable all channels(by <Space> key), maybe you'll have to switch to proper input sources for some channels(internal_mic/docking_station_mic/mix/etc)
and for example on my notebook with HDA Intel sound card I had to increase level of "Digital" channel
Thanks a lot!, that fixes the problem! But, if I restart the machine, the problem is there again.
Is there a way to make a script or something like that?
comment:10 in reply to: ↑ 9 ; follow-up: ↓ 11 Changed 14 years ago by alsroot
Replying to davidjim:
Replying to alsroot:
check alsamixer again:
$ alsamixer -V capture
if you are using pulseaudio(SoaS does it by default), use:
$ alsamixer -c 0 -V capture
and enable all channels(by <Space> key), maybe you'll have to switch to proper input sources for some channels(internal_mic/docking_station_mic/mix/etc)
and for example on my notebook with HDA Intel sound card I had to increase level of "Digital" channel
Thanks a lot!, that fixes the problem! But, if I restart the machine, the problem is there again.
Is there a way to make a script or something like that?
Sorry, this question is very distro specific(but in my mind every distro sould store levels of alsa channels on shutdown/reboot).
At least on my box Gentoo stores all levels and restores them on startup.
comment:11 in reply to: ↑ 10 Changed 14 years ago by tomeu
Replying to alsroot:
Replying to davidjim:
Replying to alsroot:
check alsamixer again:
$ alsamixer -V capture
if you are using pulseaudio(SoaS does it by default), use:
$ alsamixer -c 0 -V capture
and enable all channels(by <Space> key), maybe you'll have to switch to proper input sources for some channels(internal_mic/docking_station_mic/mix/etc)
and for example on my notebook with HDA Intel sound card I had to increase level of "Digital" channel
Thanks a lot!, that fixes the problem! But, if I restart the machine, the problem is there again.
Is there a way to make a script or something like that?
Sorry, this question is very distro specific(but in my mind every distro sould store levels of alsa channels on shutdown/reboot).
At least on my box Gentoo stores all levels and restores them on startup.
All distros do this AFAIK. What I suspect is that the overlay is not working, so changes to the main filesystem aren't persisting. Can we verify this?
comment:12 Changed 13 years ago by sascha_silbe
- Component changed from Record to SoaS
- Distribution/OS changed from SoaS to Unspecified
Bulk change distribution=SoaS -> component=SoaS
SoaS mutes capture channels by default thus check your alsamixer
or try Record-62 - it unmutes/set-to-max at starting
and feel free to reopen ticket if its not volume issue