Hey Rob,

Thanks.

There seems to be an apples and oranges thing going on here.

If I am in BIAB, and I am using midi tracks ONLY, and I change a few chords and hit generate it will NOT generate a .wav, only a new midi file, and it does so in a second.

In BIAB, you will only get the .wav file of a midi track if you RENDER it. That is, in BIAB there is a difference between generate and render as they apply to midi as far as I can tell.

Why is this important?

Because when I am fiddling with a song, and making numerous changes to the progression and such, I do not want to wait for the length of time it takes to generate a RT .wav or midi to .wav. So I will work in midi until I am ready to get .wavs.

But in the VST3 it seems I have NO CHOICE. I have to get the .wavs alongside the midi, even if I have a midi only style, and I have to wait, twiddling my thumbs, while it does so. And I have to go into my hard drive and erase all those .wav backups I will never use and never wanted in the first place, each time I generate.

So, what I am asking, as only an ask, is this:

Since the technology already exists, why can't I just get a midi generation in the VST just like it is possible in BIAB, without a .wav RENDER each time????

It makes the process much longer, and thus, will dissuade me from using the VST3 inside the DAW for very much because of this one quirk.

I will just say forget it, and work in BIAB, generate .wavs when I feel like it from BIAB, and drag them to the DAW when I am ready.

Ok, so be it.

But WHY can't I have the best of both worlds????

That is question I am asking.

smile smile smile