Is VEPro Playing Well With PT10?

[Carl Lie]

I couldn't get a straight answer from Avid on this. Is anyone using the RAM cache with VEPro successfully?

Thanks.

Carl

[filosofem]

Successfully working on WIN. VEP 4.1.8783.

[Carl Lie]

Originally Posted by filosofem

Successfully working on WIN. VEP 4.1.8783.

Thanks.

How did you set up the ram cache vs memory for VEpro?

Carl

[filosofem]

Hi Carl, Disk Cache works in two ways, dynamically around the Playhead or Timeline cached. That is, if you have enough RAM (24GB) the latter probably isn't going to be an issue with VEP. Of course this is audio file size related. It's all very well having, say, 210 voices but if the clips contain small amounts of audio file data, 210 voices isn't going to eat into the Disk Cache Size. However if you have 60 voices with clip data 20 continuous minutes long, the Disk Cache is going to be eaten very fast.

Disk Cache playing dynamically around the Playhead loads what is needed for playback leaving un-allocated RAM for other services like VEP.

[Carl Lie]

Excellent. Thanks.

I have 12 GB in now but I'm might go larger when PT10 comes. Thanks for laying that out for me.

Glad it's working.

Carl

[filosofem]

Originally Posted by filosofem

Disk Cache playing dynamically around the Playhead loads what is needed for playback leaving un-allocated RAM for other services like VEP.

I just want to pick up on this point, what you are doing in starving the allocated RAM. That is, your system might have 24GB but you only allocate Disk Cache 6GB, thus allowing Pro Tools full access address aware (4GB) and VEP picks up the rest. These are not hardwired options, they are just workflows.

[Carl Lie]

Originally Posted by filosofem

I just want to pick up on this point, what you are doing in starving the allocated RAM. That is, your system might have 24GB but you only allocate Disk Cache 6GB, thus allowing Pro Tools full access address aware (4GB) and VEP picks up the rest. These are not hardwired options, they are just workflows.

Luckily I saw a pretty decent mid sizes session (32) tracks today that loaded into 4 GB of RAM timelined cached. I'm going to figure I can get away with 4-6GB for that then I"ll leave another 4GB for Protools and add more memory to have 12BG or so for VEP.

C