tunein | TuneIn is a personalized radio station using HTML5 audio | Audio Utils library

One method uses ROW_NUMBER(). I think that it is simpler to flatten the joins in a subquery rather than pre-aggregating.

The way your code works, an app placed in count_top_3 would only have a counter > 1 if the app was listed in app[] multiple times, since you are only checking if each app is in topic_list, and not how many times it is in topic_list. In your example input, there are no duplicates in app[].

If your goal is to count how many times each app appears in topic_list, you can loop over every app in app[], and for each app, then loop over every topic in topic_list[], and count how many times the topic matches that app, storing the result in count_top_3. You can also use the count() method for this.

Example:

FOR ALL Who want to stream fro TUNEIN

Turns out that if you setup AVPlayer like that:

I have tried to play the url with different approaches but I found out something that made AVPlayer work but still don't know what happens behind the scenes...

My first approach was to initialise the AVPlayer and set the AVURLAsset resource loader delegate but, since a Reserved/Standard url scheme doesn't trigger the delegate, I was into a dead end...

Secondly and after implementing the AVPlayer like that:

Try this

There is no else if construct in bash. Instead you should use elif.

This is not possible with SMAPI currently. The experience you noted is built in to the system specifically.

It turned out Alexa can play HTTP audio feeds. I just had too put those as references inside of .m3u file, which is served by HTTPS protocol.

I assume, that TuneIn does transport some metadata here, but I am not able to figure out which protocol to use, if any.

This doesn't have anything to do with TuneIn... it's a SHOUTcast server, and it uses ICY-style metadata. In any case, unless you actually request the metadata (with Icy-MetaData: 1 in the HTTP request headers), you won't get it. You'll end up with a normal raw MPEG stream.

If you want to know more about the data, check out my answers here:

• https://stackoverflow.com/a/4914538/362536
• https://stackoverflow.com/a/16750107/362536

I don't see any SHOUTcast-style ICY metadata in your dump.

all goes well for a few hundred frames, but all at a sudden a lot of invalid frames are transmitted

It's interesting that it works initially, but then fails.

Usually for these streams, the first couple frames are wonky as the server doesn't have to know or care about the data flowing through it. It just has a fixed buffer size of 128KB or so, and arbitrarily chunks so that when a client connects, it gets that buffer plus whatever comes after it. That is, the client is "needle dropped" right into the stream and is expected to synchronize itself.

This is done with the sync word 0xFFF* or 0xFFE*. Anything before the sync should be discarded. Any frames requiring an unavailable bit reservoir should be discarded. Eventually after a few frames, you'll have a steady stream of data to decode.

Double check to make sure you don't have a buffer around from a previous file/URL, and then re-sync to the stream on initial connect.

If this isn't the problem, I'm honestly not sure what to suggest other than that some stations use broken codecs. You'd be surprised how many internet radio stations are using copies of LAME from 15 years ago.

I might also suggest, if possible, sticking with an existing codec and doing your analysis after converting it back to normal PCM.