API for RadioCaster

[Bjorn]

Would love to be able to turn broadcasting on and off on RadioCaster via API the same way we can do with RadioBOSS. Is this something that’s already possible?

Thanks!

 

[djsoft]

Would love to be able to turn broadcasting on and off on RadioCaster via API the same way we can do with RadioBOSS. Is this something that’s already possible?

RadioCaster does not have an API so it's not possible.

 

[Bjorn]

Would it be possible to add in the future? Or is there any way to use other ways to remotely start/stop stream?

 

[djsoft]

Would it be possible to add in the future? Or is there any way to use other ways to remotely start/stop stream?

I'm not sure about it, API for a small program like RadioCaster seems overkill. You may consider using RadioBOSS for streaming, it has encoder control via the API.

 

[southernfm]

This is an interesting idea that I think could benefit us too, but we do understand that RadioCaster is a smaller program.

We currently have 2 sites - studio and transmitter site. We use the pira.cz silence detector software and we'd like to invoke API commands so that when silence is detected, it stops RadioCaster on the studio site, and starts streaming on the transmitter site to allow our backup music to play to air. Then when audio resumes, it does the opposite - stop streaming on the transmitter site instance, and starts it on the studio end.

Currently it's a manual process where we stop streaming and start it manually. The only other idea I've had is getting a CMD script to force close the app, and open the other... but that screams danger...

We would use RadioBOSS, but I'm worried about the resource usage, as they're only small NUCs and running a full instance may be less reliable than the Caster software.

 

[djsoft]

Currently it's a manual process where we stop streaming and start it manually. The only other idea I've had is getting a CMD script to force close the app, and open the other... but that screams danger...

Terminating a process is not a good idea. It may damage the settings files and when it's started next, it can lose encoders or any other configuration.

We would use RadioBOSS, but I'm worried about the resource usage, as they're only small NUCs and running a full instance may be less reliable than the Caster software.

In terms of resource usage there's no much difference. Majority of CPU utilization comes from the encoding process, not from the UI. In RadioBOSS, just remove all unneeded tabs, disable nowplaying visualization (Settings > View), and it'll use about the same resources as RadioCaster.