Here is a youtube video with both v57 and v58 up and running showing two different frequencies.
Two Tone Detect V58 and V57 frequency differences - YouTube
Two Tone Detect V58 and V57 frequency differences - YouTube
After about an hour and a half generating tones with Audacity and running v58 I found it failed to picked up a tone below 515. All but two of the AB tones in my tone file have at least one tone below 515 therefore it rarely found a match. I ran the same setup with v57(a) with no problem. I agree with "mghq" in what he found.
Hope this is some help. Thanks again Andy.
I just reposted v58 to the program page after rebuilding it. I didn't make any code changes, just did a rebuild of the EXE. It appears to be working properly. Give it a shot and let me know.
Thanks,
Andy
We have a few radios kicking around. Can either the Motorola CP200 or M1225 work to scan? If so, would I use the USB programming cable to connect to the PC to work?
Rather not have to purchase a separate scanner for this.
I just reposted v58 to the program page after rebuilding it. I didn't make any code changes, just did a rebuild of the EXE. It appears to be working properly. Give it a shot and let me know.
Thanks,
Andy
I just reposted v58 to the program page after rebuilding it. I didn't make any code changes, just did a rebuild of the EXE. It appears to be working properly. Give it a shot and let me know.
Thanks,
Andy
v58 missed the DC tone last night. Well it didn't actually miss it as much as it incorrectly identified it as another tone.
There is overlap with tone tolerance, but I would think that it would pick the one closest to the actual defined value. I think I found the reason why I had my tolerance dialed in so tight. In testing, it selected the correct tone once in about 10-15 tries.
I am running at 1.0% tone tolerance
642 should allow 635.58 - 648.42
634 should allow 627.66 - 640.34
Overlap = 635.58 - 640.34
Below is my tones.cfg and attached are the tones that I captured and used to reproduce this.
Tones.cfg:
[Tone01]
Atone = 642
Btone = 1285
Btonelength = .4
Description = DC
mp3_Emails = EMAIL@EMAIL.com
alert_command = D:\TwoToneDetect\Scripts\Alert.bat [d]
playback_during_record = 1
[Tone02]
Atone = 634
Btone = 1285
Btonelength = .4
Description = ANYSTATION
mp3_Emails = EMAIL@EMAIL.com
Hi everyone,
A lot of people have been asking for a speech to text feature to translate the spoken dispatches into text. This isn't easy. Speech to text systems are still not very accurate. The systems we all use every day that are decently accurate like Google voice search on Android, Ford Sync, etc. work well because the person using them knows that they're using a voice to text system and they speak slowly and clearly, usually using common phrases. Dispatchers, not so much. Here is a link to a website where you can try Google's speech to text software:
HTML5 Presentation
You'll need to use a newer verion of the Chrome browser to use it. Instead of speaking into your microphone, use your Line In and feed it audio from your dispatch center. If your results are anything like mine, it doesn't work very well. There is a "backdoor" way to access the Google voice to text system, and I could implement this in TwoToneDetect, but I don't think the results are good enough to be useful for anyone. Give it a try with your audio and let me know if your results are any better. If it works well for enough people I can add it.
Andy
Andy
Has anyone else gotten the "Index Error" in v58? I got it once today on one of two setups monitoring the same channel and hadn't seen it before with v58.
Thanks,
Andy