Displaying 4 results from an estimated 4 matches for "nsplayer".
Did you mean:
splayer
2005 Dec 23
1
WMP mp3 stream trouble
...short (7 seconds) and are piped over and over
again.
It works fine with iTunes, RealPlayer, Winamp5.x, VLC, Whamb, but not WMP!
Here's a typical failed connection from the icecast access log
x.x.x.x - - [23/Dec/2005:12:28:24 -0700] "GET /slack HTTP/1.1" 200
14770 "-" "NSPlayer/10.0.0.3923 WMFSDK/10.0" 2
x.x.x.x - - [23/Dec/2005:12:28:29 -0700] "GET /slack HTTP/1.1" 200
45010 "-" "NSPlayer/10.0.0.3923 WMFSDK/10.0" 5
x.x.x.x - - [23/Dec/2005:12:28:29 -0700] "GET /slack HTTP/1.1" 200
7350 "-" "Windows-Media-Player/...
2018 Sep 22
0
How possible is Icecast get 2 different agents from TuneIn App?
...We have implemented auth url in our icecast instance.
So, i installed the Android TuneIn app in my phone, opened it, search for
our radio and tapped play. The request come from a load balancer that
redirect to the icecast server. But, looking at the logs we saw:
Load balancer: User-Agent=NSPlayer/10.0.0.3702 WMFSDK/10.0
X-Real-IP=177.33.155.000
Icecast: ip=177.33.155.000&agent=Lavf/57.25.100
Why the Icecast is getting a different agent (ie ExoPlayer don't have the
same behaviour)? VPN? Proxy?
Best,
Thiago
-------------- next part --------------
An HTML attachme...
2005 Aug 23
2
Cannot listen to shoutcast mount point
...o Icecast using shoutcast streaming source and
stream the mp3 source to Icecast, however whenever I attempt to listen
to the stream at the specified mount point (/channel1), I get a 404 file
not found error. \
The access.log shows:
"GET /channel1 HTTP/1.1" 404 109 "-" "NSPlayer/9.0.0.3250 WMFSDK/9.0" 0
The important part of my icecast.xml is listed below, from the original
configuration, I changed the ip for the hostname and bind-address only.
<hostname>192.168.71.5</hostname>
<listen-socket>
<port>8000</port>
<...
2004 Aug 06
5
Missing headers in Icecast2
Hi Karl,
Thanks for your help,
About the "Connection:" header, you are right, it's:
"Connection: close" and NOT "Connection: keep-alive". The protocol when the
SERVER sends the data is http 1.0. It's http 1.1 when the browser requests
the data.
I don't understand the "Content-Length: 54000000" header either. Also I
noticed the flash player on