TwoToneDetect New TwoToneDetect in the works - Python based

[Thunderknight]

This is the best option to download it. This was the website before the creator sold the program out from under all of us without notice.

And there is still a free non-commercial version available. I’m not sure why people give him a hard time about selling to IAR. There is still a free version available from official channels...that is far better than many other software packages that just go paid or disappear.

 

[jhsands]

And there is still a free non-commercial version available. I’m not sure why people give him a hard time about selling to IAR. There is still a free version available from official channels...that is far better than many other software packages that just go paid or disappear.

Redundancy doesn't work.
Most tone.cfg files have to be rebuilt.
Can't use Pushover API.
Can't use Pushbullet API.
Audio hosting shut down [I made a forum post on how to setup your own].
Should I keep going?

"Any forwarding of information from or via this software to any third party system or application, and any use of this software in conjunction with any commercial, third party notification system or application, is strictly prohibited and constitutes a direct violation of the Terms of Use of this software (unless directly authorized in writing by the owner of Two Tone Detect."

Because if you read the fine print, you can't use another service for alert delivery, which means you can't send e-mails, texts, nor anything else. It's a program sitting there on your computer. Sure, it's free, but they have you in a legal gotcha if they want to. Do you want to take the chance of going to court for thousands of dollars over sending e-mails? I don't.

You use your phone's e-mail notifier (banner)? Notification system. In violation.
Use Outlook notification banner? Notification system. In violation.
Use Outlook notification banner? Third party application. In violation.
Use Google SMTP? Third party application. In violation.
Use Microsoft 365 for SMTP? Commercial system. In violation.
Use cPanel for SMTP? Commercial system. In violation.
...

 

[canthonysmith]

Exactly my point!

 

[aaknitt]

v73g is now available via IaR with the following bug fixes:

• Fixed record delay bug
• Fixed exclude time bugs
• Fixed bug related to sending messages sequentially
• Fixed bugs with encrypting and decrypting tones.cfg files
• Removed 4 and 10 second “ignore_after” minimums for AB and long tones, respectively

Andy

 

[eekdood]

Thanks for the update Andy. Is there a prescribed method for updating TTD when using the official IaR raspberryPi image?

Also, I noticed that the audio files are building up on the system. Are they automatically pruned? Or do I need to put something in place to remove old ones?

 

[aaknitt]

Thanks for the update Andy. Is there a prescribed method for updating TTD when using the official IaR raspberryPi image?

Also, I noticed that the audio files are building up on the system. Are they automatically pruned? Or do I need to put something in place to remove old ones?

If you request the standalone version here you'll get a link to download the .tgz package for Pi that you can put on the existing image if you don't want to start from a new image.

TTD should delete audio files older than 30 days. If that's not happening let me know.

Andy

 

[WebsterEMA]

Howdy. I've been using TTD for years now with no problems. Version 68. A couple months ago it started sending out pages for department A to both departments A and B. It's not every time, but it's fairly frequent. I've unzipped a fresh copy. I've checked the config files. I've changed radios. I've changed computers. I've taken Department B out of the config file, and run a copy of TTD on a second computer with JUST B. I've run a separate instance of TTD for each department. It's still sending out the page to the correct and the wrong department no matter what I do.

I've downloaded and setup the new version, 73g, and hope it works. But in case it doesn't, any advice on what might be causing this?

Edit: And it just did it again with 73g. This worked for years no problem. I really wish I could figure out why this is happening all of a sudden.

 

[jhsands]

Howdy. I've been using TTD for years now with no problems. Version 68. A couple months ago it started sending out pages for department A to both departments A and B. It's not every time, but it's fairly frequent. I've unzipped a fresh copy. I've checked the config files. I've changed radios. I've changed computers. I've taken Department B out of the config file, and run a copy of TTD on a second computer with JUST B. I've run a separate instance of TTD for each department. It's still sending out the page to the correct and the wrong department no matter what I do.

I've downloaded and setup the new version, 73g, and hope it works. But in case it doesn't, any advice on what might be causing this?

Edit: And it just did it again with 73g. This worked for years no problem. I really wish I could figure out why this is happening all of a sudden.

If you took B out of PC1 and left only A, it's impossible for it to send emails to B.

If you took A out of PC2 and left only B, it's impossible for it to send emails to A.

Make sure the config files saved properly.

Do you have the tones.cfg file before your last edit?

Some other things are that you have a wideband receiver and are getting some noise or dispatch changed paging equipment and it is leaking over. Try turning down your tone tolerance. Have you replaced the mic cord? Do any Windows updates?

 

[DC31]

Post one of your logfiles showing a dual alert.

 

[WebsterEMA]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

 

[WebsterEMA]

Post one of your logfiles showing a dual alert.

I hope this is the right info you're wanting. I deleted the email addresses it was sending to for privacy's sake, and found what I hope was the relevant section. If not, please let me know.

 

[NotATechGuy]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

 

[jhsands]

PC1 had A. It sent the page to A. PC2 had B, and it sent the page to B. Despite the fact it was a page for A. It's acting like they're the same department. This has been going on since mid November, so I'm sure there have been Windows updates, but I can't say which ones. And as I've said, it's doing it across multiple PC's. The config files are all saved correctly at least as far as I can tell.

Dispatch is using the same radio system, but got new computers for their CAD, though they got them in July and as I said this only started in November. Not sure if they're involved with the paging part or not. Our receiver is a base station radio that we had our radio guy wire up with a standard aux cord. But as I said, we've tried a different radio with a different wire, and no good.

There was even one instance where department C triggered this issue.

Department A's tones are
Atone = 634.5
Btone = 707.3

Department B's tones are
Atone = 707.3
Btone = 634.5

Department C's tones are
Atone = 707.3
Btone = 410.8

So, I'm sure A and B being swapped, and C having the same A tone are related to the issue. But they've been that way the entire time. What would you think I should try and set the tone tolerance to?

You realize dept A and dept B are just reversed A/B tones? If dispatch drops the tones twice in a row, you get both departments triggered.

 

[WebsterEMA]

You realize dept A and dept B are just reversed A/B tones? If dispatch drops the tones twice in a row, you get both departments triggered.

I realize that, but they don't drop the tones twice in a row. Dixon and only Dixon is paged, but it triggers Clay too.

 

[WebsterEMA]

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

It's currently set at .6 for both, the default. I can scale them both up a bit. I'll also pay attention and maybe try to record the tones next time they go off, to find out how long they go for.

 

[jhsands]

It's currently set at .6 for both, the default. I can scale them both up a bit. I'll also pay attention and maybe try to record the tones next time they go off, to find out how long they go for.

You can setup Audacity (free) with VOX recording and it will be substantially easier.

 

[WebsterEMA]

You can setup Audacity (free) with VOX recording and it will be substantially easier.

Have you tried adjusting your trigger times for the A tone and/or B tone? Depending on the type of paging system your dispatch is using depends on the timings. For a typical QCII system the A tone should broadcast for 1 second and the B tone for 3 second.

I recommend increasing the trigger time of your B tone. Start low at something like 0.5 seconds and work your way up. You don't want to increase it too much because there is a chance TTD could miss the tone if it doesn't see the frequency long enough due to poor tone decoding.

Thanks for Audacity recommendation. Hadn't even heard of it. But I downloaded it and found a copy of both tones and checked. Tone A is about 1 second. Tone 2 is about 3. So I left tone A at .6 and set tone B to 2.5 seconds. Since I wasn't sure how close I should get to the actual length. If I'm understanding things right, it just has to play at least that length right? So if it doesn't catch a bit of the tone, it'll still trigger with the slightly shorter tone lengths? I'm just guessing here though, so if I'm assuming wrong please let me know.

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

 

[NotATechGuy]

Thanks for Audacity recommendation. Hadn't even heard of it. But I downloaded it and found a copy of both tones and checked. Tone A is about 1 second. Tone 2 is about 3. So I left tone A at .6 and set tone B to 2.5 seconds. Since I wasn't sure how close I should get to the actual length. If I'm understanding things right, it just has to play at least that length right? So if it doesn't catch a bit of the tone, it'll still trigger with the slightly shorter tone lengths? I'm just guessing here though, so if I'm assuming wrong please let me know.

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

You don't want the tonelength set too long, the decoder isn't exact and it could lead it it not picking up the tone at all. Your interpretation is correct. The tone won't trigger until it sees the B tone frequency for X amount of seconds you set it for. In your case, you set btonelength = 2.5 the tone won't trigger until it sees your B tone frequency for 2.5 seconds.

My recommendation for you, since the A tone is only broadcast for a maximum of 1 second, your btonelength only needs to be greater than 1 second in order to not get a false positive. Setting your btonelength to ~1.2 should be sufficient. Trial and error at this point IMO.

 

[aaknitt]

I hope this is the right info you're wanting. I deleted the email addresses it was sending to for privacy's sake, and found what I hope was the relevant section. If not, please let me know.

Looking at your log file, it appears that your sound card is picking up noise at about 639 Hz when there is no radio traffic present. This is within the tolerance band of the 634 Hz tone so when the 707.3 Hz B tone is sent and then there is silence, the silence is detected as 639 Hz and triggers the other tone set. The solution may be as simple as increasing the Audio Squelch slider a bit on the main screen to prevent that low level 639 Hz noise from being detected. You want the main screen to say "No Audio" when there is no radio traffic and show the frequencies when there is radio traffic present.

Andy

 

[jhsands]

I appreciate the aid of everyone who's helped with this. I should've asked months ago, but I've been stuborning it out in the hopes I could fix things on my own.

This filter has fixed EVERY line noise problem I have had, which might aid is what @aaknitt has mentioned about the 639 Hz always present. I have several around the area. https://www.amazon.com/Mpow-Ground-Isolator-Stereo-System/dp/B019393MV2/


Also, you may be running a mono plug into a stereo female on your PC. That can be where your noise is coming from, a line short. Use this to eliminate that issue: https://www.amazon.com/Monoprice-107129-Stereo-Adaptor-Plated/dp/B005E2XZYC/