Disk Playback Cache Size?

[dg27]

Originally Posted by BScout

Bold means complete files and not clips. It isn't an indication if it is used or not.

Thanks for clarifying.

Originally Posted by BScout

Up to you. I know what my memory vs audio disk cache needs are (even with a 100% SSD system.) I like to be aware of how much disk cache I'm using too.

How do determine what your memory vs audio disk cache needs are? I guess I need to read up on this.

Last week (when I upgraded to 12.4) I installed a dedicated Samsung 850 Pro SSD for my PT files, including audio. (My boot is also a Samsung SSD.)

Overall it seems I have fewer issues and never see any system resources errors.

[BScout]

Originally Posted by dg27

How do determine what your memory vs audio disk cache needs are? I guess I need to read up on this.

Look at Pro Tools system usage meters.

If your disk cache is maxed out and your memory usage is low, increase your disk cache.

If you memory usage is high and your disk cache usage is low, reduce your disk cache.

Just remember you're taking from memory to make the disk cache so then that memory isn't available to VIs (I don't use VIs mostly because I edit and mix). Also remember when you increase your disk cache size, your memory usage will go up some also because the memory line is also reflecting the amount that got repurposed to be used for the disk cache.

Memory always tells the big picture no matter what is using it (and that includes the disk cache size set)

[dg27]

Thanks--this is really helpful--now I get it.

I just played around with different amounts of disk cache and watched the usage meters. It seems like normal is the best bet.

[jkossov]

Hey guys,

I can't figure out if the cache is also used for virtual instruments or just for audio files. Can't find it in the manual.

Thanks

[Southsidemusic]

Originally Posted by jkossov

Hey guys,

I can't figure out if the cache is also used for virtual instruments or just for audio files. Can't find it in the manual.

Thanks

The cache function is applied on the whole timeline (session) saved into the RAM so it doesn’t matter if it’s VI or Audio.

[BScout]

Audio files only in the session (including any commits on VI tracks)

Has no bearing on what sampler VIs load.

[jkossov]

Originally Posted by BScout

Audio files only in the session (including any commits on VI tracks)

Has no bearing on what sampler VIs load.

Sure it includes commits, these are audio files.
What you're saying is not lining up with what Southsidemusic said or am I misunderstanding?

[Darryl Ramm]

Originally Posted by jkossov

Sure it includes commits, these are audio files.
What you're saying is not lining up with what Southsidemusic said or am I misunderstanding?

I suspect people are trying to say the same thing. Audio in the timeline once it is created uses the disk cache. So if you say freeze or commit a VI or route it somewhere and record the audio that all ends up in the cache.

VI samples are entirely outside that, completely managed by the VI plugin, may stream, may pre-load etc. all at the plugins control. You need to read the documentation for your VIs (none of which will say boo about disk cache and VI samples... because they are unrelated).

[BScout]

Originally Posted by Darryl Ramm

I suspect people are trying to say the same thing. Audio in the timeline once it is created uses the disk cache. So if you say freeze or commit a VI or route it somewhere and record the audio that all ends up in the cache.

VI samples are entirely outside that, completely managed by the VI plugin, may stream, may pre-load etc. all at the plugins control. You need to read the documentation for your VIs (none of which will say boo about disk cache and VI samples... because they are unrelated).

^^^^ This +1