Rendering

[synthphase]

I've been trying to render things using the HD-recorder, thinking it'll be able to render even though playing the song maxes out my CPU. I'm still getting some CPU spikes and Reaktor is turning itself off during rendering.. Is this feature to just record something fast? That is nice though I'm more interested in breaking my CPU barrier.. Is it still possible to record in silent mode? I haven't done this in ages, but I used to use the HD recorder in 90s Buzz to "render" a track that my measly laptop just could not handle.

Will "record loop" still "render" in silent mode? I don't care about the extra wait if it means I can increase the voices in my synth to 50 (for example, to see how close to white noise I get). Back in the day we HAD to render everything and we liked it!

[Joachip]

The idea of the "Render" is to harddisk record out as fast as the CPU can do. No matter how fast your CPU will be, it will always max out at least one core. This is the intention. The faster your CPU is, the faster rendering out will be.

This has another advantage: If your CPU is meeeeega slow (e.g. a Pentium-66 MHz) you will be unable to run real-time, but rendering will always work perfectly, because it does not try to play real-time, but rather whatever speed the CPU allows.

Plugins should not be affected by the actual rendering speed, but should produce the exact same output everytime, regardless of actual CPU speed. If Reaktor does not, it must be buggy.

[UNZ]

i think you can force reactor to not turn itself off (in the settings somewhere), but i don't remember properly right now.

and i guess you saw that there are multiple buttons in the HD recorder now:
record: realtime
render loop: non-realtime

[synthphase]

Well hopefully it was just my CPU and the cooling problems I was having with my old laptop. Just got a new one with a 2013 I5 proc.. Supposed to have a better power vs. performance ratio then the I7's and from a post at KVR I decided to go with more speed and less cores then vise-versa. I can ratchet up the grain number on grain cloud (kinda like voice number) without a noticeable hit to CPU, which is something I've never been able to do...

Yeah, you can supposedly turn off the CPU limiting by setting the max to 100 %.. I have to double check that setting before rendering again, now that I know it's supposed to max out a CPU core...

Another thing about rendering: In my experience it seems to not always record a perfect loop, meaning there might be a random number of leading samples before the audio actually starts. Am I nuts, or does anyone else experience this?

[UNZ]

random number of leading samples before the audio actually starts. Am I nuts, or does anyone else experience this?

it did this once or twice for me, and the samples where not empty, they contained some previous buffers. there's still some tiny bug hiding in this somewhere imho...

[Joachip]

Well hopefully it was just my CPU and the cooling problems I was having with my old laptop.

Tip: Take it apart and remove the dust that has gathered up in the fans, causing the laptop to overheat and become unstable.

I decided to go with more speed and less cores then vise-versa.

Good choice!

Another thing about rendering: In my experience it seems to not always record a perfect loop, meaning there might be a random number of leading samples before the audio actually starts. Am I nuts, or does anyone else experience this?

Beginning of recording out should be precise now, because this was fixed many versions ago. But if you have any machines that to latency compensation, it might cause this to mess up. Also, the point at which Buzz stops recording might not be precise.

[DJ Saint-Hubert]

unrelated, but I'm having a problem rendering in Buzz. Every once in a while the WAV file will have these glitches in it, only a few samples long but the noise is either silence, or as loud as 32 bit floating point allows (so when normalizing the rest of the song goes way down to near silence), in one or both channels. Anybody else get this problem?