Matt Holmes
Forum Replies Created
-
This explains the Incremental Backup options:
https://help.bombich.com/kb/explore/backup-options
Matt
-
Someone correct me if I’m wrong in any of this:
CCC uses a function called RSync to back up data. In other words, it only backs up what has changed, but you have to tell it to work that way. Just to be safe, it may be in your best interest to simply buy a new hard drive for CCC, just in case anything goes wrong. Set your TM backup in a safe place for the time being. Go ahead and download CCC and select your source and target (the new one) disks. If it tells you to format your target disk first you can do this in Disk Utility (it’s included with the OS). Format as HFS+ as CCC tells you. So, with your disks selected, you’ll see a “Cloning Options” section on the right side of the window. Select “Incremental Backup of selected items.” Below that you can have some options. I guess the safest thing would be to uncheck the “delete items that don’t exist on the source” box, though it will use more space. Anyway, now when you run the task it will only copy over things that have changed. Mind you this will still take a little while as CCC has to read everything to see what has changed, but 350 GB should be doable overnight.
CCC also allows you to schedule tasks, so you don’t have to manually initiate the backup everyday and redo all your settings. Just click the “Save Task” button at the bottom and follow the prompts. Hope this helps.
Matt
-
How ’bout this: took me two reboots after the update (not a normal thing), one with the update installation and the second a manual reboot. Final Cut refused to open after multiple attempts in between the two.
-
Sorry for the scare everyone. Should have tried the second reboot first, then combined into one post. Usually don’t have to do that though. Happy 10.6.7.
-
OK, the normal system update restart wasn’t enough. Had to shut down and reboot. Seems to be working fine now.
-
Just updated, final cut won’t open now. Going to shut down and reboot. I’ll let you know if I find anything
-
Any more findings on this? We’re having a similar issue: very inconsistent results. Some clips come in fine, others seem to have an arbitrarily set out point. This happens with batches, ie importing an entire card or folder (using ShotPut to transfer to XSAN). It’s scary, thinking you’ve lost a take, and then finding that it’s all there in the original H.264. A re-import fixes the problem, but that requires double checking all of your import files. Anyway, thought I’d check. Thanks. Maybe we’ll try reinstalling the plugin.
-
Just checking, but did you up the bit depth in your AE project to at least 16-bit?
-
Transcode all original H.264 to Proxy using Compressor. Import the Proxy files into FCP, log, and edit. With picture lock, point final sequence or video bins back to H.264 (will have to add reel names manually). Then Media Manage (trimming the footage), and recompressing as ProRess 422. Now we can add graphics, do color correction, and any finishing work.
Again, I think Log and Transfer is probably simpler, but the above does work. The key was adding the reel names.
Thanks again.
-
Shane,
Thanks for the tutorial. Haven’t used Log and Transfer much, so that was helpful and is definitely an option for us.
We were trying something similar, just using Media Manager instead of Log and Transfer, but to do that we would have to point our sequence back to the H.264 first so that on the second Manage it could use that to recompress to full ProRes 422. So yes, it would only reference the H.264. Any other finishing would be done in the ProRes 422. More complicated, but does limit the amount of material transcoded to full quality. Hope that makes sense.
Matt