RTAS VI's still very inefficient

[usastra]

Here's a preview of test of the RTAS VI efficiency compared to AU/VST. Interestingly though is that the RTAS fx engine is holding up pretty good as can be seen here

[roberts]

I print EVERY SINGLE instrument. Version updates, session load times, old session recalls, CPU stress, opening on different systems, opening session on different platforms,
audio timing is tighter than midi, fewer memory issues.
There are are dozens of reasons to print and not a single GOOD reason NOT to.
I can't tell you how many times times this practice has saved my back.

[guitardom]

Originally Posted by roberts

I print EVERY SINGLE instrument. Version updates, session load times, old session recalls, CPU stress, opening on different systems, opening session on different platforms,
audio timing is tighter than midi, fewer memory issues.
There are are dozens of reasons to print and not a single GOOD reason NOT to.
I can't tell you how many times times this practice has saved my back.

Midi vi's are 10 samples off on average.

And a good reason not to do it; don't want to. Just a thought.....

avid is well aware of the inefficiency of rtas in comparison to vst and au. This has been a complaint for many years. certainly hope something is in progress to get it updated and more efficient.

[MacPC]

The good reason not to print to audio is if you're working in film and the filmmakers are re-editing all the time. One used to get locked picture and have time to work with that, but the expression "locked" is fast becoming a quaint anachronism.

Under those circumstances, staying in midi makes more sense and doesn't add the clutter of unusable soundfiles that no longer match the picture.

[roberts]

Originally Posted by MacPC

The good reason not to print to audio is if you're working in film and the filmmakers are re-editing all the time. One used to get locked picture and have time to work with that, but the expression "locked" is fast becoming a quaint anachronism.

Under those circumstances, staying in midi makes more sense and doesn't add the clutter of unusable soundfiles that no longer match the picture.

That's what I do music film and I record it down because many systems that I transfer may not necessarily have that VI I am using. Changes are easy just punch that part in that needs a change. When they are doing the final film mix they are long past any major changes minor fixes are easy even even it's printed.
to the above Poster VI's shift in MIDI timing. all the time that's WHY you should ALWAYS PRINT. Plus now with HEAT you audio must be printed anyway. That's where really comes into play nice on VI's
Not priting is going to give a hundred times more headaches that printing ever will.

[Eric Lambert]

For the best of both worlds, print at the end, not during.

[critza]

I print sometimes, and then i just use hide and make inactive on the Instrument track. If i need to make any changes just show and make active again.

[Benoni]

Originally Posted by critza

I print sometimes, and then i just use hide and make inactive on the Instrument track. If i need to make any changes just show and make active again.

yep. this works fine for me as well.

[L-Dogg]

Can't you just print to audio and then, after saving the settings of the VI, get rid of that VI while saving/hiding the instrument track with the MIDI recording?

This way you have lost the CPU intensive VI but you still have that MIDI performance and if you need to you just dial up the VI according to your notes.

Yes, the RTAS environment is very inefficient.

[usastra]

Interestingly though, this only goes for RTAS VI's.
RTAS insert plugins are about the same as their vst/au counterparts.