similar to: MuSe problem

Help!! I compiled liveice on a more-or-less stock RH 7.1 (2.4.2-2) server install. It starts, appears to connect (to a Shoutcast server), lame runs using an appropriate CPU %, lists OK on yp.shoutcast.com - but clients can't connect properly (ICY 200 OK then stalls) - & the liveice console "vu display" is blank. With VERBOSE 10 I get: l3_side->main_data_begin: 1064 Resvoir

Sorry, I know it's marginally unrelated to icecast, but it most certainly affects all American citizens interested in MP3/Ogg Vorbis: http://dailynews.yahoo.com/h/zd/20011018/tc/why_the_riaa_owes_us_all_an_apology_1.html What the hell do they think they're doing? -- Nate "sublime" Kohari --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

lundi 27 mai 2002, 07:27:32, Akos Maroy a écrit : > Matt Boersma wrote: >> on the average of every couple weeks. I tried darkice, but it doesn't >> deal with lame correctly. So I wrote a script to resurrect liveice when > Could you elaborate on this? In what respect does darkice not deal with > lame correctly? Personnally I have those error messages repeting with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <p>On Sun, Dec 08, 2002 at 08:28:41PM +0100, Thai DANG wrote: > Pardo Juan Fernando wrote: > >Somebody can answer me wich stream is better...Liveice or Muse ? > > I tried MuSe, it works well but : > - the interface is a bit slow when it is streaming (especially for > adding songs dynamically) > - I didn't manage to

On Tuesday 13 January 2004 03:04, Mihai RUSU wrote: > Hi > > I have recently downloaded icecast 2 (I am an old icecast 1.x user) and > tried to use it with my ices 0.2.3 (which works on icecast 1) but fails on > login. Also I have tried with MuSe 0.8.1 and same error too. After some > digging into the sources I found the problem to be with _check_pass_icy() > which receives a

Pardo Juan Fernando wrote: > Somebody can answer me wich stream is better...Liveice or Muse ? > > --- >8 ---- > List archives: http://www.xiph.org/archives/ > icecast project homepage: http://www.icecast.org/ > To unsubscribe from this list, send a message to 'icecast-request@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Michael and thanks for answer! On Tue, 13 Jan 2004, Michael Smith wrote: > This shouldn't be being passed to _check_pass_icy() at all - this isn't the > "icy" (shoutcast nasty ugly) protocol at all. We support that (icy) protocol > because it's widely used - but it's a horribly ugly hack to pretend that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I have recently downloaded icecast 2 (I am an old icecast 1.x user) and tried to use it with my ices 0.2.3 (which works on icecast 1) but fails on login. Also I have tried with MuSe 0.8.1 and same error too. After some digging into the sources I found the problem to be with _check_pass_icy() which receives a "strange" pass to compare

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 annunciazio' annunciazio'! dyne.org autoproduzioni & the FreakNet Medialab proudly present: __ __ ____ _____ ___ ___ _ | \/ |_ _/ ___|| ____| / _ \ / _ \ / | | |\/| | | | \___ \| _| | | | | (_) || | | | | | |_| |___) | |___ | |_|

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 annunciazio' annunciazio'! dyne.org autoproduzioni & the FreakNet Medialab proudly present: __ __ ____ _____ ___ ___ _ | \/ |_ _/ ___|| ____| / _ \ / _ \ / | | |\/| | | | \___ \| _| | | | | (_) || | | | | | |_| |___) | |___ | |_|

I'm a volunteer who runs the mp3 streaming for KGNU-FM in Boulder, Colorado. We stream live at 64K with Linux, icecast 1.3.12+ minor patches, liveice, and lame 3.92. It easily supports 32 internet listeners 24x7 from a donated 400MHz Pentium II. Liveice is the only problem--it does its job of connecting the soundcard rec in to the lame encoder and to icecast, but dies without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <p><p>re all! about the running question (as i read on the http://icecast.org website in the 3rd party software section) if MuSE is working with icecast2, here is the answer: it definitely does :) the problem was fixed a couple of months ago in the CVS code, now we have a new stable release which will get hopefully soon properly packaged

On 13.11.20 13:22, Paul C. Anagnostopoulos via llvm-dev wrote: > Your suggestion for two passes is indeed my plan if simply using 3-byte sizes is not acceptable. I don't want to duplicate all the logic in a second length-calculating function, so I would just have special logic for the three matching operators with children and use the existing function for the rest, passing a null output

Would it make sense for TableGen to generate the outer OPC_SwitchOpcode offset table? At 11/13/2020 07:53 AM, Nicolai Hähnle wrote: >That said, if we are seriously thinking about the performance of the byte code, perhaps some of these opcodes should be reconsidered at a higher level anyway. > >For example: The overall bytecode always begins with an OPC_SwitchOpcode implemented as a

I took a look at all the OPC_SwitchOpcode operators in the matching tables. Almost every target starts with a large one, which is now cached by the interpreter. Instead, TableGen could build the opcode -> offset table. But there are also many other opcode switches with between 10 and 70 cases. To speed these up, we could embed a sorted opcode -> offset table right in the matcher code. Or,

Yes, we can. But I think either solution is going eliminate the relaxation step completely, Either we will always use 3-byte sizes or we will make a first pass to size everything and then a second pass to emit the code. Either way, no relaxation is necessary. >Can we skip the relaxation step if comments aren't being emitted? >Comment emission is off by default in CMake configuration.

I'm toying with the idea of writing a Samba-oriented Win95/98/NT logon window. I know it's possible to replace Windows' logon mechanism with another. Novell's Client32 does this. I know there's also standards to make a network service available to Windows' change-password mechanism (so I can fire smbpasswd on the other side). That could be an alternative to establishing

As a perpetual Rails dabbler, I make an awful lot of typical beginner mistakes. And the logs are always either too verbose or too sparse to help me. And it started me thinking. I came from one of the largest production OLTP systems in the world, and the one thing that helped us manage troubleshooting in both development and production was extensive, obsessive, flexible logging. Every operation

Your suggestion for two passes is indeed my plan if simply using 3-byte sizes is not acceptable. I don't want to duplicate all the logic in a second length-calculating function, so I would just have special logic for the three matching operators with children and use the existing function for the rest, passing a null output stream. Or I could conditionalize all the output on another function

IMHO, our big picture challenge is that multiple explanations for several topics are spread out over several different docs and pages One parameter is frequently discussed in four or more places (QSG, files reference pages, file comments, main documentation, etc.) That gives multiple perspectives, which can be good, but can also lead to at least the appearance, especially to a beginner, of