Open GoogleCodeExporter opened 9 years ago
Stream does send meta data. Most players see it, but see it inconsistently. Jon
Trowbridge knows a bit more about this, but we were testing once in the studio,
both on same build of OS X with same version of iTunes pinging the same direct
stream address and I got meta data just fine, he did not.
In doing research, it seems the shoutcast metadata spec is unreliable at best,
which accounts for the inconsistencies. But it is there.
Original comment by mike%chi...@gtempaccount.com
on 26 Dec 2010 at 9:36
To make this thread complete, the Playlist Tracker does indeed submit ID3 data
to Live 365 using its API, here:
http://code.google.com/p/chirpradio/source/browse/playlists/tasks.py?r=10847f762
1decbb232f5cf6be04a68e0b7a779f2#78
However, I have not seen this ID3 data update in iTunes after the *first* time
you open the steam.
Original comment by kumar.mcmillan
on 13 Jan 2011 at 9:21
I know this hasn't been touched since 2011, but I'm working on this. In order
for our stream to include ID3 metadata, we need to provide it to the ProStream
(c.f. pg. 39 of the ProStream manual).
I'm working on a service that will provide the data to the Prostream. Once I'm
happy with it, I'll try to get it included in the Chirp codebase and then
install it at the station.
--Agocs
Original comment by camer...@gmail.com
on 27 Sep 2014 at 11:44
I wrote a service to fix this. I'll need to install it in the studio and
reconfigure the ProStream to complete the fix.
https://github.com/agocs/chirp-current-track-announcer
Original comment by chris.ag...@gmail.com
on 28 Sep 2014 at 4:23
This looks great. Can you rename your repo so that the master is under the
chirpradio org? You can still keep a fork in your account but this will make it
easier to collaborate on. I sent you an invite to become a member of the
chirpradio org. https://github.com/chirpradio/
Original comment by kumar.mcmillan
on 29 Sep 2014 at 4:16
Hey Kumar, thanks for the invite. It looks like you only gave me committer
rights, which does not let me transfer a repo to chirpradio or create a repo.
If you create a repo called chirpradio/chirp-current-track-announcer, I will
add that as a remote, push everything to it, take down the original, and then
fork the new chirpradio repo. Thoughts?
Original comment by chris.ag...@gmail.com
on 29 Sep 2014 at 4:33
Oh, whoops. I added you to a new team within the org that should now let you
create repos. Let me know if you have any difficulty. If you are able to turn
on two factor auth for your github account that would be helpful.
Original comment by kumar.mcmillan
on 29 Sep 2014 at 5:01
I see that I've been added to owners, but it still won't let me transfer the
repo. I'm going to get some sleep and see if I can figure out what's up in the
morning.
Original comment by chris.ag...@gmail.com
on 29 Sep 2014 at 5:09
I added you to owners at first but then I found a way to add you to a team that
has write access so I removed you as an owner. You can't create repositories?
Hmm. If it doesn't work I can put you back in owners.
Original comment by kumar.mcmillan
on 29 Sep 2014 at 6:08
Actually, I think owners are the only ones who can create repositories. I
decided just to fork your project into chirpradio
https://github.com/chirpradio/chirp-current-track-announcer . You should have
push access to it!
Original comment by kumar.mcmillan
on 29 Sep 2014 at 6:13
Original issue reported on code.google.com by
clouserw
on 29 Nov 2010 at 7:13