Displaying 20 results from an estimated 3000 matches similar to: "Too many "too many errors""
2004 Aug 06
0
Too many "too many errors"
Let me explain more of my testing.
I take the same laptop (a cheap compaq). I point winamp at my icecast
server, which is one hop away (frame relay T1). After 30-40 min I get
stuttering and eventual disconnect.
I point same winamp on same laptop to random icecast server(s). It's
fine for more than 2 hours, at a higher bitrate even. (I am
broadcasting at 40kb, I tested rates at 96 and 128kb.)
2004 Aug 06
1
Too many "too many errors"
Jack Moffitt <jack@icecast.org> writes:
> Are you using shout?
No, using winamp with the shoutcast plugin to get audio from an analog
stream.
------
Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org
>>> The opinions expressed above are entirely my own <<<
"You have rights antecedent to all earthly governments; rights that
cannot be repealed
2004 Aug 06
4
Too many "too many errors"
$ egrep "Too many errors" icecast.log | wc -l
975
$ egrep "client not receiving data fast enough" icecast.log
975
$ egrep "Accepted" icecast.log.0 | wc -l
4076
Hmm. I tried a windows laptop box (kinda slow) and indeed after about
30-40 minutes playback starts stuttering and eventually disconnects
from the icecast server.
Nothing else is running on this
2004 Aug 06
0
Too many "too many errors"
I have a patch that will fix your stuttering problem, apply to version
1.3.10.
In src/sock.c line 533, replace the original line (return n;) with
this:
return (t==0) ? n : t;
This will not help you if your client is legitimately not able to
receive data fast enough, but should correct the stuttering.
If you want more information, or a "proper" patch, let me know.
Mark
$
2004 Aug 06
3
Too many "too many errors"
> In src/sock.c line 533, replace the original line (return n;) with
> this:
>
> return (t==0) ? n : t;
>
> This will not help you if your client is legitimately not able to
> receive data fast enough, but should correct the stuttering.
>
> If you want more information, or a "proper" patch, let me know.
Didn't I apply this patch to cvs?
jack.
2004 Aug 06
1
Why doesn't yp.icecast.org show my stream?
Jack Moffitt <jack@xiph.org> writes:
> What are you trying to do that you get that error?
I sent an improperly formatted URL to your server. I've corrected this
since. =)
> id=69 is the normal success code. You'd get -1 if it failed I think.
> What's your ip address? I'll go check the logs.
The ip address of my streaming server is 216.133.255.2
> Other
2004 Aug 06
1
Why doesn't yp.icecast.org show my stream?
Jack Moffitt <jack@xiph.org> writes:
> Now I see the problem. This will not cause anything to show up. You
> have no sources.
Eh?
-> sources
Listing sources
[Id: 509] [Sock: 14] [Time of connect: 18/Feb/2002:20:55:14] [IP:
205.147.43.110] [State: 1] [Type: pulling relay] [Proto: x-audiocast]
[Clients: 2] [Dumpfile/fd: (null)/-1] [Priority: 0] [Song Title: ] [Song URL:
2004 Aug 06
5
Too many "too many errors"
> > Hmm. I tried a windows laptop box (kinda slow) and indeed after about
> > 30-40 minutes playback starts stuttering and eventually disconnects
> > from the icecast server.
> >
> > Nothing else is running on this box. What gives? Why am I losing about
> > 25% of the connections to this error?
>
> Are you using shout?
Let me clarify here with the
2004 Aug 06
1
Why doesn't yp.icecast.org show my stream?
Dave Hayes <dave@jetcafe.org> writes:
> Darkice has:
> public = yes
> So I check darkice:
> Icecast.cpp:
> ...
> str = "\nx-audiocast-public: ";
> sink->write( str, strlen( str));
> str = getIsPublic() ? "yes" : "no";
> sink->write( str, strlen( str));
> and then icecast:
> ....
> else if
2012 Apr 24
1
Attempting to boot into ramdisk on 8.3
I have a build process (which worked at release 7.3) that makes a
bootable ISO using a ramdisk image as the boot volume. At release 8
it panics right after reporting the real memory size with:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
...
[thread pid 0 tid 0 ]
Stopped at pmap_enter+0x19a: moveq (%rcx),%r14
(I have the text frozen on
2004 Aug 06
0
Why doesn't yp.icecast.org show my stream?
Once again, I'm clueless as to what is going on because I don't have
the source or logs to yp.icecast.org. I am touching yp.icecast.org fine:
[14/Feb/2002:01:39:22] directory_touch_xa([yp.icecast.org:80])
completed...server id = 69
but my radio station isn't shown. More details on my setup:
xmms -> darkice 0.7 -> relay icecast server -> main icecast server
2004 Aug 06
0
Bad stuttering with Winamp 2.80
Jack Moffitt <jack@xiph.org> writes:
>> > If you've isolated it to winamp, why complain here? :)
>> I wasn't complaining. I was attempting to see if anyone else had seen
>> this problem.
> I was joking :)
Heh, wasn't sure. The tone of the list had been down lately...
> Does streaming from a web server have the same problem? I assume you
> tested
2004 Aug 06
1
Why doesn't yp.icecast.org show my stream?
[Reposted here, silence on the icecast list, is this deliberate?]
Once again, I'm clueless as to what is going on because I don't have
the source or logs to yp.icecast.org. I am touching yp.icecast.org fine:
[14/Feb/2002:01:39:22] directory_touch_xa([yp.icecast.org:80])
completed...server id = 69
but my radio station isn't shown. More details on my setup:
xmms -> darkice
2004 Aug 06
1
1.3.11 instability on MIPS?
Mike hodson <mystica@darktech.org> writes:
> Is there any way I could debug why the server unexpectedly dies?
It's simplistic, but have you tried forcing all icecast code to
compile with gdb support enabled, then running it in GDB?
------
Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org
>>> The opinions expressed above are entirely my own <<<
2004 Aug 06
3
Bad stuttering with Winamp 2.80
The only thing that has changed is the winamp version number. My
radio streams are unaltered (to the point of the same process
connecting to two versions of Winamp).
What happens is that I begin to hear skips in the stream. Soon the
stream is full on stuttering, as if a square wave was modulating
the volume control.
Anyone else experience this?
------
Dave Hayes - Consultant - Altadena CA, USA
2004 Aug 06
0
FreeBSD in general
Matt Boersma <boersma@genomica.com> writes:
> from 0.8 - 2 % CPU time and about 4MB of resident memory. I even
> "renice -10" it at the suggestion of someone else on this list.
> Lame (or another encoder) will be by far the biggest CPU consumer.
Have you tried rtprio at all? I understand this may be the only thing
running on your box, but still...
> If you don't
2004 Aug 06
1
[SOLVED] Re: [icecast-dev] Why doesn't yp.icecast.org show my stream?
Just following up to myself here so this will be in the archive
for people.
The problem was in darkice 0.7. There is a patch required to make
it comply with the x-audiocast-public "standard". You can get the
latest CVS to fix the problem.
------
Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org
>>> The opinions expressed above are entirely my own <<<
2004 Aug 06
0
using in home LAN
the Arioch <Arioch> writes:
> I think that the folllowing options could be very good to see:
> 1) list of enabled/disabled ip masks for clients
...
I thought you could set this kind of stuff up in the config file?
> 1) list of our LAN servers (to choose one to connect on launch)
> 2) ability to request from current server list of online servers
> 3) filtering list 2) throug
2004 Aug 06
0
Step by Step
timf <Tim> writes:
> What would be really helpfull is if someone could give me a step by
> step guide to getting a Multicast Stream up and running.
One of the tools you have to use is non open-source (gasp) and
available from www.live.com. If anyone knows any real open source
tools, please let me know. =)
If you can hold out a bit, I am getting Yet Another DVMRP tunnel "any
day
2004 Aug 06
0
admin 'rehash' broken in icecast 1.3.12?
Beau D Simensen <simensen@halogen.org> writes:
> I tried admin rehash for the first time since upgrading to 1.3.12 today. The
> rehash took at least 30 seconds [If not longer -- I didn't time it very
> closely] and icecast slowly snuck up to 99% CPU usage. I tried issuing the
> 'alias' command just to try and get a response from the console and that
> never