|
FCPX is not that bad, I had someone come to me for a fine edit and color correction for a short done entirely in FCPX and I got the hang of it in an hour or do. I think it's easier to cut your teeth with a project already in working condition so I'd look at opening up something existing or using an app called 7 to FCPX to convert a Final Cut Pro 7 project to X and then start playing with it
|
# ¿ Aug 3, 2014 16:04 |
|
|
# ¿ Apr 24, 2024 20:58 |
|
FCPX definitely has tracks. They're kind of funky to learn but once you know how to manipulate them they work.
|
# ¿ Aug 13, 2014 21:16 |
|
Starting the audio before or after the cut makes it a more natural transition
|
# ¿ Aug 19, 2014 22:43 |
|
Todieat20, have you considered upgrading to a solid state drive, adding RAM or a better video card? I have a 2006 Mac Pro with an SSD, 18gb ram and an and hd4870 video card and it's still faster than new machines I use at work
|
# ¿ Aug 20, 2014 02:25 |
|
Just finished a documentary I shot in Ferguson right after the Mike Brown killing. It's rough but that's because I aimed to get it out into the news cycle rather than clean it up more. https://www.youtube.com/watch?v=G1sdBPVzQpI FERGUSON: No Justice, No Peace
|
# ¿ Aug 26, 2014 20:43 |
|
The stroke is just difficult. I have a 2.5 minute video that uses strokes to draw out people's movement across maps and it wants 12 hours to render. After effects be cray
|
# ¿ Dec 12, 2014 22:14 |
|
Why is dropbox banned? That's literally the single best answer.
|
# ¿ Dec 23, 2014 23:24 |
|
He's been editing on a laptop so CPU was most likely the biggest bottleneck.
|
# ¿ Jan 5, 2015 16:21 |
|
I have an AE comp that's got 15 layers of strokes detailing the path of people out of ancient Africa and across a world map with a camera pan along it. 45 seconds. I'm now on day 2 of rendering it and it still expects 95 more hours to go
|
# ¿ Feb 8, 2015 18:20 |
|
Literally it's 15 layers of single-line strokes, 15 layers of solids with circular masks that grow for when a stroke gets to its location, camera + null for control, and then a world map that loops horizontally. I just restarted the export when after effects bottomed out on memory and now it's at 350 hours and counting, averaging 1 frame every 2 minutes on a 60fps composition. It would probably be faster to advance it frame by frame, export each frame, then stitch together the frames in another composition. Edit: I'm going to guess that the problem is that each stroke is a 9000x9000 pre-comp solid that I stencil the stroke on. The problem is that it's a 1080p video so the stroke will have to cover that entire screen but at this point I think I will just re-create the entire thing with smaller solids and use one master stroke with each other line coming out from it instead of all starting from the same location. Will suck but 3 hours of work to reduce time is better than 300 hours of render time bassguitarhero fucked around with this message at 20:38 on Feb 8, 2015 |
# ¿ Feb 8, 2015 20:29 |
|
Nah, I'm just remaking the map and strokes, it seems to be freakinf out over the world map being 9000x9000, and having a generated grid behind it along with a textured solid for the water. I flattened the whole precomp and that alone made the entire thing more manageable. Maybe half a day of rendering. I guess I do need a new computer soon, this Mac Pro 1,1 is finally getting long in the tooth
|
# ¿ Feb 8, 2015 21:06 |
|
I would use after effects, render the images out to a video file, then use compressor to convert it to something final cut will be happy to play with, like apple pro res
|
# ¿ Feb 10, 2015 16:30 |
|
Or try using QuickTime to convert the audio to aiff
|
# ¿ Feb 14, 2015 16:21 |
|
I made filmeditdb.com which allows you to create and track a list of assets, it's better for archival materials because you're not looking at "0155427-02.mov" for every exported camera clip but if she's good at managing her files it would be really helpful for organizing your clips. You can even export a .csv of all your assets, if/when they're used in the film, etc.
|
# ¿ Feb 17, 2015 02:48 |
|
Sorry! It looks like my server host migrated me to another server and restarted it afterwards, so I had to re-run the commands to start the webserver. It's back up now. The tutorial video needs to be updated as well to match with the new layout, but it'll get there. bassguitarhero fucked around with this message at 17:29 on Feb 18, 2015 |
# ¿ Feb 18, 2015 17:10 |
|
If you have any feedback or think of things that could be in there but aren't, hit me up with them, I built it based on my experiences working as an assistant editor on a semi-large doc and working off a FileMaker Pro doc, but there are probably a lot of things I overlooked so if there's ways to improve it, I definitely will
|
# ¿ Feb 19, 2015 16:38 |
|
quote:
|
# ¿ Mar 6, 2015 15:59 |
|
I'm not sure about lightworks but a lot of editing programs will allow you to highlight a clip, then hit + or -, then type in a number and hit enter and you will move the clip forwards or backwards by that many frames in the timeline.
|
# ¿ Mar 14, 2015 21:00 |
|
I would also look into your video ram, if premiere needs to dip into your system ram so much you may be having a problem with your video card
|
# ¿ May 28, 2015 15:27 |
|
In particular I would cut frames out between shots vs repeating, the head turn starts in the closeup then the longer shot starts pretty much in the same place where it would probably be better suited if you cut out a bunch of frames between that head turn and leave just a few frames of the turn finishing in the longer shot. The jump comes from the fact it looks like the same shot because the action is repeated whereas a match on action will still let you cut most of those frames out
|
# ¿ Jun 13, 2015 19:02 |
|
|
# ¿ Apr 24, 2024 20:58 |
|
Video copilot was great for me because it teaches you how to do complex-looking stuff really easily so the tutorial results are dope, and the videos are funny. Once you do enough of those you normally have the chops to start exploring more stuff
|
# ¿ Jul 7, 2015 19:24 |