last.fm – Soundcard busy or not present: Just restart it!
- Wednesday, March 4, 2009, 10:39
- Computers, Internet, Music, Tips & Tricks
- 1,370 views
- 2 comments
From what I’m gathering, there seems to be quite the amount of people getting the “Your soundcard is either busy or not present.” error when trying to listen to last.fm’s radio.
I didn’t pay much attention to it until it started happening on a more regular basis and, well, annoying me. At first it would show the error every other day and then play normally, but recently it’s every single time I turn on my pc.
This error happened to me on more than one computer and a quick google search told me that I wasn’t the only one! I don’t know if last.fm is working on this, but the quick-fix solution is quite simple: just do what it says!
Restart the application like it says on the error dialog and you’re be fine! But don’t forget that last.fm’s scrobbler minimizes and closes itself to your system tray, so to really close it you’ll have to go there, right-click the last.fm icon and choose “Exit” from the menu.
After doing that just start the scrobbler again and everything should work great. I never had a second error (in the same windows session) after fully restarting the application.
Again, this is not a solution, just a quick fix to get you by… 
Related posts
About the Author
Hugo Sousa has written 129 posts on this site.
Hugo is a software developer, specialized in PHP, SQL and .NET technologies. He started coding out of curiosity and need for a small temporary website and instantly fell in love with development. With a passion tech, gadgets, movies, tv shows and photography, Hugo tries to find time to write about as much topics as possible.
Comments (2)
Trackbacks
Write a Comment
Gravatars are small images that can show your personality. You can get your gravatar for free today!
I’ve used last.fm for thousands of hours without ever seeing that error. Then today, after tweaking XP, I can’t get rid of it. I killed last.fm (I even checked to make sure the process wasn’t running). Now I have to start trying to figure out what service I stopped that’s causing the problem. I already looked, and it’s not obvious… If I even figure it out, I’ll come back to add an update.