I have seen many impressive multiple scanner setups and it got me wondering on how do you listen/record your scanners? I understand you can use ProScan to have the scanners recorded, but do you do anything extra with the recordings? Like have them in a web page for easy retrieval or an email sent daily for the links? Do you have a special web page you created that displays your scanners so you can review them (other than ProScan’s web server). I am going to be setting up 1 or 2 scanners to listen to my local police/fire and have been thinking on how the recordings can be presented. Just want to hear what you all have done with your setups.
Multiple Scanner Listening
- Thread starter zwheeloc
- Start date
- Status
@buddrousa ?
Each reciever instance I use saves with distinctive filenames locally (on the appropriate VM) , they get rync'd to the fileserver every 6 hrs and used for analysis/review (if needed), and then usually deleted after 30 days. Instances delete the files after being rsync'd successfully after 24 hours (to avoid filesystem bloat).
Each reciever instance I use saves with distinctive filenames locally (on the appropriate VM) , they get rync'd to the fileserver every 6 hrs and used for analysis/review (if needed), and then usually deleted after 30 days. Instances delete the files after being rsync'd successfully after 24 hours (to avoid filesystem bloat).
Last edited:
I've been streaming since 2005 and have been making archives available for download almost as long. Things have changed in one form or another through the years but I archive in multiple ways
Locally, ProScan logs every transmission from each radio into a folder with a year, month, and day subfolder. One ProScan instance for every radio running.
My Icecast streaming computer runs a custom bash script that records each feed and breaks it into 30 minute chunks. It saves and stores the file and then pushes a command to my website to add that file to the database. After some time, those files are purged do to space limitations.
Other SDRs get archived based on the software I am running and what their dedicated function may be.
Locally, ProScan logs every transmission from each radio into a folder with a year, month, and day subfolder. One ProScan instance for every radio running.
My Icecast streaming computer runs a custom bash script that records each feed and breaks it into 30 minute chunks. It saves and stores the file and then pushes a command to my website to add that file to the database. After some time, those files are purged do to space limitations.
Other SDRs get archived based on the software I am running and what their dedicated function may be.
I have files dating back for years
If you are recording a P25 (Lincoln, MA PD) I take it that you cannot save metadata on the audio stream of who is talking and have a web page show the ID of the transmission (like when dispatch talks, you will see dispatch displayed and when it switches to a car, it will show which car). I suppose you could have each transmission be a separate file and save the file with the talkgroup and ID and then possibly play them in sequence while translating the file name of who is speaking… Just would love to have a web page that when I press play, it will display who is speaking as the conversation goes on...
if your program records the RID & TGID in the filename, your website could parse the current filename and display (current talker, tgid, time & date) on the screen. Will depend on your coding prowess.
serial14
Member
- Joined
- Sep 20, 2020
- Messages
- 64
I've thought about this as well, and continue to do so. I've really come to enjoy scanning & finding new signals so my scanner collection is growing.
I started with ProScan to automate recording received signal meta data and audio recordings. The capabilities of ProScan are fantastic and has taken me a long way on my journey. I continue to utilize ProScan from time to time. Using it with more than one scanner at a time though didn't quite fit how I wanted to work. I absolutely don't view this as something against ProScan. Rather, how I want to utilize my scanners doesn't match what ProScan excels at.
I've been working on developing my own Scanner Software that specifically focuses on interfacing with multiple scanners at the same time. As an analogy, I'd put forth what the Data Center / Server room industry has done. Moving from single application on a single server to cloud computing or other clustering techniques. Like ProScan it records/logs/shares meta data on received signals and also records the associated audio and saves it to a file system.
In terms of File management, everything gets saved to a mapped network drive on my NAS. A typical folder structure is used to manage the date/time, system, and individual files. For play back, I simply use a media player( VLC, Windows Media Player, Audacity, etc ). I think there is opportunity for making this a little bit better, but haven't gotten that far yet.
I think I'd like to disclose more about my software project in the future, especially if there is interest from fellow RR members who have have "too many scanners" and "not enough scanners" all at the same time. Its still pretty raw right now and want to get a little bit farther before doing so. I've demonstrated to my self the approach & concept works and better matches how I personally want to utilize my scanners.
I started with ProScan to automate recording received signal meta data and audio recordings. The capabilities of ProScan are fantastic and has taken me a long way on my journey. I continue to utilize ProScan from time to time. Using it with more than one scanner at a time though didn't quite fit how I wanted to work. I absolutely don't view this as something against ProScan. Rather, how I want to utilize my scanners doesn't match what ProScan excels at.
I've been working on developing my own Scanner Software that specifically focuses on interfacing with multiple scanners at the same time. As an analogy, I'd put forth what the Data Center / Server room industry has done. Moving from single application on a single server to cloud computing or other clustering techniques. Like ProScan it records/logs/shares meta data on received signals and also records the associated audio and saves it to a file system.
In terms of File management, everything gets saved to a mapped network drive on my NAS. A typical folder structure is used to manage the date/time, system, and individual files. For play back, I simply use a media player( VLC, Windows Media Player, Audacity, etc ). I think there is opportunity for making this a little bit better, but haven't gotten that far yet.
I think I'd like to disclose more about my software project in the future, especially if there is interest from fellow RR members who have have "too many scanners" and "not enough scanners" all at the same time. Its still pretty raw right now and want to get a little bit farther before doing so. I've demonstrated to my self the approach & concept works and better matches how I personally want to utilize my scanners.
I see that phone app 5-0 Radio has this feature and I've been collating the TGIDs and comparing them to RadioReference database. I've noted nearly 50+ (and counting) TGIDs not in the RR master dbase for Seattle Police Dept however I don't know what to do with them. Check out the app and see what you think. It seems evident from the TGIDs I've logged that they're for mobile police radios.
Simply appending them to my Favorites for Puget Sound Emergency Radio Network (aka PERS) SPD talk group doesn't result in added listening. So I'm thinking more metadata is needed such as digital squelch code or something.
TGIDs are all that's needed. it probably because your location is receiving another site and the TGID are not affiliated with that site.
Try changing the system to ID Search so it will pick up all TGIDs affiliated with the site/s you're receiving.
- Status
Similar threads
