Repository navigation
|
With crossfade enabled, does the DSP work add latency when I hit pause, seek, or change volume? |
Answered by
e2sy
Oct 19, 2026
Replies: 1 comment
|
No — that's the v0.8 standing guardrail: audio DSP may add latency to start, never to control. Seek/pause/volume respond instantly even while the Forge is churning. The crossfade work is confined to the audio start path (fading one track out while the next fades in), so the control path stays untouched. The same philosophy shows up elsewhere: every job runs on the worker pools, and the UI thread only paints. |
0 replies
Answer selected by
e2sy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No — that's the v0.8 standing guardrail: audio DSP may add latency to start, never to control. Seek/pause/volume respond instantly even while the Forge is churning. The crossfade work is confined to the audio start path (fading one track out while the next fades in), so the control path stays untouched. The same philosophy shows up elsewhere: every job runs on the worker pools, and the UI thread only paints.