Help!@! Memory Error -108

[jessrho]

Hi Does any genius out there recognize and know what to do about the error message -108 when I try to start up my DP6 ? I'm on a year old Quad Core Zeon with OS 10.5.5. I can't open my project; i get this error message "An error occurred while reading from the disk. The file was not loaded. MacOS error: Ran out of memory (-108)
HELP !!?!!! please ( I have 9 gigs of memory, that should be enough) I have an important recording session today and I can't even open my project

[monkey man]

Will it load after removal of all components and perhaps 3rd-party MAS plugs?

Are you able to load the chunks into a blank template?

Did you try all the usual pref-trashing procedures (DP prefs and AU cache)?

Will the project load when copied to another location? Another drive?

[martian]

Will the project load when copied to another location? Another drive?

I get this if I try to open over a network drive- have to copy file to local drive first now... PIA

[jaygro]

This happened to me last week. Tried to use the "load" command in a new project. Still got the error. I ended up using a back up that I had.

This was a real pain. I had the project open then got the error after I did some volume automation and hit play. Project wouldn't open since that point.


jay

[bdr]

Do you have a lot of Vi's active?

Try opening DP without the VI's active and then maybe reconfigure your VI's so you don't have so many open at once eg open one at a time and freeze tracks then turn them off. I had a few -108 errors when I had a lot of instances of Play active so tried to re-open the file, clicked 'cancel' as each instance of Play was loading, and basically rebuilt my VI tracks.

Brett

[scottg]

It;s the plugin pre-rendering!! I found turning that off in the DP6 preferences>Audio plugins works..

Glad they tested that before releasing it,,, good going MOTU!

[jessrho]

hey thanks for the responses good people. i ended up calling motu and they helped me work around it. i had to open a new project and then load the chunk from my corrupt/unopenable file. i still got the -108 error message when i loaded the chunk, but then when i pressed ok to the error message the new/old corrupt/unloadable chunk was there under the chunks tab. so i salvaged all my audio files from there and made a whole new project version. whew!

[cchord59]

It;s the plugin pre-rendering!! I found turning that off in the DP6 preferences>Audio plugins works..

Glad they tested that before releasing it,,, good going MOTU!

I have the same problem, but I can't find that setting anywhere in dp 6. Can you tell me exactly where it is?
thanks

[scottg]

DP6 menu,,, PREFERENCES>AUDIO PLUG-INS.. Easy to find.. Turn that crap off they obviously did NOT test well and you should be good to go!

I wish they would test their software before releasing it! I mean, if it's not gonna work on my brand new right outta the box MacPro 8-core with 10gb RAM,,, it ain't gonna work for anyone!

I am seriously considering switching to Logic after 10 years and many professional albums done... Sad,, just sad..

[nathanpinard]

DP6 menu,,, PREFERENCES>AUDIO PLUG-INS.. Easy to find.. Turn that crap off they obviously did NOT test well and you should be good to go!

I wish they would test their software before releasing it! I mean, if it's not gonna work on my brand new right outta the box MacPro 8-core with 10gb RAM,,, it ain't gonna work for anyone!

I am seriously considering switching to Logic after 10 years and many professional albums done... Sad,, just sad..

I'm' weighing responses like in in switching from Logic to DP.

Sounds like some instability issues that are normal. Logic is the same way honestly.

And Logic doesn't have nearly as much organization as DP.

Still...I will see how things pan out.

[scottg]

All I can say is I AGREE,, DP is better than LOGIC in their structure but I have to work,, and work fast.. Can not have this constant issues and untested software.. They are obviously a very sloppy company who does not think testing is important or is convinced use "end-users" are using just MOTU stuff without any other plugs, etc..

BTW - Have you ever tried LOGIC with the plugins? It is sweet!! Everything WORKS as promised.. Native Instruments,, VSL,,, everything is easy--- works like it should... and don't get me started on ProTools.

MEMORY ERROR ISSUE: Since I turned off plugin pre-rendendering (in prefs) it has worked beautifully! Again--- I'm on a new MacPro 8-core with 10gb ram with Apogee audio.. There is no reason DP6 would not to work WITH rendering on other then MOTU did not test DP6 fully (and yes, I talked with their tech support who was totally unhelpful).

Good luck.

[Dan Walsh]

I just ran into the error 108 prob this morning as well. For absoultely no apparent reason. I don't have any vi's on the song, just a drum kit, a bass and a stereo guitar track running some eq plugs and a few gates on the kit. It is bizarre that the file got corrupted. I did use the method below from jessrho though and everything is back to norm.

This kinda stuff makes me jittery though. I'm not taxing my mac at all and the file was fine when I saved it 2 days ago. I'm hopin' this isn't an ongoing prob. I've been runnin' 6.01 solidly for the past few couple m onths with no probs. I hope it stays that way.....

hey thanks for the responses good people. i ended up calling motu and they helped me work around it. i had to open a new project and then load the chunk from my corrupt/unopenable file. i still got the -108 error message when i loaded the chunk, but then when i pressed ok to the error message the new/old corrupt/unloadable chunk was there under the chunks tab. so i salvaged all my audio files from there and made a whole new project version. whew!

[Dan Walsh]

So now I got a prob. The file I just saved in the new project is apparently still corrupted even though I had it workin'. I just went to re-open the new one and I'm gettin error 108 again.

I have no idea why....any one got ideas? I'm really not taxing the system at all. 10 audio trax and a couple of verb aux returns and a little bit of automation. Minor volume adjustments and panning.

I'm stumped.....

[Mr. Quimper]

I experienced my own corrupted DP 6 project about a month or so ago and it's turned me into a habitual backer-upper if not a Logic looker-atter. I'd had the problem before w/ DP 5.13 but this was the very first project I attempted w/ DP 6.

The rate at which this corruption occurs REQUIRES that MOTU implement an automatic backup function like Pro Tools and Logic.


Then again, if DP project files become corrupted so easily, why should I assume the software would be able to produce usable/stable backups?

[Dan Walsh]

Anyone got an idea that can help?? I can totally load the chunk into a new project, and everything works fine. When I save and close the new project and bring it up again it gives me the memory error 108. I'm baffled. I've done some searching about trashing prefs, but I'm afraid. very afraid. If I do trash pref's, what'll happen??

Sorry if this has been covered a gazillion times, but I'm afarid to wade in and start trashin stuff

So now I got a prob. The file I just saved in the new project is apparently still corrupted even though I had it workin'. I just went to re-open the new one and I'm gettin error 108 again.

I have no idea why....any one got ideas? I'm really not taxing the system at all. 10 audio trax and a couple of verb aux returns and a little bit of automation. Minor volume adjustments and panning.

I'm stumped.....