Feedback in Metro apps, specifically xbox music

[Tom T]

Have a strange problem, when switching songs in xbox music app I get feedback, even though the sound is fine while playing. Noticed this also with a youtube app. At first I thought this has to be a hardware problem but when I accessed youtube through the desktop IE there is no problem. Also on the Metro side games are fine, no audio problems. Just curious if anyone else has experienced this, if not I am going to assume it is some app I've installed.

Really appreciate any thoughts.

 

[ArnoldC]

I can't relate to "feedback" but when I change tracks to NEXT or PREVIOUS there is no "noise" in between track change.

There was a time though, I think my second Patch Tuesday, that when I switch apps, I hear a loud distortion of the currently playing music before the switch over to another app. I just closed the Music app, re-started it and never occured since.

 

[Tom T]

Not sure if feedback is really accurate, but it is the same sound you get when you plug a guitar into a live amp before the plug is fully seated. It doesn't have anything to do with the jack though because it occurs whether you are using headphones or not....very strange. It just occured to me to try and access youtube through the Metro IE and see if occurs there.

 

[ArnoldC]

Yes, I understand that feedback (really hard to describe the sound), so if it's a short feedback, that sometimes sounded like a microphone feedback, but very short, I think I heard it too in the past right after an upgrade. I mentioned about distortion in my previous post, maybe they're related.

Have you tried a restart? Complete shutdown, then cold boot?

 

[tonyz3]

yep I been hearing this a lot since the update in the youtube app and a little in the music app. very slight but it is def there since the upgrade. Not all the time thought but I do pick it up or it is more noticeable when wearing headphones-

 

[Tom T]

Cold boot doesn't seem to help, I wish I could pinpoint exactly when it started, but it seems like it may have occurred after an update dated the 13th. Seems to me it was tagged as a system hardware update, but I will have to check.