MOTUnation.com

I think I may be going insane. Either that or I am just realizing that I already am insane.


So...I was working on a huge project from 8 AM to 4 PM. I took a break at 4 for a while and then went back to DP and opened the project.

The project file had reverted back to a version from 10:30 AM.

I know this from getting Info on the project name in Finder.


What the heck?

I had saved the file probably 50 times from 10:30 to 4. I had 10 backup Save A Copy files from 10:30 to 4. The last backup was 20 minutes before 4PM, so luckily I just lost the last few passes of a guitar track. But, obviously, this could have been a disaster in the works given different circumstance. The guitar tracks were still in the Audio folder, so I was able to drag them into the latest backup file and continue.


This is the second time this has happened to me. I go to open a DP project, and DP opens the project and it is apparent that the last hours of saving were not actually happening. How is this possible?

Has anyone ever experienced this?

Thanks for reinforcing the fact that I am indeed crazy.

Gee!!! cbergm7210 that's awful ... Hope you didn't loose too much of your work. Does this happened to you on DP6?
I'm asking 'cause if it is a DP6 bug I think is a serious bug and everybody here should be warned. As far as I can tell it never happened to me, but I'm still on DP 4.61. (and I did order an upgrade to DP6...that I'm not pretty sure to use it yet....whenever it arrives).

Cheers.

open the file and save as a copy again, this time, look at the path it's saving to, it could be other than your project file.

Something similar has happened to me a few times.

I'm constantly saving as part of my work flow, but there have been instances (probably too big a hurry in my case) where I probably selected "Save As..." as opposed to "Save A Copy As...".

If you do "Save As" then the project that is still on the screen is actually different than the one you started with. In other words, If I opened "Today's Music" from my ATA drive, worked on it a bit and then did a "Save As" to a Firewire drive, the project on the screen now will subsequently "Save" all changes to the Firewire drive and not the original ATA.

Clear as mud?

(Still working on my morning coffee, but I think I got this all right!)

Buzzy

Yep. looks like I'm not crazy after all.

Yesterday I had sworn that the Save As thing was the culprit, but for the life of me I could not find the file that I might have inadvertently switched over to because of the Save As instead of the Save A Copy As. But you guys gave me another idea of how to search, so I looked for a Backup file that was created at 10:30, and sure enough, Backup #5 was the one. There was the file I was working on since 10:30.

Thanks for the nudge, fellows. I was hoping this was operator error, and indeed it was.

Cheers,

Chris

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

MIDI Life Crisis wrote:Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Time Machine is your friend.

Absolutely!!!
At the end of the day I back up to a secondary audio drive then I use Time Machine on two separate drives. One TM drive for my system, and the other TM drive for my main audio and secondary audio drive.

Happens to me sometimes too... (5.13, dual 1.4 G4 ...ya ya I know... soon...)

Actually there's a thread on the DUC about the same behaviour in PT... It seems to happen only with APPLE-S Saves rather than choosing save from the File Menu. It's POSSIBLE that OS X doesn't record some keystrokes and they never get to the software, so you've hit save, but the computer hasn't ACTUALLY saved...

This has happened to me several times in 5.1x. I'd worked on a client's file for 3 hours, saving regularly (not Save As, or Save A Copy As, just Save, definitely to the same path. It's why I started using AutoSave - http://www.versiontracker.com/dyn/moreinfo/macosx/22707 - which saves multiple backup versions at regular intervals. (The only problem I've found with AutoSave is that if you have a complicated session with long save times and the save happens while you're playing the file, you have no control over stopping playback until the save has completed.)

At the time I investigated all the possibilities mentioned above and never found a reason. Fortunately since those few times it has not recurred.

So it looks to me that it is kind of DP5.x issue.
Can anobody address same behavior on DP6?.
Thanks.

iPerformer wrote:So it looks to me that it is kind of DP5.x issue.
Can anobody address same behavior on DP6?.
Thanks.

What issue? The original poster admitted that the "problem" he was having was his own fault - using Save As instead of Save a Copy As.

1nput0utput wrote:

iPerformer wrote:So it looks to me that it is kind of DP5.x issue.
Can anobody address same behavior on DP6?.
Thanks.

What issue? The original poster admitted that the "problem" he was having was his own fault - using Save As instead of Save a Copy As.

Not true in my case.

1nput0utput wrote:

iPerformer wrote:So it looks to me that it is kind of DP5.x issue.
Can anobody address same behavior on DP6?.
Thanks.

What issue? The original poster admitted that the "problem" he was having was his own fault - using Save As instead of Save a Copy As.

Sorry, I don't know if I understand what you said. Are you saying that Save As shouldn't work as supposed and Save a Copy As should?. I think that even if you do a Save As or Save a Copy As both should do the job , in different ways, but basically save your work. So I think that there is an issue.