troubles with the audio

Hello,

I have issues with the audio part of multiplicity.

My config:

2 computers under windows 10:

- the main: laptop which is listening

- the slave: desktop which is sharing

The 2 computers are on the same subnet => subnet that is putted as private network. No special security on hte network)

 

The connection to the audio work than after a while there is no audio going out anymore. The rest of the program(moving the mouse, sharing files,... ) still works.

The only solution I found was to restart multiplicity on the main computer.

Tests that I made:

disabling the share audio on boths one by one and on both in same time => didn't repaired

trying to change the passcode and putting it back on the slave => didn't worked

switching the share audio from the slave & the main than putting it back => did not worked

tryed to switch off the firewall (which if I'm not wrong can't be the problem because the problem would be from begining than no?) => did not fixed

- I didn't tryed yet by VPN network => if needed I can make the test

 

The feeling I had was that the process to share the audio switched off but it's the slave who is sharing and the main who is getting the audio and it's the main who I restart to fix the issue.

So I tryed to restart the process on the main by disabling the receive option but it failed.

 

Could you pleas fix it because it a bit borring.

Thanks

5,528 views 7 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

When this happens, see if turning off \ on the sender resolves it:

Sean Drohan
Stardock Support Manager

Reply #4 Top

Quoting katlarouge1995, reply 3

I already tried but it did not fixed it.
End of katlarouge1995's quote

What about on the receiver as well?

Sean Drohan
Stardock Support Manager

Reply #5 Top

I tryed on both.

The only way I found was to restart totaly the app or restart the process.

Reply #6 Top

Hello,

Sorry to hear you are having trouble.

I will forward this on, thanks for the feedback.

Sean Drohan
Stardock Support Manager