Activity log for bug #884694

Date Who What changed Old value New value Message
2011-11-01 10:47:14 Sean M. Pappalardo bug added bug
2011-11-01 10:49:20 Sean M. Pappalardo description I just discovered that, even though I chose 2ms in the preferences, PA reports that I'm actually getting 14ms. But _the GUI controls are still more responsive_. While we wait for the control system redesign, can't we just force the latency value low for those GUI and input elements that are inextricably tied to it? (Ideally create separate AudioLatency and GuiLatency values.) I just discovered that, even though I chose 2ms in the preferences, PA reports that I'm actually getting 14ms. But _the GUI controls are still more responsive_ than if I choose 11ms, still getting 14 on the audio. While we wait for the control system redesign, can't we just force the latency value low for those GUI and input elements that are inextricably tied to it? (Ideally create separate AudioLatency and GuiLatency values.)
2011-11-07 05:50:40 RJ Skerry-Ryan summary Artificially decrease the latency for GUI controls Use a small PortAudio user-buffer size regardless of host latency.
2012-09-11 18:57:12 Daniel Schürmann mixxx: assignee Daniel Schürmann (daschuer)
2012-09-11 18:57:16 Daniel Schürmann mixxx: status Confirmed In Progress
2013-03-23 12:53:19 Daniel Schürmann mixxx: status In Progress Triaged
2013-03-23 12:53:23 Daniel Schürmann mixxx: assignee Daniel Schürmann (daschuer)
2020-05-10 18:22:06 Daniel Schürmann tags frame-rate gui latency response engine
2022-10-08 19:06:48 Swiftb0y bug watch added https://github.com/mixxxdj/mixxx/issues/6063
2022-10-08 19:06:49 Swiftb0y lock status Unlocked Comment-only