Fantastic! I've really come to appreciate the versatility of liquidsoap although its been a challenge (for me) to understand the rather terse documentation.
Great info here, following the previous posts in this thread I'm now feeding my audio stream to 2 different icecast servers simultaneously, but, I'm also looking to have the metadata feed both servers. Is there a way I can do that? Thanks!
I assume you have metadata going to a stream already?
if not add -M then the name of the .json file that has the talkgroups in each of you op25 command lines.
Excellent! Although liquidsoap can be intimidating to configure, its very stable. Running op25 and liquidsoap as services gives you the ability to independently upgrade or make changes to op25 without disrupting liquidsoap and thereby dropping your connection (feed) to BCFY and listener connections.
Thanks for your response, your posts have been very helpful to me. The configuration I'm going for is feeding identical data (talkgroups) to an icecast server running on my local lan and then also feeding the broadcastify server. So, same audio, same talkgroup data to both servers.
Great info here, following the previous posts in this thread I'm now feeding my audio stream to 2 different icecast servers simultaneously, but, I'm also looking to have the metadata feed both servers. Is there a way I can do that? Thanks!
Unclear. You'd have to research whether liquidsoap can receive metadata and multiplex it. The "normal" op25 metadata setup sends direct to the destination server, but what you'd need in this case is op25 to send to liquidsoap and then liquidsoap to send onward.
When I saw how easy it was to generate multiple audio streams from liquidsoap it just begged the question about the metadata.
I'm not a developer though and I'm pretty sure you and Bill know way more than I ever want to about liquidsoap and how metadata is handled! Thanks to you, Bill and anyone else who came up with the current methods. It has been rock solid for me.
When I saw how easy it was to generate multiple audio streams from liquidsoap it just begged the question about the metadata.
I'm not a developer though and I'm pretty sure you and Bill know way more than I ever want to about liquidsoap and how metadata is handled! Thanks to you, Bill and anyone else who came up with the current methods. It has been rock solid for me.
I've never really looked into the metadata side of liquidsoap until earlier today. It has some capabilities of manipulating it when it is already embedded in the stream, but I couldn't see a way of receiving the metadata from op25. Conceivably you could achieve the same functionality by streaming to a local icecast2 server and then have that server forward the streams on to the two remote destinations.