Final Cut Pro X - Import AVCHD?
Can FCPX import AVCHD files directly, or do they still need to be converted first? I have MTS files from a Panasonic GH2 digital camera that are in AVCHD that are grayed out when I try to import them.
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Helpful articles for Final Cut Pro for Mac, Final Cut Pro for iPad and Final Cut Camera:
Can FCPX import AVCHD files directly, or do they still need to be converted first? I have MTS files from a Panasonic GH2 digital camera that are in AVCHD that are grayed out when I try to import them.
This proved to be extremely useful. Thank you to factualfilms, Tom Wolsky and Jakob. I managed to complete my mini-project but reverted to Final Cut pro 7.03. It was much like putting on an old pair of shoes that fit beautifully and gave relief from the new shoes that made it difficult to even walk. I am persisting with FCP X but when you have to keep stopping your work to come here, Help or YouTube to see how you go about doing a simple task you now have to do in a different way to what you're used to, it's easier and quicker to use the old tool that just does it as expected. (It's that element so typical of Apple software over the years that seems to be slipping away recently)
The last straw was when every time I used the blade tool in FCP X, it automatically closed the gap produced and put everything out of sync. I'm sure there's a simple way of avoiding it doing that, but I just didn't have the time to research it.
Many thanks again for such useful help and tips.
I absolutley get that. And I did the same as you with two projects but then got so fed up with the rendering and found so mny features in X that I stuck with it. Sure ... not as fast to start ad still some things I have to "remember" but it takes a while to learn new softare doesn't it. And even more frustrating when you are moving across from somethin you are completely comfortable with.
It took me a ocuple of years or more from absolute scratch with FCP Legacy to be totally fluent.
I love the real time stuff and now am completely used to and cpmfortabel with the audio all being with the video. In fact I think the audio trimming and editing is a vast improvement
And that is a bit problem for some working with big deadlines for sure.
For me the thing I culd not get used to was not having tracj all forwards ool (Shift T or tttt) and using Gaps took a while to become second nature. In fact I don't know why they do not make a bigger del our of how importsnt it is to use Gaps if you want to get on with FCPX.
Without Gaps I would not be able to use FCPX.
But the longer you look and the deeper you go the better it gets.
I know you're right, and I am back to working with X. There's a lot to like, I know, but like you said it requires time and patience to reap the rewards. Best to learn it whilst experimenting/playing rather than when you have a project that needs to be done yesterday.
Your point about Gaps - are you referring to the Position Tool?
You are very helpful, very much appreciated.
Yes but I also "Insert Gap" Option-W all the time to give myself breathing space/elbow room. It might be just the way I work.
Right, gotcha thank you!
New to camcording/video editing, so pls have me excused if my comment is misplaced.
Having read through a lot of these posts, I understand the main clue is to maintain the camera folder structure when importing to Mac, to avoid transcoding video files/quality loss, and still be able to edit video files in FCP and/or iMovie.
I have an iMac (late 2012), and a Canon Legria HF M52 camcorder recording both AVCHD and MP4. Having struggled a bit importing videos to Mac using USB (having both AVCHD and MP4 recordings on the 32 gb internal memory), and having the Canon camcorder set up with WiFi, I´ve found the best (at least the easiest for me) option to be importing video files wireless (both AVCHD and MP4 files are transferred directly to a dedicated folder).
However, then the video files are transferred as separate files (e.g .mts file), without folder structure. Still, the video size when transferred wireless to Mac indicates high quality video. In order to edit video files, I have therefore been using the ClipWrap application to rewrap the .mts files.
If one follow some of the previous posts here, ClipWrap will generate quality loss? ..and wireless transfer of video files if therefore useless?
kjoglum wrote:
If one follow some of the previous posts here, ClipWrap will generate quality loss? ..and wireless transfer of video files if therefore useless?
I wouldn't be concerned about quality loss – whether you just rewrap to mov or transcode to Pro Res.
You could also import directly into FCP.
Russ
Does the camera record to card?
Camera records to 32GB Dual Flash internal memory. I have the option of using additional SD card, but I don´t see any reason yet, having sufficient internal memory for my private use (3 hrs at best quality, 1920x1080 resolution).
So, if rewrapping .mts files (transferred wireless) goes without quality loss (e.g ClipWrap), and there is no real benefit of importing full folder structure, I guess wireless transfer / rewrapping files would be my preferred option. I.e. being an easy way of saving raw video on my iMac / simple folder structure on my iMac / still easy editable in FCP/iMovie.
From what I have read the only people who have problems importing direct into FCPX are the people who try and do so direct from camera. I don't know why. Have you tried with the SD card and a card reader/slot in Imac?
You should never mix formats on the same media. Using cards allows you to separate the formats. MPEG-4 needs to be converted or optimzied for use in FCP. You need to import into FCP using USB not WiFi.
One of the things that most surprised me about FCPX is it's ability to edit native H264. That said like you I would always advice Optimise to Pro Res.
Apologize my ignorance, but I cannot see why/how the formats should mix. Videos recorded in MP4 format are found under the MP4 folder on the camera´s internal memory (playback mode), and videos recorded in AVCHD format are found under the AVCHD folder on the camera´s internal memory (playback mode). The video files are therefore separated on the camera´s internal memory.
When transferring video files wireless, the files are transferred to the destination folder of the iMac as manually set up under the camera´s WiFi settings, creating a new folder [transfer date] and saving the video files under same. If for instance having 1 MP4 recording and 1 AVCHD recording in the memory, each are being saved as separate files; MP4 recording as MP4 file, and AVCHD recording as MTS file. To make an example, a 2 sec recording made both in MP4 format and AVCHD format becomes 3.9 MB for the MP4 file, and 11.5 MB for the MTS file.
As the camera is set up for WiFi transfer, I cannot understand why the video files should loose any of its content as compared to USB transfer. Even with 1 file for each recording, the content should be the same?
For me it would be a desired option to just transfer raw video files for Mac storage for possible future editing. Video files are playable, but MTS files would need rewrapping to be editable.
They are in a single directory database. I don't know how this specific camera handles the database, but when they're mixed FCP will often see one and not the other. But do whatever you want. I'm telling you what the recommended procedure is. You'll probably find this in your camera user manual somewhere as well.
If you use WiFi the folder structure and database of the recording is destroyed. You will have to convert and rewrap. Again I'm just telling you what's best practice and recommended SOP, but you can go however you want.
Hi
Clipwrapping mts files, using the rewrap only option, is lossless. The original AVCHD data is not changed, just put into a mov wrapper. File size essentially does not change.
Seeing as you are using *internal* memory in the camera, rather than a removable card, it sounds like getting the mts files into their own folder on your mac via WiFi would be the easiest way to do things. Recording to a card and putting that into the slot in the computer or a fast card reader allows direct native import to FCPX. This would be quicker, and because the folder structure can remain intact there is no need to clipwrap, but you don't have that option.
If you import and edit the wrapped movies within FCPX in their native AVCHD format - ie you do not transcode to ProRes on import - then there is no loss of quality at all. Fille sizes will be as compact as they possibly can be. The only problem with this approach is that the CPU requirement is significant, especially if you are trying to play multiple HD AVCHD tracks at once.
If, alternatively, you create optimised (ProRes) proxies on import, the general consensus is that while there is some possible data loss on conversion, it is essentially imperceptible. ProRes proxy movies require much less CPU to play back, scrub and edit etc. Unfortunately, ProRes files are MUCH bigger than AVCHD files, and they must be stored somewhere.
So if I were you I'd not shoot in MP4 but stick to AVCHD, move the mts files over wiifi to your mac, clip-wrap them and import to FCPX without creating proxies. Then, see how easy or difficult it is get your FCPX editing done in native AVCHD. Only set FCPX to ggenerate ProRes proxies if your computer is too slow while working natively on on AVCHD data.
You *could* get ClipWrap to create ProRes versions of the mts files, and them import these directly to FCPX, however this will fill up your hard disks very quickly.
If it was me, I'd record to a card, put that in the slot in my computer, and directly import the AVCHD without any fuss into FCPX.
In your case however, I'd reckon the easiest approach to be to wifi to your mac, ClipWrap the mts files you want to work on, and ifinally mport these to FCPX. Only issue here is file size.
Could you do some tests and get back to us with what you find?
Chris.
Final Cut Pro X - Import AVCHD?