There is no way to scan "in the background" while receiving another transmission on a conventional (i.e. non-trunked) channel. When it is receiving a transmission, the scanner's RF is tuned to that frequency. To check any other frequency for radio traffic, the scanner must retune the RF to the frequency to check, and when it does that it will stop being tuned to the original traffic...and you hear a break while that happens.
I hear what you're saying and I understand all that and it makes perfect sense. I am just saying this could be improved on greatly as it can be scanned in the background. Every conventional frequency is stored in an internal bank. So in the firmware it can be programmed to follow certain rules. As it shouldn't be listening for traffic or open squelch, it should be checking for open circuit instead on a certain bank and if that bank is set to priority and it's circuit is open then close the current bank if not a priority channel and open the priority channel for transmission.
scan => if priority => close non priority => open priority => else => continue scanning
As it is now it's listening for traffic when it can be done in the background via an open and closed banked. Multi task wouldn't be something I would think would be hard to implement as it's done in all kinds of devices these days. So basically instead of listening it's looking for a open or close bank and if it's set to priority.
Not sure what RS scanner you had, but 25 years ago, I was doing scanners at RS, and none of the scanners back then can do what you describe.
It's a Pro-95 and I promise it does this. I wish there was a way I could take a video to demonstrate this. I could probably make one with Wx Priority even though there isn't any severe weather. Even on the 996XT it interrupts when Wx Priority is on on the Pro-95 it doesn't.
Not sure what your 4th paragraph means. Talkgroups are by definition on trunked systems, but you refer to it as being associated with a conventional system. What you mean probably makes sense, but what you wrote I'm having trouble following. Maybe I need another cup of coffee...
I probably missed worded that. I meant groups, not really talk groups persay. Like on my conventional systems I have them broken down into groups. For example one system is called Balch Springs. I have groups, one for PD and one for Fire. If I set all the fire freq to priority in that group but don't turn on Priority or Priority + scan and one of those priority freq receives traffic it will automatically switch to that priority channel within that conventional system regardless of the current traffic and without interrupting to check for traffic. It even shows P on the screen to indicate it's a priority channel. BUT if there is conventional traffic regardless if it's priority or not, preemptive priority scan for the trunk or P25 system won't break in if it detects a priority channel. If will only do preemptive priority IF the current traffic is from a trunk or P25 system. That just seems like a fundamental flaw. That all goes back to detecting open closed banks. If it has to listen for traffic it should be able to do that in the background without it interrupting current non-priority traffic.
I may not have it set up correctly or missing something but that is how I have observed it for the past few days. I guess I need to try to find a way to make a video to demo this behavior as I know it's a little hard to explain it without proof.
