Reid Alt
1
Apple Final Cut Pro X Coin
1
COW Coin
Forum Replies Created
-
Crap, the more and more digging I am doing, the more it looks like FCPX won’t edit AVCHD natively, even though everything I read beforehand (even from Apple!) indicated that it would. Well, that sucks. I guess I’m just gonna keep all the footage on an external HDD and import the footage from there, creating only one copy on my internal iMac hard drive. I suppose that’s a solution, but I just don’t like the idea of double importing.
I’ll leave the thread as unanswered for a little bit longer, in hopes that someone may be able to prove me wrong (or right?) and that I’ve just been missing one simple step. Thanks a lot for all the help, everyone.
-
But that article doesn’t mention anything about being able to turn auto-conversion off or on. Since the setting allows for the program to stop making those .MOV files, that’s what I’m looking to do. The article and your post only reference how FCPX works under preset standards, and that’s what I’m trying to get disabled.
-
That shouldn’t be the case if I uncheck the preference for FCPX to do so. Apple even says that FCPX can edit native ACVHD files, so I know that’s not true.
Can’t find the Apple document, but I did find some decent information: https://www.shedworx.com/final-cut-pro-x-avchd-support
-
It appears to be full-on files. An example:
The source file of a 18 second clip I have is 45.1 MBs, in AVCHD. In the Movies > Final Cut Events folder, the same clip is now classified as a .MOV file, and is 45.6 MBs.
I am just getting so tired and not having any clue why this is happening. Thanks again for all the past and future help. I’m starting to wonder why I waited so long to join this forum in the first place… 🙂
-
Thanks for the reply!
So, I did what you said (after I found out how to restore the Library folder in my Home folder [Apple removed it in OS 10.7 Lion – lovely]), and then rebooted FCPX and imported some footage. It still copied my footage into my Movies > Final Cut Events folder.
Thanks for the help though. I just can’t wrap my head around how this kind of stuff wouldn’t have gotten bug tested. I’m really hoping that this kind of crap gets fixed in future releases.