steve0622
Member
ok....thanks for the advise...will give those options a try and continue testing.
I am testing the 59 version and all is working ok with 1 exception. To monitor, i am using an woxoun uvd1p dual band radio with ems on side A and fire on side B. That has worked out good at capturing the pages for both since they are 2 different frequencies. Took a little tweaking but that end including the volume is working perfect. The issue im having is my email address is set under mp3 for both tones, but when I recieve the message on my galaxy s III, I am receiving the .mp3 and the .amr. There are no email addy's under the .amr. Anyone experiencing the same thing? I can post the log file, but will be later this evening. Currently our fire dept. is using the software from Comtekk, which isnt detecting the tones most of the time, and I can't seem to get anyone from tech support on that issue. We are looking to move our current system from comtekk to TTD if we can get everything configured and operational.
1) Yes, I'm confusing you with the picture. The picture shows an A tone length of .6 seconds.
2) Unlike v58, the program doesn't wait before looking for the Btone. Once the A tone is over, it expects the Btone to begin immediately (with no gap between tones), and it has to be continuously present for the length of Btonelength in order for the alert to be generated.
Andy
Thanks for the clarification. Now I am wondering how your program knows to look a the last 400ms of the A tone. All the tones that i monitor for start with about 500ms of dead air transmission (probably the PL tone?) just prior to the start of the A tone. If the program is calculating where to start looking for the A tone, at what point does it start that calculation, the start of audio or the start of the A tone? In my case those two points are 500ms apart.
It doesn't care when the A tone starts. It's continuously sampling audio. In the case of the example in the picture, when it sees a sequence of audio that includes .6 seconds of A tone immediately followed by 2 seconds of B tone, it will generate an alert for that tone set. It doesn't care what comes before or after that audio sequence.
Andy
Where do you set the A tone length? I'm not seeing that option in the editor.
Gotcha. And the log.txt file lists the freq for each of those 200 ms samples. Set the atonelength to 0.2 and it will look for a btone after detecting the a tone in one sample. Set it to .4 and it will require two a tone samples consecutively before the b tone, etc
I have been using 58a for a couple weeks testing and just today decided to try and switch up to ver 59. A little later there was a tone out for a fire dept that uses a longtone of 433.7 for some reason this caused the program to detect and send a message 4 times. Any thought what may have caused that?
I have been using a tone length of 7 and debounce of 3 when I put it back to 58b everything worked fine again.
Tones.cfg
[Tone1]
Atone = 368.5
Btone = 539.0
Btonelength = 3
Btonedebounce = 2
Description = Amb
mp3_Emails = "JohnD"<xxxxxxxxxx@vzwpix.com>
exclude_from = 22:00
exclude_to = 07:00
ignore_after = 60
[Longtone1]
Longtone = 433.7
Longtonelength = 7
Longtonedebounce = 2
Description = Fire
ignore_after = 60
mp3_emails = "JohnD"<xxxxxxxxxx@vzwpix.com>,"Grt Sheriff"<xxxxxxxxxx@vzwpix.com>,"Kevin Chief"<xxxxxxxxxx@vzwpix.com>
Log.txt
uccesfully retrieved local tone info
Succesfully retrieved local tone info
Tone1
Longtone1
defaultdict(<type 'list'>, {'Fire': array([ 433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7,
433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7,
433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7,
433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7, 433.7,
433.7, 433.7, 433.7]), 'Amb': array([ 368.5, 368.5, 539. , 539. , 539. , 539. , 539. , 539. ,
539. , 539. , 539. , 539. , 539. , 539. , 539. , 539. ,
539. ])})
defaultdict(<type 'list'>, {'Fire': 1, 'Amb': 0})
Andy,
Has there also been a change in the calculation of the tone tolerance in v59? I have 2 A tones that are very close and when the tolerance is set too high (1%) the tone is incorrectly identified prior to v59. In v59, it actually identified both tone sets (very cool) but it should have only seen one. It seems that my tone tolerance of .5% is not being calculated.
With .5% I expect the A tones to have no over lap:
795 (791.025 - 798.975)
806 (801.97 - 810.03)
Found the issue with this. I had hard-coded a 2% tolerance into v59 for testing and forgot to change it back to being configurable. I just posted a v59a that has a fix for this that should give the correct tolerance.
Andy
I apologize if this has been previously asked and answered-
Is there a way to configure TTD to "listen" to the audio output feed going to the computer "speakers" rather than the mic or line input?
In other words, can you configure TTD to monitor a streaming feed from the internet? I have thought about using a patch cable to hardwire the speaker output back into the line input, but I wonder if there is a way to "switch" the audio source in software settings.
Thanks