Pro Tools locking...

[shanabit]

No freeze function in LE, yo have to PRINT the tracks with the effects on it

[RadioMoo]

Originally Posted by shanabit

No freeze function in LE, yo have to PRINT the tracks with the effects on it

AudioSuite: this is like putting a track in waveform view in Audition and adding an effect (as opposed to using the effects rack on the track itself in multitrack view).

You can, however, automate the Bypass button on PT's plugins so that the plugin is only "turned on" when it's needed.

[the1Hub]

[QUOTE=RadioMoo;987520
You can, however, automate the Bypass button on PT's plugins so that the plugin is only "turned on" when it's needed.[/QUOTE]
even with the plugin bypassed it still loads the cpu down as much as if it were in the path

[shanabit]

Originally Posted by RadioMoo

AudioSuite: this is like putting a track in waveform view in Audition and adding an effect (as opposed to using the effects rack on the track itself in multitrack view).

You can, however, automate the Bypass button on PT's plugins so that the plugin is only "turned on" when it's needed.

Forgot about audiosuite LOL thanks for hte correction

[AlexLakis]

Set the output of the track to a bus. Then create a new track and select that bus as the input and arm it for record. Record. This is commonly referred to as "printing" a track. It's also a handy way to print a single pass of automation if that's all you need from an effect or MIDI instrument that doesn't support automation.

Also, correct me if I'm wrong, but not all plugins have audiosuite versions?

Also, bypassing an insert will not load it out of memory. Disabling the insert will.

[RadioMoo]

Originally Posted by AlexLakis

correct me if I'm wrong, but not all plugins have audiosuite versions?

That is correct, and there are even some AudioSuite plugs that don't have a Digirack version! PITA!

Originally Posted by AlexLakis

bypassing an insert will not load it out of memory. Disabling the insert will.

Originally Posted by the1Hub

even with the plugin bypassed it still loads the cpu down as much as if it were in the path

No, if you watch your CPU meter when bypassing and un-bypassing plugs, you'll see that bypassing does decrease CPU usage.

[AlexLakis]

Originally Posted by RadioMoo

No, if you watch your CPU meter when bypassing and un-bypassing plugs, you'll see that bypassing does decrease CPU usage.

I believe The1Hub is right, a bypassed plugin is still fully loaded into memory.

Notice the slight delay when disabling and re-enabling plugins. This is the time it takes to completely unload the plugin from memory or completely load it back in. When bypassing a plugin, you do not experience this delay because the plugin stays loaded in memory, the audio is just "re-routed."

Perhaps, on some plugins, by bypassing the plugin, certain aspects of the plugin are in turn disabled (the "bypass meter section" on the Crysonic plugins comes to mind,) but the plugin will still eat up CPU power unless disabled.

[the1Hub]

Originally Posted by RadioMoo

No, if you watch your CPU meter when bypassing and un-bypassing plugs, you'll see that bypassing does decrease CPU usage.

picture pictures pictures

ok so here are 6 pictures of a protools session in various states of operation.

the first it the session with transport stopped and the plugin in active.


the second is with the transport stopped and the plugin active


the third is with the transport stopped and the plugin bypassed notice no major difference between the bypassed and unbypassed plugin on the cpu meter.


fourth has the transport in playback and the plugin bypassed


fifth has the transport in playback and the plugin unbypassed. there is a very neglegible amount of cpu usage increase on this one. i beleve this is attributed to active information the gui displays on the screen. if you close the plugin dialog box the cpu returns to the same level as in the fourth picture (see picture six)

and for whatever its worths this is a 24 44.1 session with a 256 buffer on the interface and a level 2 dae playback buffer with 1 processor enabled. running on a dual g4 fw800 1.42 ghz with 1 gig ram. 002R interface.

[the1Hub]

number 2

[the1Hub]

number 3

[the1Hub]

number 4

[the1Hub]

number 5

[the1Hub]

nnumber 6

[the1Hub]

number 6

[RadioMoo]

Originally Posted by the1Hub

the third is with the transport stopped and the plugin bypassed notice no major difference between the bypassed and unbypassed plugin on the cpu meter.

I notice no major difference, but I don't notice no difference.