Jalcide:
lukasbrooklyn:
vanhaze3000:
May i ask why you need sample accurate automation so bad when making EDM music ?
I am a EDM music producer for your years, but maybe i miss something and could learn something from you about this issue in Cubase.
it’s not such a big deal but a nuissance-- esp. when it comes to timing events precisely to the start of a measure, bar, etc. let’s say you’re trying to open up a filter or bypass a plugin on a drum bus precisely at the drop time. any kind of micro delay here hinders your efforts, so you’d need to compensate manually…
Yeah, it’s a huge nuisance. I’ve got a project right now that keeps falling apart at the seams, because every time I have to unfreeze something to make a simple arrangement change, it never refreezes the same exact way. It’s close, but it just sounds “off” because of aggregated effects of all the automation (and plugins, themselves) never freezing the same way, twice. Even with peak management on buses and techniques to minimize phase cancellation (strategic EQing, mono-izing low frequencies, careful M/S placement, etc.), it’s still a headache.
I should be bouncing to audio and committing.
This was why Studio One was almost the holy grail for me, their “transform” feature, but they didn’t get it right. Freezing (what they call “transforming”) flattens MIDI patterns, no round-trip, those pattern choices are gone forever. That was a deal-breaker. And, the freezing / unfreezing was a crash factory for me (had to switch back to Cubase).
I’m not sure if sample accurate automation, alone, would solve my freeze/unfreeze woes, but it’s certainly a per-requisite.
I wonder how sample-accurate FL Studio really is. Does the VST spec even support that? Is it up to each plugin developer to support that notion? Is it only with stock, or certain, plugins that FL Studio can claim this?
also note that automation ‘response time’ will change depending on your audio buffer size. so if you’re running out of CPU and decide to extend the buffersize of your soundcard, rapid automation may start sounding tiny bit different (in realtime playback, anyway). not sure if any daw is not a victim to this.