-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
allow to set threshold for MixxxApp::notify() event warning #14015
base: 2.5
Are you sure you want to change the base?
Conversation
settings key is [Config],NotifyMaxDbgTime
10ms are already a relative high threshold, as this thread must render every 16.6ms a new waveform, which consumes several milliseconds on it's own. This means, that every occurence nearly certainly indicates an event, that result in a frame drop. |
Just an example of a quick test session: start Mixxx, select a track, load it, open preferences, adjust latency, apply.
This is used in developer sessions only, so performance is not as high as in user sessions, and I don't care about framedrops in these sessions. Almost all logged events are irrelevant for what I'm usually testing, hence a custom threshold makes sense to have a clean log. |
FYI when running the S4 Mk3 script I get repeatedly |
Do you mean that the waveforms are glitch free, or that the frame drop counter does not count drops. The later is also not working if the event queue is blocked. |
Sorry, I meant |
Thanks for the explanation. I guess logging each and every event > 10ms doesn't improve the situation ? ; ) |
To reiterate:
If you fear a custom value migh be forgotten, we may remember devs of that by printing the threshold info at startup (log). Anyhow, I'll (have to) incorporate this into my dev branches, because for example when contiously logging controller values the event logs disrupt my workflow and I sometimes scroll back in the log stream to check whether I missed another logging of interest. in other cases I'll simply use the 'warning' log level. |
The settings key is
[Config],NotifyMaxDbgTime
.At least on my machine there's so many events that take longer than 10 millis, and I want to reduce log spam.
There are probably more elegant ways to accomplish this, ie. keep
MixxxApplication
clean, like avoid adding a method and no new includes in its header. If you agree this is worth being implemented, please suggest better ways.