USB Webcam microphone not working until re-plugged
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I use pulseaudio + pavucontrol
So I boot in with the device plugged in the USB port.
I check the Input device tab in the Volume Control application (pavucontrol) I see only my GEMIX_WEBCAM_USB_AUDIO Analog Mono
and it doesn't react on any sound.
Then I re-plug the USB device and it starts reacting to the sound (you know sort of blue horizontal indicator).
The problem is that it will stop reacting to the sound as soon as I reboot or make:
pulseaudio -k
pulseaudio -D
Every time to make it wakeup I need to physically re-plug it ....
What can be done to avoid it ?
[liza@liza ~]$ pacmd list-sources | grep -e device.string -e 'name:'
name: <alsa_output.pci-0000_00_1b.0.analog-stereo.monitor>
device.string = "0"
name: <alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono>
device.string = "hw:1"
I also added this device as a default in the /etc/pulse/default.pa below the line ### Make some devices default
### Make some devices default
set-default-source alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono
pulseaudio webcam microphone pavucontrol usb-device
asked Mar 21 at 12:32
Dmitriy Klyushin
165
add a comment |Â
up vote
0
down vote
favorite
I use pulseaudio + pavucontrol
So I boot in with the device plugged in the USB port.
I check the Input device tab in the Volume Control application (pavucontrol) I see only my GEMIX_WEBCAM_USB_AUDIO Analog Mono
and it doesn't react on any sound.
Then I re-plug the USB device and it starts reacting to the sound (you know sort of blue horizontal indicator).
The problem is that it will stop reacting to the sound as soon as I reboot or make:
pulseaudio -k
pulseaudio -D
Every time to make it wakeup I need to physically re-plug it ....
What can be done to avoid it ?
[liza@liza ~]$ pacmd list-sources | grep -e device.string -e 'name:'
name: <alsa_output.pci-0000_00_1b.0.analog-stereo.monitor>
device.string = "0"
name: <alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono>
device.string = "hw:1"
I also added this device as a default in the /etc/pulse/default.pa below the line ### Make some devices default
### Make some devices default
set-default-source alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono
pulseaudio webcam microphone pavucontrol usb-device
asked Mar 21 at 12:32
Dmitriy Klyushin
165
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I use pulseaudio + pavucontrol
So I boot in with the device plugged in the USB port.
I check the Input device tab in the Volume Control application (pavucontrol) I see only my GEMIX_WEBCAM_USB_AUDIO Analog Mono
and it doesn't react on any sound.
Then I re-plug the USB device and it starts reacting to the sound (you know sort of blue horizontal indicator).
The problem is that it will stop reacting to the sound as soon as I reboot or make:
pulseaudio -k
pulseaudio -D
Every time to make it wakeup I need to physically re-plug it ....
What can be done to avoid it ?
[liza@liza ~]$ pacmd list-sources | grep -e device.string -e 'name:'
name: <alsa_output.pci-0000_00_1b.0.analog-stereo.monitor>
device.string = "0"
name: <alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono>
device.string = "hw:1"
I also added this device as a default in the /etc/pulse/default.pa below the line ### Make some devices default
### Make some devices default
set-default-source alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono
pulseaudio webcam microphone pavucontrol usb-device
asked Mar 21 at 12:32
Dmitriy Klyushin
165
I use pulseaudio + pavucontrol
So I boot in with the device plugged in the USB port.
I check the Input device tab in the Volume Control application (pavucontrol) I see only my GEMIX_WEBCAM_USB_AUDIO Analog Mono
and it doesn't react on any sound.
Then I re-plug the USB device and it starts reacting to the sound (you know sort of blue horizontal indicator).
The problem is that it will stop reacting to the sound as soon as I reboot or make:
pulseaudio -k
pulseaudio -D
Every time to make it wakeup I need to physically re-plug it ....
What can be done to avoid it ?
[liza@liza ~]$ pacmd list-sources | grep -e device.string -e 'name:'
name: <alsa_output.pci-0000_00_1b.0.analog-stereo.monitor>
device.string = "0"
name: <alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono>
device.string = "hw:1"
I also added this device as a default in the /etc/pulse/default.pa below the line ### Make some devices default
### Make some devices default
set-default-source alsa_input.usb-Aveotek_GEMIX_WEBCAM_USB_AUDIO-02.analog-mono
pulseaudio webcam microphone pavucontrol usb-device
pulseaudio webcam microphone pavucontrol usb-device
asked Mar 21 at 12:32
Dmitriy Klyushin
165
asked Mar 21 at 12:32
Dmitriy Klyushin
165
asked Mar 21 at 12:32
Dmitriy Klyushin
165
asked Mar 21 at 12:32
Dmitriy Klyushin
165
asked Mar 21 at 12:32
Dmitriy Klyushin
165
165
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
SOLUTION:
I was looking through the output of the:
pacmd list-source
and noticed that my * index 1 device had status: suspended (asterisk - indicates that the device is the default one)
There is a solution for such situation described on the wiki.archlinux
So I opened /etc/pulse/default.pa
and commented out the line:
load-module module-suspend-on-idle
restarted pulseaudio:
pulseaudio -k
and now in the output of the:
pacmd list-source
* index 1 device has status: idle (and the status changes to RUNNING - when it's used by an application for ex. guvcview)
So that's the solution.
As well I'd also like to mention that I previously experienced the situation when the mic of this device wouldn't record audio at all. And the solution was to choose "Analogue Stereo Output" in the Buit-In Audio section on the Configuration tab of the Volume Control app (pavucontrol). This way I got rid of the conflict - when the system didn't know what source to use - the built-in mic or the external one.
answered Mar 21 at 15:16
Dmitriy Klyushin
165
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
SOLUTION:
I was looking through the output of the:
pacmd list-source
and noticed that my * index 1 device had status: suspended (asterisk - indicates that the device is the default one)
There is a solution for such situation described on the wiki.archlinux
So I opened /etc/pulse/default.pa
and commented out the line:
load-module module-suspend-on-idle
restarted pulseaudio:
pulseaudio -k
and now in the output of the:
pacmd list-source
* index 1 device has status: idle (and the status changes to RUNNING - when it's used by an application for ex. guvcview)
So that's the solution.
As well I'd also like to mention that I previously experienced the situation when the mic of this device wouldn't record audio at all. And the solution was to choose "Analogue Stereo Output" in the Buit-In Audio section on the Configuration tab of the Volume Control app (pavucontrol). This way I got rid of the conflict - when the system didn't know what source to use - the built-in mic or the external one.
answered Mar 21 at 15:16
Dmitriy Klyushin
165
add a comment |Â
up vote
0
down vote
SOLUTION:
I was looking through the output of the:
pacmd list-source
and noticed that my * index 1 device had status: suspended (asterisk - indicates that the device is the default one)
There is a solution for such situation described on the wiki.archlinux
So I opened /etc/pulse/default.pa
and commented out the line:
load-module module-suspend-on-idle
restarted pulseaudio:
pulseaudio -k
and now in the output of the:
pacmd list-source
* index 1 device has status: idle (and the status changes to RUNNING - when it's used by an application for ex. guvcview)
So that's the solution.
As well I'd also like to mention that I previously experienced the situation when the mic of this device wouldn't record audio at all. And the solution was to choose "Analogue Stereo Output" in the Buit-In Audio section on the Configuration tab of the Volume Control app (pavucontrol). This way I got rid of the conflict - when the system didn't know what source to use - the built-in mic or the external one.
answered Mar 21 at 15:16
Dmitriy Klyushin
165
add a comment |Â
up vote
0
down vote
up vote
0
down vote
SOLUTION:
I was looking through the output of the:
pacmd list-source
and noticed that my * index 1 device had status: suspended (asterisk - indicates that the device is the default one)
There is a solution for such situation described on the wiki.archlinux
So I opened /etc/pulse/default.pa
and commented out the line:
load-module module-suspend-on-idle
restarted pulseaudio:
pulseaudio -k
and now in the output of the:
pacmd list-source
* index 1 device has status: idle (and the status changes to RUNNING - when it's used by an application for ex. guvcview)
So that's the solution.
As well I'd also like to mention that I previously experienced the situation when the mic of this device wouldn't record audio at all. And the solution was to choose "Analogue Stereo Output" in the Buit-In Audio section on the Configuration tab of the Volume Control app (pavucontrol). This way I got rid of the conflict - when the system didn't know what source to use - the built-in mic or the external one.
answered Mar 21 at 15:16
Dmitriy Klyushin
165
SOLUTION:
I was looking through the output of the:
pacmd list-source
and noticed that my * index 1 device had status: suspended (asterisk - indicates that the device is the default one)
There is a solution for such situation described on the wiki.archlinux
So I opened /etc/pulse/default.pa
and commented out the line:
load-module module-suspend-on-idle
restarted pulseaudio:
pulseaudio -k
and now in the output of the:
pacmd list-source
* index 1 device has status: idle (and the status changes to RUNNING - when it's used by an application for ex. guvcview)
So that's the solution.
As well I'd also like to mention that I previously experienced the situation when the mic of this device wouldn't record audio at all. And the solution was to choose "Analogue Stereo Output" in the Buit-In Audio section on the Configuration tab of the Volume Control app (pavucontrol). This way I got rid of the conflict - when the system didn't know what source to use - the built-in mic or the external one.
answered Mar 21 at 15:16
Dmitriy Klyushin
165
answered Mar 21 at 15:16
Dmitriy Klyushin
165
answered Mar 21 at 15:16
Dmitriy Klyushin
165
answered Mar 21 at 15:16
Dmitriy Klyushin
165
165
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1017925%2fusb-webcam-microphone-not-working-until-re-plugged%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password