SDS100/SDS200: Close call frequency from wav file

[Ubbe]

If you play a closecall wav file in the scanner and the display show info like TG's and subtones, then those data have to come from the wav header file and nowhere else. Look at the hex values in the header and try and match the display info with the hex values. The frequency isn't stored in text mode and the TG and subtones are probably also not stored as ascii text but as hex. Subtones could be stored as a 1 for CTCSS and a 2 for DCS and another position could have a 1 for the first possible subtone 67Hz and 2 for the next 69.3Hz and so on. So you probably need to compare different closecall wavs that have different subtones or TG's to be able to tell where in the header the data are stored.

/Ubbe

 

[deim]

Now show frequency.
like this:

D:\radio rec\4E865DDD\2019-04-06_11-53-53.wav 433.9750Mhz
D:\radio rec\4E86604A\2019-04-06_12-11-29.wav 462.4250Mhz
D:\radio rec\4E8662B4\2019-04-06_12-30-16.wav 462.4250Mhz
D:\radio rec\4E8768B8\2019-04-07_13-15-59.wav 158.1750Mhz
D:\radio rec\4E8972D7\2019-04-09_14-27-34.wav 165.1625Mhz

CloseCall.exe

drive.google.com

 

[Firekite]

Awesome! The more info we can get from saved CloseCall alerts (PL tone, NAC, other ID, etc), the more easily we can add to and refine the RR database. I think that’s fantastic.

 

[deim]

Add DCS, CTCSS, RAN code decoding

now in program output we can see codes:
D:\temp\Samples\CTCSS.wav 166.7375 Mhz CTCSS:146.2 Hz
D:\temp\Samples\CTCSS2.wav 167.2625 Mhz CTCSS:127.3 Hz
D:\temp\Samples\DCS.wav 163.850 Mhz DCS:565
D:\temp\Samples\DCS2.wav 164.50 Mhz DCS:364
D:\temp\Samples\NX48.wav 159.875 Mhz RAN:1
D:\temp\Samples\NX96.wav 158.3125 Mhz RAN:1
or
D:\radio rec\4E8768B8\2019-04-07_13-15-59.wav 158.1750Mhz no code
D:\radio rec\4E8972D7\2019-04-09_14-27-34.wav 165.1625Mhz no code
if no digital or analog code in close call.

CloseCall.exe

drive.google.com

 

[deim]

Can somebody send me Close call with RAN>16, DMR and APCO P25 NAC?

 

[deim]

Rewrite application and add some new futures.
Now you can write path to your folder with Uniden wav files and this program analyze them and generate Catalogue.csv.
csv file with next columns:

File name

Duration

Scan mode

Frequency

Code

Favorite name

System name

Department name

Channel name

Scan modes:
Close call, Normal scan and Search mode.
Now you can quickly find files with required frequency, favorites, systems...
If you open file in Excel you can sort files by different criteria:

Or like this:

catalogizator.zip

drive.google.com

 

[Ubbe]

Is it possible for you to add some code in the future when there is a trunked system and the frequency cell is empty? The frequency of the trunked channel starts at 4FC hex 1276 dec. The user ID or text tag in ascii starts at 55C hex 1372 dec, if that also could be included. Thank you very much for your efforts.

/Ubbe

 

[deim]

Is it possible for you to add some code in the future when there is a trunked system and the frequency cell is empty? The frequency of the trunked channel starts at 4FC hex 1276 dec. The user ID or text tag in ascii starts at 55C hex 1372 dec, if that also could be included. Thank you very much for your efforts.

/Ubbe

Ok. I will plan it on the next release

 

[deim]

Add new columns:

File name

Duration

Scan mode

Type

Frequency

Code

Favorite name

System name

Department name

Channel name

TGID

UID

UID Name

Type - radio transmission type

Tgid, UID, UID name - for trunk systems only.

Find interesting difference between SDS100/436hp.
If your favorite system have Unit ID name for this UID, UID in decimal form not write in wav file in SDS100.
In the same situation 436hp write both info, UID Name and UID in decimal form.

catalogizator.zip

drive.google.com

 

[Ubbe]

Than you very much for this wonderful catalogizator program! It's so much easier now to analyze the recordings. It even beats Whistler EZ-scan functionality when importing the result in a calc program.

There's a third mode, Search with Scan that are treated as Scan mode and the values from the search hits end up in the wrong place and also contain nonrelated info. All information, except trunked frequencies, are displayed so it's no big deal and it might be difficult to get a reliable trigger to instead set search mode, if that actually are correct, for those recordings.

/Ubbe

 

[deim]

Than you very much for this wonderful catalogizator program! It's so much easier now to analyze the recordings. It even beats Whistler EZ-scan functionality when importing the result in a calc program.

There's a third mode, Search with Scan that are treated as Scan mode and the values from the search hits end up in the wrong place and also contain nonrelated info. All information, except trunked frequencies, are displayed so it's no big deal and it might be difficult to get a reliable trigger to instead set search mode, if that actually are correct, for those recordings.

/Ubbe

Hi! Can you send me some examples with "Search with scan" mode. Unfortunately i haven`t got this kind of files and can`t recorder them because i am on business trip without my scanners.

 

[Ubbe]

Hi! Can you send me some examples with "Search with scan" mode. Unfortunately i haven`t got this kind of files and can`t recorder them because i am on business trip without my scanners.

There's no rush. I've waited three years for a better record analyze function so I can wait a couple of weeks or months until you are home and have some spare time.

Scan mode Type Frequency Favorite name System name Department name Channel name
normal scan mode bU 00.00 Mhz Search with Scan Search with Scan 420-423 422.5000MHz
normal scan mode bU 00.00 Mhz Search with Scan Search with Scan 420-423 Nt 0: S 0: TG 139: U 8383

2017-04-28_00-10-00.wav

drive.google.com

2017-04-27_23-55-15.wav

drive.google.com

/Ubbe

 

[deim]

Add support "Search with scan" mode wav files.
fix wav file duration calculating

Catalogization.exe

drive.google.com

 

[deim]

Thank you very much for help! This is last version of my program without GUI.
If you find critical bugs i fix them of course))). Just send me message.
Now i write another program whith next futures:

• filtering wav files by different criteria directly in program without CSV.
• Export filtered files in m3u playlist
• Export filtered files in CSV files.
• Play wav files directly in program.
• Sorting columns by ascending/descending like in Excel.

I think developing my new program takes 2-3 week, maybe more.

Demo video:

ps. When one simple question turn into interesting project for me))))

 

[Ubbe]

Super helpful program! So easy now to do traffic analyzes.

Small bug in the produced csv file. When there's a zero in the frequency it is deleted. A frequency like 405Mhz ends up as 45Mhz.

/Ubbe

 

[deim]

Super helpful program! So easy now to do traffic analyzes.

Small bug in the produced csv file. When there's a zero in the frequency it is deleted. A frequency like 405Mhz ends up as 45Mhz.

/Ubbe

Can you send me files with this frequency please. I try to fix this bug.

 

[Ubbe]

It's strange. I got 10 files with the middle zero missing in the csv file but one correct, and they are the same frequency.
Maybe I should try and run the program several times and see if the results differ. Yes, after the program where run several times it always strips the middle zero in the MHz and it is only in recordings done in search mode.

47_8812.wav

drive.google.com

49_85625.wav

drive.google.com

409_8562.wav

drive.google.com

/Ubbe

 

[deim]

i catch the bug. In different scan modes uses different algorithm to extract frequency.
in this case frequency contain in two byte 04 and 05 (405 Mhz) program take first byte 04 and concatenate it with second "05", but drop first falf byte because it zero.

bug fixed.

Catalogization.exe

drive.google.com

 

[Ubbe]

Excellent! Works perfect now!

/Ubbe

 

[deim]

New version with GUI: Uniden wav files player and organizer