newmacguy
Oct 9 2006, 03:47 AM
Hi,
I recently updated my mac book pro, including a quicktime update - which I've discovered from the SnapZ Pro FAQ means that I needed to reset my SnapZ Pro prefs in order to capture movies again.
Unfortunately, I discovered this after I had already captured a couple of movies - live on-line demonstrations - and the movies appeared to have been saved (I heard "That's a Wrap"), but were not because quicktime was out of whack.
So, I'm wondering, since movies are saved to scratch files before being converted to .mov's, is it possible to recover my original movie data from the scratch files. And if so, where would I find the files?
Thanks, any help would be appreciated.
...Also, I'm very comfortable with unix, so if the solution involves dropping out to the command line, I'm quite happy to do that (running OSX 10.4.7).
Kepi
Oct 9 2006, 10:23 PM
QUOTE(newmacguy @ Oct 9 2006, 02:47 AM)

So, I'm wondering, since movies are saved to scratch files before being converted to .mov's, is it possible to recover my original movie data from the scratch files.
Short answer: unfortunately, no

Long answer: can't remember the entire gist of the situation, but I can assure you it's not possible.
newmacguy
Oct 9 2006, 10:36 PM
QUOTE(Kepi @ Oct 9 2006, 11:23 PM)

Short answer: unfortunately, no

Long answer: can't remember the entire gist of the situation, but I can assure you it's not possible.
Well, that's a real bummer. Maybe SnapZ should detect when this situation happens and issue a warning (?), because it seems to happen any time you install something that affects quicktime (i just installed a wmv plugin today, and SnapZ stopped working again). Seems like a pretty serious flaw that should be easy to fix, or at least there could be a way to help prevent users from losing data.
Thanks for the reply and the info though.
David Dunham
Oct 16 2006, 04:46 PM
Hello-
Unfortunately, Kepi is correct. Those files are not recoverable.
This should be a very rare occurance, but I do seem to be getting it more frequently. It is in our bug database, and if there is something we can do on our end to catch it and prevent it from happening, we will.