> Can you give the load/idle numbers for no MIDI device enabled? (that way we
> see a baseline for no polling going on at all)
12% idle/55% load.
I have no issue with simply increasing the polling interval.
> Also, I don't really see why you use QThread::msleep(1) instead of just
> increasing kPollIntervalMillis to 2 in controllermanager.cpp.
It only sleeps when the poll didn't see any data. So if mixxx starts taking in a stream of data (scratching), it'll hopefully not sleep. It does increase latency from no data to data though, which will be common scenario (no midi input to hitting a button, for instance). Honestly I thought there were limitations of midi over usb that prevented data from coming in at 1ms intervals so this could all be for naught.
> Can you give the load/idle numbers for no MIDI device enabled? (that way we
> see a baseline for no polling going on at all)
12% idle/55% load.
I have no issue with simply increasing the polling interval.
> Also, I don't really see why you use QThread::msleep(1) instead of just er.cpp.
> increasing kPollIntervalMillis to 2 in controllermanag
It only sleeps when the poll didn't see any data. So if mixxx starts taking in a stream of data (scratching), it'll hopefully not sleep. It does increase latency from no data to data though, which will be common scenario (no midi input to hitting a button, for instance). Honestly I thought there were limitations of midi over usb that prevented data from coming in at 1ms intervals so this could all be for naught.