Has anyone got it working? is the password <username>:<password> like sctrans v1 or is it different?

Have you tried stopping and starting it a few times? On certain installs of the alpha I had to start and stop the stream when I setup a sc_trans v2 stream.

I don't know why though, but it seemed to work fine after that.

Tried doing that no difference

Please explain exactly what you are trying to do?

Is it just create a new server with shotcast V2 and Sc_trans V2? I presume you have had no problems creating the server, it just never starts up?

If so, have you tried creating another stream and uploading different media to rule out your server?

He's trying to broadcast live - has anyone been able to do this, what dj port do we use? Some instructions would be great!
I also use a "2nd auto dj type", and it provides a special "dj port".
It uses the older SHOUTcastv1 and sc_transv2
 -- with Centova Cast v3, it seems to only allow either SHOUTcastv1 and icess_cc or SHOUTcastv2 and sctransv2.......or is there a way?

And why won't my Flash player work? Is anyone else having problems with the built in flash players?
http://174.127.115.165:2199/start/auto/

They work using Icecast and icess_cc - -- but not SHOUTcastv1 and icess_cc

Are you referring to WHMSonic??

As far as I'm aware for Centova, there is no need for seperate DJ port. You use the same port as the stream is on (Just like with Centova 2.2.4)

Centova 3.0 only allows Ices-cc to be used with Shoutcast V1 and Sc_TransV2 to be used with ShoutcastV2

Sadly, only Steve can answer development questions and he is away (Please don't think I work for Centova in any way because I don't! but I have been using the new product for months now in alpha conditions)

I have also setup 2 relays, 1 uses shoutcast V1 and the flash player doesn't work, the other uses shoutcast V2 and the flash player works fine so I am guessing this is a bug...

Mark

Thanks Mark, that explains a lot -- I was even looking in the configs for a dj port #!!
Yes, the flash players work with SHOUTcastv2 and Icecast, s --so it must have something to do with SHOUTcastv1, glad it's not just me!! 

Right basically what i mean is centova cast v3 supports sctrans v2 which in turn supports auto dj override, this means that you do not need to disconnect the auto dj to be able to stream a live show.

I have been trying to get this to work however i am having problems with the connection...

Now i have recently had the problem in which sctrans v2 is crashing when the server starts.

It says the server has started and i press play on the auto dj and the auto dj just stops.

hope that answers the questions you have about the problem occurring

Yes SC2 and sctrans2 has only worked once for me, gave up on it for now -- also had high loads using it and with the last.fm -- I disabled that and all DB errors are gone now

With SC1 and icess_cc  -- does any1 also have this problem

http://174.127.115.165:8002/

The stream url is stuck at icecast.org --and the station is not listed in the SC directory


Also, it would seem if we set up a cron to run every 5 min and run /etc/init.d/centovacast restart -- it would correct a lot of problems -- such as current listeners, it only works if you restart or reload

Im probs just going to stick using whmsonic until everything is working properly... best way to deal with it

He's trying to broadcast live - has anyone been able to do this, what dj port do we use? Some instructions would be great!
I also use a "2nd auto dj type", and it provides a special "dj port".
It uses the older SHOUTcastv1 and sc_transv2
 -- with Centova Cast v3, it seems to only allow either SHOUTcastv1 and icess_cc or SHOUTcastv2 and sctransv2.......or is there a way?

im broadcasting right now. everything works fine for me. indiecore.net (using centovacast3 and shoutcast2)

not trying to bump or anything but the beta has survived spikes of listeners from 0-83 without delay. But sometimes it will crash with high number of listeners.

As far as I'm aware for Centova, there is no need for seperate DJ port. You use the same port as the stream is on (Just like with Centova 2.2.4)

sc_trans v2 provides its own DJ port that you use if you want to fade cleanly from autoDJ to live broadcast and back.  Nothing to do with CC.

The instructions for doing this are provided in the sc_trans v2 documentation.

Sadly, only Steve can answer development questions and he is away (Please don't think I work for Centova in any way because I don't! but I have been using the new product for months now in alpha conditions)

True, but this is an sc_trans v2 question, not a CC dev question.

not trying to bump or anything but the beta has survived spikes of listeners from 0-83 without delay. But sometimes it will crash with high number of listeners.

Listeners are served by your ShoutCast server, not Centova Cast... there is no interaction between listeners and CC so regardless of how many listeners you've got, there is no possibility of them crashing CC.