Audio jack problems due to multiplicity

from Stardock Forums

I had some headphones plugged into my primary computer (running seamless) then switched them over to my secondary to listen to something as I'm not sharing audio between computers.

Now the audio jack isn't working on either computer.

Opening the sound devices, the headphones are showing up as a disconnected device (can't reconnect them) on my secondary only, and they are named with my primary's computer name.

I have tried uninstalling, reinstalling and updating the audio drivers to no avail. Anyone else had this problem before?

multiplicity
4,500 views 4 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your questions/problems to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

That doesn't sound like a multiplicity caused problem.  It does not install any audio drivers for audio sharing and no new devices will show on either computer.  It is purely a local capture solution.

Assuming sharing is disabled (otherwise when sharing the source computer will be muted) there should be no impact on audio what so ever.

It is going to sound like a silly question but are you sure the headphones have not developed a fault as that would explain them not working on two computers and unplugging will be the most likely time they would fail.

DeskScapes - Bring your desktop background to life.
Reply #3 from Stardock Forums Top

Yes, you're right and I initially thought that too but it's not just the one pair of headphones - the headphone jack essentially seems to have failed on both computers. No device is working on either computer now.

Reply #4 from Stardock Forums Top

Quoting leafyy1, reply 3

Yes, you're right and I initially thought that too but it's not just the one pair of headphones - the headphone jack essentially seems to have failed on both computers. No device is working on either computer now.
End of leafyy1's quote

The only thing Multiplicity could ever do is alter the jack detection and it will have only have asked about that if no output devices were detected.  It would also require you to confirm it as it is a prompt and it would have only have even checked that on the capture end and so not both computers anyway. 

If that is the case it can be undone with a registry edit, but it shouldn't stop a port working, purely make it always think something is plugged in so as to not be muted always.

An easy way to tell is to look for the following registry keys using regedit

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0000\GlobalSettings

There is a key called EnableDynamicDevices which would default to 1 (or possibly not existing at all)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96C-E325-11CE-BFC1-08002BE10318}\0000\Settings

There is a key called ForceDisableJD which would default to 0 (or again possibly not existing at all)

If those are not those values then you can set them to be that and reboot.

---

Or actually an easier way would be to go to Multiplicity audio, click advanced settings and untick the Disable Windows 7/8 jack detection if it is ticked as MP would then adjust that setting for you :)

Also remember whilst MP is set to share audio you will get no audio from the sending machine locally, only on the computer it is being sent to.