Quote:
Originally Posted by R-Capi
Thanks for the info. I'm going to start testing the XM stream in more detail. My concern is that this might be a Windows Media Player issue, because I simply fetch the URL from XM and pass it to the embedded player. Why it locks up my application is yet to be determined.
It could take a few days of testing before I can reproduce this with enough regularity to fix it.
|
I'm kind of agreeing with you on the WM part. It must be in the way that you're incorporating it with your code, instead of sending a URL to the player itself.
I've also noticed that with this version, it can take a good 30 seconds to respond to a command sometimes. I said before that I stream all day. By streaming all day, I risk draining my battery really fast, so I keep it on the USB charger (USB to PC, with USB connections disabled in Activesync). This keeps me charged and listening to music while at work.
When I'm ready to leave for the day, I do one of two things. I either hit stop and then disconnect the cable, or I disconnect the cable and then hit stop. Either way, it doesn't seem to respond to my command.
Yesterday, because it wasn't responding from me hitting stop, I hit the X to close the application (x-button feature, close applications on x). The player closed, but the music continued to play.
Whenever this happens, I tend to later see that the program is still running in the background, but no music is playing.
Now that I think about it, it's almost as if the media player part is "taking over" it's application presence in the task manager. Kind of like a shell or something. So when I hit x, it's only closing the media player.