Video editing

[ColdCase]

I use a GoPro to record 1080P while riding the bicycle. Its best to reduce the need for stabilization while shooting using as stable mounting as possible.

I use a recent 6core MacPro to stabilize the video after edits, and let it run over night. Usual takes a couple hours to do 15 minutes.

You want to complete all your cuts and edits before applying the stabilization effects as anything you change changes the math and the clip will have to run through stabilization again. Stabilization does the math between cuts, and desides on the proper zoom level and crop bases on the worst case it sees. If you have particularly shaky parts, you may want to insert cuts before and after (on the time line) so that the rest of the clip can use less aggressive settings, as was mentioned, aggressive stabilization reduces resolution.

I'll have to check memory usage the next time. I typically edit the camera produced video.

 

[sachman]

I keep my current projects on a 1tb external SSD and constantly have to do housecleaning to keep enough free space. When I'm done with original media, I move it to an big external hard drive.

I like this, I may do this,

sachman: Posted from Apple, below, just in case you didn't read it yet lol:


Just noticed it wasn't linked, and probably explains it best to me

Also, I find it funny that people don't like the new version of FCPX. I will admit it reminds me of the DAW interface more than any other editor I've used over years

Looking at the reviews on the app store - a lot of people having issues with crashes etc. I think I will trial it anyway though

 

[Boyd01]

I find FCPX to be very stable. I had a third party audio plugin that would cause it to crash erratically. But aside from that I think I've only experienced two crashes since I started using FCPX almost three months ago, and I've used it every day for at least 4 hours. My legacy version of Final Cut Pro would crash a couple times every day.

The more I use FCPX, the more I like it. Quite a lot of powerful features in one reasonably priced package and it runs really smoothly on my quad Mini.

 

[joema2]

....Looking at the reviews on the app store - a lot of people having issues with crashes etc. I think I will trial it anyway though

I use both Premiere CC and FCPX professionally. I'm editing a 20 terabyte documentary on FCPX. In general FCPX is more stable than Premiere but they can both crash. If you handle enough content and codecs, any video editing software will occasionally crash.

The book "Behind the Seen" chronicles famous editor Walter Murch's use of legacy FCP to edit Cold Mountain. It was the first time a feature film had been edited in any NLE besides Avid: http://a.co/iQMuKFB

Despite the then-immature state of FCP, Murch felt the risk wasn't that great since Avid crashed all the time, sometimes staying down with a corrupt database for days at a time. His previous film The English Patient had been stalled for several days due to Avid crashes.

I would describe FCPX 10.3.4 as quite stable and robust but with any software there are lurking "islands of instability" -- combinations of hardware, software, plugins, codecs and workloads -- which exposes bugs.

I would not make the decision to use or not use FCPX or Premiere based on stability. In general they are both sufficiently stable on a well-configured machine to do the job. On an iMac and especially if using H264, FCPX is much faster due to use Quick Sync. However rendering/exporting speed is only one item in the workflow, and major motion pictures have been edited with both Premiere and FCPX.

Another option is DaVinci Resolve 14, which has been greatly improved in this version and is free.

 

[thizisweird]

Looking at the reviews on the app store - a lot of people having issues with crashes etc. I think I will trial it anyway though

I would describe FCPX 10.3.4 as quite stable and robust but with any software there are lurking "islands of instability" -- combinations of hardware, software, plugins, codecs and workloads -- which exposes bugs.

this 100%

I think this is one of the most overlooked explanations by the end-user. eh, it happens