Commtting a VI and Reverb…

[Sparky1]

Originally Posted by Eric Lambert

Confirming what Jeff said -- it should be identical. It may not phase-cancel because many reverbs have some randomization built in, but the Commit method isn't sonically compromised in any way.

Thanks for the confirmation Eric Lambert


Sparky

[Marsdy]

Originally Posted by Sparky1

Thanks for the reply Jeff.


In your opinion - do you think the sound changes much if the part is committed compared to bussed to another track and recorded?


Sparky

Further to Jeff and Eric’s reply, there’s another circumstance where a committed selection or track might sound slightly different from the original.

Many Kontakt libraries have round robin triggering of samples. A committed selection or track might have different sample triggered at any given point when compared to the original Instrument Track running live. They wouldn’t be identical in other words and would not phase cancel.

[DonaldM]

Originally Posted by Sparky1

Now that's something I never considered - I like it...

May try this...

Thanks DonaldM



Sparky

I understand the need to commit, especially when so many VI's seem to be such CPU hogs. Committing reduces the load. Normally when I create a patch in a VI, I will often leave in other fx such as chorus or phaser because they are part of the patch and the sound I want for the part. But reverb and delay are a bit different in that respect, so that's why I like to do them separately after committing. Also, with reverb, while a lot of the built in reverb fx on VI's is good, its not as good as dedicated reverb plugins, and far more limited options. Same for delay fx.

[DonaldM]

Originally Posted by EGS

Or, don't commit at all and leave all adjustments/tweaks available during the final mix.

Assuming one has the CPU horsepower to do that, which isn't always the case for a lot of users, especially in home studio setups. But even with the necessary horsepower, I still find I prefer to do final mixes with everything committed to audio. I also do it because it forces me to commit to the part and the patch, too. Otherwise I might get bogged down with over-tweaking a patch in the mix...and that's never a good thing!

[Eric Lambert]

Originally Posted by DonaldM

I understand the need to commit, especially when so many VI's seem to be such CPU hogs. Committing reduces the load. Normally when I create a patch in a VI, I will often leave in other fx such as chorus or phaser because they are part of the patch and the sound I want for the part. But reverb and delay are a bit different in that respect, so that's why I like to do them separately after committing. Also, with reverb, while a lot of the built in reverb fx on VI's is good, its not as good as dedicated reverb plugins, and far more limited options. Same for delay fx.

Same here, though it depends on my stage in the production. If I'm close to having the mix done, I'll include everything in the Commit. If there's still a lot of work to do then I want to be able to edit those FX and verbs.

[Eric Lambert]

Originally Posted by Marsdy

Further to Jeff and Eric’s reply, there’s another circumstance where a committed selection or track might sound slightly different from the original.

Many Kontakt libraries have round robin triggering of samples. A committed selection or track might have different sample triggered at any given point when compared to the original Instrument Track running live. They wouldn’t be identical in other words and would not phase cancel.

Good point about canceling. Though this is another reason someone might want to Commit. I've had cases where violin VIs simply offer too much variance in their round-robins, and sometimes those options are not so good. The way to keep them consistent -- playing only the notes you want them to play -- is to Commit (though in these cases I tend to print by routing the VI to an audio track, that way I can work my way left to right at a quick pace).

[Marsdy]

Originally Posted by Eric Lambert

Good point about canceling. Though this is another reason someone might want to Commit. I've had cases where violin VIs simply offer too much variance in their round-robins, and sometimes those options are not so good. The way to keep them consistent -- playing only the notes you want them to play -- is to Commit (though in these cases I tend to print by routing the VI to an audio track, that way I can work my way left to right at a quick pace).

Yes been there done that! Same applies to the big drum VIs where some hits sound better than others even at the same velocity.

So yes a good reason to commit and remove the variable. That said, some libraries allow you to reset round robins with MIDI CC’s or keyswitches so there’s scope for predicability there. PITA though!

[Sparky1]

Originally Posted by DonaldM

But even with the necessary horsepower, I still find I prefer to do final mixes with everything committed to audio.

Yes… this is how I have been approaching mixes as well.

I used to either commit or record a VI as I went along - but would find I often made changes to a VI instrument passage and would have to re-commit or re-record that segment. Not a big deal - but have lately been leaning towards leaving as many VI’s as they are and enjoying the on demand flexibility.

Sparky

[chrisdee]

I've used time to find the best sounding and most CPU friendly VI's atleast on my system (around 5 years old PC build).

This way I can run everything live during composing, arranging and mixing without thinking about hoging the computer. The few tracks that might cause issues I freeze.

[Eric Lambert]

Originally Posted by chrisdee

I've used time to find the best sounding and most CPU friendly VI's atleast on my system (around 5 years old PC build).

This way I can run everything live during composing, arranging and mixing without thinking about hoging the computer. The few tracks that might cause issues I freeze.

Unfortunately, sometimes the best sounding VIs are the ones that are the least CPU friendly. Thankfully, modern CPUs are wicked fast. I have a MacStudio Ultra and haven't had to freeze tracks, but I'm very familiar with the process from my days with the previous trashcan Mac, especially towards the end of its life.