I've been thinking about this a bit more... What about using the title at the top as a hot spot? Right now, touching the title when you're not in the music source that's serving it takes you to that source (e.g., if XM's playing it takes you to XM, if an MP3 is playing it takes you there...). So what about if you touch it when you're IN the host module you write the track info to a file?

I have one final request for XM functionality. Again, on this one, I'm not sure if yours or David's area:

Right now, the only way to stop XM audio is to either switch to other media, or close Centrafuse. Well, in most circumstances, my routine is to, while listening to XM, close CF and hibernate my pc. When I return and start up CF, XM audio automatically starts since that's what was playing when I closed CF. This is actually a great feature, BUT, sometimes I want to have control of this and tell CF that I don't want any audio at all playing when I open it. Currently, the only way to do this as far as XM audio is concerned, is to switch to mp3, then stop the mp3, then close CF. In other words, there's no manual way to stop XM audio once you're in the XM module.

The solution? A simple Stop button for XM. This is what they have in SD. When I'm exiting SD, I hit the stop button first, and XM audio stops. Then when I return to SD, no audio is playing until I tell it what to do.

Looks like there is an issue when using XM in buffered mode, and another user verified in another thread that they have it too: When listening in buffered mode, after a few minutes (maybe 3) the title bar on the top left of the screen changes to "Buffered Audio, " and it will not change back to the name of the song unless you change the channel, then change it back to the station you were on. After that, another 3 mins goes by, and same thing all over again.

I assume you need a log. I'll get you one as soon as I get back to the car.

Should be fixed in the next release, code handling this and a whole bunch of other things is MUCH improved.

Can someone post me the log.txt file in the DocsAndSettings/LocalSettings/AppData/Centrafuse/Plugins/SatRadio folder? The item of interest in the log when this happens is the text "PowerMode Change:", if this text is not in the log file, then CF is not properly emitting the resume event. If it's in there, it's a problem with the satradio dll. We can also see whats happening in the log after the event is received.[COLOR=#a31515]

I'll go get this file, but I suspect that CF isn't sending the event.. There are other things that are hosed after a resume. (Nav voice being one of them) I dropped a note in the main thread about that a while back.

Just a side note the SatRadio software in the next release is a very stable, much improved release, better response times for everything like changing channels, etc, lower CPU usage, in some cases CPU usage has been reduced by 15%, very satisfied with the latest build..

Can someone post me the log.txt file in the DocsAndSettings/LocalSettings/AppData/Centrafuse/Plugins/SatRadio folder? The item of interest in the log when this happens is the text "PowerMode Change:", if this text is not in the log file, then CF is not properly emitting the resume event. If it's in there, it's a problem with the satradio dll. We can also see whats happening in the log after the event is received.

I have an issue with my SPDIF-In, and SIRIUS... It stays on even though I go to MP3 music, and doesn't mute. Having my MP3's playing at the same time as my SIRIUS is a little un-nerving. I saw this issue earlier in the thread, and I will try to repeat it this morning on the way to work to make sure it is not a fluke.