Alias streaming logic

[Austin Hruskach]

I use a "wildcard" alias to record (and stream) all p25 talkgroups 0-65535. This works great for monitoring new and unknown talkgroups. But with this In effect, I can't disable any talkgroups / aliases from streaming and recording because that alias range logic wants to stream it.

I use that wildcard to stream everything to broadcastify calls, but I also want to disable the upload of specific talkgroups that I believe shouldn't be streamed publicly. With the wildcard active, if I disable the streaming for that talkgroup, it still slips thru and gets uploaded.

I wish that if a talkgroup is included in a single TGID alias, and an alias with a TGID Range, the single TGID alias would take priority in streaming/ recording preference.

Or, if any one instance of a TGID has streaming/ recording disabled, that should make all instances of that TGID on any alias to not stream. 

[John Perry]

I have the same kind of setup, I think. Been using Sdrtrunk for years and I honestly still don't fully understand some the alias stuff. 

So what I did was I made a wildcard group called FULL that pushes almost everything to calls, openmhz, rdioscanner, etc, (wildcard talkgroups are definitely the fastest way to discover new stuff.)

But personally I don't care to listen to things like Supervisor Barbra from the City Buses keying up for 10 mins or John from the Power company saying a bunch of city circuit numbers from down in the hole, but some people DO like to listen to that stuff. 

So to "solve" this problem, I made another alias group called LOCKOUT,  and put the lockout alias into the streaming channels you don't want that extra stuff to play.   

Also I had to do some odd logic in the FULL group list, so for example if your "wildcard "list is 0-65535, but you wanted to lockout only TG 3000. you would need split the list. So I remake my FULL alias list so it would be TG's 0-2999, then TG's 3001-65535 which bypasses 3000. 

(I now just take the TG's I want to lockout and feed the numbers to AI to make my lists because it got fragmented over the years from doing it in my head.)

So I guess you have to build a lockout list like I did. And everything you don't lockout can still go to CALLS if you wanted, and the listener can make a playlist and sort it all out, but for regular Broadcastify type feeds you can't do that.

I have one regular Broadcastify feed that plays the wildcard talkgroups, but doesn't play the lockouts. 

This all will probably confuse you. But it's how I solved the issue. I had to work it backwards so I don't really understand it myself.

[John Perry]

Maybe instead of changing how overlapping aliases take priority, SDRTrunk could add a TGID exclusion box to the range alias. So if FULL is 0–65535, you could exclude 3000 (or a list of TGIDs) and those TGIDs simply wouldn't match FULL.

That's basically what I'm doing manually now by breaking FULL into multiple ranges around the TGIDs I want excluded. It would solve this without changing the existing alias logic and potentially affecting other setups.