PT10 and Kontakt

[steveskinner]

Difficult to reduce the instances of VI that I used, since I had 1 open. As far as I can tell, it's not a RAM issue. There is now 16GB of RAM available in PT10 when there used to be only 8 in PT9. When I get the clicks and pops, or error messages, the Activity Monitor shows a hard drive spike, not a CPU spike. The CPU is only about 10%. My sample drive is separate from my audio drive, internal SATA, and in fine shape. Something is wrong here.
I may try VE again. The last time I did it crashed a lot.
Still learning Logic.

[steveskinner]

I know you're all saying that it's not Avid's fault for various reasons. But my situation is that I plunked down 7 grand on the upgrade because the Avid product rep said that with the HDx card handling more of the load I would be able to run a lot more virtual instruments. Then, after the upgrade, I find I can run fewer virtual instruments. When I call Avid to try to work it out, they say Kontakt 5 is not supported so there's nothing they can do. I'm not in a happy place.

[TOM@METRO]

If you don't have the desire to run VEPro, you could try Reaper. Pick up a demo and ReWire it to Pro Tools, then run Kontakt in Reaper. This works very well for me.

[Emcha_audio]

Originally Posted by steveskinner

Difficult to reduce the instances of VI that I used, since I had 1 open. As far as I can tell, it's not a RAM issue. There is now 16GB of RAM available in PT10 when there used to be only 8 in PT9. When I get the clicks and pops, or error messages, the Activity Monitor shows a hard drive spike, not a CPU spike. The CPU is only about 10%. My sample drive is separate from my audio drive, internal SATA, and in fine shape. Something is wrong here.
I may try VE again. The last time I did it crashed a lot.
Still learning Logic.

Mate, PT 10 can not see more than 3.5 gig because it's a 32 bit application, that has always been the case for 32 bit applications. It's how it is. PT 10 does not see 16 of ram. it sees only 3.5 gigs of ram. So yes it's a ram issue.

When Pro tools becomes 64 bit (next version) then it will be able to access all the available ram on your motherboard, without any tricks as ram cashing (which is only available on hdx- hd-N and through the toolkit) ect. And that ram cashing is only good for the timeline (audio files) not plugins. So until PT 11 comes out, you will be limited to the maximum ram access a 32 bit application offers.

[mykhal c]

the extra ram that PT10 uses is for 'audio' files only (playback). but this is a separate address space that PT10 creates to be able to do this. VIs are still restricted to the 32bit app limit...4gb...which in Windows is really about 3.5gb as previously stated. VEPRO5 is the way to go IMHO...much more efficient in runnin' VIs.

[steveskinner]

Thanks. I'll check out Reaper. I'll also lower the RAM use of the instruments.

[musicman691]

Originally Posted by steveskinner

Thanks. I'll check out Reaper. I'll also lower the RAM use of the instruments.

There's not a whole heck of a lot you can do to do that except to render to audio one vi at a time. You'll just have to either go the Reaper rewired route or try VE Pro again. With proper setup it should work (VE Pro that is) quite well without problems.

[Marsdy]

Originally Posted by Emcha_audio

Mate, PT 10 can not see more than 3.5 gig because it's a 32 bit application, that has always been the case for 32 bit applications. It's how it is. PT 10 does not see 16 of ram. it sees only 3.5 gigs of ram. So yes it's a ram issue.

When Pro tools becomes 64 bit (next version) then it will be able to access all the available ram on your motherboard, without any tricks as ram cashing (which is only available on hdx- hd-N and through the toolkit) ect. And that ram cashing is only good for the timeline (audio files) not plugins. So until PT 11 comes out, you will be limited to the maximum ram access a 32 bit application offers.

Theoretically PT can see 4GB RAM. The reality is a LOT less than this.

On my system PT throws up a memory error at 2.7 or 2.8 GB RAM usage according to OSX's Activity Monitor. Usually I've crashed well before then so I keep PT memory usage below 2.3 GB . It does't matter if you've got 32GB.... PT will start running out of memory at well UNDER 3GB and you will crash and burn.

Also a number of VIs eat up memory and don't release it properly. It pays to regularly restart PT when opening new sessions etc.

As mentioned MANY times in this thread and others, this is all a result of PT still being a 32 bit app. Logic, DP, VE Pro etc. were just as bad until they went 64 bit and many high end plug ins are STILL 32 bit only anyway.

Until PT goes 64 bit, keep PT's memory usage below 2.5 GB at most, use Kontakt's Memory Server or use a 3rd party VI host, (VE Pro is the best.)

Finally set your buffer to at least 256K and preferably higher.

It's also worth mentioning that a few VIs are having issues with PT10. Trillian and BFD to name but two.

[steveskinner]

Thanks for the tips. I'm less angry now.
I'm working with Reaper and unfortunately the 64 bit version doesn't work as a ReWire slave so I'm still getting problems. Better than PT alone, though. Is VE Pro 64 bit?

[brianjanthony]

VE Pro is 64 bit AND it rocks. You can use 32 and 64 bit versions along side each other, with both feeding PT at the same time. (keeping your 64 bit plugs in one and the 32 in another if you like). And its great for making templates up and things like that. Stable as heck in my world, and i use it 80+ hrs a week.