Hello,Yeah I know, "this program is tottaly useless" and "it's useless piece of software" because everybody knows how easy it is to circumvent encryption and the laws around doing so. It's not like encryption is actually designed to stop people listening at all. All is required is a simple XOR and your right to go.
Comments like this really inspire me.
Where does this occur? Plug-in or TTT....The only thing I have seen is that somtime it do not update text for the LA.
Not sure why this occurs, I looked at my Virtual Audio Cable settings (which worked OK) and it uses the ranges 1-2 channels, 8-16 bit and 22050-48000 Hz....As far as audio recording options are concerned, when VAC is set to "2 channels 16 bit 48000 Hz" the message "ERROR-(samples/sec)" pops up. I had to create a VAC channel and set "1 channel 16 bit 22050 Hz".
Both TTT and plug-in can do this. Please read through the documentation.My question is if it is possible to edit the names "MNC" and "LA"? If someone had such data he could enter them and TTT program would show them in the window like "MCC". This would be a great solution because during propagation you can receive many stations from far away and you would know from where the signal is being received, what user.
Does this crash TTT? You say YES
How often does this occur? You say most of the time, but sometimes works.
Is there a error number with the message? You say no, just crash of TTT
In addition to the questions above:When does this error occur. At program start, after period of time, on closing, after changing a option?
What is TTT mode (Single/Dual) and it's selected record options and are any logging option on.
Without out any crash logs (from TTT or Windows), this will be difficult to locate cause of crash.
Does Windows not generate any events for the crash in "Event Viewer"?
1002 Application Hang error logged in event viewer followed by a Windows Error Reporting 1001
Should I expect to see a TTT crash log? Nothing in the root folder.
We discussed back in this post about your recording issue (which turn out to be the filename length).
I asked a few questions that may apply here to tracking down the issue.
This was where no files were created at all - I'm now operating out of root of drive so that issue isn't applicable here.
In addition to the questions above:
Does the crash occur at the very start of call, through the call or at very end of call?
Does turning the recording OFF stop the crashing?
I'm running in single mode, plugin works as expected when recording is disabled so nothing suspect with the plugin or settings.
Crash appears to happen at the start of a call, I haven't noticed a set pattern though as there isn't much activity in my region. I have turned off recording and everything has been working fine for the past few hours.
The strange thing is that yesterday I noticed a couple of successful recordings in the directory. Could it be that a specific type of call is problematic, but others are fine? If there is anything in any of the .txt files to look for I'll certainly have a look.
Latest version (v1.8.6.0) can be found here: MEGA - Download
Release post here
Not if TTT is crashing/hanging.1002 Application Hang error logged in event viewer followed by a Windows Error Reporting 1001
Should I expect to see a TTT crash log? Nothing in the root folder.
Honestly I don't know.The strange thing is that yesterday I noticed a couple of successful recordings in the directory. Could it be that a specific type of call is problematic, but others are fine? If there is anything in any of the .txt files to look for I'll certainly have a look.
Thanks, will have more of a dig. Might try ProcMon to see if any attempts are made to write to the directory, and whether or not that fails.OK thanks for the feedback.
Not if TTT is crashing/hanging.
Honestly I don't know.
Only two things come to mind when you say that it only occurs at call start:
#1. seems unlikely as you say your running TTT from the HDDs root folder (e.g. C:\TTT).
- File path is too long.
- Issue setting up the recording.
I have just added a test for this (path length) and it will show message in status window when condition is seen and no recording will attempted.
#2. The record method (MCI) is a bit dated now and problems maybe occurring in Windows 10 (if you are you are using it).
If a call to the recording system is hanging for some reason, then any error trapping is not going to fire.
Only returned errors from calls are handled or other basic runtime errors.
I can't think of anything at the oment to test/look for to help with this.
Latest version (v1.8.6.0) can be found here: MEGA - Download
Release post here
I need the line that is circled. As many as you can, and from different people so I can validate my method.
The carrier is "Current:" 2604 with the frequency of 865.1125 MHz.