I often remote in to my PC with RDP. Instantly a pop up appears generated by FxSound that it has crashed. This is a handled error. This is a severe nuisance because when I use the PC through the console again I never remember to relaunch FxSound. Since the error is handled, why can’t FxSound simply suspend operation instead of crashing? Following that, if a connection event occurs, it can test to see if it’s the console to either resume or remain suspended. If there is no event for this, test every couple of minutes to see if resuming is possible.
never used RDP, my half-cent no-fact-based guess is it could be platform incompatible. maybe an application can crash in VM or remote control due to platform-not-supported? (but again, not sure how you use rdp in your case just cooked up a theory)
another cooked up idea: if you forget to never remember relaunch fxsound, try make a schedule task with conditional trigger or just a schedule to periodically relaunch fxsound (every hour starting the moment pc’s loged in, for example). I do this with some other stuffs that I absolutely needed them to not offing-themselves while I’m in middle of a task
@dmcdivitt In RDP FxSound Audio Enhancer device will not be available for FxSound to function. We can consider detecting RDP session and disable FxSound.
while I’m in middle of a task