Displaying 20 results from an estimated 6000 matches similar to: ""no encoder" error"
2004 Aug 06
1
"no encoder"
Hi,
I am a new user of icecast, and need help with the set up.
I am streaming two independent streams with shout (mount 1:shout1, mount
2:shout2). Icecast accepeted both streams on mountpoints /shout1 and
/shout2. I tried to receive each stream with Winamp using
"<a href="http://<IP">http://<IP</a>>:8000/shout1" and "<a
2004 Aug 06
0
"No Encoder"?
Hi,
the answer can you find in the manual.
Set the port of your WinAMP client to 7999.
There is the manual part:
2. Configuration file (icecast.conf)
-port
This is the port the icecast server uses for all connections. Admins,
clients, and sources, they all connect to this port. The old behavior,
having the clients on 8000 and the encoder on 8001, is too ugly and creates
some problems with
2004 Aug 06
0
"No Encoder"?
What's happening in IPF ? Got any log info there?
<p>> ----- Original Message -----
> From: Marcelo Gulin <marcelo@gulin.com.ar>
> To: <icecast@xiph.org>
> Sent: Tuesday, April 09, 2002 11:44 PM
> Subject: [icecast] "No Encoder"?
>
> Hi guys!
>
> Thanks to your help I've my IceCast/LiveIce server up & running but
> I´m
2004 Aug 06
2
"No Encoder"?
Hi guys!
Thanks to your help I've my IceCast/LiveIce server up & running but
I´m still having problems:
My IceCast server is on the internal LAN and it's NAT'ed behind an
OpenBSD IPF firewall. Here's my network setup:
Internet ---- [OpenBSD firewall] ---- hub ---- [IceCast server]
| |
+
2004 Aug 06
3
"No Encoder"?
Hi!
Sorry! I forget to mention that port 8001 it's open at the firewall
too. So winamp should work fine with this configuration.
Thanks anyway Kurt!
Any other ideas?
Marcelo Gulin
<p>-----Original Message-----
From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org] On Behalf
Of Kurt J. Dreistadt
Sent: Miércoles, 10 de Abril de 2002 06:43 a.m.
To: icecast@xiph.org
Subject: Re:
2004 Aug 06
4
Problems streaming high bitrate over a LAN
I am trying to stream various 320kbps MP3s across my 10Mbps LAN. Either locally
or across the network, freeamp and xmms prefetch a chunk, then play it, then
fetch another chunk etc. No continuous streaming. shout gets a lot of !s between
its "."s when sending the file to icecast. Any ideas?
--
Always hardwire the explosives
-- Fiona Dexter quoting Monkey, J. Gregory Keyes, Dark
2004 Aug 06
2
Problems streaming high bitrate over a LAN
On Fri, May 25, 2001 at 10:43:33AM +0200, Martin Hierling wrote:
> HI,
>
> sounds like my problem discussed her two or three weeks ago.
> Add "sleep_ratio 0" to your icecast.conf.
>
> regards Martin
Thank you very muchly. It works now. Any idea how to synchronize 2 players on
the same stream? End up with ~ 1 s phase difference. NAS might be more
appropriate...
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
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
0
kicking " client not receiving data fast enough "
Hi there !
As i tried that radio finally installed, i got that message from the
server after ~ 1 minute ...
I reduced and forced the streaming to 44000 instead of the 128000
proposed as default_bitrate in shout.conf.
Now i can listen for 12 minutes and 46 seconds before i got the message.
what's going on ? Should i modify the throttle parameter ?
I have a DSL access for information
2004 Aug 06
0
Problems streaming high bitrate over a LAN
toad wrote:
> I am trying to stream various 320kbps MP3s across my 10Mbps LAN. Either locally
> or across the network, freeamp and xmms prefetch a chunk, then play it, then
> fetch another chunk etc. No continuous streaming. shout gets a lot of !s between
> its "."s when sending the file to icecast. Any ideas?
You're probably hitting up against a limitation of the OS
2004 Aug 06
0
Problems streaming high bitrate over a LAN
HI,
ounds like my problem discussed her two or three weeks ago.
Add "sleep_ratio 0" to your icecast.conf.
regards Martin
--
----------------------------------------------------------------
/"\
\ / ASCII Ribbon Campaign
X Against HTML Mail
/ \
----------------------------------------------------------------
- Martin Hierling -
2004 Aug 06
0
Problems streaming high bitrate over a LAN
Hi,
On Fri, May 25, 2001 at 09:44:28PM +0100, toad wrote:
> On Fri, May 25, 2001 at 10:43:33AM +0200, Martin Hierling wrote:
> > HI,
> >
> > sounds like my problem discussed her two or three weeks ago.
> > Add "sleep_ratio 0" to your icecast.conf.
> >
> > regards Martin
> Thank you very muchly. It works now. Any idea how to synchronize 2
2004 Aug 06
1
AW: Icecast1: "Client din't data fast enough"
Hello Geoff, Hello Hagen,
I have also this problem, I use shoutcast with shout. on a Sun SPARCServer 5
with 170 Mhz, and I don't know what I can do. Making higher buffering at the
server-side ?!? but where ?
Using a better Maschine (Sun Ultra60 with 2x450 UltraSPARCII Processor) its
the same problem: the stream is broken with "Client din't data fast enough"
in Logfile. I hear
2002 Apr 03
2
format of http stream?
I am streaming ogg via inetd. Basically, I am outputing like:
oggenc -Q -b 1 -o - /some/wave/file.wav
This works fine with ogg123 (other than that I want the bit rate to be
lower than 55-100 range that it is doing).
I am using:
Ogg123 from vorbis-tools 1.0rc2
OggEnc v0.8 (libvorbis rc2)
But, FreeAmp for Windows slowly buffered up to 100% then said "Skipped
Corrupted File".
And
2004 Aug 06
0
Problems with xmms & freeamp
At 11:59 PM 2/3/02 +1100, you wrote:
>
>Hi all,
>
>I've just set up a test icecast2 server (download and compiled from cvs
>about an hour ago) - very simple setup, all it does is use ices to stream
>in an .ogg file that I converted from an mp3, using mpg123 & oggenc.
>(I've used the sample conf files with the directory stuff removed. I've
>also tried it
2001 Oct 03
0
Launching OGG streams
Hi all:
;I wish to raise something that has, in my opinion, not been properly dealt
with. With the iminent release of icecast2 and vorbis 1.0, I feel that it
needs to be sorted out.
The problem is that of how to launch an ogg stream from a web browser. In
short, what metafile should be used, or do we need to invent our own? Let
me illustrate the problem. Using MP3 streaming as an example, we
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
2
connection problem
I am pretty sure that the integrity of my mp3's is okay. I know that music
match shreds the mp3 data and produces mp3 files that are not ISO compliant.
I always use WaveLab and the radium codec to encode my sets and enable the
ISO compatibility option at all times. This problem only seemed to come
about with winamp 2.7 but if sonique is doing it to, I don't know...
What about relaying? Do
2000 Jul 25
2
Library issues (BOUNCE vorbis-dev@xiph.org: Non-member submission from [rob@emusic.com]) (fwd)
BTW, I need a volunteer to upgrade xiph.org to MailMan or the like. I'm
officially sick to death of majordomo.
(Or, if you want to code all the features I want in majordomo, that's fine too
;-) I'm a little bit out of time, see....
------- Forwarded Message
Sender: robert@emusic.com
I just brought the FreeAmp codebase up to speed with the latest Vorbis
source. In doing so,