Artist and song name from icecast stream

Hello. Historically happened that I’m not often checking this support forum and can not immediately see that someone wrote some message to me. Don’t know if there will be any future for this project, cause only 200+ people are using it, so currently I’m mostly using it as my portfolio project and updating time to time if I have some ideas for improving it.

You asked about height of green spectrum and about some custom title… The height is not a problem for me, I can add such ability.

And also you say about custom song title, in this case I have a question, how are you going to set this title? Is it should be done by some javascript call, or player should read this title from some web page element, or you have any suggestions about how it should work?

Hello dear,

Thanks for your reply.

We hope you don’t abandon the project. It’s a very interesting application. Maybe there are few users because they haven’t discovered your application yet.

As for the features I suggested, I think having a parameter that defines the Y scale of the spectrum analyzer in number of pixels from the shortcode will be very interesting.

Regarding the presentation of artist/song names in an alternating manner based on a configurable time, in the same place in the UI where the station name is displayed (UIRadioStation name=”station_name”), whose new functionality will make the player support streams based on Icecast, if for example, the shortcode parameter is equal to “UIRadioStation name=”icecast”, and additionally has a second parameter such as icecast_json_url=”https://fqdn….”, your code will start to search for the JSON that brings data from the radio station and display for example the fields “server_name” and “title” (and even others), it would be a very interesting feature. The player will be even more interesting for web radio systems based on Icecast.

In shortcode, if the value for “UIRadioStation name=…” is different from “icecast”, your code will normally treat it as the station name. But if it is “icecast”, it would have to have the second parameter “icecast_json_url” to obtain the JSON and you can process and present in the UI the JSON fields that the user wants to present in the UI, where there could be N other parameters like “ice1=server_name ice2=title ice3=genre” and so on. Of course, you can improve how the user would enter the references of the JSON parameters in the shortcode. The parameter name should be the same as the JSON.

The standard Icecast JSON (https://icecast.org/) that I am citing is according to the following URL: https://radio.sarrorecords.com.br:8000/status-json.xsl

Since my English is not the best, I hope you understood the suggestion.

Thanks in advance.

Best regards

Currently released v1.40. With ability to set the spectrum height and play icecast, hope that everything works well.

Here is an example how to set spectrum height to 150px:
[UIMediaPlayer file=”/demo.mp3″ spectrum=”#4fcb1d 150″]

And here is an example how to play the icecast:
[UIMediaPlayer radio_station=”0″]
[UIRadioStation type=”icecast” url=”https://radio.sarrorecords.com.br:8000/status-json.xsl” interval=”3s”]
[/UIMediaPlayer]

Or you can also set extra name for the station, here is an example:
[UIRadioStation type=”icecast” name=”[my icecast]: ” url=”https://radio.sarrorecords.com.br:8000/status-json.xsl” interval=”3s”]

Currently hardcoded it to one of the engines that belongs to streams playback, hope that it will work fine

• This reply was modified 2 months, 3 weeks ago by iamzhirik.

There was some copy paste issue on the text above that converts double quote into & # 8221 ; – hope you understand what I mean

Dear Alex,

That’s amazing! Congratulations!

The spectrum analyzer is working fine.

Regarding Icecast, it’s working partially, that is, I used the new configuration exactly as below, and the UI showed the “name” and “title” perfectly, however, the stream didn’t play?

[UIRadioStation type=”icecast” name=”Sarro Records” url=”https://radio.sarrorecords.com.br:8000/status-json.xsl” interval=”3s”]

In the JSON there is the URL of the stream which is the “listenurl” field in the JSON tree. I don’t know how you’re doing it. “listenurl” is the URL of the stream. Since the traditional URL that contained the stream address is replaced by the JSON URL, I don’t know how you handled the URL of the stream itself, which didn’t play.

Another thing that didn’t work was the interval. In this case, would interval show “name” first, then after 3s it would show “title”, then after 3s it would show “name” again and so on, but is static as “name” plus “title”.

I really appreciate you helping me and I’m sure you’ll be helping everyone who uses Icecast-based streaming.

Many thanks.

Best regards

Dear Alex,

So, one problem I’ve noticed is that even when I change the color of the spectrum analyzer, it always stays green.

At this moment and until further tests, I’m keeping the color in amber, but it always shows green. At this moment, until you give me feedback regarding what was reported in the last message, the configuration I’m using is the following:

[UIMediaPlayer radio_station=”0″ mode=”extended” color=”#FFBF00″ width=”730″ spectrum=”#FFBF00 100″]

[UIRadioStation name=”Sarro Records” url=”https://radio.sarrorecords.com.br:8000/deephouse” interval=”3s”]

[/UIMediaPlayer]

Many thanks.

Best regards

Dear Alex,

I have identified a problem. Even if you define the stream URL as the one in the JSON “listenurl” field, this may cause CORS issues (as per the link below). Ideally, in the shortcode configuration, you should have a field for the stream URL and another for the Icecast JSON URL.

https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

And there may be configurations like mine where I use a reverse proxy (in my case NGINX), where externally it is HTTPS, but internally on the LAN it is HTTP. And since Icecast informs the internal URL in the “listenurl” field, this becomes a problem, which is why it is necessary to have two fields, one for the stream URL and another for the Icecast JSON URL so that you can obtain information about the stream (artist/song).

I hope I was able to convey the problem to you.

Many thanks.

Best regards

I also don’t like those CORS features. As I understand you want something like this:

[UIRadioStation type=”icecast” listenurl=”https:// radio.sarrorecords.com.br:8001/deephouse ” icecasturl=”https:// radio.sarrorecords.com.br:8000/status-json.xsl ” interval=”3s”]

Right?

Dear Alex,

Yes, that’s right.

Many thanks.

Best regards

Just released v1.41. And applied this change, but changed a little the shortcode, so right now it looks the following:
[UIMediaPlayer radio_station=”1″]
[UIRadioStation url=”https:// radio.sarrorecords.com.br:8001/deephouse ” type=”icecast” icecasturl=”https:// radio.sarrorecords.com.br:8000/status-json.xsl ” interval=”3s”]
[/UIMediaPlayer]

• This reply was modified 2 months, 2 weeks ago by iamzhirik.

Dear Alex,

So, except for not showing the name of the radio station, which is in the “server_name” field alternating with the “title” field of the JSON, it is working, that is, the “title” field is showing very well and playing the stream perfectly. However, the “station_name” parameter (which is not in the JSON) continues to work and replaces the “server_name”, but widhout alternating, only together before of the “title” field.

The spectrum color is also not following the “spectrum” field that I set to “amber”, but remains green.

But for me it worked, because until then I used a shortcode with PHP code to show the artist and song name before the player. Now, it is not necessary more, the player itself shows artist/song.

My configuration was as follows:

[UIMediaPlayer radio_station=”1″ mode=”extended” color=”#FFBF00″ width=”730″ spectrum=”#FFBF00 100″]
[UIRadioStation url=”https://radio.sarrorecords.com.br:8000/deephouse” type=”icecast” icecasturl=”https://radio.sarrorecords.com.br:8000/status-json.xsl” interval=”3s”]
[/UIMediaPlayer]

However, I think that alternation functionality is a good option that could leave more space for the “title” field, since there are long song names. Also it bring possibilities to presenting more information.

I think that some features could be implemented based on Icecast, of course if you wish, so that it could meet the tastes of many users more broadly. For example, the alternation with the “server_description” field, as long as the user also had the option of which available fields the user wants to present. It is just a suggestion.

This my streaming service is not yet was released. I am in the process of adjusting it, but it will soon be in production.

[credentials offer removed by moderator]

I leave my sincere thanks. Your player is very cool.

Best regards

• This reply was modified 2 months, 2 weeks ago by regivaldocosta.
• This reply was modified 2 months, 2 weeks ago by Steven Stern (sterndata).

@regivaldocosta

 Please don’t offer to send or post logon credentials on these forums: https://www.ads-software.com/support/guidelines#the-bad-stuff

It is not OK to offer, enter, or send site credentials on these forums. Thanks for your cooperation.

> ?However, the “station_name” parameter
In my player there is no such parameter as I know. So, not sure if I understand what you want to say

> The spectrum color is also not following the “spectrum” field
Maybe text editor added some invisible formatting if you edited shortcode. Here is some example of invisible formatting: https://alex-player-dev.x10.name/tmp/invisible-formatting.png. Try to copy all the text to “notepad” and paste it back to WordPress – this will clear the invisible formatting. I hate this invisible formatting stuff, but in most cases this can be the problem, I hope…

> It is just a suggestion.
In this case this feature definitely not in priority. I also hove some ideas about the player, but right now working on another project and this player not in priority for me at the moment. Maybe in closest future will improve this player with my little ideas.

> This my streaming service is not yet was released. I am in the process of adjusting it, but it will soon be in production.
Once you will have some release you can show me, interesting how it will look like ??

Also right now this player has only 4 star rating, so possibly this means that player is not perfect. If it is not hard for you, you can write a short feedback about your experience with the player.

Dear Alex,

I made a mistake, the native field is “name”, not “station_name”.

I copy/past the all shortcode content in two differents editor (gedit and notepadqq on Linux), but it no solve the problem.

About your priorities, I understand you.

As soon as the website is 99% ok, I will leave feedback.

I will definitely be giving feedback on this excellent player.

Thank you for all.

Best regards