similar to: on-demand source as default mountpoint

Hi icecasters, Is there a way to attach a static file to a source client without using the /file subdirectory? What I'm trying to do is have a static file broadcasted on-demand via http://fooblah:8000/, but I can't uses ices (I think) since that just throws the file to the server without any sense of timing. If I use ices, listeners could tune in during the middle of the static file,

/me grumbles about upcoming finals: I note that the mountpoint entry displays the current songs title and artist, but not the album. In the particular case of my station, album is often more important (recognizable) as there are a variety of pop/classical artists who do music for anime. So I'd like to add an album nature but am going to need a quick overview on how stats.xml is generated.

On Tue, May 11, 2004 at 04:21:07PM +0200, Marcos B wrote: > I am trying to set up a stream server for audio archives. > I've just tried Icecast2 / Ices, and it is really good stuff, > but I cannot yet get what I want : streaming on demand. Icecast isn't really designed for this. You could mount each file you want to host at a separate location and use individual ices instances

Hello, I have a problem with icecast icecast-2.0-kh8: - the source disconnect - icecast didn't notice it - the source cannot reconnect until - the source cannot reconnect (it tries every 8 seconds) - after two hours, the source is able to reconnect Here is the interesting parts of the log files: Thanks for your advices and help. Chris (icecast machine has +3sec in its time, that's

Hello ., maybe this could be again a stupid question... But I've tried over serval weeks to get a on demand relay stream from A southcast server. I have defined a mountpoint via an alias directive at the icecast.conf file. At the logfile a would recognize the two lines.. -->On demand realy for [.] -> [.] failed, damn! -->Kicking unknown 0 [.] [No encoder], connected for xx

>> This is how it looks. Source are mounted OK, when I try to connect with >> client it always connect to the same mountpoint (this time is /low) >Remind me - what client are you using? It mightn't handle mounts properly ... though I can't think of one that doesn't anymore. Winamp 2.81 Mitja --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project

can anybody explain to me the mountpoint that is mentioned by icecast version 1.3.12? I see that the mountpoint is /default what does this mean and how can I change it in the icecast.conf file. I am running this on a freebsd 4.7 STABLE release. - Noah <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from

> > > > MY QUESTiON -- if the main server is a relay for the studio , can i also > > connect local ices2 streams/mountpoints to it ? ? ie. a second, > > differently named set of dialup/hispeed.ogg mountpoints for the timed > > re-broadcasts . > > Yes, you can do that. <p>just lo0king at the ices2 .xml config now , i am (currently) using the /~msmith

After I installed the latest nightly build, it looks like the fallback works without rebuffering. I do see one problem -- when the main mountpoint stream restarts, the fallback continues to play. Once I stop the fallback mountpoint stream, the main mountpoint stream restarts, but only after client rebuffering Also, during the mountpoint switchovers, sometimes the meta-data is lost in the

I just was looking at the CVS nightly build of the icecast2\src\source.c and see that the mountpoint fallback is now implemented (compared to the 2.0.0 release's source.c) I was hoping to use this feature to support a multi-home radio station that has a master mountpoint stream and offsite "guest" mountpoints. These guest mountpoints would attach on a scheduled based and,

# icecast Icecast Version 1.3.12 Initializing... Icecast comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of Icecast under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. Starting thread engine... [05/Jan/2003:15:14:38] Icecast Version 1.3.12 Starting.. [05/Jan/2003:15:14:38] Starting Admin

With IceS2 this is easily accomplished by copying the 'ices-playlist.XML' file (I have 3 copies in the same directory with different names). Then define a new mount point in the xml file and point to a different play list file within the XML ( random can be enabled in the xml). Once this is complete, in terminal start ices2 with each xml. ~ $ sudo ices2 /media/music/ices-playlist_s.XML

Hi there. I wonder if it's possible (even non natively with icecast but some other tools/means) to connect to one mountpoint with more than one stream. What I want to do is a radio-show with two or more moderators or announcements from the server admin on some stream. I know that this _could_ sound wired if one plays rock, the second plays pop and the third tries to talk. But, given that we

In the ices-playlist.XML file there are two tags <logpath>/pathtofile</logpath> and <logfile>ices.log</logfile> You can choose a different name for each instance/stream: <logfile>mylist.log</logfile> Or you can change the path for the each instance/stream: <logpath/media/music/</logpath><logfile>ices.log</logfile> Just be sure the account

I've got a jukebox type programme streaming out through multiple Ices (0.4) sources, and an Icecast (2.2) server streaming to the listeners over the web. As a new user starts to play tracks on the jukebox, it writes a new ices.conf file (with the specific mountpoint, bitrate etc for that user) and spawns an instance of Ices to stream out that user's music. As it stands today Icecast

Hi! After closing the radio station app, the mountpoint keeps showing up on the admin page. Reconnecting is not possible. At reconnection attempt, the log file says: [2024-11-11 15:44:23] INFO connection/_handle_source_request Source logging in at mountpoint "/radio" from 87.141.43.247 [2024-11-11 15:44:23] WARN connection/source_startup Mountpoint /radio in use I tried different

It looks like default behavior is for Icecast to expose its web interface on the same address and port as any mountpoint. E.g.: mountpoint = https://server.com/listentome web app = https://server.com/ I'd like to restrict the web interface to ONLY A CERTAIN IP ADDRESS AND TCP PORT so that it is not accessible on the public IP. E.g.: mountpoint = https://server.com/listentome web app

> Well, a number of reasons. Dedicated streamers are better at streaming > audio/video than webservers, In theory. In practice this is not true. Apache is far more robust than any streaming server I've seen yet, and far more stable. Many of the scaling issues have been addressed, and the drawbacks are minimal. Streaming servers should be better for two reaosns. 1) they can be more

On 11/11/2014 01:58 PM, Payes Anand wrote: > Hi everybody, > > I am having a problem with the use of domfsfreeze command. > > It is freezing all the filesystems present on the domain, > > instead of freezing just the mountpoints provided. > > I am issuing the command-- > > # virsh domfsfreeze <domain> --mountpoint <mountpoint> > > Output

Hi guys > > Hi > > 2008/9/21 Jordi Sala <poperbu at gmail.com>: > >> Hi, >> >> Awstats (awstats.sourceforge.net/) or sawmill (http://www.sawmill.net/) do >> what you want. >> > > Webalizer - streaming version: > > http://webalizer.bzhtec.com/ > > Chip Scooter > > > I have tried webalizer but later my try I