Advantage of hardware is that once recorded/rendered the audio there is virtually no load on daw. Just an audio track is virtually no cpu.cs759 wrote:You would be able to render events or tracks faster and easier than recording hardware, freeze tracks, no dealing with patches offline.shaunyata wrote:My question is this (and this is not sour grapes): if I already own a Wavestate with the free Editor/Librarian software, why would I need the Native VST? What more functionality would I gain from the VST that I don't already have? I can easily integrate the Wavestate with Ableton--do it all the time.
The Native interface looks like another version of the Editor software. The 4 lanes have a more expanded layout that's a bit easier to read.
About the only advantage I can think of is that I won't have to route the audio through an audio converter, like M-Audio. That saves a few extra steps.
VST instruments is very different in that regard, until frozen. The best daw IMO for freezing is Cakewalk/Sonar where all rendered outs in timeline on VST instruments get their own audio track. One press to freeze it all, and one press of a button to unfreeze. Cakewalk also disable and remove resources as they freeze instruments.
So it's a little about daws too, I think, how smooth freezing is. Cubase hide all audio rendered in the pool, you have no visual contact in timeline while working with the audio. You have to look at original midi to know where you are pretty much.(I ran 9.5 last, if not changed since)
StudioOne I also find a bit annoying that you have to disable instruments manually when rendered a track to really gain cpu.(I ran 4.6 last).
I run all hardware through a patch bay, and just redirect to the audio inputs I have when recording audio. So as I first had 2 audio inputs was still enough.
And also possible to do at least rough phones mixes on a weak laptop while traveling or something. Tour bus or whatever.
