David Eaks
Forum Replies Created
-
The database has become self-aware and is evolving on its own
-
Well, I didn’t even know about your blog and had even missed that you posted a link until Bill mentioned it. I started reading it while on break between shoots. Looks like I’ll be a regular reader now.
Put a link in your sig.
-
There’s no option for that, the files must go into the events transcoded media folder. You can move the event and project to the external. I think that’s your only option for getting the transcode files to go to the external.
-
In the project library, select a project then choose File> delete project render files. It will give you a choice to delete ALL Render files or delete unused render files. If you choose to delete unused render files, it will clear up some space and leave the renders that are used in the sequence so you won’t have to re-render.
More important is the statement “no, I’m not working off a hard drive, I’ve lost material that way”. Of course you mean “not working from an external Hard drive, and of course it is also a hard drive which is inside your computer that you are working from. Regardless of using an internal or external hard drive, it’s still a hard drive. It will fail and you will lose material yet again. My point is that you need to get a backup system in place. You must have at LEAST two copies of the original material, on separate drives. I’d recommend another drive dedicated to Time Machine as well. Working from an external drive is not only standard practice, but is also recommended by many as opposed to working from the system drive that your OS and Apps are installed on. It’s a lot to ask of a crappy spinning disk hard drive… Run my OS, run my NLE, play my media, create thumbnails and wave forms, play my media, render my effects etc. etc. etc. and do it all at once really fast! An external RAID array is a good thing.
-
If UpToLehman2 is in place exactly where you want it and you don’t mind overwriting the beginning piece of video on the LehmantocoreIV clip, “overwrite to primary” should do that just fine. All the audio should stay right in place and the beginning of LehmantoCoreIV should automatically get a J-cut.
Select UpToLehman2 and press-
Command-Option-Down
-
Isn’t it a general “best practice” to not be working in your NLE while running backups of your projects and media? I can see how FCPX wouldn’t like seeing two identical drives with identical files and structure. So, just don’t open FCPX while a backup drive is mounted. I also tend to keep every project and event but the one I’m working on hidden from FCPX using Event Manager X. If all your projects and events are hidden from FCPX on both your media drive and backup drive, I’m not sure that FCPX would even care whether or not they are both mounted at the same time.
I only mount backup drives when it’s time to do a backup (including time machine). I’ll make sure the trash is empty, reboot, run backup, then eject the drive when it’s done.
-
So Create Disc has the same menu templates and you were able to burn the existing files?
I’ll submit the same request too.
-
Tim, your actions were just as respectable as they were necessary. I can’t help but feel some level of relief, there was an absurd amount of frustrating-to-read and nonconstructive posts. The pastures are better for their annihilation.
I quite enjoy reading the vast majority of banter in a variety of the forums here, not to mention all the selfless, trouble shooting assistance, tips, tools and advice freely given by all the regulars here. Since discovering CreativeCOW a few years ago, I’ve always felt it to be of some higher caliber (for lack of a better description) in its level of professionalism and collaborative atmosphere. The only way I figure that “feeling” could come about in relation to a Disscussion Forum, is through the quality of the discussions themselves. Which is a direct result of every post by each member of the community. Hey, nothing is perfect, people will get into it, but it’s feelin pretty good around here right now.
Thank you for your efforts.
Once I realized what this thread was about, this scene immediately came to mind-
Tim “The White”
https://youtu.be/SFogXTIv3MY -
You could use a program like DVD Studio Pro or Toast. Just bring the two A/V files for the DVD from the shared items folder into your burning app of choice. It won’t have the same menu template, but that surely isn’t the highlight of these DVDs.
*edit
Sorry, I forgot that you said “with the same menus and sub menus” by the time I started typing.
Compressor has the same templates. I have had many experiences with submitting a compressor batch with a job action set to burn a disc. When the destination folder has identical files to the ones that will be created (similar goal as you, re-burn a previously encoded and burned disc). Compressor will “see” that the files already exist and in batch monitor instead of showing “encoding frame xxxxxxxxx of xxxxxxxxx” it says “copying destination file”. That only takes a minute or two then the burn starts. I haven’t been able to reproduce it reliably, I just a hope that it does the copy thing instead of encoding it all again. Maybe it would work for you.
-
Installing the new FCPX 10.1 on an old Mountain Lion system then updating to Mavericks seems like it would have increased potential to experience odd issues in the long run. I would say its “best” to do a clean install of Mavericks, then a clean install of FCPX 10.1.
And I would say that because it’s exactly what I will do when it’s released, but I’m a clean-install-aholic and rarely “update” major changes to the OS or mainly used Apps (I updated to 10.0.9). Instead of updating, a perfectly working System drive goes on the shelf and a newly formatted drive goes in. With good organization and saving of install files and disc images, installing everything is a snap (for example if you still install stuff like FCS 3 from the Discs, you’ve just got to make disc images and experience the time savings). Of course none of this happens on a production machine until critical workflow elements have been tested with the new software on a secondary Mac.
It’s been an evolving process over the last few years, which designed itself out of necessity, reading COW posts, cautiousness and a quest for stability. Seems to cut down on “oddities”, that way you only have to deal with actual bugs. Though I’ve been messing with Mavericks since the betas, it hasn’t made it to my main edit suite yet.
On the other hand, the new Mac Pro will ship with Mavericks, so there’s really no question. Only choice is to install FCPX 10.1 on Mavericks. ; )