Login to the steamcast web panel. Can you see your xml sheet in your browser?

You will need to provide your mount username and password not the admin. Apart from that you will need to contact Spacial with your issue because we have no control over listing in that directory nor did we have anything to do with the statistics relay product.

What you should look into is voice tracking. The idea is you pre record your voice segments and then layout the play order and do the transitions. Since you are using SAM check out this article. http://support.spacialaudio.com/wiki/SAM_Voice-Tracking

Just a quick update, the online log grapher has been updated to zoom for those with tons of listeners, this helps with graph readability.

It's only going to get nicer, if there is anything anyone at all would like added to the panel, now is the time.

Flash doesn't really handle SHOUTcast well on it's own at this point. The caching done by the browser is detrimental to the process. You will need some sort of server to be a middle man between flash and shoutcast.

To a client such as winamp, no there is no difference.

We have made some updates to the forum board system. This upgrade allows us to stay current and as secure as possible. Several services rely on the phpBB system to authenticate you for service. If you have any troubles with these services please let me know so I can correct any issues.

Either method involves upload speed. The only difference between 'push' and 'pull' is who/what initiates the source connection (server or source encoder).

You will need to contact your host provider and ask them where your server is located.

This is likely because you did not include http:// preface to the web url in your encoder. You will need to do this.

Unfortunately this information doesn't help me, I need logs any activity surrounding the crash, reproducibility, etc.

I would say that this is due to the 64bit environment. The out of memory error is strange.

that seems reasonable.

Has anyone gotten steamcast to work successfully in a 64bit environment? Also you might try disabling some of your mounts until the crash goes away to see if we can pinpoint a source.