Build 256 issue

[abides]

I will start to use new build 256 but when i test it the client is goes "buffering stage" and stop at 2.nd second of the stream. There is nothing related in the server logs. Its just client is not continue to stream. (Client is Winamp)

Is there anyone else have similar issue with this new build?

[DrO]

email a DNAS log with full debug logging enabled which shows the issue happening as well as a link to the DNAS server and also the version of all players which are having issues to support @ shoutcast dot com and it'll be looked into next week (am technically meant to be on holiday as of this reply).

[neralex]

Same here and it's happen only in winamp while listening the stream. All other mediaplayers are working fine, also the embedded audio tags, flashplayers etc. Switched back to SHOUTcast Server v2.4.2.167/posix(linux x64).

[DrO]

still haven't seen any log from abides, whereas I've seen one from neralex but don't have much to go on in it. so as per my comment here, will be looking into this more thoroughly over the next few days.

[ram130]

Been testing in winamp for a while. Is your stream aac or mp3? I got a stream up here on the latest build. Test it in winamp and see if you get the same issues:

AAC: http://server.hitzconnect.com:8563/hitzcmobile
MP3: http://server.hitzconnect.com:8563/hitzchd

[neralex]

ram130, your installation works fine on my end. Which kind of source connection type you are using, v1 or v2? I will play again now a new round with this build. Maybe i can found more details.

Edit: Ok i have tested again with the same issue. I tried to play the stream with windows mediaplayer, VLC and the HTML5 audio player on the DNAS summary page without this issue. Only in winamp (latest version) it will stop the stream. As source i'm using the Transcoder/posix(linux x64) v2.0.0.64 with outprotocol=3 to get Ultravox/2.1 Source connection type: v2.

In the logfile of sc_serv aren't errors reported - tested with all enabled DEBUG options.

[DrO]

i've now reproduced the Winamp-specific playback issue with test streams neralex has provided me earlier this evening. ram130's streams work fine in Winamp as matches with neralex's observation.


so my initial thought is that it's likely to be a source specific issue (especially with a beta sc_trans being used) which is triggering the issue. whether it's then the DNAS at fault or not I cannot say for certain until further debugging is done.

but as it's affecting the only listener client I'm aware off that supports the 2.x listener protocol and the stream is being fed with a beta source running in 2.x mode, this may be a setup specific issue (based on a specific source, DNAS and client chain).


and it would be handy if abides could provide some more information on the setup being used so we can help determine if my postulation above is correct or not.

[DrO]

for those following this (as I've replied to neralex directly with more information), when the test stream which is showing the issue is relayed and the relayed version is then played by Winamp it works without issue. so we might be a bit closer to finding the cause of the issue...

[ram130]

ram130, your installation works fine on my end. Which kind of source connection type you are using, v1 or v2? I will play again now a new round with this build. Maybe i can found more details.

Edit: Ok i have tested again with the same issue. I tried to play the stream with windows mediaplayer, VLC and the HTML5 audio player on the DNAS summary page without this issue. Only in winamp (latest version) it will stop the stream. As source i'm using the Transcoder/posix(linux x64) v2.0.0.64 with outprotocol=3 to get Ultravox/2.1 Source connection type: v2.

In the logfile of sc_serv aren't errors reported - tested with all enabled DEBUG options.

Yes my source is V2. It seems your source is the issue. Maybe try V1.

[electroradio]

Same Problem, i use the source v1, now works!

[neralex]

electroradio, you are using also the transcoder or another source? Also based on linux?

[electroradio]

I use SAM Broadcaster with v1 source, works fine. but v2 source has this issue

[DrO]

the known issues has been updated regarding this issue as it has now been fixed internally.

the recommended workaround until a newer DNAS is released is to connect a source in v1 mode instead of v2 mode if the issue is being experienced. if not experienced then there is nothing needing to be changed.

[moucina]

Hello Guys,

I am experiencing the same issue on rpi dnas server . I am using sc_trans on linux 64 bit as remote encoder on another machine . However when I try to set outprotocol to 1 in sc_trans I can not get sc_serv to sc_trans connectivity . Only when outprotocol is 3 the two apps are happy with each other .

mo

[DrO]

you most likely need to adjust the source password so the stream connection on anything other than stream #1 will work when sc_trans is running in 1.x mode (as per http://wiki.shoutcast.com/wiki/SHOUT...Source_Support). there should also be error messages in both of the logs if that doesn't help as to the reason of the connection refusal.