Future VI performance and features?

[nightjar]

Can you share some hints?

Will V.I. in AAX Native have more efficient use of CPU cycles than current RTAS?

Will V.I. in AAX DSP go "far beyond" what is possible in AAX Native?

Will the disk-caching feature of PTHD10 affect how future V.I. will function?

[djjedidiah]

Just for reference of current VI performance, which I don't think anyone can say is "game-changing"

dawbench

[Dism]

Originally Posted by djjedidiah

Just for reference of current VI performance, which I don't think anyone can say is "game-changing"

dawbench

Which has nothing to do with anything, realistically, since PT is still a 32 bit host. Until it goes 64 bit, there's no way to compare VI performance with another 64 bit host. If the comparision were between Cubendo and Pro Tools with VE Pro, it would be another story entirely. He even says that the test is irrelevant to a 32 bit OS... but since PT is still 32 bit, it's a rather unfair comparison.

When we see AAX VIs in action in a 64 bit environment, then we can compare performance values.

[Dism]

Originally Posted by nightjar

Can you share some hints?

Will V.I. in AAX Native have more efficient use of CPU cycles than current RTAS?

Will V.I. in AAX DSP go "far beyond" what is possible in AAX Native?

Will the disk-caching feature of PTHD10 affect how future V.I. will function?

VI performance isn't really determined by CPU cycles, it's RAM that has far more of an effect.

It also depends on whether or not any AAX VIs will be hosted on DSP.

Disk Cache has nothing to do with VI performance.

[filosofem]

Originally Posted by nightjar

Will V.I. in AAX Native have more efficient use of CPU cycles than current RTAS?

Does MOD Delay III out perform MOD Delay II with the current Audio Engine? Will a 64-bit Pro Tools application with the current Audio Engine provide better AAX performance?

Originally Posted by nightjar

Will V.I. in AAX DSP go "far beyond" what is possible in AAX Native?

Lets rephrase the question, will DSP still out perform Native?

[djjedidiah]

Originally Posted by Dism

Which has nothing to do with anything, realistically, since PT is still a 32 bit host. Until it goes 64 bit, there's no way to compare VI performance with another 64 bit host. If the comparision were between Cubendo and Pro Tools with VE Pro, it would be another story entirely. He even says that the test is irrelevant to a 32 bit OS... but since PT is still 32 bit, it's a rather unfair comparison.

When we see AAX VIs in action in a 64 bit environment, then we can compare performance values.

Fair enough to a certain extent, but comparing Cubendo to PT with VE Pro is ridiculous. Of course that would be very different. You are using an entirely separate product to work around Pro Tools' abysmal VI performance. With all due respect, that's a silly statement.

A side question for me is why does Pro Tools seem to keep up when we're using effects plugins, but lags behind so much on instrument plugins?

[Dism]

Originally Posted by djjedidiah

uestion for me is why does Pro Tools seem to keep up when we're using effects plugins, but lags behind so much on instrument plugins?

64 bit.

[filosofem]

Originally Posted by djjedidiah

why does Pro Tools seem to keep up when we're using effects plugins, but lags behind so much on instrument plugins?

Personally, I think, that that question is an excellent example of what is wrong with Avid Virtual Instruments and a 64-bit application isn't really the solution to this problem. If a 64-bit applications primarily purpose is to expand the memory then why isn't the existing Avid Virtual Instruments efficiently handling it's operations at 32-bit? That is, not all Avid Virtual Instruments require a 64-bit memory allocation, sample content.

[sunburst79]

Originally Posted by filosofem

Personally, I think, that that question is an excellent example of what is wrong with Avid Virtual Instruments and a 64-bit application isn't really the solution to this problem. If a 64-bit applications primarily purpose is to expand the memory then why isn't the existing Avid Virtual Instruments efficiently handling it's operations at 32-bit? That is, not all Avid Virtual Instruments require a 64-bit memory allocation, sample content.

Word. As they say.

RTAS works just fine with effects, not that it couldn't be better mind you. It's VI's where it falls flat. And while moving to 64Bit is a good thing from the point of RAM access its not in and of itself going fix VI performance issue's. Hopefully AAX is better with VI's.

RTAS must die.

[propower]

Originally Posted by sunburst79

Word. As they say.

RTAS works just fine with effects, not that it couldn't be better mind you. It's VI's where it falls flat. And while moving to 64Bit is a good thing from the point of RAM access its not in and of itself going fix VI performance issue's. Hopefully AAX is better with VI's.

RTAS must die.

Totally agree...... but would add that some effects like TL|Space, IR1_L and Eleven all can bring a powerful system to its knees in no time.......

But for VI's we absolutely need high efficiency to b able to run low buffers......