The default ices.conf.dist file from the source distribution contains:
<!-- Header protocol to use when communicating with the server.
Shoutcast servers need "icy", icecast 1.x needs
"xaudiocast", and
icecast 2.x needs "http". -->
<Protocol>http</Protocol>
I haven't checked the code to see if this is used for anything, though...
On Fri, Feb 26, 2016 at 12:44 PM, Marvin Scholz <epirat07 at gmail.com>
wrote:
> Can you show me the context where <Protocol> is used?
>
> On 26 Feb 2016, at 18:42, A. Craig West wrote:
>
> > So why does the ices.conf file have
<Protocol>http</Protocol> ic it is
> > going to use icy anyways?
> >
> > On Fri, Feb 26, 2016 at 2:00 AM, Marvin Scholz <epirat07 at
gmail.com>
> wrote:
> >
> >> On 26 Feb 2016, at 7:03, A. Craig West wrote:
> >>
> >>> I have been trying to access the "artist" and
"title" metadata in the
> >>> xml
> >>> files as separate entities, But have found thar artist is
missing, and
> >>> title contains a combined form.
> >>> My source is a modified version of ices-0.4 sending mp3
streams. The
> >>> modification is to attach artist and title metadata instead of
song,
> >>> which
> >>> seems tobe working, in that both the artist and title are
present.
> >>> What
> >>> does shout_set_metadata do? I have tried to use wireshark to
see what
> >>> is
> >>> being sent to the server, but it doesn't appear to be
anything
> >>> obvious...
> >>> -Craig
> >>
> >> For MP3 streaming metadata ICY is used, which is not capable of
having
> >> separate Artist and Title
> >> metadata bust just one single combined string for metadata, as far
as I
> >> know.
> >> So there is no way to get that information if you use MP3, sorry.
> >>
> >>> _______________________________________________
> >>> Icecast mailing list
> >>> Icecast at xiph.org
> >>> http://lists.xiph.org/mailman/listinfo/icecast
> >> _______________________________________________
> >> Icecast mailing list
> >> Icecast at xiph.org
> >> http://lists.xiph.org/mailman/listinfo/icecast
> >>
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> _______________________________________________
> 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/20160226/1993dc93/attachment.htm
This is not about metadata, just how to connect to the server to transmit the stream. How metadata is handled is different depending on the format, modern formats like Ogg don't need the ICY metadata "hack" to work, but MP3 does not support metadata at all that's why icy metadata is used. If you stream in a format like Ogg with a proper source client, Icecast will display metadata fine, it's just not possible with MP3. On 26 Feb 2016, at 18:50, A. Craig West wrote:> The default ices.conf.dist file from the source distribution contains: > <!-- Header protocol to use when communicating with the server. > Shoutcast servers need "icy", icecast 1.x needs "xaudiocast", > and > icecast 2.x needs "http". --> > <Protocol>http</Protocol> > > I haven't checked the code to see if this is used for anything, > though... > > On Fri, Feb 26, 2016 at 12:44 PM, Marvin Scholz <epirat07 at gmail.com> > wrote: > >> Can you show me the context where <Protocol> is used? >> >> On 26 Feb 2016, at 18:42, A. Craig West wrote: >> >>> So why does the ices.conf file have <Protocol>http</Protocol> ic it >>> is >>> going to use icy anyways? >>> >>> On Fri, Feb 26, 2016 at 2:00 AM, Marvin Scholz <epirat07 at gmail.com> >> wrote: >>> >>>> On 26 Feb 2016, at 7:03, A. Craig West wrote: >>>> >>>>> I have been trying to access the "artist" and "title" metadata in >>>>> the >>>>> xml >>>>> files as separate entities, But have found thar artist is missing, >>>>> and >>>>> title contains a combined form. >>>>> My source is a modified version of ices-0.4 sending mp3 streams. >>>>> The >>>>> modification is to attach artist and title metadata instead of >>>>> song, >>>>> which >>>>> seems tobe working, in that both the artist and title are present. >>>>> What >>>>> does shout_set_metadata do? I have tried to use wireshark to see >>>>> what >>>>> is >>>>> being sent to the server, but it doesn't appear to be anything >>>>> obvious... >>>>> -Craig >>>> >>>> For MP3 streaming metadata ICY is used, which is not capable of >>>> having >>>> separate Artist and Title >>>> metadata bust just one single combined string for metadata, as far >>>> as I >>>> know. >>>> So there is no way to get that information if you use MP3, sorry. >>>> >>>>> _______________________________________________ >>>>> Icecast mailing list >>>>> Icecast at xiph.org >>>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast
The ices2 code in many ways seems more limited than the ices0 code, particularly with metadata. There doesn't seem to be any way to include metadata at all with icecast2 and playlists, particularly with scripts. Is there a reason this was removed?? On Fri, Feb 26, 2016 at 3:47 PM, Marvin Scholz <epirat07 at gmail.com> wrote:> This is not about metadata, just how to connect to the server to > transmit the stream. > How metadata is handled is different depending on the format, modern > formats like Ogg > don't need the ICY metadata "hack" to work, but MP3 does not support > metadata at all > that's why icy metadata is used. If you stream in a format like Ogg with > a proper > source client, Icecast will display metadata fine, it's just not > possible with MP3. > > On 26 Feb 2016, at 18:50, A. Craig West wrote: > > > The default ices.conf.dist file from the source distribution contains: > > <!-- Header protocol to use when communicating with the server. > > Shoutcast servers need "icy", icecast 1.x needs "xaudiocast", > > and > > icecast 2.x needs "http". --> > > <Protocol>http</Protocol> > > > > I haven't checked the code to see if this is used for anything, > > though... > > > > On Fri, Feb 26, 2016 at 12:44 PM, Marvin Scholz <epirat07 at gmail.com> > > wrote: > > > >> Can you show me the context where <Protocol> is used? > >> > >> On 26 Feb 2016, at 18:42, A. Craig West wrote: > >> > >>> So why does the ices.conf file have <Protocol>http</Protocol> ic it > >>> is > >>> going to use icy anyways? > >>> > >>> On Fri, Feb 26, 2016 at 2:00 AM, Marvin Scholz <epirat07 at gmail.com> > >> wrote: > >>> > >>>> On 26 Feb 2016, at 7:03, A. Craig West wrote: > >>>> > >>>>> I have been trying to access the "artist" and "title" metadata in > >>>>> the > >>>>> xml > >>>>> files as separate entities, But have found thar artist is missing, > >>>>> and > >>>>> title contains a combined form. > >>>>> My source is a modified version of ices-0.4 sending mp3 streams. > >>>>> The > >>>>> modification is to attach artist and title metadata instead of > >>>>> song, > >>>>> which > >>>>> seems tobe working, in that both the artist and title are present. > >>>>> What > >>>>> does shout_set_metadata do? I have tried to use wireshark to see > >>>>> what > >>>>> is > >>>>> being sent to the server, but it doesn't appear to be anything > >>>>> obvious... > >>>>> -Craig > >>>> > >>>> For MP3 streaming metadata ICY is used, which is not capable of > >>>> having > >>>> separate Artist and Title > >>>> metadata bust just one single combined string for metadata, as far > >>>> as I > >>>> know. > >>>> So there is no way to get that information if you use MP3, sorry. > >>>> > >>>>> _______________________________________________ > >>>>> Icecast mailing list > >>>>> Icecast at xiph.org > >>>>> http://lists.xiph.org/mailman/listinfo/icecast > >>>> _______________________________________________ > >>>> Icecast mailing list > >>>> Icecast at xiph.org > >>>> http://lists.xiph.org/mailman/listinfo/icecast > >>>> > >>> _______________________________________________ > >>> Icecast mailing list > >>> Icecast at xiph.org > >>> http://lists.xiph.org/mailman/listinfo/icecast > >> _______________________________________________ > >> Icecast mailing list > >> Icecast at xiph.org > >> http://lists.xiph.org/mailman/listinfo/icecast > >> > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > 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/20160229/68ca4023/attachment.htm
I have just been re-reading the ices0 code, and it appears that if the protocol in the configuration is set, the complete metadata IS being sent to the icecast server, using HTTP GET /admin/metadata. Is the server ignoring this? On Fri, Feb 26, 2016 at 3:47 PM, Marvin Scholz <epirat07 at gmail.com> wrote:> This is not about metadata, just how to connect to the server to > transmit the stream. > How metadata is handled is different depending on the format, modern > formats like Ogg > don't need the ICY metadata "hack" to work, but MP3 does not support > metadata at all > that's why icy metadata is used. If you stream in a format like Ogg with > a proper > source client, Icecast will display metadata fine, it's just not > possible with MP3. > > On 26 Feb 2016, at 18:50, A. Craig West wrote: > > > The default ices.conf.dist file from the source distribution contains: > > <!-- Header protocol to use when communicating with the server. > > Shoutcast servers need "icy", icecast 1.x needs "xaudiocast", > > and > > icecast 2.x needs "http". --> > > <Protocol>http</Protocol> > > > > I haven't checked the code to see if this is used for anything, > > though... > > > > On Fri, Feb 26, 2016 at 12:44 PM, Marvin Scholz <epirat07 at gmail.com> > > wrote: > > > >> Can you show me the context where <Protocol> is used? > >> > >> On 26 Feb 2016, at 18:42, A. Craig West wrote: > >> > >>> So why does the ices.conf file have <Protocol>http</Protocol> ic it > >>> is > >>> going to use icy anyways? > >>> > >>> On Fri, Feb 26, 2016 at 2:00 AM, Marvin Scholz <epirat07 at gmail.com> > >> wrote: > >>> > >>>> On 26 Feb 2016, at 7:03, A. Craig West wrote: > >>>> > >>>>> I have been trying to access the "artist" and "title" metadata in > >>>>> the > >>>>> xml > >>>>> files as separate entities, But have found thar artist is missing, > >>>>> and > >>>>> title contains a combined form. > >>>>> My source is a modified version of ices-0.4 sending mp3 streams. > >>>>> The > >>>>> modification is to attach artist and title metadata instead of > >>>>> song, > >>>>> which > >>>>> seems tobe working, in that both the artist and title are present. > >>>>> What > >>>>> does shout_set_metadata do? I have tried to use wireshark to see > >>>>> what > >>>>> is > >>>>> being sent to the server, but it doesn't appear to be anything > >>>>> obvious... > >>>>> -Craig > >>>> > >>>> For MP3 streaming metadata ICY is used, which is not capable of > >>>> having > >>>> separate Artist and Title > >>>> metadata bust just one single combined string for metadata, as far > >>>> as I > >>>> know. > >>>> So there is no way to get that information if you use MP3, sorry. > >>>> > >>>>> _______________________________________________ > >>>>> Icecast mailing list > >>>>> Icecast at xiph.org > >>>>> http://lists.xiph.org/mailman/listinfo/icecast > >>>> _______________________________________________ > >>>> Icecast mailing list > >>>> Icecast at xiph.org > >>>> http://lists.xiph.org/mailman/listinfo/icecast > >>>> > >>> _______________________________________________ > >>> Icecast mailing list > >>> Icecast at xiph.org > >>> http://lists.xiph.org/mailman/listinfo/icecast > >> _______________________________________________ > >> Icecast mailing list > >> Icecast at xiph.org > >> http://lists.xiph.org/mailman/listinfo/icecast > >> > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > 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/20160229/72a196f3/attachment.htm