Hello, Thomas_B._Rücker, ======= At 2019-09-09, 08:36:43 you wrote: ======> >I am not familiar with a file called "icecast_run.xml". >Could this be a local modification to your installation? > >You should be able to check which one is used by opening the >"icecast.bat" file that you are using to start the server.aha!! You nailed it! I have no idea why but the package I downloaded months ago (Icecast v2.4.3) came with the batchfile premade and the actual configs seem to be this oddly named file... (I recall being confused as to why there would be TWO config files, but I've seen stranger things in the past so I editted both to reflect my needs...) So here is the actual working config: Now I don't see anywhere in which I can put the extra mount points (nor do I recall a port designation for the 2nd stream mentioned at all tonight). <icecast> <hostname>wilder Zone</hostname> <location>My Wilderness</location> <admin>wilderzone.radio at gmail.com</admin> <shoutcast-mount>/rock</shoutcast-mount> <listen-socket> <port>8080</port> </listen-socket> <listen-socket> <port>8081</port> <shoutcast-compat>1</shoutcast-compat> </listen-socket> <limits> <clients>20</clients> <sources>4</sources> <queue-size>524288</queue-size> <client-timeout>30</client-timeout> <header-timeout>15</header-timeout> <source-timeout>10</source-timeout> <burst-on-connect>1</burst-on-connect> <burst-size>65535</burst-size> </limits> <authentication> <source-password>NotaRealPassword</source-password> <relay-password>NotaRealPassword</relay-password> <admin-user>admin</admin-user> <admin-password>NotaRealPassword</admin-password> </authentication> <http-headers> <header name="Access-Control-Allow-Origin" value="*"/> </http-headers> <fileserve>1</fileserve> <paths> <logdir>./log</logdir> <webroot>./web</webroot> <adminroot>./admin</adminroot> <alias source="/" destination="/status.xsl"/> </paths> <logging> <accesslog>access.log</accesslog> <errorlog>error.log</errorlog> <loglevel>3</loglevel> <logsize>10000</logsize> </logging> </icecast>>_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast= = = = = = = = = = = = = = = = = = = Best regards. Foxxe wilderzone.radio.2 at gmail.com thewilderzone.sytes.net wilderzone.radio.2 at gmail.com 2019-09-09
Multiple streams are generally separated by the path that is used to access it, they all run on the same port. This is determined by the stream source when it connects to the server On Mon, 9 Sep 2019, 11:35 wilderzone.radio.2, <wilderzone.radio.2 at gmail.com> wrote:> Hello, Thomas_B._Rücker, > > ======= At 2019-09-09, 08:36:43 you wrote: ======> > > > >I am not familiar with a file called "icecast_run.xml". > >Could this be a local modification to your installation? > > > >You should be able to check which one is used by opening the > >"icecast.bat" file that you are using to start the server. > > aha!! You nailed it! I have no idea why but the package I downloaded > months ago (Icecast v2.4.3) > came with the batchfile premade and the actual configs seem to be this > oddly named file... (I recall being confused as to why there would be TWO > config files, but I've seen stranger things in the past so I editted both > to reflect my needs...) > > So here is the actual working config: > > Now I don't see anywhere in which I can put the extra mount points > (nor do I recall a port designation for the 2nd stream mentioned at all > tonight). > > <icecast> > <hostname>wilder Zone</hostname> > <location>My Wilderness</location> > <admin>wilderzone.radio at gmail.com</admin> > <shoutcast-mount>/rock</shoutcast-mount> > <listen-socket> > <port>8080</port> > </listen-socket> > <listen-socket> > <port>8081</port> > <shoutcast-compat>1</shoutcast-compat> > </listen-socket> > <limits> > <clients>20</clients> > <sources>4</sources> > <queue-size>524288</queue-size> > <client-timeout>30</client-timeout> > <header-timeout>15</header-timeout> > <source-timeout>10</source-timeout> > <burst-on-connect>1</burst-on-connect> > <burst-size>65535</burst-size> > </limits> > <authentication> > <source-password>NotaRealPassword</source-password> > <relay-password>NotaRealPassword</relay-password> > <admin-user>admin</admin-user> > <admin-password>NotaRealPassword</admin-password> > </authentication> > <http-headers> > <header name="Access-Control-Allow-Origin" value="*"/> > </http-headers> > <fileserve>1</fileserve> > <paths> > <logdir>./log</logdir> > <webroot>./web</webroot> > <adminroot>./admin</adminroot> > <alias source="/" destination="/status.xsl"/> > </paths> > <logging> > <accesslog>access.log</accesslog> > <errorlog>error.log</errorlog> > <loglevel>3</loglevel> > <logsize>10000</logsize> > </logging> > </icecast> > > >_______________________________________________ > >Icecast mailing list > >Icecast at xiph.org > >http://lists.xiph.org/mailman/listinfo/icecast > > = = = = = = = = = = = = = = = = = = = > > > Best regards. > > Foxxe > wilderzone.radio.2 at gmail.com > thewilderzone.sytes.net > wilderzone.radio.2 at gmail.com > 2019-09-09 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190909/6a998c5a/attachment.html>
Hello, A. Craig West,>Multiple streams are generally separated by the path that is used to access >it, they all run on the same port. This is determined by the stream source >when it connects to the serverSeriously? Just because they are in a different folder? What about subfolders?? I have short sound bites in the main folder followed by some singles in the next level and the next level has full albums. How will that affect this? = = = = = = = = = = = = = = = = = = = Best regards. Foxxe thewilderzone.sytes.net wilderzone.radio.2 at gmail.com 2019-09-09
Hi, On 9/9/19 3:34 PM, wilderzone.radio.2 wrote:> Hello, Thomas_B._Rücker, > > ======= At 2019-09-09, 08:36:43 you wrote: ======> >> I am not familiar with a file called "icecast_run.xml". >> Could this be a local modification to your installation? >> >> You should be able to check which one is used by opening the >> "icecast.bat" file that you are using to start the server. > aha!! You nailed it! I have no idea why but the package I downloaded months ago (Icecast v2.4.3) > came with the batchfile premade and the actual configs seem to be this oddly named file... (I recall being confused as to why there would be TWO config files, but I've seen stranger things in the past so I editted both to reflect my needs...) > > So here is the actual working config: > > Now I don't see anywhere in which I can put the extra mount points > (nor do I recall a port designation for the 2nd stream mentioned at all tonight).Yes, those fields are not included in your configuration file, but can be inserted. It's kind of arbitrary, but you could insert those <mount>…</mount> sections/lines after the second </listen-socket> and before the <limits> line. I *strongly* recommend to create a backup copy of the working config file! It's easy to miss something and end up with Icecast refusing to start.> <icecast> > <hostname>wilder Zone</hostname> > <location>My Wilderness</location> > <admin>wilderzone.radio at gmail.com</admin>So this line defines to which mountpoint a Shoutcast source client gets redirected:> <shoutcast-mount>/rock</shoutcast-mount>That's an implicit mount definition. If you want to be able to use Shoutcast source clients for either mount, then your configuration will have to change a bit. It's described here: https://icecast.org/docs/icecast-2.4.1/config-file.html#backward-compatibility-with-shoutcast-source-clients If you need help with making those modifications, I'm sure there are people on the mailing list who can lend a hand.> <listen-socket> > <port>8080</port> > </listen-socket> > <listen-socket> > <port>8081</port> > <shoutcast-compat>1</shoutcast-compat> > </listen-socket> > <limits> > <clients>20</clients> > <sources>4</sources> > <queue-size>524288</queue-size> > <client-timeout>30</client-timeout> > <header-timeout>15</header-timeout> > <source-timeout>10</source-timeout> > <burst-on-connect>1</burst-on-connect> > <burst-size>65535</burst-size> > </limits> > <authentication> > <source-password>NotaRealPassword</source-password> > <relay-password>NotaRealPassword</relay-password> > <admin-user>admin</admin-user> > <admin-password>NotaRealPassword</admin-password> > </authentication> > <http-headers> > <header name="Access-Control-Allow-Origin" value="*"/> > </http-headers> > <fileserve>1</fileserve> > <paths> > <logdir>./log</logdir> > <webroot>./web</webroot> > <adminroot>./admin</adminroot> > <alias source="/" destination="/status.xsl"/> > </paths> > <logging> > <accesslog>access.log</accesslog> > <errorlog>error.log</errorlog> > <loglevel>3</loglevel> > <logsize>10000</logsize> > </logging> > </icecast> >Cheers, TBR
Hello, Thomas_B._Rücker,>> >>> I am not familiar with a file called "icecast_run.xml". >>> Could this be a local modification to your installation? >>> >>> You should be able to check which one is used by opening the >>> "icecast.bat" file that you are using to start the server. >> aha!! You nailed it! I have no idea why but the package I downloaded months ago (Icecast v2.4.3) >> came with the batchfile premade and the actual configs seem to be this oddly named file... (I recall being confused as to why there would be TWO config files, but I've seen stranger things in the past so I editted both to reflect my needs...) >> >> So here is the actual working config: >> >> Now I don't see anywhere in which I can put the extra mount points >> (nor do I recall a port designation for the 2nd stream mentioned at all tonight). > > >Yes, those fields are not included in your configuration file, but can >be inserted. >It's kind of arbitrary, but you could insert those <mount>…</mount> >sections/lines after the second </listen-socket> and before the <limits> >line. > >I *strongly* recommend to create a backup copy of the working config >file! It's easy to miss something and end up with Icecast refusing to start. > > >> <icecast> >> <hostname>wilder Zone</hostname> >> <location>My Wilderness</location> >> <admin>wilderzone.radio at gmail.com</admin> > >So this line defines to which mountpoint a Shoutcast source client gets >redirected:the email addy does this? THAT gets a bit more confusing.>> <shoutcast-mount>/rock</shoutcast-mount>I truly don't understand HOW the hell shoutcast even gets mentioned in the configs at all. To me that's like going to Domino's Pizza and ordering a Big Mac (no sense at all)> >That's an implicit mount definition. >If you want to be able to use Shoutcast source clients for either mount, >then your configuration will have to change a bit. >It's described here: >https://icecast.org/docs/icecast-2.4.1/config-file.html#backward-compatibility-with-shoutcast-source-clients >If you need help with making those modifications, I'm sure there are >people on the mailing list who can lend a hand. >I've been working on this with the mailing list literally ALL NIGHT and only got a few instances of understanding of all this. (but have been searching for help other places with absolutely no luck at all - I have an easier time finding help with OS/2 and they've not used that since 1994!!) Icecast docs aren't very easy to understand and they mention very little about each setting and they NEVER mention why shoutcast ANYTHING is used at all, so I see "shoutcast-mount" and "mount" to mean TWO DIFFERENT THINGS and making them similar in phonic structure only adds to confusion. In short, I'd have an easier time learning Cantonese from a deaf person with a hair-lip! = = = = = = = = = = = = = = = = = = = Best regards. Foxxe wilderzone.radio.2 at gmail.com thewilderzone.sytes.net wilderzone.radio.2 at gmail.com 2019-09-09
Hello, Thomas_B._Rücker,>Yes, those fields are not included in your configuration file, but can >be inserted. >It's kind of arbitrary, but you could insert those <mount>…</mount> >sections/lines after the second </listen-socket> and before the <limits> >line. > >I *strongly* recommend to create a backup copy of the working config >file! It's easy to miss something and end up with Icecast refusing to start. >I suspect something in that specific clipping is badly wrong (or at least out of phase with the rest of the configuration. It didn't work.> >> <icecast> >> <hostname>wilder Zone</hostname> >> <location>My Wilderness</location> >> <admin>wilderzone.radio at gmail.com</admin> > >So this line defines to which mountpoint a Shoutcast source client gets >redirected: >> <shoutcast-mount>/rock</shoutcast-mount> > >That's an implicit mount definition. >If you want to be able to use Shoutcast source clients for either mount, >then your configuration will have to change a bit. >It's described here: >https://icecast.org/docs/icecast-2.4.1/config-file.html#backward-compatibility-with-shoutcast-source-clients >If you need help with making those modifications, I'm sure there are >people on the mailing list who can lend a hand. > > >> <listen-socket> >> <port>8080</port> >> </listen-socket> >> <listen-socket> >> <port>8081</port> >> <shoutcast-compat>1</shoutcast-compat> >> </listen-socket> >> <limits> >> <clients>20</clients> >> <sources>4</sources> >> <queue-size>524288</queue-size> >> <client-timeout>30</client-timeout> >> <header-timeout>15</header-timeout> >> <source-timeout>10</source-timeout> >> <burst-on-connect>1</burst-on-connect> >> <burst-size>65535</burst-size> >> </limits> >> <authentication> >> <source-password>NotaRealPassword</source-password> >> <relay-password>NotaRealPassword</relay-password> >> <admin-user>admin</admin-user> >> <admin-password>NotaRealPassword</admin-password> >> </authentication> >> <http-headers> >> <header name="Access-Control-Allow-Origin" value="*"/> >> </http-headers> >> <fileserve>1</fileserve> >> <paths> >> <logdir>./log</logdir> >> <webroot>./web</webroot> >> <adminroot>./admin</adminroot> >> <alias source="/" destination="/status.xsl"/> >> </paths> >> <logging> >> <accesslog>access.log</accesslog> >> <errorlog>error.log</errorlog> >> <loglevel>3</loglevel> >> <logsize>10000</logsize> >> </logging> >> </icecast> >> > >Cheers, > > >TBR > > >_______________________________________________ >Icecast mailing list >Icecast at xiph.org >http://lists.xiph.org/mailman/listinfo/icecast= = = = = = = = = = = = = = = = = = = Best regards. Foxxe wilderzone.radio.2 at gmail.com thewilderzone.sytes.net wilderzone.radio.2 at gmail.com 2019-09-09
Hi, On 9/9/19 8:22 PM, wilderzone.radio.2 wrote:> Hello, Thomas_B._Rücker, > >>>> I am not familiar with a file called "icecast_run.xml". >>>> Could this be a local modification to your installation? >>>> >>>> You should be able to check which one is used by opening the >>>> "icecast.bat" file that you are using to start the server. >>> aha!! You nailed it! I have no idea why but the package I downloaded months ago (Icecast v2.4.3) >>> came with the batchfile premade and the actual configs seem to be this oddly named file... (I recall being confused as to why there would be TWO config files, but I've seen stranger things in the past so I editted both to reflect my needs...) >>> >>> So here is the actual working config: >>> >>> Now I don't see anywhere in which I can put the extra mount points >>> (nor do I recall a port designation for the 2nd stream mentioned at all tonight). >> >> Yes, those fields are not included in your configuration file, but can >> be inserted. >> It's kind of arbitrary, but you could insert those <mount>…</mount> >> sections/lines after the second </listen-socket> and before the <limits> >> line. >> >> I *strongly* recommend to create a backup copy of the working config >> file! It's easy to miss something and end up with Icecast refusing to start. >> >> >>> <icecast> >>> <hostname>wilder Zone</hostname> >>> <location>My Wilderness</location> >>> <admin>wilderzone.radio at gmail.com</admin> >> So this line defines to which mountpoint a Shoutcast source client gets >> redirected: > the email addy does this? THAT gets a bit more confusing.Please note the colon, that sentence refers to the line BELOW.>> <shoutcast-mount>/rock</shoutcast-mount> > I truly don't understand HOW the hell shoutcast even gets mentioned in the configs at all. To me that's like going to Domino's Pizza and ordering a Big Mac (no sense at all)To stay in that analogy: If you only ever ate Big Mac's and suddenly find yourself in a different burger "restaurant" and only know to say "give me Big Mac!", then there are two likely outcomes: * Staff will tell you to leave as they can't serve you *exactly* that * Staff will try to *interpret* what you are saying and match that to their menu to serve you to the best of their ability. Icecast does exactly that. You are coming to it with Shoutcast software which says "Here, take Shoutcast stream!". With a tiny bit of configuration (shoutcast-mount) Icecast will be able to serve the client despite it speaking "a foreign language". It's basically like a note to staff "If someone asks for a Big Mac, serve them our XYZ Burger".>> That's an implicit mount definition. >> If you want to be able to use Shoutcast source clients for either mount, >> then your configuration will have to change a bit. >> It's described here: >> https://icecast.org/docs/icecast-2.4.1/config-file.html#backward-compatibility-with-shoutcast-source-clients >> If you need help with making those modifications, I'm sure there are >> people on the mailing list who can lend a hand. >> > I've been working on this with the mailing list literally[removed for language] I understand that you are frustrated, but I must advise you that your tone is not acceptable. Please refrain from insulting us or I will have to put a stop to this. I understand that the documentation is hard to make sense of for you, thus I have emphasized that we can help. Do you want help with this? Thomas B. Rücker Icecast maintainer
Hello, Thomas_B._Rücker, Initially I was asking for a working example file with more than one stream instance. Something that I can take as an example to work from. I've not gotten that yet, despite posting 2 config files; both that came with the install package. Trust me, if there were other choices for streaming servers than just icecast and shoutcast; I'd be running there to see if THEY have any real support. Consider this for a moment before you pull that hangman's rope. I've been trying to solve this mystery since February and have only found a sprinkling of sites here and there that will even TALK about streaming server software and of those few, I've come across abuse and ignorance in plenty. This software has little to no docs to speak of (not unlike Blender which to my knowledge has absolutely NO docs at ALL in my 8 years of searching.) Of all the results I've gotten last night THIS is what I've learned: The icecast package I got had TWO config files in it, one apparently was an example file (although there was no indication of it's example status by any "paperwork" and the other was setup merely for one stream. Any documentation I've seen shows only one thing; confusion and misdirection. ie: "shoutcast-mount" has STILL not been explained as to it's actual function and WHY it's called as such despite the fact it has NOTHING at all to do with shoutcast. And where are these multiple stream configs I've asked repeated for? (or any help in plain english in that direction?). My current status in this quagmire is that I HAVE TO host 2 streams on TWO machines because NO ONE has bothered to answer the question I asked (see the subject line for that little detail) I want to be able to put this mess behind me ONE AND FOR ALL, without more excessive stress from kids that think it's funny to troll people on the internet! I am seriously wondering if it was a smart idea to ever allow the US on the internet in the first place!! ======= At 2019-09-10, 01:01:48 you wrote: ======> >[removed for language]I'm sorry if english disturbs you but I don't speak my mother tongue.>I understand that you are frustrated, but I must advise you that your >tone is not acceptable. Please refrain from insulting us or I will have to put a stop to this. > >I understand that the documentation is hard to make sense of for you, >thus I have emphasized that we can help.Do you want help with this?I am ready if you are. DOS and BASIC (back in the 70's) was easier to learn; NOTHING should be this tedious. = = = = = = = = = = = = = = = = = = = Best regards. Rev. Foxxe Wilder wilderzone.radio.2 at gmail.com thewilderzone.sytes.net 2019-09-10