Log spammed with `Warning [VinylControlProcessor 1]: VinylControlProcessor could not write signal quality report for VC index: `

[jus]

If VC inputs are configured, but no Timecode signal is coming trough the input path.

I think is is pretty common to configure the inputs you regularly use as defaults.

[Owen Williams (ywwg)]

Is there any point in logging this error at all? I would just as soon remove it.

[jus (jus)]

None i could think of, other the debugging.

[Christian (ubuntu-linux-user)]

IMHO, this bug about log spamming is not a duplicate of #1269559 about a endless loop and a segfault.

I can confirm the log spamming. Mixxx repeats printing a large amount of warnings into the log when VC is enabled and no timecode signal is sent. It is recurring, but not endless. I do not experience a segfault or other kind of crash.

I think there's no problem when the user has a record stopped while the program is running. Thus, this program state should not be reported as warning. It may be logged on debug level, but the number of messages should be limited to a certain time range then.

The code already contains a TODO about the spamming and about rate limiting as possible solution, but no fix was commited yet. See https://github.com/mixxxdj/mixxx/blob/93841fd8fbe8a5c78a06c6275b5f304df86a07f0/src/vinylcontrol/vinylcontrolprocessor.cpp#L123

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7372