Multiplicity is not working when gpu is connected to soundbar to provide audio

I have a Nagamachi 9.2 soundbar with 4k and HDR passthrough capability.  There is no way to turn off this passthrough capability on the soundbar.  My secondary computer is connected to a monitor via DP 1.4 from an AMD 5700 GPU to provide video.  The secondary computer is connected to the soundbar via a high speed 2.1+ HDMI cable from the same GPU to provide sound.  Thus there are two cables coming out of the GPU--one DP, and one HDMI.  When I connect the GPU to the sound bar, the GPU recognizes the soundbar and gives me the option to use the soundbar as an audio device.  The screen will black out for less than a second and returns to normal function.  However, Multiplicity simply does not work-- either the mouse flickers or lags horribly, or the mouse disappears.  Multiplicity works normally once I disconnect the GPU from the sound bar.  Again, the screen will go black for less than a second and return to normal function.  I can connect the secondary computer to the sound bar with an analogue connector without problems.  But I won't be able to utilize the sound bar's advanced Dolby Atmos functions.  This error is 100% reproduceable.  

I believe it is a software issue.  The connection of the secondary computer via GPU to the sound bar via HDMI interferes with the functioning of Multiplicity.  Does anyone know what's going on?  If there is no solution, then Stardock please fix it.  

Other than this problem, I love this program.  It is so much better than a real KVM switch.  

I have the KM product for $20 bucks, not the KVM product for $40 bucks.  You think upgrading will resolve the issue?

 

2,581 views 4 replies
Reply #1 Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 Top


This error is 100% reproducible.  
End of quote

There is just no way I could create your environment to test with. What I dont understand is how anything to do with sound would affect MP.

For the GPU, I guess I would see if there were driver updates.

Sean Drohan
Stardock Support Manager

Reply #3 Top

The primary computer uses NVIDIA HD audio from the primary GPU to the sound bar via HDMI 4k/120mHz.  The primary GPU is connected to the primary monitor via DP 1.4.  The secondary computer uses AMD HD audio from the secondary GPU and is connected to the same sound bar via HDMI 4k/120mHz.  The sound bar has 4k pass through.  Whenever I turn on the appropriate HD connection on the sound bar to the secondary computer, there is a momentary black screen--as if the soundbar is taking over video.  But this screen resolves.  The secondary monitor only gets feed from the  secondary GPU not the sound bar.  I am not sure whether Multiplicity is being fed twice -- both to the monitor and sound bar.  And it is this double feed that may be causing the problem.  There is no video to coming from the sound bar.  If MP is dependent on the video feed from the sound bar, it just won't get it.  And it just won't work.  But removing the connection to the sound bar while keeping just the GPU to monitor connection permits MP to work again.  I guess I was wondering if there was any way to control what feed MP uses.  

Reply #4 Top

Quoting 1samurai, reply 3

The primary computer uses NVIDIA HD audio from the primary GPU to the sound bar via HDMI 4k/120mHz.  The primary GPU is connected to the primary monitor via DP 1.4.  The secondary computer uses AMD HD audio from the secondary GPU and is connected to the same sound bar via HDMI 4k/120mHz.  The sound bar has 4k pass through.  Whenever I turn on the appropriate HD connection on the sound bar to the secondary computer, there is a momentary black screen--as if the soundbar is taking over video.  But this screen resolves.  The secondary monitor only gets feed from the  secondary GPU not the sound bar.  I am not sure whether Multiplicity is being fed twice -- both to the monitor and sound bar.  And it is this double feed that may be causing the problem.  There is no video to coming from the sound bar.  If MP is dependent on the video feed from the sound bar, it just won't get it.  And it just won't work.  But removing the connection to the sound bar while keeping just the GPU to monitor connection permits MP to work again.  I guess I was wondering if there was any way to control what feed MP uses.  
End of 1samurai's quote

While this is not easy to follow, the 'feed' for KVM connections is what is sent by the Secondary.  If you have both the primary and secondary connected to a common device that is involved in handling video, then that indeed could be a cause.

Sean Drohan
Stardock Support Manager