Help!@! Memory Error -108

scottg · Post by **scottg** » Mon Jan 05, 2009 10:31 pm

OK.. I'll say it again (please read my post this time),,, from my experience it has NOTHING to do with chunks or corrupted files! It has to do with MOTU NOT TESTING THEIR NEW PRE-RENDER PLUG-INS option implemented in DP6.. Audio is overwhelming the memory buffers..

SOLUTION: Go to DIGITAL PERFORMER MENU>Preferences>General-Audio Plugins> Two drop-down menus,, Default for new projects & Current Project,,, set them both to "All Plug-ins Real-Time" and you should be fine (at least it worked for me). I had this error until I turned that crap off--- since then, no problems..

My guess is your settings on those projects are going to "pre-render".. Now you understand?

MOTU really needs to FIX this, test it properly, then release it ONLY if it works! Really pisses me off! I really hate software companies that are sloppy and do not fully test their software however have no problems asking $200+ for their crappy almost working upgrade.. They are more interested in getting your money than making rock-solid software people can relay on,, that's not cool!

Anyways, I just got Logic today--- so far it looks cleaner and more functional than DP6!!

martian · Post by **martian** » Tue Jan 06, 2009 12:11 am

+ 1 (08)

monkey man · Post by **monkey man** » Tue Jan 06, 2009 7:24 pm

FWIW Dan, there's no need for concern as far as that pref trashing is concerned; just drag 'em to the desktop, fire DP up, do the re-saving and pop 'em back after quitting DP.

scottg · Post by **scottg** » Sat Jan 17, 2009 2:38 am

I think none of you are reading my post or solution to the Memory Error -108,,, so I will not post again..

The solution is in the preferances--- plugins,, pre-rendering! Obviously they didn't test it well--- so it causes the error..

Does anyone read these posts or just ignore everything,, and continue to talk of "corrupted files"???

humm,, funny forum... I hope some one stops are reads this stuff--- I've had no problems since I turned that crap off!

Good luck to you all!

Dan Walsh · Post by **Dan Walsh** » Sat Jan 17, 2009 8:21 am

Scott G

I read your posts. 3 Times. And although I appreciate your helpfulness, the pre-render function is not where my prob lies. I have tried your method. 3 Times. I still have the same prob, with only this particular song. I have 6 reasonably big projects with 10 or 12 songs in each on the go right now, and they are all working fine.

Anyways, thanx for the help.

monkey man · Post by **monkey man** » Sat Jan 17, 2009 8:44 pm

Just for the record too, Scott, I think you'll find that most if not all who're following the thread would've read your posts. What would be the point otherwise?

Your characterisation of the forum leaves much to be desired, IMHO. "Give it a chance, and try not to assume the worst" would be my humbly-submitted advice.

Mr_Clifford · Post by **Mr_Clifford** » Tue Jan 20, 2009 4:13 pm

The -108 (ran out of memory) error seems to run a bit deeper than just the VI/FX pre-rendering. DP 6 seems to have some serious memory management issues. I suspect it's not the pre-rendering per-se, but rather DP not managing the memory properly when it dumps the samples, then re-loads them again etc. - which, of course, it does a lot when pre-rendering is turned on. It also seems to have issues with changing between different sequences.

I'm running a project for a documentary at the moment with a couple of VI's (all in V-racks, pre-rendering turned OFF on all of them) and Reason hooked up via Re-Wire. All is fine when working on the first chunk/sequence, but when I change chunks to work on different cues, it starts to build up. First it just starts to slow down a bit, then I get lots of 'beach-ball-of-death's and have to wait for simple operations, eventually I'll go to do something and I get the dreaded 'ran out of memory' error. So in my case it's not even needing to load and un-load VI's/FX.

Once I get this error, the only way to get things back to normal is to re-boot the computer. Just shutting down DP (&Reason) and opening up again isn't enough. So DP isn't even putting the memory right when closing the application.

kassonica · Post by **kassonica** » Tue Jan 20, 2009 4:32 pm

Mr_Clifford wrote:The -108 (ran out of memory) error seems to run a bit deeper than just the VI/FX pre-rendering. DP 6 seems to have some serious memory management issues. I suspect it's not the pre-rendering per-se, but rather DP not managing the memory properly when it dumps the samples, then re-loads them again etc. - which, of course, it does a lot when pre-rendering is turned on. It also seems to have issues with changing between different sequences.

I'm running a project for a documentary at the moment with a couple of VI's (all in V-racks, pre-rendering turned OFF on all of them) and Reason hooked up via Re-Wire. All is fine when working on the first chunk/sequence, but when I change chunks to work on different cues, it starts to build up. First it just starts to slow down a bit, then I get lots of 'beach-ball-of-death's and have to wait for simple operations, eventually I'll go to do something and I get the dreaded 'ran out of memory' error. So in my case it's not even needing to load and un-load VI's/FX.

Once I get this error, the only way to get things back to normal is to re-boot the computer. Just shutting down DP (&Reason) and opening up again isn't enough. So DP isn't even putting the memory right when closing the application.

I think you are so close to what is happening with DP it's scary.

Maybe this is why they have taken so long for an update.

monkey man · Post by **monkey man** » Tue Jan 20, 2009 5:31 pm

Exactly. Cliffo is on the money, at home base, spot on and drowning in jack's pot, but MOTU can't get near him 'cause of his avatar. A conan-drum, to be sure...

larryssp · Post by **larryssp** » Wed Jan 21, 2009 7:35 am

Yes, this is exactly what is happening. And yes, I have made the necessary preference adjustments as recommended by MOTU tech also. Even working just in MIDI - once you get to around the third project you'll see this Memory 108 - I can play and rewind, but nothing else - I need to shut down and then I can get back to work. So, MOTU, and I'm told by my beta testing friend that they are close to sending out an update, has sent us all a version that makes working very difficult. I have experienced this with many other pro apps over the years, but you never get used to it.

Larry

superjeezus · Post by **superjeezus** » Sun Jan 25, 2009 2:53 pm

I started seeing this problem for the first time today. Something else I noticed right before getting the '108' error message, is that DP's performance meter was pegging out when I wasn't even doing anything in the sequence--not playing, editing, nothing. It eventually settled down (who knows why?), but then it was constantly hovering around 30-40%. This on an 8-core Mac with tonz of RAM and fast HDs. The project was extremely small: one bassline VI, one audio track, a few MIDI tracks triggering a couple VI's running in Plogue Bidule with audio rewired back to aux tracks in DP.

Anyone else seeing high processor utilization on DP's meter when getting this error? OS-X's Activity Monitor shows barely any processor utilization on all cores when this is going on.

(Sheesh, and I went to all the trouble to set up external slave machines and a local install of Plogue Bidule to host VI's and get them out of DP so the sequencer could purr along at low CPU utilization....)

EDIT: Oh, and one more question--are you guys using any MOTU VI's when seeing this behavior? I never use Bassline, but was using it in my project today just to play with it a bit. Like I said, it was the only VI running within DP and it is the first time I have seen this error....

Mr_Clifford · Post by **Mr_Clifford** » Sun Jan 25, 2009 3:26 pm

superjeezus wrote: EDIT: Oh, and one more question--are you guys using any MOTU VI's when seeing this behavior? I never use Bassline, but was using it in my project today just to play with it a bit. Like I said, it was the only VI running within DP and it is the first time I have seen this error....

No. The project I'm having lots of trouble with has 1 EW Collossus (with about 2 instruments loaded), and 1 UVI (also with 2 instruments), in conjunction with Reason via Re-Wire. When Reason isn't running I don't seem to get the problems as much, but that could be that it just takes longer to max out the RAM.

superjeezus · Post by **superjeezus** » Sun Jan 25, 2009 3:55 pm

Mr_Clifford wrote: When Reason isn't running I don't seem to get the problems as much, but that could be that it just takes longer to max out the RAM.

I wonder if it has anything to do with Rewire? I am relatively new using Rewire, and I just started seeing the error.....

Mr_Clifford · Post by **Mr_Clifford** » Sun Jan 25, 2009 4:37 pm

superjeezus wrote: I wonder if it has anything to do with Rewire? I am relatively new using Rewire, and I just started seeing the error.....

I think Re-wire is definitely a factor. But people are reporting the problem when just using VI's in DP, and particularly when using 'pre-render' because it dumps samples and then reloads them next time you rec-enable the MIDI track.

For me it's more having Reason loaded up, then switching sequences in DP that's causing the problems, but that's only because I have very few VI's running, and I run them in a v-rack with no pre-rendering. I really hope the update that's supposedly about to be released fixes this problem.

scooter · Post by **scooter** » Mon Jun 08, 2009 2:22 pm

I'm noticing that the deeper I get into a chunk with sequences the more trouble I have with getting the out of memory error messages also.
Also, using a V-Rack within the chunk.
I wonder if MOTU could address this??

scooter

MOTUnation.com

Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108

Re: Help!@! Memory Error -108