As I said in the other thread, there is some buggy code in the yp initialization. I have since removed that code so once the next version is out it should be fixed in the mean time. My yp initialization needs alot of work and unfortunately I am short on time.

To stop steamcast from using the yp ...

ok, I will get this patched up for the next version, I think this is the same bug that is causing problems in the Win32 version.

sc_trans_linux will only play local mp3s.

I do not know of many command line sourcing programs that will do what you need. Most people will figure out a way to get the source program to run at the location of the mp3's or move the mp3's to a better source location.

I have looked in my code and the error you describe is not something Steamcast is throwing. Although that doesn't mean it is not involved or some how causing this problem.

Does the error you describe display at the encoder or within the CLI window of Steamcast?

Could you post a screen log of the ...

for nsv use nsvtools www.nullsoft.com/nsv/ and either a shoutcast, icecast, or Steamcast server.

what type of video format do you want to use?

we utilize xml to send stats due to the multiple source capabilities a 7.html would just not be very good nor follow any particular standard.

go to http://localhost:8000/status.xml on your server to see an xml sheet server stats.

for an example of getting stats to work go to www.radiotoolbox.com ...

post your log.

well my goal currently is to get out a build once a month. My fear with going any faster is bugs not being caught and stability not truely being tested. My test server generally runs for about 2 weeks before I unleash them on the public.

I have fallen behind on development due some recent life ...

No, I have no release schedule, I do in my mind but not one I prefer to put in public view.

Development will end once some milestones are passed

1. Steamcast Administrator (API/Application)
2. On-Demand Support
3. Steamcast Stat Service

Once these are complete and some bugs are ironed out I will ...

well the next revision has a fix for this.

As with any beta program I really don't think it is production ready, although I really would like people to use it. The more people who use it, the more issues can be resolved and the quicker the pace of development time. On that note, I wouldn't replace ...

i have pretty much rewrote the code there. The problem is that there is an initial spike of data that is not accounted for. For now just disable that feature to keep it from knocking you off.

yes, I need to go through and do some heavier tests of the logging capabilities under multiple platforms. I think that once I get the GUI admin interface going this may become less of an issue as console logging won't be neccessary.

Windows Media is pretty much closed to only WMS platforms. Even then it can be tough as you have to proove your worthyness. I wouldn't waste time with it until you have a major following.

hmm, interesting, well keep me informed of the situation.