Allow upload of different talkgroups to different OpenMhz systems

[bab5871]

I guess this is more of an enhancement/feature request. Currently you can define a system and upload talkgroups to a single OpenMHZ system. In the interest of reducing the number of SDR dongles required it would be awesome to be able to split a system to upload to multiple places.

For example I currently run a stream to broadcastify/openMhz of a specific subset of talkgroups for Fire/EMS. I would additionally like to process other talkgroups from the same system and upload them to a separate Police/Sheriff feed for broadcastify/OpenMhz.

It seems this is possible for at least Broadcastify via some modifications of the scripts used as documented here. It would be great to have this ability with OpenMhz uploads as well with the intended goal being to not have to add more SDR dongles to a system if possible.

[ratmandu]

This could probably be done pretty easily with an external upload script. I've got one that I use for uploading the same file to multiple OpenMHZ instances here: https://github.com/ratmandu/trunk-recorder-multi-uploader

I don't think it would be too hard to add some logic to check the talkgroup before upload, and choose the endpoint to upload to based on that.

[robotastic]

I could be wrong, but I think this should be possible using a different talkgroup.csv file for each "system". You would end up monitoring the control twice, once for each subset of the system, but it shouldn't take too many resources. In the talkgroup.csv for each system, just include the TGs you want recorded. If you set the recordUnknown flag to true for each system, it will only record the talkgroups in the .csv.

[bab5871]

Would you need extra hardware to do this? Currently running two dongles off of an LNA/splitter and would like to keep that the same rather than worrying about splitting to 4 dongles. The idea being monitor the same system and upload police talkgroups to one OpenMHZ/Broadcastify stream, and Fire/EMS to another separate one.