TwoToneDetect New TwoToneDetect in the works - Python based

[FVFD23]

I am still using v56. It works great but every once in a while I get false messages sent to my phone/e-mail. Is this common or is there a way to adjust this from happening?

 

[brian79z]

It looks like it can't find a sound card to use. If you're copying over the config.cfg file from a different computer that might cause some issues. You might want to manually set the input and output devices to 0 by editing config.cfg with a text editor. Also if it's a newer computer you may need to have a cord plugged into the audio input in order for it to recognize the sound card. Finally, you can always check the log.txt file for errors even if you're not using the debug version.

Andy

The in/out audio settings was already at "0"
The input was already occupied with the scanner

The log file from the debug is what I posted on the last message.

help?

 

[aaknitt]

I am still using v56. It works great but every once in a while I get false messages sent to my phone/e-mail. Is this common or is there a way to adjust this from happening?

You can increase the value of the Btonedebounce parameter, that should help. Or, upgrade to the newest version, that should also help.

Andy

 

[aaknitt]

The in/out audio settings was already at "0"
The input was already occupied with the scanner

The log file from the debug is what I posted on the last message.

help?

Are you able to record from your scanner using Windows sound recorder?

Andy

 

[brian79z]

Are you able to record from your scanner using Windows sound recorder?

Andy

Yes.
I have TTD56 on computer 1
I installed TTD63 on computer1

Configured TTD63.
Closed TTD56
Opened TTD63debug. Got a quick flash of the DOS window, which I captured a screenshot and shown here.
TTD63 closed out automatically. Nothing open or operational.

Opened up TTD56... continue to use this for past few days. Still get tons of false pages even with Btonelength at 2.9
Would like to upgrade so I can take advantage of the Atonelength feature

thanks

 

[aaknitt]

Yes.
I have TTD56 on computer 1
I installed TTD63 on computer1

Configured TTD63.
Closed TTD56
Opened TTD63debug. Got a quick flash of the DOS window, which I captured a screenshot and shown here.
TTD63 closed out automatically. Nothing open or operational.

Opened up TTD56... continue to use this for past few days. Still get tons of false pages even with Btonelength at 2.9
Would like to upgrade so I can take advantage of the Atonelength feature

thanks

As a temporary fix you should be able to increase Btonedebounce to help with the false pages. v63 should still work though. What happens if you copy the config.cfg file from v56 into the v63 folder? Will it run then?

Andy

 

[ffryan76]

I just updated to v63. I am using the remote config. I just copied the tones, remote, and config files over from v61. Is that the correct way or do I need to manually re enter the information?

 

[aaknitt]

I just updated to v63. I am using the remote config. I just copied the tones, remote, and config files over from v61. Is that the correct way or do I need to manually re enter the information?

That should be fine going from v61 to v63.

Andy

 

[aaknitt]

Yes.
I have TTD56 on computer 1
I installed TTD63 on computer1

Configured TTD63.
Closed TTD56
Opened TTD63debug. Got a quick flash of the DOS window, which I captured a screenshot and shown here.
TTD63 closed out automatically. Nothing open or operational.

Opened up TTD56... continue to use this for past few days. Still get tons of false pages even with Btonelength at 2.9
Would like to upgrade so I can take advantage of the Atonelength feature

thanks

Also, you might try v61 instead of v63. Not sure if that will make much difference but if it does there are some things I can look into that may need tweaking.

Andy

 

[brian79z]

v63 should still work though. What happens if you copy the config.cfg file from v56 into the v63 folder? Will it run then?

Andy

BINGO!

Ok.. need to find out what's different that prevented the v63 program window from popping up.
I did a comparison between config files..

v56 has zeros as a leader or follower to a number or decimal -- 6.0 0.03 30.0
v63 does not -- 6 .03 30
---changed the config.. no difference

v56 changed my gmail password into a random character mix with 3 extra characters
v63 was different characters.
----changed the config (copy paste)...
-----I found the enemy.. and the enemy is I. A mistyped password

I am now trying something that worked on older versions... running 2 different TTD at the same time on the same computer, but different versions and different page identification titles.
If what worked in the past still works today, I should be able to run both simultaneously and both should function independent of each other.

This way, I can use the same scanner to fine tune the v63 (texts to me only), while v56 keeps pumping along like normal. (with typical false texts.. even with bounce set at 2)

thanks

 

[kc8oye]

This would be hard to get right, since if a dispatcher pauses partway through a dispatch it could terminate the recording, which wouldn't be desirable.

Andy

hrrm, it didn't quote the whole message.. but this was in reference to a MAXimum recording time, I'm interested in such a feature too. Some of my recipients aren't interested in receiving several hundred k of dribble from a long winded dispatcher..

 

[brian79z]

Andy:
New issue with running v63 alone on the computer (just updated)

All of the recordings are full of echo on v63

The v56 does not have any echo at all. Same scanner, same computer, same input, same everything.

 

[webby52]

I too am using v56 and v63. No issues until I added a ground loop isolator. Now theres no hum in the recording, but now they are both falsing big time. I went into the tones file and adjusted the btonelength to 3 and btonedebounce to 4 on v56 and upped the atone/btone length to .9 in v63. Now v63 is working no falses yet (been a few hours) but v56 wont load. I get the same window as above and although I can't provide a screen shot (and there is no log file in any of my versions) I thought I was having sound card issues as well. This seems unlikely as I am running v63, and another program and they are both recording. I checked the config file and it was set to 1 and 2 for incoming and outgoing. I changed it to 0 for both and still won't load. All I can make out is something about trace and then the window closes.

 

[aaknitt]

Andy:
New issue with running v63 alone on the computer (just updated)

All of the recordings are full of echo on v63

The v56 does not have any echo at all. Same scanner, same computer, same input, same everything.

Do you have Playback During Record enabled? If so, what input are you using (what's the name of it)?

Andy

 

[aaknitt]

I too am using v56 and v63. No issues until I added a ground loop isolator. Now theres no hum in the recording, but now they are both falsing big time. I went into the tones file and adjusted the btonelength to 3 and btonedebounce to 4 on v56 and upped the atone/btone length to .9 in v63. Now v63 is working no falses yet (been a few hours) but v56 wont load. I get the same window as above and although I can't provide a screen shot (and there is no log file in any of my versions) I thought I was having sound card issues as well. This seems unlikely as I am running v63, and another program and they are both recording. I checked the config file and it was set to 1 and 2 for incoming and outgoing. I changed it to 0 for both and still won't load. All I can make out is something about trace and then the window closes.

When you added the ground loop isolator, did the audio levels change? It sounds like it may be decoding audio all the time, which means you may need to adjust the Audio Squelch slider up on the main screen. You should only see tone frequencies being decoded when there is radio traffic present.

As for v56 not starting up, did you edit the tones.cfg file manually or by using the Tones Editor GUI? If manual, it sounds like something got messed up with the manual edit. If something is bad with the syntax of the tones.cfg file the program may not start up. To see what the error message is, open a command prompt and run the _debug version of the program from the command line.

Andy

 

[brian79z]

Do you have Playback During Record enabled? If so, what input are you using (what's the name of it)?

Andy

Yes I do.

I just switched from microsoft audio adapter to the Realtek audio.
I can still see input on the TTD screen as well as the windows audio recorder.

Will see what happens.

Thanks!

 

[aaknitt]

hrrm, it didn't quote the whole message.. but this was in reference to a MAXimum recording time, I'm interested in such a feature too. Some of my recipients aren't interested in receiving several hundred k of dribble from a long winded dispatcher..

If you want to record for a set amount of time, just set Release Time = 0 and then it will record for the length set in Record Seconds. Record Seconds sets the minimum record time. The max record time is hard-coded to 60 seconds, but can be less if there is a silence greater in length than Release Time.

Andy

 

[brian79z]

Do you have Playback During Record enabled? If so, what input are you using (what's the name of it)?

Andy

Andy:

I tried to swap from Microsoft audio to realTek audio on the input and output.
---no difference. Still VERY enhanced echo sound.
Yes, playback during record enabled

Went back to V56... and no echo.

help?

 

[aaknitt]

Andy:

I tried to swap from Microsoft audio to realTek audio on the input and output.
---no difference. Still VERY enhanced echo sound.
Yes, playback during record enabled

Went back to V56... and no echo.

help?

As a troubleshooting step, try disabling Playback During Record and see if that gets rid of the echo. Any chance you have duplicate tone sets in your tones.cfg file?

Andy

 

[brian79z]

As a troubleshooting step, try disabling Playback During Record and see if that gets rid of the echo. Any chance you have duplicate tone sets in your tones.cfg file?

Andy

No duplicate sets.

Deleted field for playback during record. Here is what it looks like now.