Closed gumaerc closed 1 year ago
Thanks for the detailed bug report. At the moment the application uses audio events and state to help determine when a Parsec session starts. A few months back I was working on a version that didn't use audio at all. I was planning on finishing that version eventually anyway. No time like the present.
I also have this issue, any potential workaround we can do ourselves in the meantime? :)
Nothing I can think of beyond unplugging/disabling the device it's having trouble with.
Obviously that's not a great solution. I should have an updated version available for download in a month or so.
If you feel like compiling the current code branch yourself, the preview_3_0 branch has the most up to date version. Everything seems to be working now, but no promises I won't break something between now and release 😅.
If you don't have it, you can download Visual Studio Community for free. You'll also need the Microsoft Visual Studio Installer Projects 2022 extension if you want to build the installer.
Fixed in version 3.0.0.
OS: Windows 10 21H1 19043.2006
Log output:
It looks like it's crashing when scanning audio devices or something? I have a ton of connected audio devices: