Actually, i consider CPU usage a MAJOR problem in audio production!
Go and have a look at a pro tone studio. - Do you think they’re all stupid spending thousands of EUR on DSP power ;-)) - Think about it.
When you run - for example - only one polyphonic instance of Albino VST you easily gain a few % of CPU used on a Core-2-duo machine. And this then is ONE channel, without FX. - Now imagine 30 Channels, plus the FX Busses … It is soooooo quick to fill up a CPU.
Of course, you can render one pattern to WAV - no question, but this is a very unhandy way of working.
Oh and yes, that was still 44.1 khz. The 192 khz knob on my sound card is probably more for showing off and will never get really any useful. ;-)))
I think there is a big difference in the way people work. If you do some oldskool tracking where mainly samples are played and just a few FX then you are fine. But if you try to work more the way like a tone studio works with EQ, Compressor, Sidechaining, Delay Compensation, Vocal processing plugins, etc., you end up having a hard time very quickly.
It doesnt sound too much, if one plugin “only” takes 2-3% of cpu. The problem is - we’ve only got 100% !
Already the master bus for itself can take considerable time of CPU. - EQ, multiband dynamics/Compressor, (multiband) stereo narrower/widener, master reverb, exciter, loudness maximizer/limiter, dithering, inspector XL. - with that alone fill up at least one CPU
well, hehe this is probably why this is done in a separate task, right? - ack.
however …
… In Cubase for example, the freeze feature was hi hi highly appreciated by many users.
To cut a long story short: i dont even think it is necessary to have a NATIVE renoise freeze. - it would already be very helpful to have a decent VST cross plattform one. i hope i will find one, and then i’ll be very happy.
I guess, the spare development time of Renoise developers might be better used on topics which cannot be easily work-around’d (awesome english) with third-party plugin products.