Pro tools 7 "could not complete request because there is not enough memory". w/pic

[brianhood]

I was just minding my own business quantizing drums on a song with this message popped up. All i did was try to make a crossfade. no matter how many times i try, this still pops up. It wont let me make cuts either.
i've tried removing all inactive regions and it still does this.
anyone have any idea what i did to cause this or how it could be fixed? I couldn't find anything on google about it(everything with this message was related to photoshop)

I have 4 gigs of ram, so i wouldnt think this would be the problem(especially this early into the recording process with so little going on plugin and region wise). I dont really know what kind of info you guys would need from me to help fix this problem other than im running windows xp pro

 

[Metaltastic]

Well clearly it's because your using Windows Media Player 9, how antiquated


But seriously, no clue dude - PT seems to be pretty shaky on PC's IME!

 

[STINNETT]

.... I dont really know what kind of info you guys would need from me to help fix this problem other than im running windows xp pro

Cue the MAC fanboys.

 

[Ermz]

I'm assuming the issue lies with HDD space. How much do you have free on the disk where your session is saved? The thing is that whenever you make cuts like that, you're creating new audio regions and files.

 

[brianhood]

Cue the MAC fanboys.

lamo

I'm assuming the issue lies with HDD space. How much do you have free on the disk where your session is saved? The thing is that whenever you make cuts like that, you're creating new audio regions and files.

i didnt even think of that. I just checked it though, and i still have over 300 gigs free, so no problems there.

 

[Ermz]

Very odd. Have you tried consolidating the files up to the point where you're working and seeing if that frees up any of ProTools' imaginary resources?

 

[brianhood]

Very odd. Have you tried consolidating the files up to the point where you're working and seeing if that frees up any of ProTools' imaginary resources?

yeah that did the trick.

doesnt make since to me why it would do that on this session though(with only 3 songs worth of drums, and no scratch tracks). I've had a session with 8 songs in it and they all had drums and scratch guitar tracks. I quantized and edited the drums one song at a time, but i had no problems about "not enough memory." Im sure i had at least twice the number of active regions too.

weird


guess it's time to get a mackuke:

 

[Ermz]

ProTools can do some weird things at times. It's one of the less stable DAWs I've used (though its pure editing power makes up for it). It could have to do with processes you are running in the background. ProTools is very selective about what it wants to share its space with. I'd disable as many background processes/services as humanly possible and see if it happens again.

Though it is good workflow procedure to consolidate every so often to speed up its read times, which often are limited by the rate at which it can grab all those regions off the HDD at once.

 

[James Murphy]

meh, pro tools has been rock solid for me. the most stable DAW i've ever used. but i'm on HD, so can't really say if it's the same for LE or M-Powered.

 

[Trep]

The first thing i Noticed is that you Havent got any of the Customer support updates. (it says in the window header)

http://www.digidesign.com/index.cfm?navid=3&langid=100&eid=4731&categoryid=36

Here is the Download for CS update 8. If it is a bug, this may fix it. If not Installing this gives you all bug fixes to date anyway.

Hope it helps

EDIT: haha i just read back and see you fixed the problem..

Install that anyway though

My bad

 

[Ermz]

I'm not doubting that at all, James. It's a hell of a platform - amazingly powerful.

Just as a PC user, and one that has tried a few DAWs over time, I've found ProTools to be the most subject to external factors, such as background services, anti-virus scanners, which plug-ins are installed (certain sets totally crashed the app on boot) etc.. Not to intentionally try to denigrate the platform, but running PT7 on various HD systems at local studios I've run into even more issues than at home. A lot of it seems to be subject to how the machine is set up, and how well maintained it is.

Recently, PT7.4 LE has been running flawlessly for me at home. Though there always seem to be some bugs left in there. Local studio owners I associated with made that observation long before I did.... apparently they all had issues with their Control 24s and the HD expansion card for Apogee interfaces (to forego the use of the 96 or 192 i/os). It never quite ran as solid as they would've liked.

 

[brianhood]

The first thing i Noticed is that you Havent got any of the Customer support updates. (it says in the window header)

wtf?

I dont see it...am i blind?

i'm on HD, so can't really say if it's the same for LE or M-Powered.

one day i shall have this Pro Tools HD....
i still have a long way to go, alot to learn, and tons of cash to save up before i could benefit from switching over though haha

 

[Ermz]

What he means is that it would say in the header if you DID have the CS updates. Just grab them and you'll run into less issues!

 

[James Murphy]

yeah... PC issues then. i've never used PT in windows, just Mac, and it's been excellent. no stability issues at tall.

 

[MetalJonesy]

right a quick one about how many instances of drumagog you have running. as ive run upto around 11-14 before and its played up, even though the CPU usage is right below half drumagog can affect it big time! id suggest bouncing a few tracks down with your samples and turning off a few instances of it! oh and instead of using the PC's cpu usage thingy, can you try it with the PT 'gas monitor' cpu/rtas useage, as it could differ a bit!

 

[Trep]

What he means is that it would say in the header if you DID have the CS updates. Just grab them and you'll run into less issues!

haha yer thanks Erm

 

[poidaobi]

yeah... PC issues then. i've never used PT in windows, just Mac, and it's been excellent. no stability issues at tall.

 

[AStudio]

Check in Preferences --- Operation Tab --- then check the Open Ended Record Allocation part --- Click the limit to: then put 60.

Make sure it is not set to 1 minute for example. If you record a take that exceeds the time limit you have set it will error.

For example mine is set to 10 minutes, if i record a continuous take that lasts more than 10 minutes pro tools will error my ass.

Hope it helps

 

[Skinny Viking]

Check in Preferences --- Operation Tab --- then check the Open Ended Record Allocation part --- Click the limit to: then put 60.

Make sure it is not set to 1 minute for example. If you record a take that exceeds the time limit you have set it will error.

For example mine is set to 10 minutes, if i record a continuous take that lasts more than 10 minutes pro tools will error my ass.

Hope it helps

+1

That was my 1st thought as well ... I used to have problems similar to your until I discovered this little option after much searching

 

[mark.james]

I've been using PT in Windows ever since it became available, and after v5 I've had pretty much no problems at all.

When I do run into the rare, weird problem with a session I usually create a new one and import everything from the old session. That usually takes care of any problems.


Mark