RAM & Pro Tools

[kings79]

This could be a big topic and we may need some Avid people to help. But...

RAM. What tasks does RAM get utilized in Pro Tools. What uses alot of RAM and what doesn't.

I want to know everything from session loading to hitting play.

RAM & Pro Tools.

[EGS]

Scroll down to "Memory": https://www.pro-tools-expert.com/hom...pro-tools.html

[kings79]

Originally Posted by EGS

Scroll down to "Memory": https://www.pro-tools-expert.com/hom...pro-tools.html

Thanks man. That is helpful. But I'd like to know exactly what is using RAM and when.

PT Expert
"Memory - The memory meter shows how much system RAM is being used by Pro Tools. If you are using Pro Tools 10 and earlier, which are 32 bit applications, then this is limited to around 3GB, irrespective how much RAM you may have installed in your computer. Pro Tools 11 is a 64 bit application, so is theoretically able to access as much memory as you throw at it. Plug-ins, particularly Virtual Instruments with large libraries use lots of memory so it is good to have as much in your computer for Pro Tools to access. However you need to remember that Pro Tools accesses RAM for other functions too, this includes; The Audio and Video Engines, plug-ins and disk cache (if available & enabled)."

[EGS]

Originally Posted by kings79

...But I'd like to know exactly what is using RAM and when...

Perhaps you could test on your own rig:

Boot computer, quit all apps, & check mem usage in Activity Monitor: https://support.apple.com/guide/acti...ctmntr1004/mac
Launch PT, video engine off, no disk cache, no VIs. Check Activity Monitor.
Video engine on: check Activity Monitor.
Disk cache on and set to ??? size; check Activity Monitor.
Add a VI; check Activity Monitor.
Add other VIs etc etc etc

[kings79]

Originally Posted by EGS

Perhaps you could test on your own rig:

Boot computer, quit all apps, & check mem usage in Activity Monitor: https://support.apple.com/guide/acti...ctmntr1004/mac
Launch PT, video engine off, no disk cache, no VIs. Check Activity Monitor.
Video engine on: check Activity Monitor.
Disk cache on and set to ??? size; check Activity Monitor.
Add a VI; check Activity Monitor.
Add other VIs etc etc etc

I've done all that. Ther is too much lag.

I want to hear from the experts for a definitive answer.

[its2loud]

Plug-ins, VI’s, and Disc Cache. Avid Video Engine uses RAM too if you’re using that.

[kings79]

Originally Posted by its2loud

Plug-ins, VI’s, and Disc Cache. Avid Video Engine uses RAM too if you’re using that.

What about Loading Sessions, Audio Suite, the Mix Engine, channel meters ect..?

yes I use the Video Engine.

[musicman691]

Originally Posted by kings79

What about Loading Sessions, Audio Suite, the Mix Engine, channel meters ect..?

yes I use the Video Engine.

There's no real numbers on that that you'll find. Knowing what each little bit takes up ram-wise won't tell you anything. It's the program as a whole you should be concerned about. I have to ask - why do you need to know all those kinds of details? Or is this just some academic exercise? What exact problem are you chasing? You mentioned something about lag. Lag where? In what operation?

[JFreak]

Originally Posted by its2loud

Plug-ins, VI’s, and Disc Cache. Avid Video Engine uses RAM too if you’re using that.

This.

Algorithmic (a.k.a. normal) plugins do not consume much memory, you could have lots of those in sub-gigabyte systems two decades ago. Audiosuite as well, not a problem as it is CPU constrained nonrealtime process. Video Engine should be turned off if you do not need it and using Disc Cache is optional, but here's the thing... some VI's are optimised to use as much memory as there is while some older ones (such as Synthogy Ivory II) are optimised to use as much storage performance available, reducing memory footprint and making your storage scream.

I am currently testing a fully loaded M1 Mac Mini which obviously maxed at 16GB memory. No problems so far (except Sonnox Pro Codec does not work yet), but adding huge amount of VI's becomes a problem at some point. Looks to be enough for my workflow though.

[musicman691]

Originally Posted by JFreak

This.

Algorithmic (a.k.a. normal) plugins do not consume much memory, you could have lots of those in sub-gigabyte systems two decades ago. Audiosuite as well, not a problem as it is CPU constrained nonrealtime process. Video Engine should be turned off if you do not need it and using Disc Cache is optional, but here's the thing... some VI's are optimised to use as much memory as there is while some older ones (such as Synthogy Ivory II) are optimised to use as much storage performance available, reducing memory footprint and making your storage scream.

I am currently testing a fully loaded M1 Mac Mini which obviously maxed at 16GB memory. No problems so far (except Sonnox Pro Codec does not work yet), but adding huge amount of VI's becomes a problem at some point. Looks to be enough for my workflow though.

And some vi's like the East West Play engine can either run from disk or load all into ram on a per voice instance. And you have those like Kontakt that can load the initial bit of sound and stream the rest. There are no real hard and fast numbers. And if you have a modeled vi like some pianos are they use a minimal amount of ram.