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 >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20160226/9d4e6393/attachment.htm
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
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
Good morning, On Fri, 2016-02-26 at 12:42 -0500, A. Craig West wrote:> So why does the ices.conf file have <Protocol>http</Protocol> ic it is > going to use icy anyways?ices 0.x is no longer supported for more than a decade. It uses a HTTP based upstream but downstream is ICY as MP3 can not be transmitted over HTTP with metadata. And ICY's metdata support is broken all the way. *Those problems are inherent to MP3 streaming.* We really recommend not to use MP3 at all. Ogg/Vorbis and Opus don't have those problems. Have a nice day. -- Philipp. (Rah of PH2) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part Url : http://lists.xiph.org/pipermail/icecast/attachments/20160226/a8198edc/attachment.pgp
The problem is thatthere are still platforms that can't be depended on to have support for Ogg Vorbis. On Fri, Feb 26, 2016 at 1:26 PM, Philipp Schafft <lion at lion.leolix.org> wrote:> Good morning, > > On Fri, 2016-02-26 at 12:42 -0500, A. Craig West wrote: > > So why does the ices.conf file have <Protocol>http</Protocol> ic it is > > going to use icy anyways? > > ices 0.x is no longer supported for more than a decade. > It uses a HTTP based upstream but downstream is ICY as MP3 can not be > transmitted over HTTP with metadata. And ICY's metdata support is broken > all the way. > > *Those problems are inherent to MP3 streaming.* > > We really recommend not to use MP3 at all. Ogg/Vorbis and Opus don't > have those problems. > > Have a nice day. > > -- > Philipp. > (Rah of PH2) > > _______________________________________________ > 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/155f88d6/attachment-0001.htm