Help-Can't open some files... getting error id=108

[MIDI Life Crisis]

I remember a similar file crisis (but on PT) where the tech opened them as raw in Audacity (freeware) then exported them back in PT. Might work??? Good luck.

Oh yeah... Audacity! Cool suggestion and a great little freeware program.

Thanks guys. If he can't get it working now... well, new Mac time!

[kassonica]

Error 108 is not enough memory.

Have U any other apps running when you open these docs.

Try opening them from DP or use load.

[pencilina]

If he can't get it working now... well, new Mac time!

Or maybe a dp downgrade. These kind of annoying problems are usually because something new was introduced or changed on a stable system. Did you clean out your non-motu plugins and try and restart/reopen?

[MIDI Life Crisis]

Error 108 is not enough memory.

Have U any other apps running when you open these docs.

Try opening them from DP or use load.

A corrupted file might contain an endless loop or other invalid instruction resulting in a -108 error. No? And it could also be bad RAM that finally died. But yes, it is defined as not enough memory in the available 'heap.'

Related to kassonica's comment, you might check the Activity Monitor to see what else could be hogging the memory. Spotlight Indexing is notorious for such problems. Even in Leopard. In fact, I am currently experiencing this on my machine, where mds is consuming over 100% of my CPU resources according to Activity Monitor- and spotlight isn't indexing any longer! But that's MY problem and hopefully it will settle down.

Programs that run will use both RAM and virtual memory, consuming both RAM and HD space so it can be a little tricky to track down.

[kassonica]

Yep

Its sounding very hardware based to me, HD and/or ram failure maybe on the cards. I'd be doing a full BU ASAP.

I could be wrong I HOPE I am.

Because your computer is quite old and its an laptop it rings alarm bells.

Check your ram in system profiler and see if it's seeing it all.

Also i'd run tech pro or some other diagnostic app just in case.

One more thing, can you open these from another computer?

[RenaissanceMan]

thanks again everyone. this is fantastic feedback. glad i stopped by here!

some more feedback and questions:

okay... if i am able to load the sound files into another program and resave them, will dp still recognize and place all of the splices/cuts/pastes/fades, etc. if it can reload them? if not, i'm stuck redo'ing all the audio for this tune, i'm afraid.

if my computer is dying, (and i pray that it is not), wouldn't i also have problems loading other files? this problem right now is not intermittent; i am only having probs with 1 particular tune.

fwiw, my machine is a 1.0 ghz g4... i have the last evolution of the titanium before the aluminums came out. interestingly enough, i did have to replace my hard drive a couple of months ago due to failure. fortunately, i keep backups!

so, 108= out of memory????? in that case, it is POSSIBLE that if i upgrade my ram the problem will go away? i'm not running any other apps when i run DP.

also... i don't have any other plugins other than the DP included ones. the ONLY other plugins available are the ones that appear as if they were installed by garageband. DP appears to include them in its list by default. could THESE be the culprit?

btw, i even tried deleting the audio, analysis, and fades folders in the project... file still would not load. it's as if the corruption is in the dp song file, itself, and not the audio, but that's just a wild guess.

i guess you could also say that i've done a reinstall... i was running version 5.12 this morning when i started having the problem, and then downloaded and installed 5.13 in hopes that it would solve my problem.

one of my music colleagues lives in my neighborhood and is also running DP. i'm going to try to load on his computer next and see what happens. i'll report back.

i really appreciate all the help so far-

[MIDI Life Crisis]

... if i am able to load the sound files into another program and resave them, will dp still recognize and place all of the splices/cuts/pastes/fades, etc. if it can reload them?

... i am only having probs with 1 particular tune.

1) If you save the files with the exact same name and the exact same format, that would be your only chance that DP will think they are the same files and maybe compute your fades.

2) I was under the impression the problem was more widespread, based on your initial post:

Some of my tunes will not load anymore. When I try to load them, the screen goes through its window draws for the project, pauses for a moment, and then a window pops up informing me:

Cannot load file "songname". Error ID=108

I frequently load these songs to work on them, and only a couple of them are giving me this problem. As I mentioned earlier, it appears to have started out of the blue... Does anyone know how I can fix this? Thanks in advance-

Had I realized it was only one file (project) I would have done the troubleshooting quite a bit differently and STARTED with rebuilding the audio files. I think that may be your only hope at this point. You might still be able to save any MIDI data and might be able to reconstruct the entire file once you rebuild the audio (assuming that is even possible).

I'm outta here!

[RenaissanceMan]

... if i am able to load the sound files into another program and resave them, will dp still recognize and place all of the splices/cuts/pastes/fades, etc. if it can reload them?

... i am only having probs with 1 particular tune.

[snip}

2) I was under the impression the problem was more widespread, based on your initial post:

Had I realized it was only one file (project) I would have done the troubleshooting quite a bit differently and STARTED with rebuilding the audio files. I think that may be your only hope at this point. You might still be able to save any MIDI data and might be able to reconstruct the entire file once you rebuild the audio (assuming that is even possible).

sorry for the confusion, MIDI life crisis! in my flustered state i just have been focusing on one of the problem tunes while testing all of the post suggestions. there are only 2 of them right now that are giving me this problem... the rest from my latest album project are fine. it is these same tunes that give the error codes and crash; it's only repeatable for these.

as i mentioned before, there were a handful of instances in which the "error id=108" problem was resolved by trashing prefs or opening from a "MIDI only" state in DP. throughout this latest issue, i've been opening and testing my other current album project tunes to see if i have the same issue, but so far so good on the latest ones.

[MIDI Life Crisis]

sorry for the confusion

No apology necessary, but thanks. That happens to me in sites where I am a novice (FinalCut; Apple Discussions - where the geeks rule!) I didn't mean that as an insult or chastising, just to alert you to the fact that I may have sent you out for a few wild geese....

[sndhse]

RenaissanceMan, have you found a solution yet? How big is the file. If you would like to FTP me the file (just one to start with. Let's see if it works) I will try to open it here at the studio. Send me a PM and we can go from there.
I hope that will help put your mind at ease.
It's happened to me before.
John

[martian]

i had a similiar prob last week - crashing on open... no error just pure PIA!!

put the audio files in the trash - ( don't empty it. )

can u open the seq now? It notify that audio files are missing... just click ok

once file is fully open - then drag audio files folder back into the correct place - probably have to click replace as DP would have made a new (empty) folder

If this works - it's a prob with an audio file - you could

(a) try compacting project - you may lose some info doing this like soundbite gain,..

(b) save as OMF and choose WAV or AIFF - Dp will then remake the files... batch them back to SDII using "sound grinder" - that will be a lot less effort than QTpro

hope this helps

[RenaissanceMan]

i had a similiar prob last week - crashing on open... no error just pure PIA!!

put the audio files in the trash - ( don't empty it. )

can u open the seq now? It notify that audio files are missing... just click ok

once file is fully open - then drag audio files folder back into the correct place - probably have to click replace as DP would have made a new (empty) folder

{snip}

hi martian-

thanks for the tip. i tried this, but the file still crashes before it even notifies me it can't find the audio.

[RenaissanceMan]

okay!!! i got the file loaded. hoorah!!! it's not gone!

However, I need you experts to explain this one to me... Fortunately, I had a couple of older versions of DP 5 on my hard drive. I tried running DP version 5.1 and attempted to load the troubled files. viola! they loaded without trouble. i then resaved and tried to load the file again from 5.13. same problem all over again. it appears i can only load these particular songs from 5.1.

is this a bug, or could this truly be a memory issue??? is it possible that 5.12 and 5.13 are taking up more memory than 5.1 and causing this problem for my more resource intensive files?

is there any reason i shouldn't run my latest projects in 5.1?

man, i'm breathing a sigh of relief, but i'm still baffled why what is going on.

[RenaissanceMan]

anyone have any idea why i can only open these files using version 5.1?

[martian]

nope! maybe cos DP can be a bit flakey as you can see!

I've been struggling with crash on save on and off for a year now....

almost wished I could just use 4.61 that was rock solid for me.... just soundbite gain missing...