Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Demodulation is significantly slower via urh_cli #992

Open
braedinski opened this issue Aug 2, 2022 · 1 comment
Open

Demodulation is significantly slower via urh_cli #992

braedinski opened this issue Aug 2, 2022 · 1 comment
Labels
feature

Comments

@braedinski
Copy link

Expected Behavior

Messages should be appended to the ProtocolSniffer.messages list as soon as they are available.

Actual Behavior

There is a significant lag when using urh_cli compared to the URH GUI. It's almost as if messages are being polled for every 5 seconds (not saying this is the case but for explanation's sake), compared to URH where - when a signal is demodulated, it appears almost instantly.

Steps To Reproduce

Compare the delay between urh_cli and URH GUI when demodulating any signal. In my case, it was FSK using default settings, obviously the frequency has been changed.

Platform Specifications
  • OS: Kali Linux
  • URH version: 2.9.3
  • Python version: 3.10.4
  • Installed via pip
@braedinski
Copy link
Author

Evidently ProtocolSniffer only attempts to run __demodulate_data once the buffer exceeds ProtocolSniffer.BUFFER_SIZE_MB. Reducing the size of this buffer to say 1 MB will increase the "reaction time" but it's still not as fast as the URH GUI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@braedinski @andynoack