similar to: MuSE 0.9.1 codename STREAMTIME

-----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

-----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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, May 04, 2004 at 07:42:52PM -0700, cloper wrote: > The reason I ask about the sound card is because i tried a few, like > muse, and it wanted a /dev/dsp which i could not get working properly. Hi cloper, did you tried with muse -o ? that deactivates usage of the soundcard. anyway, if /dev/dsp is not present, muse runs anyway.

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

I cannot connect MuSe (using line in) to my icecast server. I get thoses messages repeting : Internal buffer inconsistency. flushbits <> ResvSizebit reservoir error: l3_side->main_data_begin: 1640 Resvoir size: 1792 resv drain (post) 5 resv drain (pre) 0 header and sideinfo: 120 data bits: 679 total bits: 804

jaromil, > > > > wanted to ask again if someone has some online documentation on the > > icecast (or shoutcast) protocol at the socket/data level. > > have a look into MuSE/libmpeg/httpinput.cc (http://muse.dyne.org) > i hope that code can help you figuring out > No actually not. It just makes the connection to the shoutcast/icecast server. I've gotten this

On Fri, Mar 30, 2001 at 07:55:59PM +0200, Arvid Gregersen wrote: > and tell me that it is possible to make icecast broadcast titles or id3 > tags. I refuse to believe that you all can talk so fondly of a program > that gives you the ability to make a radiostation but not tell its > listeners what is on the air.. That is just too weird.. So what do YOU > do to tell people what they

> if you stream with MuSE (actually at the 0.6.1) you can easily specify > metatags as title, url and description from confortable input fields > embedded in the gui ( http://muse.dyne.org ). MuSE is GPL'ed software. Is that title dynamic (ie: does it change per song to list the song name)? Or is it a one time static thing? Louis --- >8 ---- List archives:

On Tue, May 01, 2001 at 07:50:52AM -0400, Andreas Schiffler wrote: > Hi all, > > wanted to ask again if someone has some online documentation on the > icecast (or shoutcast) protocol at the socket/data level. > > I'd like to write my own reader routine that can feed data to the mp3 > decoder. I've gotten as far as getting the actual stream after the GET > request,

On Friday 25 March 2005 16:01, Geoff Shang wrote: > Ondrej P. wrote: > > Is there a way to allow 2 or more DJs talk on the same station at the > > same time using Icecast2 ? > > Possibly. The two signals will need to be combined at some point, they > will need to be decoded and mixed together. http://muse.dyne.org > The latency of Ogg Vorbis or > MP3 makes this

-----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

We are running an icecast2 server in conjunction with our LPFM radio station and need a little advice. We have been serving a single 128k ogg stream from a remote server and would like to make additional formats available (e.g. mp3, lower bandwidth, etc.) I would think this has been done a few thousand times and there would be a "best practice" but I can't find it. Our basic

On Thu, 11 Apr 2002, Beau D. Simensen wrote: > in any event, if there are some great alternatives to liveice or darkice out > there, i'd be happy to look into them. i was extremely happy to have found > ices a few months ago. it had been there all along, just not described or > explained very well. i'm guessing there is something else out there i just > didn't notice

I was actually thinking of implementing something like this for ices, Such that the user could dynamically request songs to be streamed to the server. Makes it easier for wrapper applications (such as jukeboxes) to control the stream rather than relying on files and SIG's for RPC. Is there anything like this being planned? B At Tuesday 04:27 PM 4/2/2002, jaromil wrote: >On Tue, Apr

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

On Tue, Apr 02, 2002 at 11:57:45AM +0200, Andrea Glorioso wrote: > >>>>> "j" == jaromil <jaromil@dyne.org> writes: > > j> as it is today, xml-rpc bindings are available for several > j> languages: * Python, Java, Perl, TCL, ASP, COM, PHP, Zope, > j> AppleScript, REBOL, * Dylan, Common LISP, Real Basic, UserLand > j>

On 1/23/08, jaromil <jaromil@dyne.org> wrote: > nope. we have a freej specific mailinglist, see http://lists.dyne.org Ah, so sorry. > freej is statically including theora-mmx or offering to be dynamically > compiled to system-wide theora libraries (so the issue is then > delivered to the distribution) Most distros should be already using the latest beta, so that should

-----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 re all, these days we're busy on freej development with a final release hopefully due in july, including a full suite for video compositing and streaming in javascript (xulrunner 1.9) and python (c++ -> swig), see debian pkgs: http://packages.debian.org/sid/libfreej-dev we will also have a carbon/osx (and native quicktime) free

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 re all, this patch has not been integrated in Debian yet, hence the Icecast2 package still segfaults after filling up all the memory with its leak. as this is a critical bug, while it seems that the current Debian mantainer for the icecast2 package has abandoned its duty, i'm kindly asking the attention of debian developers included