MOTUnation.com

Looks like you jinxed it after all, Shoosh.
Bummer.

Your fantastic run with DP of late gave me much hope.
Now, I'm preparing for GuineaPigville.

I had an interesting error a while back, (I think it said disk error) where I had started recording, then I think I hit undo before I stopped recording (because it was a bad take) (oops) and then hit save...

Shoosh,
Send me your DP session file and I'll take a look at it. Archive it to a .zip file and email it to
magicd@motu.com

Dave

mighty magic Dave to the rescue!

Shooshie, don't use Firefox to send or receive your file from Dave,
use Safari.

I had trouble opening the file Dave sent back to me with Firefox.

Thanks Dave !
Dan

I archived it as a zip file and sent it in email using Mail.

Thanks MagicDave!


Shooshie

That's terrific, Shoosh, especially given your recent TS experience.

Way to go, Magic One.

After a whole day of work done and lost, I got to this final conclusion:
"System Exclusive messages" from Kontakt 3, was the problem in corrupting the DP5 file. Not able to open the file because of a "reading 103 error".

Good luck.

Shooshie wrote:Posted: 05 Feb 2008 05:36 am Post subject: I'm gonna jinx it, but I've gotta say it:
Digital Performer 5.13 has not crashed on me since I installed Leopard. Someone correct me if I'm wrong. When was the "quit on rewind" bug? That was DP 5.13, wasn't it? Was that happening in 10.4.11? Or Leopard? Whatever. That bug lasted about a week or two, if I recall. I don't know what fixed it. But it seems as if I've been clean since Leopard.

In any case, I've been working away on a lot of things, including audio, MIDI, recording, editing, bouncing, yadda, yadda... and no crashes. This feels like the old days, and I'm loving this.

Ok, I guess I'd better go knock on wood now, or throw salt over my shoulder, or catch a Leprechaun and steal his lucky charms, because I've said it now, and... aww... heck. This is DP. It's not going to crash. No need to be superstitious. This is great!

Shooshie
_________________

ha ha ha, whose got the exploding head now

go patriots 2008-09

dave pine wrote:

Shooshie wrote:Posted: 05 Feb 2008 05:36 am Post subject: I'm gonna jinx it, but I've gotta say it:
Digital Performer 5.13 has not crashed on me since I installed Leopard. Someone correct me if I'm wrong. When was the "quit on rewind" bug? That was DP 5.13, wasn't it? Was that happening in 10.4.11? Or Leopard? Whatever. That bug lasted about a week or two, if I recall. I don't know what fixed it. But it seems as if I've been clean since Leopard.

In any case, I've been working away on a lot of things, including audio, MIDI, recording, editing, bouncing, yadda, yadda... and no crashes. This feels like the old days, and I'm loving this.

Ok, I guess I'd better go knock on wood now, or throw salt over my shoulder, or catch a Leprechaun and steal his lucky charms, because I've said it now, and... aww... heck. This is DP. It's not going to crash. No need to be superstitious. This is great!

Shooshie
_________________

ha ha ha, whose got the exploding head now

go patriots 2008-09

Aha... but it STILL HAS NOT CRASHED!!! No, this was due to something else, and I think I've found it. I installed Wiretap Studio on my hard drive about the time that this disk error happened. I have just discovered that it installed three plugins without my knowledge: camelphat, camelcrusher, camelspace. I think it was the installation of this, which probably was something I did while DP was actually open (duh!) which caused this disk error.

Shooshie

GREAT NEWS!!

Magic Dave helped me get this all worked out. I'm back into my old file again, and I haven't lost any work! I think it may have been related to that install which unknown to me, added camelphat, camelcrusher, camelspace to my AU plugins, while DP was open. Stupid move on my part. But it may well have been the problem. I don't have proof, and probably never will, but it's always a good idea to close your apps before installing ANYTHING.

Shooshie

What I did was open Shooshies file on my computer. He sent me just the DP session file with no audio. The file opened with no problems for me. I got error messages about missing audio files and plugs that were referenced by the file that I don't have installed.

I deleted the references to the audio files and cleared the missing plug-ins and sent the file back to Shooshie. Shooshie tells me the file opened for him at that point.

That suggests to me that the DP session file was not corrupted. The symptoms suggest that the problem was either the referenced audio or something to do with one of the plugs (which included sample based instruments) that Shooshie uses, but I don't have on my computer. I don't know yet which it is, but Shooshie and I are still working together to further diagnose.

Although I don't like to speculate on tech problems in public until we nail the specific cause, I also know that people do want to know if there is some sort of problem within DP or what might be causing these problems. In this case I strongly suspect that the problem is actually an audio file or possibly a sampled instrument that was referenced by the DP file.
With a little more testing on Shooshies end, we may be able to narrow it down and report back.

Happy to get the file back for ya Shoosh!

Dave

Thanks Dave! Love the report. Very refreshing,

if i had to choose between the pats winning or shoosh getting his great work back, i guess i'd have to go with shoosh.

happy for ya, that kind of thing is the worst, glad it worked out.

I have been having this EXACT problem for the last year, and have yet to rectify the issue--incidentally im NOT using Leopard--though i AM using NI stuff extensively--particularly Kontakt 2, which is pretty much 90% of my MIDI stuff.

I have been using DP for 4 years now with no incident, but starting last spring, I started having a recurring issue with files being irretrievably corrupted. At the time I was using DP 5.01 on a Mac G4 powerbook. I was (and had been since I had been using DP!) using Waves plug ins.

Inexplicably I started to get a "103 error" message when I tried to open files I was working on. This means the file was corrupted and could not be opened. I tried a work around a number of people on the user boards suggested-- opening a new file, then trying to load the corrupted sequence, but this just resulted in the same error message. This issue is intermittent, although if the computer crashes during use, it is often corrupted afterwards...but not always! Also, sometimes files that I ahd previously had no problem opening will suddenly become corrupted later, even if I hadn't worked on them recently.

I have since changed to a Mac Pro with intel dual core processor. I called tech support this fall and the technician insisted that my problem was an incompatibility with my Waves plug ins (despite the fact that I had exhaustively updated them and DP with every available patch for intel compatibility etc). I completely purged my system of any trace of Waves, which seemed to work for a while--and I was horrified to find that a few weeks later, the problem was recurring!!!

I have personally not found it to be an audio related issue--in fact the only was I could resurrect some of the damaged sequences was to create a new file then import the audio and place it in the sequences via time stamp. Odd that I've ben scanning user groups for a quit a while trying to get to the bottom of this and suddenly find it cropping up.

I DONT have Wiretap though--to the best of my knowledge? I'll check for those pulg ins thoigh...thanks!

I don't know about any Wiretap connection with Camel Audio but I'd just like to say that I have CamelPhat, CamelSpace, CamelCrusher, and Cameleon 5000 installed on my Mac Pro and my G4 and I've never had a problem with them. In fact, they're all over everything I do.

Just posting this lest people get the wrong idea about these truly excellent Camel Audio products...

Kind regards.