.
.
You mean freezing a track, correct?ouroboros wrote:Just to clarify as it's been a while; it's still ok to render single shot perc hits, right? around 10 instances and my CPU craps out. Not layering/ not seperate for attack/body, etc. Just renders of single presets.
No, that you're not allowed to do. The reason is simple. For synth wave's that don't trigger the same for each note (a big problem for creating kicks on some synths) by creating a wav file, you get around that problem. That is why creating wav files is not allowed.ouroboros wrote:No as my host does not technically "freeze tracks".
I programmed a snare in OBXD
I rendered that snare to .wav file that I then use in my pattern editor.
In a 4 bar pattern I might trigger that sample 16x.
Instead of asking the vst to generate 16x snare sounds, I trigger the one .wav file 16x and save cpu.
'years past this was fine, but I am aware things change, even if my workflow doesn't
You are free to use that sample while you are making the track to save CPU and to turn off those instances.Vortifex wrote:I was thinking about joining in for fun but I wanted to ask about one of the rules. If I come up with a percussion sound that requires 4 instances of the synth, can I bounce that and use the sample instead? The rules said not to use a sample for consistency but what if the sound is consistent?
I think OSC should reconsider this `rule`.z.prime wrote:Right, well, the issue is exactly that... consistency. In fact, this synth is one that the rule is specifically pertinent for. With OBXD it is NOT consistent. The oscillators are free running, they don't restart, so sampling a single hit is actually going to yield a different result (although you can mask this somewhat by other things such as adding an instance or more for the attack transient, making a slight attack time on the meat of the kick, etc...).ssj71 wrote:I think that's keeping the spirit of that rule since it would sound identical, but I think what most of us do is write out the song and bounce the whole track if bouncing is necessary. That way it doesn't look like you cheated if someone looks at your project files.Vortifex wrote:I was thinking about joining in for fun but I wanted to ask about one of the rules. If I come up with a percussion sound that requires 4 instances of the synth, can I bounce that and use the sample instead? The rules said not to use a sample for consistency but what if the sound is consistent?
Agreed ... you simply have to live with it and use it. The main point of rules like this is that everyone is working on a level playing field, especially when there are quite a number of different DAW's in use as well. The whole thing is very much part of the "challenge".ontrackp wrote:It comes with the territory with some synths. If oscs always trigger differently there are always small differences. Part of the fun.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026
