There's no special character in the filename, and all other systems and departments record 100%.
Close Call Hits is the only system that has trouble recording.
Nope.
Here's a sample file name for Close Call Hits, which has the intermittent problem:
D:\Media\ScannerAudio\2018-04-26\Search with Scan\Close Call Hits _ _ 18-59-34-461.mp3
And here is a sample filename from another system, which records correctly 100% of the time as far as I can tell:
D:\Media\ScannerAudio\2018-04-27\Chambersburg Area School District - Clarks Knob\Transportation _ School Buses 5 _ 07-45-41-450.mp3
If the number of characters was an issue, the Chambersburg system would have more issues than Close Call Hits.
Given that I first noticed the problem after upgrading to firmware 1.16, is it possible that it could be a firmware issue somehow? Is ProScan looking for data that normally accompanies audio data to start recording (like the channel / frequency / system metadata), such that if that data was not sent or malformatted, that recording would not be started, even if audio data is sent and streamed normally?
I've been playing around with some of the 'View' options in ProScan, and different ways to take full advantage of dual monitors.
I'm running ProScan's View mode as 'Scanner Only (Detached Window). I'm displaying the scanner only on one monitor with resolution set at 1920 x 1080 and a Scale and layout set at 175%. This makes the scanner itself really big (like it would if the monitor was set to a lower resolution and I can read it at a quick glance, even from across the room!
Then I drag the History Log over to the other monitor with resolution also set at 1920 x 1080, but the Scale and layout set at 100%. This makes the log info smaller so it will fit the screen and show all of the information, as if the resolution was set higher!
Nothing really can be done in the software for this type of issue.
You misunderstood. It's not an issue, it's a feature! I'm complimenting your software for having the ability to do this.
That's the way I wanted it. I can set it so it's the same on both monitors, but I actually wanted the scanner really big. But I wanted the log smaller, so I can view all the data. Now I have the best of both worlds.
Okay very good to hear, I was worried for a minute.
I know this is a really big thread so I am sorry if it has been asked already.
Are there any plans for Whistler TRX to be a supported scanner?
Is there a feature in the database editor where I can sort frequencies in an analog system from smallest to largest?
Can someone in the right direction. So I record the traffic via WIFI from my 536HP ?
Also is there a manual for the PROSCAN ?
Big Thanks.-