I agree this is a bit of a gimmick, however a 30 seconds delay (or 10 seconds delay as seen here) is still sometimes useful.

The other features you mentioned are great too, and will also improve this plugin.

XM online updated their website last night, and since then, when I listen to a stream through foo_XM, it throws an error with the Microsoft Visual C++ Runtime Library, mentioning that foobar2000 has requested the runtime to terminate it in an unusual way. (rowr) ahem.

Anyway, looks like they made some change that is causing things to barf and fall over.

Interestingly enough, once I ignore the error and move the window off the screen telling me about it, everything works just peachy fine.

I just uploaded a new version 1.2.1 to the foo_xm site a few minutes ago that should fix the recent problem. They changed the format of the channel list and caused a runaway regular expression. Thanks.

Hot damn, thanks!

@ FrozenSpoon

Can you please rebuild foo_xm with the latest fb2k SDK so it will be compatible with 0.9.6 b1 on vista?

Thanks in advance!

I just uploaded 1.2.1.1 which should work on 0.9.6 beta + Vista. However, I don't have Vista to test on so let me know if it is still broken.

It seems to have done the trick, thanks!

I would love to have a sirius plugin for foobar. Please

Hey, I just noticed that since Sirius screwed everything up I can't see XM 202 on the main list when I update it. Did they break things?

Hard to justify doing this now that the channels are almost completely the same.
Grab the newest 1.2.2 version from the website. The new channel data was larger than I expected it to be and missed out on the last few channels.

@ FrozenSpoon

While running the latest version (1.2.2) after some hours of playback of some XM channel, the memory usage of foobar increses to several hundreds of megabytes (in some cases close to a gigabyte of commited bytes)

When stopping the playback, and playing a regular mp3, the memory is getting released.

Any idea why this is happening?

Sounds strange, I'm not seeing that behavior. I just played a channel for 3 hours and memory usage was ±100KB of when I started. What foobar version and Windows version are you using? (hard to believe those would make a difference though)

Any chance you can list the components you have installed? Have you added/updated any recently? Pure conjecture, but I'm wondering if a different component is leaking and it's only really noticeable when playing a track for hours. It may be worth playing a plain Internet radio station for several hours and see if it too is showing this problem.

Donno if its related, but try this:

Start a regular stream, and press pause, after 1 minute press resume. Notice the lack of change in memory usage.

Now start an XM stream, and do the same procedure, notice the sudden rise in memory usage.

Yes, well, when paused the component "acts like a tivo" which is arguably wrong, but then again, could be useful.

Unless you had been pausing during the track when the memory usage was spiraling out of control, this behavior is unrelated.