ProScan: Official Software Thread

[ProScan]

ProScan Version 1.7 Build 2 includes the RadioReference Imports feature, improved Scanner Over IP, and bug fixes.

Supported scanners are the BCD996T, BC796D, BC785D, BC780XLT, BC296D, and the BC250D.

I'm thriving to make this the best Computer Aided Scanning program and suggestions are very much appreciated.

http://www.proscan.org/index.htm

Bob

 

[ProScan]

Whoot.

It will be nice to be able to have some different titles for the tags rather then whats programmed in the scanner. Sure it makes sense to be to see like 2ops37 but others may not know where that is.

For the Web Server & ScanCast? Is this what you're suggesting? Choose the custom format option and put in the text to be streamed out.

Next version 4.2 out in about ten days has a few minor changes. It looks like this:

 

[webstar22]

For the Web Server & ScanCast? Is this what you're suggesting? Choose the custom format option and put in the text to be streamed out.

Next version 4.2 out in about ten days has a few minor changes. It looks like this:

Thats exactly it. I was just whooting because I seen you posted that it will be possible to get it a little more customized.

 

[ProScan]

Next version 4.2 is just about ready. Release is planned for Friday. Anyone wishing an advance copy, email me.

 

[kzav]

I've been checking out the program, and it's definitely the best scanner program I've used so far, I'll be registering soon.

One issue, and it's probably my own error, when using the recording feature, the program seems to add new transmissions to the .wav files based solely on the talkgroup number, and without regard to the system. So, where two systems use the same talkgroup number, their transmissions get mixed together.

I'm using the program with a BCD996XT on conventional P25 channels (which most police departments in my area use) programmed as P25 One-Frequency Trunk systems to pick the unit IDs, and it seems that most of the systems use a talkgroup of "1". So when the scanner stops on Police Department A, using a talkgroup of 1, then stops on PD B, also using a talkgroup of 1, ProScan seems to put them together in one .wav file. ProScan doesn't start a new .wav file until the scanner stops on a system using a different talkgroup number. If I leave ProScan recording even for a short period of time, I get a .wav file with a mix of transmissions from four or five different police departments that all use talkgroup 1.

I found the setting to Separate Recording Each Activity, and that creates a separate file for each transmission. This fixes the problem of different systems being combined, but I'd rather have one file per system.

Am I missing a setting somewhere?

 

[ProScan]

I've been checking out the program, and it's definitely the best scanner program I've used so far, I'll be registering soon.

One issue, and it's probably my own error, when using the recording feature, the program seems to add new transmissions to the .wav files based solely on the talkgroup number, and without regard to the system. So, where two systems use the same talkgroup number, their transmissions get mixed together.

I'm using the program with a BCD996XT on conventional P25 channels (which most police departments in my area use) programmed as P25 One-Frequency Trunk systems to pick the unit IDs, and it seems that most of the systems use a talkgroup of "1". So when the scanner stops on Police Department A, using a talkgroup of 1, then stops on PD B, also using a talkgroup of 1, ProScan seems to put them together in one .wav file. ProScan doesn't start a new .wav file until the scanner stops on a system using a different talkgroup number. If I leave ProScan recording even for a short period of time, I get a .wav file with a mix of transmissions from four or five different police departments that all use talkgroup 1.

I found the setting to Separate Recording Each Activity, and that creates a separate file for each transmission. This fixes the problem of different systems being combined, but I'd rather have one file per system.

Am I missing a setting somewhere?

Your right about the recorder not using the channel to match the tgid. I will make it so the freq or tgid must match the system/site and channel in an upcoming release.

 

[datainmotion]

The keyboard shortcuts are sc heduled for a upcoming release. I will be doing more then just the spacebar and want to spend time on it to do it right.

Bob,

Just wanted to let you know how much some of us "mobile users" appreciate you considering this addition! Looking forward to it!

Thanks,

Mike

 

[kzav]

Your right about the recorder not using the channel to match the tgid. I will make it so the freq or tgid must match the system/site and channel in an upcoming release.

Great, thanks!

 

[ProScan]

I just released ProScan Ver. 4.2

ProScan supports the BCD996XT, BCD396XT, BCT15X, BC346XT, BCD996T, BCD396T, BCT15, BR330T, BC796D, BC785D, BC780XLT, BC296D, and the BC250D scanners.

• Added - History and Recording column resize and reorder capable.
• Added - Web Server - IP addresses logged to the Web Server Log.txt.
• Added - DMA portable scanner type - Put back in the Function Hold button on the virtual keypad.
• Added - Web Server and ScanCast - The current and peak listeners are shown.
• Added - Web Server and ScanCast - Metadata tag streaming added Unit ID's to the custom format.
• Added - Web Server and ScanCast - Metadata tag streaming added option to get data from file.
• Added - ScanCast - Secondary check if the IceCast / Shoutcast server is not responding. Before only the TCP connection is checked.
• Added - Audio level indicators now are colored green to yellow to red.
• Changed - History logging consolidated the Frequency and Talk Group ID grids.
• Changed - DMA DB - Only show the "Save Current Data" when the file closes if the data has changes.
• Changed - Web Server and ScanCast - Changed the method of streaming tags to the in-band method on IceCast servers. WinAmp now shows the tags instantly.
• Fixed - UID was showing only six digits instead of seven.
• Fixed Standard rebanding calculation.
• Fixed - ProScan Icon option set to "Display Colors" could cause application crash.

Bob

 

[randybcd396t]

4.2 is another great release. I'm running out of things to wish for.

 

[webstar22]

4.2 working good here. But I've run into an issue, my current provider for icecast which is incidentbroadcast just sent out an email saying they are shutting down (that sucks) so I think I am going to need to switch to rr.com now for my feed. But RR.com doesn't allow you to broadcast swat (TAC channels) so is there any ETA on getting sometype of mute flag for a talkgroup so it will record will just not get broadcast over the ScanCast.

 

[ProScan]

4.2 is another great release. I'm running out of things to wish for.

I wish I was running out of things to do. No end in site.

 

[randybcd396t]

I wish I was running out of things to do. No end in site.

The reason I'm running out is you are always thinking ahead. Keep up the good work.

 

[kennyblues]

Thanks for the update. Initial impressions are it works and looks good. My problem with the radio ID's seems to be solved, further scanning and logging needed at this end.

 

[mrkelso]

Giving 4.2 a run now on my Mac using Parallels and windows xp.

Stable as a rock and i like all the changes you made.

 

[jobes]

Another great release, Bob

 

[NYRHKY94]

Best "all-in-one" software package for the Uniden line out there - hands down!

 

[clayman]

Perhaps I'm missing something, but it appears to me that when doing a Custom Search and logging with the "Each Transmission New Row" checkbox cleared, the first hit on a frequency with a PL or DPL tone creates a line in the logging screen with the proper tone/code. However, getting hits with different PL/DPL tones/codes do not add another line with the proper value, instead it seems to be counted as a hit on the first freq/tone combo line. I really love ProScan, and it's logging/control interface is head & shoulders above the rest, I'm just trying to get each freq & PL/DPL to log with the total number of hits. I haven't tried having "Each Transmission New Row", but in the past the log files were enormous and took a lot of time to consolidate when each hit was a separate line in the log file.

Thank you Bob for a great program and all the time you've invested!

Clayton

 

[cabrubaker]

4.2 Web Server Stream Issues

I had to go back to version 4.1 of thee software to keep my Web Servers running. Version 4.2 is causing issues with distorted audio and constant buffering when using media players on handheld devices especially.

I thought the problem was related to installing version 4.2 over 4.1 so I did a clean install of 4.2 and still have issues. I also tried Scannercast to prove this and have no issues with this program either. Something in Version 4.2 is all I can figure.

Chris

 

[ProScan]

Perhaps I'm missing something, but it appears to me that when doing a Custom Search and logging with the "Each Transmission New Row" checkbox cleared, the first hit on a frequency with a PL or DPL tone creates a line in the logging screen with the proper tone/code. However, getting hits with different PL/DPL tones/codes do not add another line with the proper value, instead it seems to be counted as a hit on the first freq/tone combo line. I really love ProScan, and it's logging/control interface is head & shoulders above the rest, I'm just trying to get each freq & PL/DPL to log with the total number of hits. I haven't tried having "Each Transmission New Row", but in the past the log files were enormous and took a lot of time to consolidate when each hit was a separate line in the log file.

Thank you Bob for a great program and all the time you've invested!

Clayton

If you have a DMA type scanner, look for the option "DMA Scanners Only - Wait Up To 2 Seconds For Tone On Conventional Systems." located in the general options, logging section and check the check box.

If this option is checked, then the tone from the scanner will look for a match in the log.

On Non DMA type scanners, no attempt is made to match the tone with the log.

Tone logging is a problem because the tone info from the scanners arrive after the transmission starts and the log entry is made. On non DMA scanners, it can be 15 seconds. The tone detection is faster with the DMA scanners but not instantaneous.

 

[clayman]

Thank you much, I'll give it a try.

Clayton