Quantcast

Sound Mixer issue

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Sound Mixer issue

emuhuron
Okay folks, I'm resubmitting this only because the email string length is under review and I need sound to my microphone resolved:

My last issue is with "Sound Mixer" in the final package.  Somehow, the Recording Tab has the microphone muted.  That defeats the use of a webcam. Which package in the thinstation build is the builder for "Sound Mixer" in TS?  And, if possible where is the command or line of code to UN-Mute the microphone option?  Should I hard-code in application package or line command in the Session file?

To recap, here's what I know:  The TS-build sees the microphone only AFTER I start my vmware vdi webcam (that's fine). In the TS Multimedia application list, called "Volume Control"-- it's Recording tab sees the webcam and the volume level jumps up-and-down as people talk near the microphone.  However, the person on the other end of the webcam call (in the VDI) doesn't hear me until I've unmuted the application "Sound Mixer"- Recording tab Microphone setting "Toggle audio recording from Microphone"(lower right of volume control in the tab window).

How do I build my package with "Toggle audio recording from Microphone" unmuted?  Where do I make the change?  For reference, even the Thinstation development environment has it muted.
  
=====================================================
Brian Koch

------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Sound Mixer issue

Don Cupp
So, depending on the variances in your hardware, you might be able to get away with an alsactl restore. Our alsa init script ( build/packages/alsa/build/extra/etc/init.d/audio ), is not smart enough to set whatever control you are setting via the sound mixer. You could, go to a machine ( in a diagnostic mode ), and run alsactl monitor, then change the setting via mixer, this should will hopefully tell you what is changing, then start with developing a simple rule at the bottom of the init script that achieves the same result. Other options include doing alsactl store, saving the resulting config file, transferring to build env, inserting into image, and then run alsactl restore on the client.

Whatever happens, let us know. Interesting corner case, wish I had more time to look at it.


On Wednesday, November 16, 2016 12:37 PM, Brian Koch <[hidden email]> wrote:


Okay folks, I'm resubmitting this only because the email string length is under review and I need sound to my microphone resolved:

My last issue is with "Sound Mixer" in the final package.  Somehow, the Recording Tab has the microphone muted.  That defeats the use of a webcam. Which package in the thinstation build is the builder for "Sound Mixer" in TS?  And, if possible where is the command or line of code to UN-Mute the microphone option?  Should I hard-code in application package or line command in the Session file?

To recap, here's what I know:  The TS-build sees the microphone only AFTER I start my vmware vdi webcam (that's fine). In the TS Multimedia application list, called "Volume Control"-- it's Recording tab sees the webcam and the volume level jumps up-and-down as people talk near the microphone.  However, the person on the other end of the webcam call (in the VDI) doesn't hear me until I've unmuted the application "Sound Mixer"- Recording tab Microphone setting "Toggle audio recording from Microphone"(lower right of volume control in the tab window).

How do I build my package with "Toggle audio recording from Microphone" unmuted?  Where do I make the change?  For reference, even the Thinstation development environment has it muted.
  
============================== =======================
Brian Koch

------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general



------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Sound Mixer issue

emuhuron
Don, thanks for the idea.  I'll see if I can figure that out. I do know in the tmp/vmware-tsuser folder that one of the logs shows the microphone being muted when connecting to my VDI--right after it successfully connects to my webcam.  Ironic-- "I see your webcam, I want to work with it, now shut up!"...

Additional thoughts:  
1.  It appears that Sound Mixer is Gnome-related.  I don't know where in Gnome it might preset the mic volume to 0 or mute though.
2.  When I start my webcam in the VDI, Pavucontrol's Recording tab sees the mic and shows that it hears me speaking.  Albeit, no microphone is heard in the VDI until I unmute Sound Mixer.
3.  The sound option in the VDI that makes no sense:  We have VMware Horizon 6.  RTAV is a part of it.  I've configured the VMware config file for usb redirection for the audio to function.  We would tend to believe what we need the following settings in Google Hangouts (our webcam app) to be:  Camera set to VMware, Microphone set to Vmware, and Speakers set to VMWare.  That's what we believe.  Currently, when unmuted, the only settings that work: Camera set to Vmware, Microphone set to Default, Speakers set to Communications.  Truly odd.




Brian Koch
IT Dept
City of Taylor, MI
(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Wed, Nov 16, 2016 at 8:52 PM, Don Cupp <[hidden email]> wrote:
So, depending on the variances in your hardware, you might be able to get away with an alsactl restore. Our alsa init script ( build/packages/alsa/build/extra/etc/init.d/audio ), is not smart enough to set whatever control you are setting via the sound mixer. You could, go to a machine ( in a diagnostic mode ), and run alsactl monitor, then change the setting via mixer, this should will hopefully tell you what is changing, then start with developing a simple rule at the bottom of the init script that achieves the same result. Other options include doing alsactl store, saving the resulting config file, transferring to build env, inserting into image, and then run alsactl restore on the client.

Whatever happens, let us know. Interesting corner case, wish I had more time to look at it.


On Wednesday, November 16, 2016 12:37 PM, Brian Koch <[hidden email]> wrote:


Okay folks, I'm resubmitting this only because the email string length is under review and I need sound to my microphone resolved:

My last issue is with "Sound Mixer" in the final package.  Somehow, the Recording Tab has the microphone muted.  That defeats the use of a webcam. Which package in the thinstation build is the builder for "Sound Mixer" in TS?  And, if possible where is the command or line of code to UN-Mute the microphone option?  Should I hard-code in application package or line command in the Session file?

To recap, here's what I know:  The TS-build sees the microphone only AFTER I start my vmware vdi webcam (that's fine). In the TS Multimedia application list, called "Volume Control"-- it's Recording tab sees the webcam and the volume level jumps up-and-down as people talk near the microphone.  However, the person on the other end of the webcam call (in the VDI) doesn't hear me until I've unmuted the application "Sound Mixer"- Recording tab Microphone setting "Toggle audio recording from Microphone"(lower right of volume control in the tab window).

How do I build my package with "Toggle audio recording from Microphone" unmuted?  Where do I make the change?  For reference, even the Thinstation development environment has it muted.
  
============================== =======================
Brian Koch

------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general



------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general



------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Sound Mixer issue

emuhuron
I put the following in the wrong email string last night.  Sorry about that.    Here's my last issue (I hope):

Okay, I've got audio.  So, I'm setting my TS.conf.buildtime audio to AUDIO_LEVEL=100.  However, when it builds, the audio is set to 45 (-21db).  Where is that 45 coming from?  It did work before I added the following script to fix my "mic mute/ volume set to 0" issue.  Now, my mic works great, but I cannot set the speaker volume.  Where to next folks? thanks again.  This came from a wiki.archive PulseAudio page about giving back control to Alsa

restore_alsa() {
 while [ -z "$(pidof pulseaudio)" ]; do
  sleep 0.5
 done
 alsactl -f /var/lib/alsa/asound.state restore 
}
restore_alsa &


Brian Koch
IT Dept
City of Taylor, MI
(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Thu, Nov 17, 2016 at 1:44 PM, Brian Koch <[hidden email]> wrote:
Don, Assuming the asound.state was a config file, I ran the alsact store and it saved to the asound.state file.  Was this the config file you were talking about?  Anyway, I copied the "new" version off and back in to my Dev station and rebuilt the image.  The new asound.state file with the changes matches up.  But, my mic is still muted.  I even altered the init.d/audio file to have everything set to "unmuted" before I built it.  When I ran the alsatrl monitor command before this, it took me two clicks before the monitor saw it.  First click would have unmuted the mic but nothing showed in the "monitor" window, the 2nd one muted it.  Alsactrl monitor showed this after 2nd click:

card 1, #22 (2,0,0,Master Playback Volume,0) VALUE (appears when I start my webcam in the VDI)
card 0, #2 (2,0,0,Mic Capture Switch,0) VALUE (appears when mic is is muted/unmuted in Gnome Volume Control).  It doesn't show what's changed to even though I can see it visually in the Volume Control.

And, as a test, I closed Gnome Volume Control with the mute off.  I re-opened it and it was muted again.  I hadn't clicked anything.



Brian Koch
IT Dept
City of Taylor, MI
<a href="tel:%28734%29%20374-1514" value="+17343741514" target="_blank">(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Thu, Nov 17, 2016 at 11:32 AM, Don Cupp <[hidden email]> wrote:
I don't use VMware, so I can't offer anything there, but gnome does not do anything with the audio on its own. Pulse has hooks, but Linux primarily relies on alsa to initialize the audio devices.


Sent from Yahoo Mail for iPhone

On Thursday, November 17, 2016, 7:33 AM, Brian Koch <[hidden email]> wrote:

Don, thanks for the idea.  I'll see if I can figure that out. I do know in the tmp/vmware-tsuser folder that one of the logs shows the microphone being muted when connecting to my VDI--right after it successfully connects to my webcam.  Ironic-- "I see your webcam, I want to work with it, now shut up!"...

Additional thoughts:  
1.  It appears that Sound Mixer is Gnome-related.  I don't know where in Gnome it might preset the mic volume to 0 or mute though.
2.  When I start my webcam in the VDI, Pavucontrol's Recording tab sees the mic and shows that it hears me speaking.  Albeit, no microphone is heard in the VDI until I unmute Sound Mixer.
3.  The sound option in the VDI that makes no sense:  We have VMware Horizon 6.  RTAV is a part of it.  I've configured the VMware config file for usb redirection for the audio to function.  We would tend to believe what we need the following settings in Google Hangouts (our webcam app) to be:  Camera set to VMware, Microphone set to Vmware, and Speakers set to VMWare.  That's what we believe.  Currently, when unmuted, the only settings that work: Camera set to Vmware, Microphone set to Default, Speakers set to Communications.  Truly odd.




Brian Koch
IT Dept
City of Taylor, MI
<a dir="ltr" href="tel:(734)%20374-1514" target="_blank">(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Wed, Nov 16, 2016 at 8:52 PM, Don Cupp <[hidden email]> wrote:
So, depending on the variances in your hardware, you might be able to get away with an alsactl restore. Our alsa init script ( build/packages/alsa/build/ extra/etc/init.d/audio ), is not smart enough to set whatever control you are setting via the sound mixer. You could, go to a machine ( in a diagnostic mode ), and run alsactl monitor, then change the setting via mixer, this should will hopefully tell you what is changing, then start with developing a simple rule at the bottom of the init script that achieves the same result. Other options include doing alsactl store, saving the resulting config file, transferring to build env, inserting into image, and then run alsactl restore on the client.

Whatever happens, let us know. Interesting corner case, wish I had more time to look at it.


On Wednesday, November 16, 2016 12:37 PM, Brian Koch <[hidden email]> wrote:


Okay folks, I'm resubmitting this only because the email string length is under review and I need sound to my microphone resolved:

My last issue is with "Sound Mixer" in the final package.  Somehow, the Recording Tab has the microphone muted.  That defeats the use of a webcam. Which package in the thinstation build is the builder for "Sound Mixer" in TS?  And, if possible where is the command or line of code to UN-Mute the microphone option?  Should I hard-code in application package or line command in the Session file?

To recap, here's what I know:  The TS-build sees the microphone only AFTER I start my vmware vdi webcam (that's fine). In the TS Multimedia application list, called "Volume Control"-- it's Recording tab sees the webcam and the volume level jumps up-and-down as people talk near the microphone.  However, the person on the other end of the webcam call (in the VDI) doesn't hear me until I've unmuted the application "Sound Mixer"- Recording tab Microphone setting "Toggle audio recording from Microphone"(lower right of volume control in the tab window).

How do I build my package with "Toggle audio recording from Microphone" unmuted?  Where do I make the change?  For reference, even the Thinstation development environment has it muted.
  
============================== =======================
Brian Koch

------------------------------ ------------------------------ ------------------

______________________________ _________________
Thinstation-general mailing list
Thinstation-general@lists. sourceforge.net
https://lists.sourceforge.net/ lists/listinfo/thinstation- general



------------------------------ ------------------------------ ------------------

______________________________ _________________
Thinstation-general mailing list
Thinstation-general@lists. sourceforge.net
https://lists.sourceforge.net/ lists/listinfo/thinstation- general





------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Sound Mixer issue

emuhuron
Don, you can't recite every line of code in the TS?  What is this world coming to?...  Yeah, I realized I forgot to include the path where I put it after sending. "/build/packages/pulseaudio/build/extra/etc/X11/xinit/xinitrc.d/pulseaudio" is where I put the script I found.  All that was originally in there was one line:  "/bin/pulseaudio --start"  ( got the script from from https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Muted_audio_device)

Also, what may an odd part:  I did follow your earlier instructions and altered the asound.state file and backed it up.  I over-wrote the original asound.state file with my new version and the settings were still the same after building my TS. So, that's when I went hunting and found the script with restore_alsa and gave it try.  I'm truly wondering if something else generates the initial state of asound.state.

I'll give your suggestion a try.


Brian Koch
IT Dept
City of Taylor, MI
(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Tue, Nov 22, 2016 at 12:15 PM, Don Cupp <[hidden email]> wrote:
All that I can think of, is that the 45 percent is stored the alsa state file, and is being restored. I don't know where exactly you have that code waiting for pulse to come up, but maybe after it, you could put a copy of some of the audio init

for card in `grep -e ":" /proc/asound/cards |cut -c2`; do
if [ -n "$AUDIO_LEVEL" ]; then
for control in Master PCM CD Video; do
if have_control $control; then
amixer sset -c $card $control $AUDIO_LEVEL% unmute
# amixer sset -c $card $control unmute
fi
done
fi
done


On Tuesday, November 22, 2016 6:33 AM, Brian Koch <[hidden email]> wrote:


I put the following in the wrong email string last night.  Sorry about that.    Here's my last issue (I hope):

Okay, I've got audio.  So, I'm setting my TS.conf.buildtime audio to AUDIO_LEVEL=100.  However, when it builds, the audio is set to 45 (-21db).  Where is that 45 coming from?  It did work before I added the following script to fix my "mic mute/ volume set to 0" issue.  Now, my mic works great, but I cannot set the speaker volume.  Where to next folks? thanks again.  This came from a wiki.archive PulseAudio page about giving back control to Alsa

restore_alsa() {
 while [ -z "$(pidof pulseaudio)" ]; do
  sleep 0.5
 done
 alsactl -f /var/lib/alsa/asound.state restore 
}
restore_alsa &


Brian Koch
IT Dept
City of Taylor, MI
<a href="tel:%28734%29%20374-1514" value="+17343741514" target="_blank">(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Thu, Nov 17, 2016 at 1:44 PM, Brian Koch <[hidden email]> wrote:
Don, Assuming the asound.state was a config file, I ran the alsact store and it saved to the asound.state file.  Was this the config file you were talking about?  Anyway, I copied the "new" version off and back in to my Dev station and rebuilt the image.  The new asound.state file with the changes matches up.  But, my mic is still muted.  I even altered the init.d/audio file to have everything set to "unmuted" before I built it.  When I ran the alsatrl monitor command before this, it took me two clicks before the monitor saw it.  First click would have unmuted the mic but nothing showed in the "monitor" window, the 2nd one muted it.  Alsactrl monitor showed this after 2nd click:

card 1, #22 (2,0,0,Master Playback Volume,0) VALUE (appears when I start my webcam in the VDI)
card 0, #2 (2,0,0,Mic Capture Switch,0) VALUE (appears when mic is is muted/unmuted in Gnome Volume Control).  It doesn't show what's changed to even though I can see it visually in the Volume Control.

And, as a test, I closed Gnome Volume Control with the mute off.  I re-opened it and it was muted again.  I hadn't clicked anything.



Brian Koch
IT Dept
City of Taylor, MI
(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Thu, Nov 17, 2016 at 11:32 AM, Don Cupp <[hidden email]> wrote:
I don't use VMware, so I can't offer anything there, but gnome does not do anything with the audio on its own. Pulse has hooks, but Linux primarily relies on alsa to initialize the audio devices.


Sent from Yahoo Mail for iPhone

On Thursday, November 17, 2016, 7:33 AM, Brian Koch <[hidden email]> wrote:
Don, thanks for the idea.  I'll see if I can figure that out. I do know in the tmp/vmware-tsuser folder that one of the logs shows the microphone being muted when connecting to my VDI--right after it successfully connects to my webcam.  Ironic-- "I see your webcam, I want to work with it, now shut up!"...

Additional thoughts:  
1.  It appears that Sound Mixer is Gnome-related.  I don't know where in Gnome it might preset the mic volume to 0 or mute though.
2.  When I start my webcam in the VDI, Pavucontrol's Recording tab sees the mic and shows that it hears me speaking.  Albeit, no microphone is heard in the VDI until I unmute Sound Mixer.
3.  The sound option in the VDI that makes no sense:  We have VMware Horizon 6.  RTAV is a part of it.  I've configured the VMware config file for usb redirection for the audio to function.  We would tend to believe what we need the following settings in Google Hangouts (our webcam app) to be:  Camera set to VMware, Microphone set to Vmware, and Speakers set to VMWare.  That's what we believe.  Currently, when unmuted, the only settings that work: Camera set to Vmware, Microphone set to Default, Speakers set to Communications.  Truly odd.




Brian Koch
IT Dept
City of Taylor, MI
(734) 374-1514 or Ext. 7550 (internal use)
Please have a ticket put in if you need an issue resolved.

On Wed, Nov 16, 2016 at 8:52 PM, Don Cupp <[hidden email]> wrote:
So, depending on the variances in your hardware, you might be able to get away with an alsactl restore. Our alsa init script ( build/packages/alsa/build/ extra/etc/init.d/audio ), is not smart enough to set whatever control you are setting via the sound mixer. You could, go to a machine ( in a diagnostic mode ), and run alsactl monitor, then change the setting via mixer, this should will hopefully tell you what is changing, then start with developing a simple rule at the bottom of the init script that achieves the same result. Other options include doing alsactl store, saving the resulting config file, transferring to build env, inserting into image, and then run alsactl restore on the client.

Whatever happens, let us know. Interesting corner case, wish I had more time to look at it.


On Wednesday, November 16, 2016 12:37 PM, Brian Koch <[hidden email]> wrote:


Okay folks, I'm resubmitting this only because the email string length is under review and I need sound to my microphone resolved:

My last issue is with "Sound Mixer" in the final package.  Somehow, the Recording Tab has the microphone muted.  That defeats the use of a webcam. Which package in the thinstation build is the builder for "Sound Mixer" in TS?  And, if possible where is the command or line of code to UN-Mute the microphone option?  Should I hard-code in application package or line command in the Session file?

To recap, here's what I know:  The TS-build sees the microphone only AFTER I start my vmware vdi webcam (that's fine). In the TS Multimedia application list, called "Volume Control"-- it's Recording tab sees the webcam and the volume level jumps up-and-down as people talk near the microphone.  However, the person on the other end of the webcam call (in the VDI) doesn't hear me until I've unmuted the application "Sound Mixer"- Recording tab Microphone setting "Toggle audio recording from Microphone"(lower right of volume control in the tab window).

How do I build my package with "Toggle audio recording from Microphone" unmuted?  Where do I make the change?  For reference, even the Thinstation development environment has it muted.
  
============================== =======================
Brian Koch

------------------------------ ------------------------------ ------------------

______________________________ _________________
Thinstation-general mailing list
Thinstation-general@lists. sourceforge.net
https://lists.sourceforge.net/ lists/listinfo/thinstation- general



------------------------------ ------------------------------ ------------------

______________________________ _________________
Thinstation-general mailing list
Thinstation-general@lists. sourceforge.net
https://lists.sourceforge.net/ lists/listinfo/thinstation- general








------------------------------------------------------------------------------

_______________________________________________
Thinstation-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/thinstation-general
Evg
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Sound Mixer issue

Evg
In reply to this post by Don Cupp
Don Cupp wrote
Our alsa init script ( build/packages/alsa/build/extra/etc/init.d/audio ), is not smart enough to set whatever control you are setting via the sound mixer.
Also, I found the strange situation: after boot with default config I haven't sound on "snd-hda-intel", but if I 'alsactl init' again in terminal, sound returns and works in freerdp and vmware view client.
Loading...