Soundcard Test Results Thread

[Brendan1]

I recently updated my Google Earth to the new 5.0 beta and discovered what to me is a serious flaw: upon startup, it will reset your soundcard settings and mute the line input (in my case) so that DRM reception is stopped.

This bug issue has been sent to Google already by others, and it does not appear to affect all machines the same way. Previous settings are reset so that existing sound paths are disrupted. Others reported that Mic settings were muted and changed, in my case the Line Input was muted and the Mic selected as the audio input.

My DRM reception has been completely cutoff in mid-log, and that is not very good in my book! Hopefully this will be fixed in the 5.0 full release.

[mvs sarma]

Originally Posted by Brendan1

I recently updated my Google Earth to the new 5.0 beta and discovered what to me is a serious flaw: upon startup, it will reset your soundcard settings and mute the line input (in my case) so that DRM reception is stopped.

This bug issue has been sent to Google already by others, and it does not appear to affect all machines the same way. Previous settings are reset so that existing sound paths are disrupted. Others reported that Mic settings were muted and changed, in my case the Line Input was muted and the Mic selected as the audio input.

My DRM reception has been completely cutoff in mid-log, and that is not very good in my book! Hopefully this will be fixed in the 5.0 full release.

Now if you freshly install DRM software, it would restore while Google earth settings won't be spoiled.

[Brendan1]

Hello Sarma,

Thank you for the suggestion, I hadn't thought of that.

Unfortunately it didn't work here. The same problem occurs after a complete re-installation, so I think Google has some work to do. It's not a huge problem, but one that is an irritation nevertheless.