Closed jonaseberle closed 2 years ago
Good catch, I think afv-native is struggling a bit with the immediate GUI use case, as we're calling those APIs 60 times per second. I will see if I can cache a lot of this stuff when the popup is created to just avoid the calls altogether.
Feel free to reopen if this has not actually been fixed!
Hey, I've just had a longer session and it went beautifully! Some more and I'll be confident enough with the audio to also book stations :)
Just at the very beginning I was not able to receive/send voice. But since I was already connected and pilots where waiting I restarted VectorAudio, reconnected and haven't had a closer look what might have caused it. Sorry! From there on I had stable and beautiful voice, including monitoring surrounding frequencies. Absolutely fantastic! Thank you!
I prefer to start
./vector_audio
from the console (actually sometimes withgdb
debugger). I always build from currentmain
.The console output contains just too many lines in my opinion. The extreme was shown during my first sessions: I always had problems after some time running
./vector_audio
until I found out that my/tmp
tmpfs
has grown to the point where it was full (by default it is half of the RAM, so 8 GB in my case). I looked at the code and couldn't find anything related to it. Then I realized that my terminal was set to have an unlimited scrolling buffer and that it used/tmp
... After setting that to max. 100.000 lines I haven't had that problem any more.Types of log messages
ContinuePoll
During normal controlling, I have a lot of:
Audio device detection
When opening the audio settings and opening any of the dropdown boxes it gets absolutely insane and is constantly outputting a huge stream of text (like several MB/s). Here's a sample:
Could we clean this up a bit or make it go to a .log file instead?
(Linux 5.17, Manjaro)