TwoToneDetect New TwoToneDetect in the works - Python based

[Deziel0495]

Thanks @aaknitt. Your change logs help a lot!

I just suggested to IaR support it would be helpful to list the current version available on the settings webpage for subscribers rather than "download the latest version". Save me from downloading it periodically to confirm I have the latest version. Having a changelog listed too wouldn't hurt. Maybe you could suggest that. 😉

 

[Andy2712]

I cannot seem to get the latest versions to run on my computer. It doesn't seem to recognize the speakers are plugged in and won't start. I can't figure it out.

 

[mattnelson26]

i rebooted my computer and now i get this error message
Traceback (most recent call last):
File "TwoToneDetect70.py", line 543, in alert
File "site-packages\pyaudio.py", line 747, in open
IOError: [Errno Device unavailable] -9985

0
after record
delay timer RODGERS ALL CALL 10:41:38 on 11/26/21
Traceback (most recent call last):
File "TwoToneDetect70.py", line 675, in alert
UnboundLocalError: local variable 'recordstream' referenced before assignment

 

[aaknitt]

i rebooted my computer and now i get this error message
Traceback (most recent call last):
File "TwoToneDetect70.py", line 543, in alert
File "site-packages\pyaudio.py", line 747, in open
IOError: [Errno Device unavailable] -9985

0
after record
delay timer RODGERS ALL CALL 10:41:38 on 11/26/21
Traceback (most recent call last):
File "TwoToneDetect70.py", line 675, in alert
UnboundLocalError: local variable 'recordstream' referenced before assignment

TTD isn't able to find your audio device for some reason. It's possible that the audio device indexes changed during reboot...you may need to reselect the audio device on the main TTD screen and restart TTD to get it working if that's the case.

 

[xxbryantd]

Is there a way to send the audio recording without the subject and body filled out? I leave it blank and it still sends a blank space in the message for where th text would be.

 

[al911er]

I think I have it corrected. Need to wait for some alert tones

Having the same issue, How did you correct it? Thanx

 

[MikeOrlando02]

Audio Cut Short

I have several agencies currently on TTD 73g, they have been all setup the same as far as tolerance, record time, delays. Everything seems to be running smoothly EXCEPT for one agency who's audio gets cut mid transmission at 15 seconds consistently. Other agencies seem to be monitoring for silence correctly. I have even increased the times slightly with the same result at 15 seconds.



Most of my agencies are at 15 seconds, but I bumped this one up to 20 and it still cuts off at 15 seconds. Not sure if the record release time is figured in there, but still a few seconds short.

Looking at the log:

543.1829268292682 4950 1640481185.699798
559.3170731707318 3041 1640481185.8785863
543.1829268292682 2813 1640481186.064343
Waiting for Silence T Rescue 19:13:06 on 12/25/21
Done recording T Rescue 19:13:06 on 12/25/21
./audio/T_Rescue_2021_12_25_19_12_47.wav
done writing WAV T Rescue 19:13:06 on 12/25/21
2172.731707317073 4123 1640481186.2501035
done converting to MP3 T Rescue 19:13:06 on 12/25/21
473.2682926829268 16468 1640481186.4350564

It appears the gap is 0.1857605 between the log entries, no where near the 0.7 release time. I don't know what I am missing, but would appreciate any direction.

I see that 73 I (or L??) has been released and I will be giving that a try to see if it resolves my issue.

 

[aaknitt]

Audio Cut Short

I have several agencies currently on TTD 73g, they have been all setup the same as far as tolerance, record time, delays. Everything seems to be running smoothly EXCEPT for one agency who's audio gets cut mid transmission at 15 seconds consistently. Other agencies seem to be monitoring for silence correctly. I have even increased the times slightly with the same result at 15 seconds.

View attachment 114103

Most of my agencies are at 15 seconds, but I bumped this one up to 20 and it still cuts off at 15 seconds. Not sure if the record release time is figured in there, but still a few seconds short.

Looking at the log:

543.1829268292682 4950 1640481185.699798
559.3170731707318 3041 1640481185.8785863
543.1829268292682 2813 1640481186.064343
Waiting for Silence T Rescue 19:13:06 on 12/25/21
Done recording T Rescue 19:13:06 on 12/25/21
./audio/T_Rescue_2021_12_25_19_12_47.wav
done writing WAV T Rescue 19:13:06 on 12/25/21
2172.731707317073 4123 1640481186.2501035
done converting to MP3 T Rescue 19:13:06 on 12/25/21
473.2682926829268 16468 1640481186.4350564

It appears the gap is 0.1857605 between the log entries, no where near the 0.7 release time. I don't know what I am missing, but would appreciate any direction.

I see that 73 I (or L??) has been released and I will be giving that a try to see if it resolves my issue.

Most likely an issue with the Audio Squelch threshold. If it's stopping at 15 seconds, it's not detecting that audio is present (even when it actually is) so the Audio Squelch slider on the main screen probably needs to be decreased. This can happen when the tones are louder than the voice dispatch...the tones are loud enough for TTD to see them but the voice isn't...reducing the squelch level should resolve it.

Andy

 

[MikeOrlando02]

I believe I am following the reason this is happening. I am currently at 53 and this does put be close to the baseline level. This would explain why it always affects this only agency if it is based on their tone levels.

If I go much lower I am going to processing the dead air more frequently as I have no more room to move. I will lower it an test, but it looks like I will be processing 24/7 to search for a tone.



Thanks Andy, Merry Christmas.

 

[MikeOrlando02]

This morning the trouble agency was paged and it again cut off at 15 seconds, despite squelch being well under the baseline audio level (it is constantly processing). Right after this page, mutual aide was requested and the next agency recorded at 32 seconds, with nearly the same settings. I will look everything over again, but kind of at a loss. Maybe this is the push to upgrade to the latest TTD?

 

[aaknitt]

This morning the trouble agency was paged and it again cut off at 15 seconds, despite squelch being well under the baseline audio level (it is constantly processing). Right after this page, mutual aide was requested and the next agency recorded at 32 seconds, with nearly the same settings. I will look everything over again, but kind of at a loss. Maybe this is the push to upgrade to the latest TTD?

View attachment 114110

Any chance you have duplicate tone values ([Tone1], etc.) in the tones.cfg file?

 

[MikeOrlando02]

Any chance you have duplicate tone values ([Tone1], etc.) in the tones.cfg file?

I have keys for [Tone1] - [Tone10], no duplicate tone key numbers

 

[Deziel0495]

Anyone use TTD with IaR and have enabled the new feature to send TTD alerts to text/email addresses?

I enabled it yesterday on my user profile. Got a test page today at 12:20, got the push notification almost instantly as usual but it's almost 2 hours later and still no text or email. I expect there to be some delay but nothing like that. I feel like I'm missing something.

Using the latest version of TTD 73I.

 

[DC31]

Anyone use TTD with IaR and have enabled the new feature to send TTD alerts to text/email addresses?

I enabled it yesterday on my user profile. Got a test page today at 12:20, got the push notification almost instantly as usual but it's almost 2 hours later and still no text or email. I expect there to be some delay but nothing like that. I feel like I'm missing something.

Using the latest version of TTD 73I.

That email delivery is on the IaR side, not in in the TTD program. If you are receiving the IaR push notification immediately, that shows the TTD program is doing its thing. I would suggest posing your question to to IaR customer support, they can probably fix it up in short order.

 

[Deziel0495]

That email delivery is on the IaR side, not in in the TTD program. If you are receiving the IaR push notification immediately, that shows the TTD program is doing its thing. I would suggest posing your question to to IaR customer support, they can probably fix it up in short order.

Yup I'm speaking with them now. Figured someone else may have ran into the same issue and could shed some light on it. I'll post my findings.

EDIT: IaR's tech team is investigating. They checked over my profile and everything is set correctly and as mentioned above they also said if push notifications are working then TTD is working as it should. No text and no primary/secondary emails as of yet, 3 hours later. More to come...

 

[MikeOrlando02]

Is email_subject a valid tones.cfg key? Is there a current list as the sample that is included with the latest TTD version is the minimum.

email_subject = [d] Page Received at [t]

 

[MikeOrlando02]

Is email_subject a valid tones.cfg key? Is there a current list as the sample that is included with the latest TTD version is the minimum.

email_subject = [d] Page Received at [t]

I found when I compared the original tones.cfg with the version after you edit tones it added the other keys I was looking for, jumped the gun with the post, but though maybe someone else could benefit.

playback_during_record = 0
gaplength =
exclude_from =
exclude_to =
post_email_command =
email_subject = [d] Page Received at [t]
email_body = [d] Page Received at [t]
alert_command =
tone_tolerance = 0.02
iar_tone_id =

 

[MikeOrlando02]

Our dispatch center pages twice in a row for all calls. I am having more issues in the latest version with catching the second tone where I want to end the first page and send and then start recording the second separately. It my understanding the tone is not put back on the detection list until the active page is completed. Is my only option here to adjust the record release time?

['Tone3', 'WRS Rescue', 1641067411.9170167, 0]
Adding WRS Rescue back to detection list after 0.0 second delay

 

[aaknitt]

Our dispatch center pages twice in a row for all calls. I am having more issues in the latest version with catching the second tone where I want to end the first page and send and then start recording the second separately. It my understanding the tone is not put back on the detection list until the active page is completed. Is my only option here to adjust the record release time?

['Tone3', 'WRS Rescue', 1641067411.9170167, 0]
Adding WRS Rescue back to detection list after 0.0 second delay

The "record time", "release time" and the "ignore after" parameters would all factor into that (though it looks like you have ignore after set to 0 already).

 

[MikeOrlando02]

The "record time", "release time" and the "ignore after" parameters would all factor into that (though it looks like you have ignore after set to 0 already).

Thanks. I have been tweaking them day by day and looking at the results.