similar to: /usr/bin/wish - required

Displaying 20 results from an estimated 9000 matches similar to: "/usr/bin/wish - required"

2004 Aug 06
2
Problem with livice
Trying to get livice to work on my FreeBSD system..major 'n00b' so bear with me :D <p>When I run ./livice I get the following ------------------------------------------------------------- /local/liveice/temp.playlist ...... done setup_pipes()... Initialising pipes for stream 0 Successfuly set up fifo .liveice_temp_files/raw.pipe0 Successfuly set up fifo
2004 Aug 06
2
Icecast and Liveice
you need to create a .m3u file to launch the media player. In this file you should have 'protocol://url:port#/mountpoint' ex: in my 'ices.m3u' I have: http://stream.goingcreative.net:8000/houze <p>Once you are done point your browser to the .m3u file to launch your media player <p><p><p><p> ----- Original Message ----- From: Jose Julian Buda To:
2004 Aug 06
6
Problem with liveice
It's an Icecast 2 server which appears to be running fine (in that I can get status.xsl up in the browser) and using the latest Liveice tarball from http://star.arm.ac.uk/~spm/software/liveice.html <p>>From: EvilOverlord <eviloverlord@kucs.net> >Reply-To: icecast@xiph.org >To: icecast@xiph.org >Subject: Re: [icecast] Problem with livice >Date: Wed, 25 Feb 2004
2004 Aug 06
1
Icecast and Liveice
<quote who="Jose Julian Buda"> > From: <ronnie@mixsessions.com> > > you need to create a .m3u file to launch the media player. In this > > file you should have 'protocol://url:port#/mountpoint' > > > > ex: > > in my 'ices.m3u' I have: > > > > http://stream.goingcreative.net:8000/houze > > in what directory do
2004 Aug 06
2
syntax for playlist
I should be more specific . What I meant to ask was - is it necessary for the directory that icecast streams or serves files from to "everyone" or the "world" have at least read permissions. I do plan to experiment with the permisions but I was just asking to see if any one had already tried this. I like to lock down my system as much as possible. Thanks for the help!
2004 Aug 06
1
format icecast.log to html
Could you elaborate on what you mean by "http log analysis tools out there on icecast log files"? <p>----- Original Message ----- From: Michael Smith To: "icecast@xiph.org" <icecast@xiph.org> Sent: Tue, 29 Apr 2003 12:28:06 +1000 Subject: Re: [icecast] format icecast.log to html "ronnie@mixsessions.com" <ronnie@mixsessions.com> said: > > I
2002 Nov 07
4
icecast + liveice won't play nicely
I have gotten icecast and live ice both up and running, but I cannot get them to play nicely together. I have the following in my configs: icecast: -- encoder_password test admin_password test oper_password test port 8000 port 8001 -- liveice: -- SERVER 192.168.1.2 PORT 8001 PASSWORD test #ICY_LOGIN X_AUDIOCAST_LOGIN -- but when I run both of them using: ./icecast ./liveice I get (from
2004 Aug 06
3
icecast 1.x vs icecast 2
There isn't much info on the website...I guess I was expecting some beter documentattion. ----- Original Message ----- From: Michael Smith <msmith@xiph.org> To: icecast@xiph.org Cc: Date: Subject: Re: [icecast] icecast 1.x vs icecast 2 On Wednesday 19 February 2003 14:01, ronnie@mixsessions.com wrote: > okay those are good reasons but where can I get more info > > The
2004 Aug 06
1
format icecast.log to html
I am currently using icecast 1.3x. I would like to know if there is a way I can dump the contents of 'icecast.log' into html or maybe format variables to create an html doc. I looked through my icecast manual but I couldn't find any info or variables used for the log file. Ultimately what I want is to see who, when, and how long it takes to dl a static file. <p><p>---
2004 Aug 06
2
xslt-config
after running sh autogen.sh and Icecast begins to complie (is this the correct term) I get the folling: .. checking for getaddrinfo... yes checking for inet_pton... yes checking for xslt-config... no configure: error: xslt-config could not be found Could some one please explain. Thanks ! <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:
2004 Aug 06
0
/usr/bin/wish - required
Thanks everyone for the quick response was Tk / Tcl <p><p><p>----- Original Message ----- From: Rakotomandimby Mihamina To: icecast mailing list <icecast@xiph.org> Sent: 14 Mar 2003 23:42:32 +0100 Subject: Re: [icecast] /usr/bin/wish - required <p>> > I believe this is Expect, the scripting language. is not wish a Tk shell or Tcl shell ? --- >8 ----
2004 Aug 06
1
IceS playlist & directory ?
Greetings Is it possible to command IceS to play from a directory instead of creating a playlist with several hundred mp3's. I have read through the threads and notice that Ices can do some great things but I am swithching from a Win2k environment so I am not familiar with python and perl. Is what I am asking possible? Is there some one willing to share scripts created for Ices?
2004 Aug 06
1
icecast 1.x vs icecast 2
okay those are good reasons but where can I get more info <p>----- Original Message ----- From: "Michael Smith" <msmith@labyrinth.net.au> To: <icecast@xiph.org> Cc: Date: Subject: Re: [icecast] icecast 1.x vs icecast 2 ronnie@mixsessions.com said: > upgrade to icecast2? Should I? > > > I have found alot on info on icecast 1.x. I am familiar with how
2004 Aug 06
1
compilling error ices-0.2.3.tar.gz
sorry about that. I decided to install the latest ices from cvs instead. However I encountered another problem. I have the latest libshout, icecast and ices. All were compilled without problems. I am trying to stream in mp3 format but when I run ices I receive errors that read something similar to '/path/to/mp3file/song.mp3 - possibly corrupt or malformed data'. The entire playlist will
2004 Aug 06
1
compilling error ices-0.2.3.tar.gz
Ooff! I am using ices2. Well that explains it then! I am new to linux and I thank you very much for your help and patience. Please just some clarification. To get cvs version of ices for mp3 streaming compatibilty with Icecast2: cvs -d :pserver:anoncvs@cvs.xiph.org:/cvs/ice login pw:anoncvs cvs -d :pserver:anoncvs@cvs.xiph.org:/cvs/ice -z 9 co ices or cvs -d
2004 Aug 06
3
icecast + liveice won't play nicely
Kerry. I would like to get a copy of this document which you speak of. I have had generic trouble in getting livice properly installed and think that would do the trick... ----- Original Message ----- From: "Kerry Cox" <kerry.cox@ksl.com> To: <icecast@xiph.org> Sent: Thursday, November 07, 2002 10:22 AM Subject: Re: [icecast] icecast + liveice won't play nicely
2004 Aug 06
0
Icecast and Liveice
in what directory do i need to put this .m3u file? <p><p>----- Original Message ----- From: <ronnie@mixsessions.com> To: <icecast@xiph.org> Sent: Monday, April 07, 2003 1:32 PM Subject: Re: [icecast] Icecast and Liveice <p>> > you need to create a .m3u file to launch the media player. In this file you should have > 'protocol://url:port#/mountpoint'
2004 Aug 06
1
compilling error ices-0.2.3.tar.gz
thnks for the clarfication. I downloaded libshout2 and ices-0.2 from cvs. I compiled libshout with out a problem but when i try and compile ices I get the following error: <p><p>checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether -lc should be explicitly linked in... no checking shout/shout.h usability... yes checking
2004 Aug 06
1
icecast 1.x vs icecast 2
upgrade to icecast2? Should I? <p>I have found alot on info on icecast 1.x. I am familiar with how to use it and what it can do for me. I may be looking in the wrong places but I feel info on icecast 2 is limitted and sometimes confusing. Is there anyone out there that can direct me to info on icecast2. Or maybe explain what the big advantage would be to change or upgrade to version 2. I
2004 Aug 06
1
mount points & multiples streams II
I have done some experimenting but if am incorrect I would like someone to correct me. I am trying to run multiple streams so what I have created additional directories such as mrock24, mRock64, and mRock128 in the '/etc/ices' directory . In these directories I have placed new conf files and playlist files respectively streaming 24, 64, and 128. These directories are also the name of the