James Ewart
Forum Replies Created
-
James Ewart
November 13, 2012 at 11:56 am in reply to: Mountain Lion/FCPX not reading AVCHD “PRIVATE” folder correctlyI just select IMPORT – MEDIA and all the options are there in the left hand bar including my card from the camera (AVCHD). Initially had some issues with the camera option and then realised that is probably for when footage is recorded to an internal camera hard drive as opposed to a car which is just a storage device.
I think selecting camera might be the red herring for people…better to transfer from a camera to a storage device and select files that way no??
-
James Ewart
November 13, 2012 at 9:53 am in reply to: Mountain Lion/FCPX not reading AVCHD “PRIVATE” folder correctlyUnless I’m getting the wrong end of the stick here it’s very simple…when you see the import window open make sure you have checked “Create optimised Media” and also in my view good to have “create proxy media” checked too for faster workflow later. Or after you have imported you can do the same thing in the Event Browser. Select the clips and then go FILE – TRANSCODE MEDIA.
I think it expects you do do the logging after you have imported but because of the background rendering this does not hold you up as you can log as soon as it appears in the Event Browser.
I think in FCP7 (or what everyone seems to all “Legacy” rather mystifyingly) most people transferred everything anyway most of the time so they have done away with logging prior to capture/transfer/import.
You can always trash clips you don’t want.
The downside of Optimising is storage space but for me everything runs a lot smoother if I bother…I now many don’t.
-
I haven’t got to Roles yet….is there no end to this learning curve?
-
Okay sorry to be slow on this. Only difference between x and c I can see is that x effectively sets in and out points in the timeline so when you overwrite it effectively “replaces from start” leaving the same duration shot in the timeline irrespective of in and out points in Event Browser. It effectively seems just a quicker way of doing a three point edit whereas if you select c and overwrite it just places the clip in the timeline forward of wherever the skimmer/playhead is is.
It is a little confusing still.
I guess it’s a question of using it a lot and the subtle difference becomes second nature
-
James Ewart
November 13, 2012 at 5:37 am in reply to: Mountain Lion/FCPX not reading AVCHD “PRIVATE” folder correctlyWell yes…optimise or transcode Media.
The Apple recommended workflow is to do this and create both optimised and proxy files I understand. I’m not sure of the advantage of working with native codecs…I dare say Brett will enlighten me but I always work inPro Res and don’t seem to get any of the issues described.
-
It puzzles me how it handles h264 so easily when this is meant to be a codec that you cannot edit in.
-
well it worries me but as we say over here “the problem may have been between the user and the keyboard”
But where did those alias files come from and what for…might they have been the proxy files?
-
Well I thought I had copied the event through the app t another drive and then wen I copied the project also I got muddles..trashed the original event on the fist drive and KABOOM…ARMAGEDDON…RED LINES EVERYWHERE.
I have found a bunch of movies in the trash..reimported them and after several attempts I have successfully relinked media but in the process I have duplicate and triplicate clips in the event browser…trouble is I do not know which of the three triplicates FCPX is using in the project because the original files were renamed and have remained renamed in the project timeline (touched on this a while back regarding renaming clips). So although FCPX has successfully managed to relink the files through metadata other than the clip name, I have no way of finding out which are the duplicate and triplicate clips in the Event Browser that I could trash and free up space.
So…a good lesson…renaming clips does not prevent relinking files as has been suggested in the past…and have projects with clips all in tact in timeline including text (bizarrely as I thought I would have to redo that).But it’s a minefield of alias files when you start looking around.
I always optimise and create proxy as advised by some Apple bloke in Amsterdam way back which may have further complicated things.
Bottom line I’ve got away with it but not quite sure how.
-
Hi Jeremy,
Well over here “nudge” does not work after selecting clip with x whereas selecting with C allows you to trim whereas x just allows to to drag the range handles.
Still not sure I quite get it.
Regards
James