Avid, I'm thinking that...

[Sean Halley]

On an official level, I am a Loo-hoo-hoo-zzzeerrrrr.

Yes, got it - I've been slammed. I just sent you an email. Hit me up.

S..

[Barry Johns]

I need LE, I do remote stuff all the time in LE. Actually, the Mbox Pro is looking sweet for this!!!

[relaxo]

Originally Posted by digidesigner

Create a new hyper-HD system with many times of the current TDM capabilities and to start this off well port your own VI's to the new TDM!

NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!

"Realize the only plugin that needs to be active is the one you're currently adjusting...all others should be quickly, invisibly, seamlessly and automatically rendered into audio."

Am I the ONLY one in here who understands that the Henry Ford quote someone posted a few days ago applies, and is possible in the here and now...
"If I’d asked my customers what they wanted, they’d have said a faster horse."

[BaileyBass]

Originally Posted by relaxo

.all others should be quickly, invisibly, seamlessly and automatically rendered into audio."

Hows that work? Creates new audio every time you make an adjustment? How do you commit to it? Perhaps I just don't understand your meaning of "render". SB

[digidesigner]

Originally Posted by Barry Johns

I need LE, I do remote stuff all the time in LE. Actually, the Mbox Pro is looking sweet for this!!!

Please don't get me wrong, I'm saying that Avid should get rid of the limitations in LE and therefore dropping LE and giving out the new Pro Tools HD Native version not only with the new Native PCIe card but with M-Boxes too! That would instantly raise the image of the software and the company.

[emluper]

Originally Posted by BaileyBass

Hows that work? Creates new audio every time you make an adjustment? How do you commit to it? Perhaps I just don't understand your meaning of "render". SB

Yeah, I have to agree with you. I would like to be in control of this "option" myself. Not to mention the "freeze track" method using Quick Punch that some people are already using is kinda cool. It's a little clunky, but it works.

[relaxo]

Originally Posted by BaileyBass

Hows that work? Creates new audio every time you make an adjustment? How do you commit to it? Perhaps I just don't understand your meaning of "render". SB

There are many ways to skin a cat I'd be best if it's all under the hood and invisible and "looks" and acts like normal PT operation of today. Any yes, any .25mm tweak of a knob kills the existing audio track and reactivates the plug ins. As soon as the plug in knob stops moving, PT begins re rendering the audio. When the render is complete, PT re-routs the signal using the audio...all under the hood so everything looks normal, even all the plug-ins "look" active and normal.

It sounds like a lot of CPU demand, but at any given time, all other tracks are audio, and no other plugins are requiring dsp, so your CPU is at 5%-10% running audio tracks, mixing and summing and other overhead tasks.

All your computer has to really do ever is render the plug-ins into one track (maybe as many as four tracks if you're quickly jumping around plugin adjustments.)

The only "ultra" about this is that it would be beneficial to have an ultra efficient turbo rendering engine to render tracks in a second or two utilizing the cpu that's almost always at 90% free.

[digidesigner]

Originally Posted by relaxo

There are many ways to skin a cat I'd be best if it's all under the hood and invisible and "looks" and acts like normal PT operation of today. Any yes, any .25mm tweak of a knob kills the existing audio track and reactivates the plug ins. As soon as the plug in knob stops moving, PT begins re rendering the audio. When the render is complete, PT re-routs the signal using the audio...all under the hood so everything looks normal, even all the plug-ins "look" active and normal.

It sounds like a lot of work, but at any given time, all other tracks are audio, and no other plugins are requiring dsp, so your CPU is at 5%-10% running audio tracks, mixing and summing and other overhead tasks.

All your computer has to really do ever is render the plug-ins into one track (maybe as many as four tracks if you're quickly jumping around plugin adjustments.)

The only "ultra" about this is that it would be beneficial to have an ultra efficient turbo rendering engine to render tracks in a second or two utilizing the cpu that's almost always at 90% free.

I fully get your idea, but for me, if it would be THAT or new hyper TDM system with real time TDM VI's I would go with the latter :) faster horse for me :)

[relaxo]

Originally Posted by digidesigner

I fully get your idea, but for me, if it would be THAT or new hyper TDM system with real time TDM VI's I would go with the latter :) faster horse for me :)

Imagine a world where we're not tied to computer cards and monster sized computers to house them or hauling around external dsp boxes etc etc...and especially, buying new sets for $6k every three years. I would rather spend $3k on an ilok asset that enables highly intelligent software than $6k on clumsy, soon outdated hardware that does the same thing.

We could all become so much more portable. I write songs on a laptop. I would love to have 30 or 50 VIs active at once on a track in a fully RTAS laden mix...if they're all audio tracks...no problem. No more printing! No more track management chaos! make new track, name, rename, change outputs to bus, PRINT IN REAL TIME, deactivate old, hide. Then to tweak again, unhide, reactivate, mute or deactivate etc. Did I forget anything? Then PRINT AGAIN! All of this over and over maybe just to get through your session without CPU overload.

I get your angle too because that's what I do, but even if the new way performed better than the horse?

[digidesigner]

I think the thing you are asking if happening will make the computer sluggish at times and I absolutely cannot accept that. CLA admits here, that he cannot stand how Pro Tools will not react fast enough when you hit play and I fully understand what he means! http://mixonline.com/studios/profile...la/index1.html