[Icecast] EZstream XML that used to work

[Steve Matzura]

Geoff,


Great to find you here.


I almost want to cut the rest of this reply off except for the very last 
part, but maybe it'll be useful to some folks.


The bottom line is that you pointed out the stream_name directive in the 
<stream> block, I totally missed that in the two-hundred-plus-line 
ezstream_full.xml file, and it's exactly what I needed to solve the problem.


I did look at ezstream-cfgmigrate, and it works as far as what it's 
supposed to do, but none of the resultant converted files worked, and 
all for the same reason--I get login failures to the Icecast server. 
This is odd because the one and only place there's a password, it's 
correct. I'm not going to pursue why it doesn't work for my files 
because while I was going through all of this, I wrote my own migration 
tool that worked well except for that one item--<sream_name>. I added 
that line to my template, ran 52 files through it, and they all work 
just as they should. If you want to know more about that, we can take it 
up off-list, but otherwise, thank you very much for pointing me in the 
right direction. It taught me to read even more carefully than I thought 
I was doing, and that's always a good thing.


On 9/20/2024 11:41 AM, Geoff Shang wrote:
> Hey Steve,
>
> On Thu, 19 Sep 2024, Steve Matzura wrote:
>
>> The problem seems to be with the <name> XML directive. I thought that 
>> if it is added to the <server> block, the name of the stream could be 
>> displayed in a player. I think the problem comes up if the contents 
>> of the server name in that directive is more than one word--i.e., 
>> contains spaces. I removed it, and the player again shows "no name" 
>> where I would expect to see one. How then does this work? I want to 
>> display my station name in this name field like I could with an older 
>> version of ezstream.
>
> first of all, this looks like it needs to be within a <stream> tag 
> inside a <streams> tag.
>
> The format of the config file has changed a lot since the early days. 
> There is a program called ezstream-cfgmigrate which may help if you 
> still have your original config file.
>
> From the ezstream-full.xml file that's in the doc/examples directory 
> of version 1.0.2:
>
>   <!--
>     Stream configuration
>     -->
>   <streams>
>     <stream>
>       <!--
>         Identifying name (default: "default")
>
>         NB: Only the "default" stream is supported at this point.
>         -->
>       <!-- <name>default</name> -->
>
> This seems to indicate that the purpose of this parameter has changed 
> (it's been a *very* long time since I looked at this).
>
> It also seems that the default value is "default", which is also the 
> only currently supported value.  This would explain the above error 
> message - there is no stream labeled "default".
>
> So you can omit this parameter entirely.
>
> What I think you want is <stream_name> which is also in the <stream> 
> section.  From further down the same file:
>
>       <!-- Various other informational settings -->
>       <stream_name>Test Stream</stream_name>
>       <stream_url>http://localhost:8000/</stream_url>
>       <stream_genre>Beeps</stream_genre>
>       <stream_description>Test tones and noise</stream_description>
>       <stream_quality>1.5</stream_quality>
>       <stream_bitrate>16</stream_bitrate>
>       <stream_samplerate>44100</stream_samplerate>
>       <stream_channels>2</stream_channels>
>     </stream>
>   </streams>
>
> HTH,
> Geoff.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20240920/93fb75ea/attachment.htm>