ShaneFosterPlays / edcast-reborn

Automatically exported from code.google.com/p/edcast-reborn
0 stars 0 forks source link

Allowing Metadata from Other Sources (And allowing to parse that Metadata) #63

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
In my years in the radio field, connecting with automation systems and getting 
their RDS (Radio Data System)/ Meta data is a challenge.  There are 3 common 
ways to do this:

- TCP Client (connect to their server)
- TCP Server (wait for a connection)
- Serial Port

All of these are pretty easy to add, I have made programs that do just that.  
Though that's not the end of it.  Once you get that RDS data, you have to be 
able to parse it.  For example:

m1234|Elton John|Your Song|04:01

Us humans know that this is music, but the computer does not.  We could tell it 
that it's music by saying "anything with m" at the start of field 0 is music, 
field 1 is artist, field 2 is title and field 3 is the duration.  That 
character separation could be anything, just using a pipe as an example.

Another method of separation is by character length:

MUS01010100  Elton John                  Your Song                  P04:01
MUS01010100  Billy Joel                  Allentown                  C05:12

Above you will see 2 (or more entries), the one with P is now playing, the one 
C is coming up.

Typically this parsing of data is done with scripting, mostly JavaScript.  If 
you have a common way of parsing out information from the metadata then you 
have live data.  This means more solutions including ad insertion and 
replacement.

This is something that RioCast should do.  It is leveling the playing field 
again. :)

Original issue reported on code.google.com by kilok...@gmail.com on 18 Oct 2012 at 1:10

GoogleCodeExporter commented 8 years ago

Original comment by jaroma...@gmail.com on 9 Feb 2013 at 2:34

GoogleCodeExporter commented 8 years ago

Original comment by jaroma...@gmail.com on 9 Feb 2013 at 2:39