- Posts: 25
- Thank you received: 3
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
About legacy media in Final Cut Pro X
I think I have both sony and gopro footage, and I'm wondering what to do. I have years of footage from my children and later on I want to create a movie when my son was for example 1, 5 and 10 years old. This means that all the footage I have collected in the past need to be available in the future. In earlier days I have migrated my imove projects into fcpx libraries and projects, and was wondering if I need to do some migration and or converting here too.
What is your approach to legacy media and how would you make this footage available for the future? Would love to hear your feedback.
Cheers,
Wilfried
Please Log in to join the conversation.
Please Log in to join the conversation.
Let's assume all gopro footage is cineform. Does the compressor allow you to convert and replace files? Or in other words you can convert cineform into h.264 copies, but your projects are still using the legacy files, thus becomes corrupted? The article on apple site does not give me much more info on this. Hope to find some more info
Please Log in to join the conversation.
Please Log in to join the conversation.
Let's not, because it isn't. Cineform is a specific codec GoPros used, and you had to set the camera's file format to specifically record in that codec. Personally, I hated it.
Please Log in to join the conversation.
When removing the gopro studio software from my computer I found by accident this project thats shows missing plugin error on the clip. Then to find out it was the timelapse clip thats was converted using gopro studio.
When checking the inspector of the clip it says GoPro-CineForm HD/4K/3D. From this I think that the cineform codec is installed by the gopro studio software and is only used when converting clips from SD card to movie clips.
I used this workflow for this particular project to create the timelapse video from a bunch of photos. Plus I also used this workflow in earlier projects to convert footage from SD card and remove the fisheye lens in the clips.
And to make it complete. My current workflow is to import the clips directly into fcpx, and use the alex4d wide angle fix to remove the fish eye. This makes it so much easier, however I didn't know that in the beginning :blush:
Anyways I would love to get some feedback on the above findings
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
As far as I know I'm safe with macOS mojave, and the issue might occur in future macOS releases. There are some tools to help you convert your footage, i.e. compressor and kyno but these tools are not for free and I don't have any experience with them.
I hope by the time this issue applies there's more info and solutions or workflow to convert your footage and or projects. Cheers and thank you for the feedback
Please Log in to join the conversation.
Sony fs700 (avc1)
Sony A7 (avc1)
Canon c300 mk1 (XF mpeg 422 50Mbs)
Canon c300 mk2 (XF-AVC long GOP 10-bit 4:2:2)
Canon 5d (avc1)
Dji mavic pro (DJI AVC encoder)
Panasonic GH5 (H.264)
At this point I'm thinking perhaps the DJI footage is what set off the alert...? Thoughts?
*I've listed the codecs as FCPX lists them in inspectors 'codecs' metadata field)
** all cameras were imported into fcpx from a camera archive where possible.
*** this library was created around the time that the Canon XF plug in was needed for the proper import of Canon footage.
Please Log in to join the conversation.
Good thing we retired that camera shortly after that project.
Please Log in to join the conversation.
discussions.apple.com/thread/8659759
Please Log in to join the conversation.
Looks like apple updated their future format support page, and gave a bit more info for us to digest.
"In the first half of 2019, an updated version of Final Cut Pro will include a feature to help you identify and convert legacy media files."
Please Log in to join the conversation.
Please Log in to join the conversation.
- nils.dettmann
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 13
I´m still personally very unhappy with the whole situation. What kept me with Mac (besides QuickView
The end of the classic quicktime framework has been lingering for some time and things have become a little less convenient (for me with eol of perian) but I have been hoping that AVFoundation would eventually develop and open up to system wide codec plugins.
Tommorrow it´s the "legacy" codecs but what about future codecs? The video world will only get more diverse - will I have to come back to transcode everything like it used to be?
Does anybody remember working with Avid before AMA linking was introduced. That was a serious hassle.
Without the ability for manufacturers to build one plugin for the whole platform , Apple is taking away one big advantage they had - at least for me. And, yes, I have already feedbacked that to Apple.
And by the way: what´s legacy is not the codecs but the quicktime framework. Would be good if Apple stated that more clearly.
Please Log in to join the conversation.
And FCPX does have a plugin architecture for manufactures to build import plugins to support their proprietary formats. Why doesn't anyone complain to the camera manufacturers about that? You tell me your footage is H.264, but who's specific proprietary implementation of H.264?
I don't see it as a problem, and am glad Apple is giving us PLENTY of time to convert old, outdated formats to newer formats that will help our workflows stay fast and easy. I don't recall any other IT company warning folks about file formats going out of date and being dropped with so much lead time, before.
Please Log in to join the conversation.
- nils.dettmann
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 13
Regarding DNxHD/HR I don´t know.
Did Apple provide ProRes support for Avid and Premiere? Serious question!
I don´t think so. Still nice to have it.
Please Log in to join the conversation.




