gnirtS
Captain
Flight distance : 5712575 ft
Offline
|
fans48f0c1a5 Posted at 9-5 07:14
Yes the only issue there is the filesizes 4k is a gig a minute and hyperlapse is160MB for 2k a minute. If you got the space 4k video is better.
File size isn't that bad.
A raw file is about 40mb an image. Assuming 2 sec intervals thats 30 a minute so 1.2Gb per minute of flying.
Assuming you want to do a roughly 15 second hyperlapse its very roughly 375 x 40 so 15gb.
Pretty much everyone is flying with 16gb or higher cards these days so plenty of storage space.
Then the h.264 video itself comes in at only about 80mb or so once properly processed.
If you use the JPGs it works out about 4gb total so significantly smaller.
The pre-set hyperlapse video thing is fairly bad - its stabilisation isnt great, its a low resolution and highly compressed so a low quality. This makes editing hard. Its also cropped, sometimes a lot due to the stabilisation algorithm.
You're always going to be better off using the still images and putting them together in photoshop/premiere/lrtimelapse or software of choice.
My personal workflow is to stuff them into LRTimelapse, edit in lightroom then render and stabilise in Premiere. But if you dont want that you can just shove the JPGs into premiere or photoshop and make a timelapse, albeit not as stable.
|
|