Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A stream consists of a seamless stream of mp3´s thats what a stream does...it stiches separate mp3´s to one large stream.</p> <p>But theres track ID-tags in the stream...not shure if you can find end and start from them or if these start exactly at the track-start or other fixed positions.</p> <p>Most stations dont send ahead info about the next track simply cause they dont know, most use auto-dj playlists where the server has to decide in the small break between old and new track what that new track will be ie: it dont decide on that while the old track is playing.</p> <p>Some stations do send info (PHP to their webpages) what the next track will be but most dont...and if they do that info is ceretainly not in the stream itself.</p> <p>Maybe a trick could be to add a delay for your listener<br> ie: what the listener is hearing currently<br> is old (up to a few minutes or 1 complete track) </p> <p>Not shure how to create such delay...maybe you need to record (buffer) it<br> and play it back with a delay (in your app or via some additional server)</p> <p>Your (not delayed) application will (hopefully) notice when the current song has ended<br> since a new one has started with a new ID2/3 tag...it will switch your listener to a new stream when his current but delayed song has ended.</p> <p>Said different ...below the surface your application is looking ahead (relative to the listener)</p> <p>You need to study the Shoutcast and ID-tag protocols. Additional silence-detection might help also (not foolproof). </p> <p>May not always work..some stations dont send ID tags others crossfade their tracks (no silence)...exactly to avoid these tricks.</p> <p>Or something like that...good luck i cant code anything..its just theory i suspect some shoutcast rippers to use this trick...i suppose they use this to scan multitple streams (in parallel) for certain preset artists-tracks. Maybe you can get some ideas by reverse-engineering those rippers. Since i have a radio myself i´m not a fan of these tricks since they steal from me while i pay for the rights....to many rippers will kill online radio.</p> <p>In the end i dont see your idea (if i understand its purpose well) as usefull anyway<br> switching from one to another stream every next track dont seem like a enjoying experience.<br> Good radiostations will have a carefully made (ordered) playlist<br> if you mess that up your listener will get to much mood/style variations in a to short time.</p> <p>The only usefull purpose for this is probably to build a automated ripper that can distract preset tracks/artist from a multitude of in parralel observed streams and record them when a wanted track is played...for many online stations those rippers are a big problem already, 10´s more of those rippers and online radio is dead...as result good quality and independent music wont be available anymore...and we will be stuck with only Youtube and other money infested conglomerates..i´m not looking forward to that....curious if you have an other usefull purpose.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload