Don't show specific metadata

[ibek95]

Hi Dmitry,

due to technical reasons I have to play an add-trigger every now and then. I send my metadata direct to TuneIn with settings like PartnerKey, ID, etc. in this field:

checkbox "current title" is of course activated
But problem then is, that this add-trigger-metadata also appears on TuneIn

Is it possible for you to build something that this specific titles (with always the same name) are somehow filtered and will NOT be send to TuneIn? So I can say; please send all current titles except the ones with the name "add-trigger" f.e.
That would be a great new feature.

(It doesn't help to just set a category with the add-trigger-track which has the setting that the title should not be shown - because I have to send the add-trigger as it is so that the server from another service recognizes it's time for adds. I am just talking about the things that are send with "GET" to TuneIn.)

 

[djsoft]

This is not currently supported. You can create a File Type and configure it to "Do not send streaming titles" but if you need those titles for something else, this will not work.

Another possibility if you create a "proxy" script on your web site. RadioBOSS's HTTP request will query your script, and it will check the track title, if it's not the ad trigger one, pass request to Tune In, otherwise do nothing.

 

[ibek95]

but if you need those titles for something else, this will not work.

Yes, that's the problem I have.

Would it be much work for you to add a new "filter"-feature like described within the settings from the screenshot? I think many users of the same webradio-service I use could profit from that.

 

[djsoft]

Would it be much work for you to add a new "filter"-feature like described within the settings from the screenshot? I think many users of the same webradio-service I use could profit from that.

Currently HTTP requests do not have any filters and we do not plan on adding those at this moment, I'm sorry. This is because requests are usually made to custom scripts, and they can implement all sorts of filtering/processing of the data received, so those filters will almost never be needed.

In your case I think a viable solution is to implement a proxy script (see the previous post), just ask AI and it'll write one for you, AIs know RadioBOSS well so it's an easy task. Deploy it on your web site and make RadioBOSS query it instead of sending requests to Tune In directly.

 

[ibek95]

just ask AI and it'll write one for you

I tried that with ChatGPT for my dedicated Windows Server 2022 but I always had 502http-errors in the RadioBoss-Log.

 

[ibek95]

Hi Dmitry, I think I found a solution now:

RadioBOSS now sends metadata to http://127.0.0.1:port/tunein instead of directly to TuneIn. The proxy forwards normal track metadata to TuneIn via HTTPS and replaces the AD TRIGGER with an individual text from me.

The original ad-trigger mechanism remains unchanged. The proxy runs under a non-admin Windows user, starts automatically at login, and stores the TuneIn Partner Key encrypted with Windows DPAPI. It listens only on localhost; no public firewall port was opened.

Would appreciate your short opinion on this