OUCH!!! DP, quit stepping on my toes! (RESOLVED! ThnxMOTU)

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

Moderator: James Steele

Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
rkriviera
Posts: 5
Joined: Thu Feb 07, 2008 12:55 pm
Primary DAW OS: MacOS
Location: Los Angeles, CA

new suspicion

Post by rkriviera »

Backing up my work has only been intermittently successful--I repeatedly save iterations of whatever Im doing and sometimes many versions back will turn out to have been corrupted.

HOWEVER--someone mentioned sysex problems with Kontakt 3..Im still using 2 (and was using 1 when this issues started..) but I am beginning to suspect that the problem may lie in sysex info/ MIDI gibberish spewed out by my keyboard controller, a CME UF8. Apparently CMEs are known for being a bit flakey, despite their great action and cheap price..upon reflection, I realized that my problem started occurring around the same time as I got the UF8. Has anyone else here had any experience with this keyboard? Or possibly aware of any known problems/incompatibilities?

thanks all!
User avatar
Proklaim Recording
Posts: 135
Joined: Tue Jul 12, 2005 10:01 pm
Primary DAW OS: MacOS
Location: N.C.

Post by Proklaim Recording »

Shooshie wrote:Just keep excellent backups. No, the reason for the error was never determined. Nor did we determine whether it was an audio file or a plugin. Dave took my corrupted file and returned it to me in two forms: one sans audio, and the other sans plugins. Theoretically one should have opened and the other not. In fact, they both opened.

I'm wondering if it's a problem that Leopard has with Firewire drives. I've moved all my working files to an internal SATA. We'll see if it happens again. Just for our info, on what sort of drives has this happened to you?

Has it actually occurred on more than one drive? If so, were they different types? Could drive age be a factor? The drive on which mine resided at the time of the error was an older drive that is always in use. Could it be just... tired? Might Leopard require drives to be perky and fresh? :D Honestly, I am clueless. "Perky" has about as much meaning to me now as "optimized" or "defragmented" at least in context of this disk-error 103.

Shooshie

I had this error happen to me when I tried using several firewire drives. The drives were from the Mackie 24/96 recorder I had before switching to DP. They were 5400rpm drives, so they may have been to slow. I had a couple of 7200rpm drives I tried on the firewire also, sometimes the file would save just fine on those, but sometimes it would not. So I switched to internal drives and have never had a problem since. All this was on my old G4 mac, I have the Mac Pro now and have never tried firewire on it, I use two internal SATA mirrored drives now. Works great.

PR
Intel Mac Pro Dual Core 2.66 ][ 5 GB RAM ][ OSX 10.6.4 ][ DP 7.21 ][ MOTU 2408 mk11 ][ Mackie d8b ][ Focusrite Octopre ][ Aardvark Aardsync ll ][ HR824's ][ Liquid Mix 3.0 ][ Waves Gold and Ren Maxx bundles 6.0 ][ PSP bundles ][ Altiverb 6.3.1 ][ Ivory Grand Pianos 1.72 ][ Eastwest Goliath ][
newrigel

Re: OUCH!!! DP, quit stepping on my toes! (RESOLVED! ThnxMOT

Post by newrigel »

Shooshie wrote:While I still have not had a crash in DP 5.13/Leopard, today a file I've been working diligently on for a while suddenly would not read from disk. Got that alert box saying "Disk Error. File could not be read from disk," along with some numbers or codes or whatnot. No problem, I thought. I've been saving copies every time I save the file, so I'll just go back to my most recent copy. As it were, that happened to have been only a half-hour prior, and for most of that half-hour I'd only been listening and modifying very slight adjustments. So, I click on it, and... "Disk Error. File could not be read from disk..." etc. Now I was getting worried. How many would I have to go through before one worked? What if ALL of them are somehow corrupted? Well, it turns out that I had to go back 4 hours to find one that wasn't corrupted. Four hours of really, really good work. I mean... Grammy quality work. (hey, as long as the big fish got away, it might as well be a PRIZE-quality big fish!!! :D)

This makes me furious. What is causing these disk errors? What the heck is going on here?

Take my advice: save a copy every time you save. (in addition to) Save it without audio files so that you can make 30 or 40 copies without filling up your drive. Every time you add audio, you can save the audio, too.

I've got to call MOTU and find out what's up with this disk error stuff.

Shoosh
I hear ya bro!
I've had the MOTU save problem as you only a few times but my Liquid Mix has TRASHED 3 projects of mine that I can't even salvage so I know where your coming from!
User avatar
Proklaim Recording
Posts: 135
Joined: Tue Jul 12, 2005 10:01 pm
Primary DAW OS: MacOS
Location: N.C.

Post by Proklaim Recording »

I hear ya bro!
I've had the MOTU save problem as you only a few times but my Liquid Mix has TRASHED 3 projects of mine that I can't even salvage so I know where your coming from!

Oh man! How did Liquid Mix trash your project? Sounds like I need to know this one, cause I use Liquid Mix all the time. Please tell us more on this, did it corrupt your DP File? Did it do anything to the audio files? Thanks for your help.

PR
Intel Mac Pro Dual Core 2.66 ][ 5 GB RAM ][ OSX 10.6.4 ][ DP 7.21 ][ MOTU 2408 mk11 ][ Mackie d8b ][ Focusrite Octopre ][ Aardvark Aardsync ll ][ HR824's ][ Liquid Mix 3.0 ][ Waves Gold and Ren Maxx bundles 6.0 ][ PSP bundles ][ Altiverb 6.3.1 ][ Ivory Grand Pianos 1.72 ][ Eastwest Goliath ][
Post Reply