Back to Blog
Chrome remote desktop sound not working7/26/2023 ![]() ![]() Keeping my ASIO DSD setup, I found that there were some recent updates to third party components:Īlso, I found a newer FFmpeg Decoder Wrapper v. I am using ASIO DSD feeding a Simaudio DAC via USB.įirst, as suggested, using a normal output method, the behaviour does not seem to appear. DSF files in this example, the problem occurs with all formats. Opening track for playback: "I:\Music\R\Miklos Rozsa\Three Choral Suites \03 - King Of Kings\21 - King of Kings Resurrection and Finale.dsf" / index: 1īTW, although these are. Opening track for playback: "I:\Music\R\Miklos Rozsa\Three Choral Suites \03 - King Of Kings\20 - King of Kings Pieta.dsf" / index: 1 Opening track for playback: "I:\Music\R\Miklos Rozsa\Three Choral Suites \03 - King Of Kings\19 - King of Kings The Lord's Prayer.dsf" / index: 1 The Foobar console logs show little difference between a 'successful' exit and a 'bad' exit. ![]() If I start Foobar from within a remote session using the laptop, when I exit that session, the Foobar problem comes up. If I start Foobar directly from the source machine (the PC), I can go in with Chrome Remote Desktop from the laptop and do whatever I want (even within Foobar), and when I exit, everything is fine. One observation (that I am trying to confirm definitively): Foobar also does not crash at this point. It sort of mimics what happens when you unplug a drive, or have some other failure in reading the source file, except that no error messages are displayed. The audio simply cuts out, and the remainder of the playlist is run through (at > 2x speed) until the end of the playlist is reached. When Foobar shows this behaviour, there are no "unrecoverable playback errors" generated, and no "not responding" messages.
0 Comments
Read More
Leave a Reply. |