Bug Description
If --log-level is set to debug, Mixxx will log controller related debug message. These messages are supposed to be logged only if --controller-debug is passed, but this last one becomes redundant.
This leads debug session to log all the controller related communication message (~60 messages per second on the S4 MK3 as references)
As a workaround, I had added some conditional login on a few of those qDebug instruction, effectively undoing some of the filtering setup that was initially set. It would be nice to properly fix it to leverage log filtering.
Relates to this discussion
Version
main
OS
N/A
Bug Description
If
--log-levelis set todebug, Mixxx will log controller related debug message. These messages are supposed to be logged only if--controller-debugis passed, but this last one becomes redundant.This leads debug session to log all the controller related communication message (~60 messages per second on the S4 MK3 as references)
As a workaround, I had added some conditional login on a few of those
qDebuginstruction, effectively undoing some of the filtering setup that was initially set. It would be nice to properly fix it to leverage log filtering.Relates to this discussion
Version
main
OS
N/A