Retrigger command is able to crash Renoise at extremely high tempo.
Put your BPM (eg 350) and LPB (eg 16) up, take a sample, trigger it repeatedly, put in the retrigger command with a low value such as 0E02…press spacebar, check the cpu going up and BAM.
Well not much of a problem you can have…I guess.
But just wondering what’s causing this.
I couldn’t get it to crash (running Renoise on Ubuntu 10.04), but if i do this (and disable CPU overload prevention in preferences) the CPU usage does quickly go up to 99.9% and stay there until a short time after I stop the song from playing.
Doesn’t crash here, cpu goes up to 99% and there is a hick up in the scrolling, but no crash. Running on a laptop core 2 duo 2 gHz, 4 gig ram, windows vista.
I can’t check the song right now, but I guess the problem may be the fact that the sample jumps are basically cross-faded together with very short clip, if that wouldn’t be done, there would be total clicking hell.
What basically happens when you do very fast retrigger is that you spawn tons of “virtual channels” which are all crossfading. If you find some thing too CPU intensive, use Render to Sample or try with bit smaller retrigger amounts.