Jim Giberti
Forum Replies Created
-
[Chris Harlan] “I think you’re fighting your own demons here, Bill, and you just stuck my face on ’em.”
You mean you’re actually trapped on that ornament Chris?
Damn you Bill, release him now! -
[Jeremy Garchow] “We resemble that comment, except it’s 80 degrees here today, so actually, it’s shorts.
And my dog is sleeping on the floor next to me.”
You call THAT a boutique Jeremy?
I’m in pajama pants with 8 Labs in the studio, and I haven’t shaved for three days, and there’s Bailey’s in my coffee, and…
-
I fully expect a 30″ iMac Pro with 64GB RAM capacity and 3 TB ports.
I don’t know why I fully expect it, but I do.
-
[Kevin Patrick] “One continuous over writing backup? So if my project gets corrupted and I don’t realize it in the 15 minute widow, I now have a duplicate of my corrupted project? I would like to understand the logic behind this. “
Don’t try and understand something that’s not there (logic) but yes, that was the “solution” in 1.0.3 to the problem they created in 1.0.
There’s one backup every 15 minutes that overwrites the previous. But remember, even that backup is meaningless unless you actually have a project corruption that won’t allow you to open the project – which is rarely the case I’m sure. Most corruption happens and grows while the project is available, so by the time it was unopenable, yes, the backup would be corrupt as well, in most circumstances.
It’s simply stupid.
Which I suppose fits with Apple’s new obsession with simplicity.
-
[Jason Porthouse] “prior to 10.0.4, X took me right back to the bad old days of regular crashing and potential data loss.”
We’ve been too swamped to update systems and the discussion as to whether Magic Bullet suffered in the update has also kept from going 1.0.4 but is sounds like it’s a real stability improvement.
I still think that carefully managing project size is the single contributing factor to lack of corruption.
But even Apple admitted to me that imported graphics (as of 1.0.3) were a bit of a wild card. -
[Kevin Patrick] “Why? Why go to the trouble of having a backup feature, but only one backup? As you say, what if you wind up with a backup of your corrupted project?”
Why, would be the $64K question for Apple. How can this possibly be seen as the “next generation” of backup?
It’s like an addiction to new and simplified that defies logic as part of it’s march towards newer and simpler.Incremental save files have obvious and enormous value in dire times – it’s proven – it works.
Replacing it with a 15 minute destructive autosave that ISN’T available to the user (everything must be hidden to be simple) can’t possibly be seen as an improvement if you understand what a backup is for.
We had two projects fail and many $Ks of hours that had to be redone because there was no incremental backup.
It won’t happen again because we duplicate regularly and we’re super aware of corruption and it’s potential.If you’ve written a perfect program that removes this need then you’re truly visionary. But seeing as though the new FCP has corruption issues like no version in a decade, a simple autosave function looks pretty smart.
-
[Jason Porthouse] “I’d simply copy the backup file into a backups folder – mirroring the structure of the FCP Projects folder. I’d do this with the event too, if substantial changes had been made. I was able easily to pull out the last good backup of both files, rename as ‘CurrentVersion…’ and replace the corrupted files. X opened up fine, no issues, and we were good to go.
“In other words you had to figure out a back door way to do what Apple should have as part of it’s essential code.
The other thing, of course, is regular (or in your case daily) duplication of the project saved to another drive.
It all works, but in the 21st century, to be suddenly dealing with things that were resolved a loooong time ago – by the same company that seems to have now forgotten about proper backups – it’s kinda kooky.
-
It is crazy not to have it, and the 15 minute, hidden autosave is unfathomably misconceived.
TimeMachine is the only reliable autosave you have.
Why?
-
[Dave Gage] “What is the basic setup made of to achieve this? Are those gap clips in there that create the “tracks”? I’ve been with FCPX since v10.00, but somehow I’m not getting this.
“Hey Dave, I can email you a project folder which is a template I made of it.
It’s a 6 Audio Track, 1 Video Track, 1 minute long empty project that you can quickly expand the time and tracks as you want.Yes those are inserted 1 frame gap clips at the top and a 1 frame audio clip at 60 seconds that forces your edited audio clips into the empty “lane” below the primary and above the audio Secondaries unless you want them to go into those dedicated “tracks”.
Here’s the 3 steps to have everything line up and start at Zero when you’re done your edit:
-When done editing, select all Secondary Gaps at first frames and Delete.
-Reselect those Secondaries and nudge “.” one frame to the right.
-Select the Primary Place Holder at the first frame and Delete.I’m sure you know this, but these are a few things to make sure you defeat magnetism when you want to:
-Use Trim Tool in Secondaries to trim adjacent clips without affecting timeline.
-Use P Tool in Secondaries to adjust clips individually without moving other clips.
-Use P Tool to create L and J cuts in Primary.
-Shift Delete to Lift clip while keeping other clips in place in either Primary or Secondaries.Hope this helps.
Jim
-
I believe Noah is Apple feedback, meaning he’s THE person that actually sits in real time and reads them.