Uploaded March 2022 | Updated September 2026, 1 week ago
Some of my viewers said the new version 3.5 of KClip 3 was problematic (on Windows), so I did some testing of 3.2.4 performance vs 3.5 performance. Summary: if you turn off the new visualizer, performance is essentially the same. If you enable the new visualizer, 3.5 uses up 15% more DAW CPU resources than 3.2.4. Also, the new visualizer is worthless. The old visualizer was much more useful for real-world use cases. On the plus side, you can make the KClip window nice and small in v 3.5.
EDIT: Grrrr - OBS flaked on me during the very last part and didn't record the end. With 50 instances and the Visualizer turned OFF, the Load (AVG) (i.e., the "CPU usage") was 0.460. Which was exactly the same as 50 instances of the older 3.2.4 KClip.
CONCLUSION - Turn off the worthless new visualizer and it's the same impact as 3.2.4, and you can at least make the window smaller now. Or just stay on 3.2.4 until Kazrog can improve performance and (hopefully) revert the visualizer back to a more useful "crest factor" view like before.
Some of my viewers said the new version 3.5 of KClip 3 was problematic (on Windows), so I did some testing of 3.2.4 performance vs 3.5 performance. Summary: if you turn off the new visualizer, performance is essentially the same. If you enable the new visualizer, 3.5 uses up 15% more DAW CPU resources than 3.2.4. Also, the new visualizer is worthless. The old visualizer was much more useful for real-world use cases. On the plus side, you can make the KClip window nice and small in v 3.5.
EDIT: Grrrr - OBS flaked on me during the very last part and didn't record the end. With 50 instances and the Visualizer turned OFF, the Load (AVG) (i.e., the "CPU usage") was 0.460. Which was exactly the same as 50 instances of the older 3.2.4 KClip.
CONCLUSION - Turn off the worthless new visualizer and it's the same impact as 3.2.4, and you can at least make the window smaller now. Or just stay on 3.2.4 until Kazrog can improve performance and (hopefully) revert the visualizer back to a more useful "crest factor" view like before.
