David Eaks
Forum Replies Created
-
David Eaks
January 12, 2016 at 9:04 pm in reply to: Delete Project Render Files & Event Render Files, DifferencesDelete generated project files will remove the selected files for only that project.
Delete generated event files will remove the selected files for all projects within that event.
Delete generated library files will remove the selected files for all projects within all events within that library.
In all three of the above methods you can choose to delete render, optimized and/or proxy files. None of these choices will delete your actual media. Yes, if you need to come back to the project, all you have to do is render again. No, your effects will not be removed from the clips in your timeline.
On the other hand, I haven’t rendered much of anything in quite a long time. I keep background render turned off and just export when the edit is complete. Unless there is something complex and it won’t playback smooth, and you actually need to watch it to see that it turned out as expected. Like, there is no need to render that same old lower third you use in every project for a particular client, when you already know exactly what it will look like. In other words, rendering is useful for playback in the timeline while editing. Rendering everything immediately before export is just a waste of time.
For reclaiming hard drive space, I use Final Cut Library Manager-
https://www.arcticwhiteness.com/finalcutlibrarymanager/ -
If you hold the Z key while making the selection then let go after, the tool will automatically switch back to what it was before.
Not a big difference but one less click, is one less click.
-
Andy Neil- “I try not to consider AE and Motion to be in competition”
What I want from Motion is for it to be generally considered as a direct competitor to AE.
But that’s not very specific. Mostly I just want 3D, objects/text, extrusion, a “round” particle etc. NOT meaning stereoscopic 3D, which I couldn’t be less interested in.
-
I put one of these in my 2008 Mac Pro a while ago. I don’t use the USB 3 ports very often but when I have it worked well. I use eSATA almost daily. It’s nice to have both interfaces and only take up one slot.
-
Oh, I forgot anout the new compressor, I’m still stuck on mountain lion and the previous FCPX and compressor versions (waiting for Matrox to release Mavericks drivers) except my testing partition on a secondary Mac. So I’m not sure about reset background processing in the latest Compressor. But I’m quite happy with the performance of 10.1 on Mavericks!
Glad compressor repair did the trick.
I definitely recommend a clean install of Mavericks and Apps. To make it easier in the future, start collecting all your application installers, whether downloaded or on disc (not including Mac App Store apps of course). Save the install files and disc images to a “all installers” folder on an external and save license keys in a text document. Once everything you need is saved and organized, clean installs are a breeze! Then clean install at every full OS or major NLE version release, it only takes a couple hours to go from formatted drive to fully functional edit suite, at least that’s the case with my setup
-
Try going to Compressor> Reset background processing. Choose “cancel and reset”.
If that doesn’t work, run Compressor Repair
I hope that helps.
-
Just looked, “Conform Speed” is now called “Automatic Speed”. Lame.
To get every frame of your 60p clips to playback, resulting in slow-mo, place the clip in a “standard frame rate” timeline. 23.98p or 29.97p. Then select the clip in the timeline and choose automatic speed from the retime menu. Your clip will double in length on a 29.97 timeline (50% speed slowmo) because your clip contains 60 frames per second and FCPX is playing frames 1-30 in the first second and frames 31-60 in the next second. In other words it’s is playing all of the 60fps, at 30fps. No skipping or recreating any frames.
Just remember that the timeline will automatically match the first clip you add to it, so first add any random clip that has the frame rate you want to edit/deliver in to lock in the timeline settings, then add your 60p clips (then delete that first clip if needed). From here it will default to play at normal speed, dropping every other frame. Once the clips speed has been conformed (er, uh, automaticed?) it will make use of the “extra” frames (1080 60p is not a standard format).
Optical flow can do a pretty good job slowing even further from here.
-
In the future, it might be a good idea to keyword/favorite/reject portions of video within the Event Browser first. Then create the multicam clip with only the clips you actually want.
It may or may not be faster to organize this way, but the resulting organization is more useful to you and you don’t risk the loss of all that work. The power of the Event Browser should not be underestimated.
Or just leave the unusable footage and gaps in the angle editor and cut those portions from the timeline, which would probably be the fastest and easiest. Personally, I don’t mind if my Angle Editor has long unusable parts or big blank gaps, it’s easy enough to cut it from the timeline. So long as it’s all synced I don’t see much sense in fussing with cleaning up. The cutting is done on the timeline (although I do tend to do scene-based color correction, remove unwanted audio channels and other global type adjustments in the angle editor).
There are plenty of ways to go about it all, but I don’t think that making selects and rejecting parts of clips from within the Angle Editor and then tidying it up is neither necessary or efficient and it totally neglects the abilities of the Event Browser.
Just some thoughts. Whatever works for you, is best.
-
Saw this in a recent email from RedShark, it has HD-SDI output and is, um, pretty small. $499, lens options available.
-
In the Timeline-
Use up/down arrows to jump to the desired edit point, select the edge of the clip you want to trim with left/right bracket, nudge the selected edit point with period/comma.Is that what you’re looking for?
I realized you must be referring to nudging the I/O point of a range selection, I was referring to nudging the ends of an actual clip.