-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invalid signal and noise readings #998
Comments
I am seeing similar issues on my setup as well. I was attributing it to local noise intrusion and had been mitigating alot of it by increasing the minduration to around 1 or 1.5 seconds. A few still occasionally get through though with the audio sounding similar to the noise captured if the squelch is set too low. If it is an intermittent noise intrusion issue and it is generally always a 999db "signal" captured, would setting some high threshold cutoff for signals (really anything over +40 or +50db would probably be suspect) work to curtail this kind of problem? |
Given the issue reported is for signal and noise of 999 my suspicion is the opposite of yours. I suspect that it an initialization value and the real value was never set for some reason. |
I'm not sure yet why they aren't always getting set to but the 999 is coming from DB_UNSET which is the default value when the recorders start/restart.
|
I'm getting json files with signal or noise as 999. I suspect something is wrong, but it's difficult to tell what based on the available information.
Examples:
(I add the multimon_ng key but I didn't manipulate the noise or signal)
The text was updated successfully, but these errors were encountered: