Run DO - UNDO command when Client gets connected disconnected, not just Starting and Quitting Session

[RebelliousX]

Is there an existing issue for this?

• I have searched the existing issues

Is your issue described in the documentation?

• I have read the documentation

Is your issue present in the latest beta/pre-release?

None

Describe the Bug

Related to #3430 but different issue.

I downloaded SetVol app from here on github and added command for DO and Undo like

For Do:

C:\temp\SetVol mute

For Undo:

 C:\temp\SetVol unmute

Which works great. The issue is, the UNDO command doesn't run when the client gets disconnected, but only when session quits. That is, if I minimize Moonlight, the client disconnects, streaming stops, but Volume still muted. If I open Moonlight and force session to quit, the Undo command runs.

I also have similar issue when running VDD trying to run UNDO command when client disconnect, for example Moonlight on Shield TV (session is on, just Moonlight minimized). The Undo command to switch back to main display doesn't run until I force quit the session from Moonlight. The host's main displplay remains black until I force quit the session even if Moonlight is disconnected.

I would like to have an option to do that, that is to Run DO and UNDO commands when client gets connected and disconnected. if changing current behavior is not feasible, at least, add and option to do so on these events.

[ReenigneArcher]

Duplicate of https://github.com/orgs/LizardByte/discussions/408

[RebelliousX]

@ReenigneArcher excuse me, sorry if I sound like a jerk, but a duplicate of an unanswered not in issues but a discussion post from 10 months ago? Probably it is better imo to leave this issue opened.

[ReenigneArcher]

This is a feature request, and we keep those in discussions.

"Issues" are for bug reports.

There's a few reasons we track feature requests outside of issues.

1. Issues are automatically closed after 100 days with no activity, and feature requests are very likely to hit this. In "discussions" they remain open until added or rejected.
2. Other user's can upvote the requests.
3. I don't want the ~110 open feature requests added to the issue list.

[RebelliousX]

Makes sense, thanks.

[RebelliousX]

With the help of ChatGPT, it wrote a PowerShell script within a minute that works beautifully

This is script will run a specific batch file when client is connected, and another when disconnected:

$logFilePath = "C:\Program Files\Sunshine\config\sunshine.log"
$connectedBatchFilePath = "C:\Temp\muteVolume.bat"
$disconnectedBatchFilePath = "C:\Temp\UnmuteVolume.bat"
$matchPatternClientConnected = "CLIENT CONNECTED"
$matchPatternClientDisconnected = "CLIENT DISCONNECTED"

# Check if the log file exists before proceeding
if (-Not (Test-Path $logFilePath)) {
    Write-Error "Log file does not exist: $logFilePath"
    exit
}

# Monitor the log file for new content
Get-Content $logFilePath -Wait | ForEach-Object {
    if ($_ -match $matchPatternClientConnected ) {
        # When the pattern is matched, execute the batch file
        Start-Process -WindowStyle hidden -FilePath $connectedBatchFilePath
    }

    if ($_ -match $matchPatternClientDisconnected ) {
        # When the pattern is matched, execute the batch file
        Start-Process -WindowStyle hidden -FilePath $disconnectedBatchFilePath
    }
}

Batch files just run SetVol.exe unmute or SetVol.exe mute preceded by @echo off and the program can be downloaded from github.

As executing the PowerShell script, probably Task Scheduler with "Run whether user logged in or not" will prevent terminal from showing up when executing the script at startup.