KnowBrainer Speech Recognition
Decrease font size
Increase font size
Topic Title: Sennheiser Presence and MB Pro, in Windows 10
Topic Summary:
Created On: 05/17/2023 04:12 PM
Status: Post and Reply
Linear : Threading : Single : Branch
 Sennheiser Presence and MB Pro, in Windows 10   - BigTech - 05/17/2023 04:12 PM  
 05/17/2023 04:12 PM
User is offline View Users Profile Print this message

Senior Member

Posts: 124
Joined: 11/25/2008

I don't know if disconnection/malfunction problems occur to anyone who is using only one headset. If not, enjoy!

If you haven't upgraded the firmware on your Sennheiser wireless headset and/or dongle, don't unless you can spell out why that's necessary. Apparently recent firmware is wrecked.

I might eventually fork over the $$$ for the current recommended headset, but maybe there is some method in Windows 10 to get the Sennheiser's to reliably work.

I'm trying a generic TP Link USB Bluetooth adapter (UB500). Using that, I get an extra icon on the Windows system tray "Bluetooth Devices" that leads to a few potentially useful Windows' settings. If possible, I will get it to work efficiently (or close). Then feel free to ask how. If I cannot do it, it probably cannot be done, but... Happy to be corrected!

Edit: Current method... Start up Windows with DNS off. Make sure the microphone is on before starting DNS. When the microphone stops working... right-click system tray icon > Profile > Manage Dictation Sources > Select the headset. That should not have to be done more than once, otherwise something is very fishy.

Edit: Sometimes power cycling the microphone works. Seems this is problematic using only the MB Pro, so let's start there.

Edit: The problem arises when the DNS mic turns off? In Vocola 2 scripts, removing instances of PlaySound() nukes most disconnects.

Edit: Yep... "PlaySound("D:\files\wav\special effects\thumph1.wav") WAIT(1) " causes the Sennheiser MB Pro to disconnect. The specific culprit might be one of the attributes DNS (or Vocola, I dunno) uses with PlaySound() . The disconnect happens with PlaySound() at the end of scripts, PlaySound() at the beginning of scripts seems fine. Seems there is another, small, cause. Might require setting the microphone to Default Device (not just Communication Device), or something else.

Edit: Still working on this, paying close attention. It's a little funky, but haven't found anything intelligible to report. I wonder if Vocola or Natlink changed or tried to enhance PlaySound(). Not an excuse for the Sennheiser firmware, but maybe a possible complication. Seems switching between the Presence and the MB Pro just requires some technique and a little patience. Must always have the microphone ON before toggling the DNS microphone icon ON. If not, by mistake, I toggle it off right away. When switching microphones, to the Presence, after choosing it from the list of microphones, seems DNS takes a little longer to process the switch.

Edit: Unless I'm missing something, the set up of both microphones is working reasonably well with the generic dongle, TP Link USB Bluetooth adapter (UB500).

August 28, 2023: Still using same. Still works. The worst problem is when starting DNS before the headset "microphone connected". Then... Shut down DNS. Turn off the microphone. Turn on the microphone. Start DNS. Must give it a couple of seconds when DNS is first started, before use. Again... Just need to make sure the wireless microphone is connected/on before the DNS program is made ready for dictation (turning on the DNS "microphone"). Similarly... The same problem happens when turning off the wireless microphone BEFORE turning off DNS. Same kind of situation. One learns not to do that.

32617 users are registered to the KnowBrainer Speech Recognition forum.
There are currently 0 users logged in.
The most users ever online was 12124 on 09/09/2020 at 04:59 AM.
There are currently 216 guests browsing this forum, which makes a total of 216 users using this forum.

FuseTalk Standard Edition v4.0 - © 1999-2023 FuseTalk™ Inc. All rights reserved.