Glitchy audio is a potentially a quite different issue to not getting smooth video playback.
You don’t say what version of kdenlive you’re using, but if you’re not on the latest appimage, do try that, the performance improvements in recent versions have been quite notable. But that said …
The results I see for fast forward video depend greatly on the codec and bitrate of the source, and the resolution rendered in the preview monitor.
If you want to see smooth 4k H.265, good luck with even getting that in realtime in any viewer if you don’t have a hardware decoder assisting.
I get the most reliably good results in kdenlive using the lo-res proxy files my camera creates for its own playback as “external proxies” with the project monitor set for 720p (but displaying at ~1080p size with kdenlive filling a 4k screen). Some source is fine at 1:1, once I start layering heavy effects, I might need to drop to 520p to stream smoothly faster than realtime…
But that’s mostly just figuring out which resource is bottlenecked and reducing the load required from it. That’s what Bernd and I were thinking you were having trouble with in our initial replies.
The audio glitches at 2x and greater speed are something a bit different though.
I can confirm I can reproduce that here, and it would seem that it’s not about your computer being saturated (or even pulse’s ability to insert annoying glitches from any source).
What it sounds like is that at 2x and greater it is simply decimating the audio packets and dropping some multiple of them. The advantage of that is it’s cheap and easy, adding almost no processing load, it automatically preserves pitch, and it needs no state information to stop, restart, rewind, speed up, slow down cleanly and immediately.
The downside is, you get a discontinuity in the waveform at every dropped packet, which will create a crackle the severity of which will depend a bit on your actual audio content.
There are options to fix that ranging from simply passing it through a low-pass filter to fully resampling it and doing pitch preservation (like the time remapping does) - but they come at a processing cost that competes with having video playback not glitching …
In a player app, where people might want to watch content at accelerated speed, that’s worth doing, even necessary for usability. In an editor, where you’re more likely to be scrubbing back and forth to find something rather than watching it for a lengthy period, it’s a bit more of a fuzzy choice.
But it might be worth adding a configuration option to let each user choose if there really are people who want more perfect high speed audio during the editing phase.