server
- Thread starter bubbles
- Start date
first double check all the format settings are correct as well as username/password/port;
also check the Centova panel to confirm your server is started and can accept the source [having access to more than one PC or a multi display computer helps, as well as friends who can check the other stuff (they can be in different locations to where you are, as long as they can contact you (an analogue telephone is still useful at least for this; as it will work even if the broadband doesn't; mobiles can make noise/interference on some audio equipment if brought too near)
also check the Centova panel to confirm your server is started and can accept the source [having access to more than one PC or a multi display computer helps, as well as friends who can check the other stuff (they can be in different locations to where you are, as long as they can contact you (an analogue telephone is still useful at least for this; as it will work even if the broadband doesn't; mobiles can make noise/interference on some audio equipment if brought too near)
try connecting from the same computer or one on the same network using some different streaming software like Eddcast Reborn or BUTT (links below)
that can isolate whether the problem is with VDJs built in client or elsewhere. One thing to beware of is certainly Shoutcast can be fussy about metadata and stream URL fields etc being supplied (either by Centovacast or your streaming client, or a combination of them) to the point it refuses to accept incoming streams and gives back strange messages like "bad answer" or "broken pipe" - which your client may or may not relay back to you (it may just say "cannot connect").
https://code.google.com/p/edcast-reborn/downloads/list
http://butt.sourceforge.net/
that can isolate whether the problem is with VDJs built in client or elsewhere. One thing to beware of is certainly Shoutcast can be fussy about metadata and stream URL fields etc being supplied (either by Centovacast or your streaming client, or a combination of them) to the point it refuses to accept incoming streams and gives back strange messages like "bad answer" or "broken pipe" - which your client may or may not relay back to you (it may just say "cannot connect").
https://code.google.com/p/edcast-reborn/downloads/list
http://butt.sourceforge.net/