Syndicated_Death

This issue keeps cropping up. This was my system utilization at the time it occurred on a wired 1gb Ethernet connection.

Sorry for venting on you! Sounds like you're stuck between a rock and a hard place. I was so used to MP being so seamless. When the issues started cropping up I quietly worked through them. The solves built over time and whittled my patience. Thanks for the service restart request in the taskbar icon. It does help. Also, thanks for the script!

That makes sense. This was expected behavior 5 years ago. Something changed. I don't know if it's how multiplicity handles sleep events or audio stack issues. I used to put both of my machines to sleep every night and in the morning they worked flawlessly. log in without extra effort and audio pass-through without interruption. Granted, 5 or more years ago I wasn't using audio over HDMI with potential HDCP issues. Working with new parameters

I applied the settings for no sleep ever. things improved on log on. screens blared the log on screen all night. is this power efficient and is this the default stardock stance?

Neither of my machines sleep despite the sleep settings. they stay on 24x7 Primary Secondar

Recurring issues are at this point.... Secondary audio send issue. At first audio from secondary required a refresh from the secondary side via "check" and "uncheck", "send audio when receiver is online" to the point I pinned "multiplicity audio" to the secondary "notification area" expecting to do this daily. This pivoted to needing to pin the "Multiplicity" icon to the "notification area" on the primary to "Restart Multiplicity processes" daily

Dead thread?

Just thought I would chime in and say I've also had the same issue. All computers are on a wired connection. Some times it happens when I'm using both machines. Sometimes when I unlock my machines in the morning, audio isn't working. Unchecking and checking, "Send audio when receiver is online." brings audio back. On a side note the service for "multiplicity audio" on the primary hasn't been running when I unlock in the morning. it's happened twic