When your computer has more than 1 sound card, you may find it cumbersome to change audio devices. The standard method requires going through the control panel or settings application , a process of multiple dialogs and multiple clicks. There is a better way.
Categories: "Computer Programming"
- 1
- 2
My primary desktop computer has an integrated audio device on the system board and a USB attached Blue Yeti microphone. Great mic, it makes me sound good on online meetings and that's a win. The Yeti in addition to being a high quality microphone also has a headphone jack underneath, which has a very high quality DAC and permits great music playback as well as the ability to hear yourself when you talk in online meetings. In my view, that last part is kindof not needed, but it is there and if you mute the microphone, you can listen to music without hearing yourself type. With two audio devices in the machine, Windows allows easy selection of default audio device for playback and default audio device for recording and as you may guess, my configuration is to use the Yeti microphone for recording and the system speakers for playback. Now, add Skype for Business audio conferencing and you'll find that when using the Yeti as microphone, Skype absolutely INSISTS on using the headphone audio connection on the Yeti as audio playback device - a device which normally has nothing plugged in. The result is that when you join meetings, the audience can hear you, but you cannot hear them.
I struggled with this for a bit, using phones to dial into meetings. I have since found the configuration screens to tell Skype to use the system speakers for conferencing.
Steve Ballmer is paraphrased in this ZDNet article saying "the company needs to ensure Windows Phone handsets can run Android apps". For a guy who spent more than 5 years writing system code for OS/2, the parallels to WinOS2 are pretty interesting. Here's the lesson: The operating system must stand on its own, or your just postpone it's death.
Written December 1, 2008. I recently received an inquiry regarding how OS/2 interrupts are handled and what is the correct action of a device driver upon being called by the OS/2 kernel. My first response was, you have got to be kidding me, the operating system has been dead for 10 years. The second response was to tell them the answer and now I write this blog so other folks might find it useful.
- 1
- 2