© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
It is not a pure CPU usage issue, its more a real time issue. We have ensure that we have the CPU in time.
When implementing it, please be aware not to overload the Qt event queue between the threads.
Mixxx is already suffering issues with the overloaded event queue, which results e.g. in waveform jerking an leak of reaktion to GUI controls.
Every additional timer driven QT event will make the things worse. We should consider to itroduce a time management based on the audo buffer / latency for the engine thread and based on the display refesh rate in the GUI thread. Maybe a third timer for MIDI (not sure). All other events should be derived from this timers, without preventing to process the following timer event in time in the next cycle.