Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy New Workflow AVCHD for FCP7

  • New Workflow AVCHD for FCP7

    Posted by Matt Goodfield on July 24, 2009 at 12:18 am

    Hi There

    At the moment I have got a Sony AVCHD Camera which records on hard drive (directly)

    A 1 minute clip will use 69mb of the camera space , if I Want to use that with FCP I have to convert in using the log and transfer windows .

    The file size then becomes huge . It goes from 69mb to 760mb crazy

    So that is the reason that I have been putting of AVCHD until now .

    I want to be able to burn all my projects on a DVD .

    But the reason why i want to use AVCHD is because I can log the footage very well in FCP , where I just normally record an MPEG then convert it using MPEG STREAMCLIP then it goes into FCP .

    Do you think even though I am not going to use HD for a few years yet that this is a good idea ?

    I could then export using DVPAL Anamprhic and there we go ! because the file sizes will be normal !!!!

    And then burn to DVD

    Cheers

    Natalie Gray replied 13 years, 5 months ago 21 Members · 32 Replies
  • 32 Replies
  • Russell Lasson

    July 24, 2009 at 2:37 am

    With FCP7, I’d look at transferring your footage to ProRes Proxy for editing, then when you’re done, just transfer the footage used from your original AVCHD files to any higher end ProRes. Should be something like Batch Transfer. Should save you quite a bit of space.

    ProRes HQ is close to 30MB/sec while ProRes Proxy is just 2-4MB/sec! That will really reduce your file sizes for editing. Any Batch Transferring should be a breeze!

    -Russ

    Russell Lasson
    Colorist/Digital Cinema Specialist
    Color Mill
    Salt Lake City, UT
    http://www.colormill.net

  • Martti Ekstrand

    July 24, 2009 at 9:05 am

    I would rather see adding AVCHD native editing for selection and rough cuts. Then transcode that to better codec for final edit, colour correction and post effects. Less waste of harddisk space and more importantly my time.

    check out my shorts: https://vimeo.com/marttiekstrand

  • Matt Goodfield

    July 24, 2009 at 12:31 pm

    You say that ProRes(HQ) is 30mb a second .

    Then why when I transcode the clip in the Log and Transfer window to ProRes the clip becomes over 500mb for a 1 minute clip ?

  • Russell Lasson

    July 24, 2009 at 3:25 pm

    Looks like you skipped over the part where I suggested converting it to ProRes Proxy. If your files are 24P then it’s only 4 MB/sec. That’s only 16GB/hour.

    Yes, it’s bigger than editing native AVCHD files, but it’s much better than the previous alternatives of ProRes or AIC. Plus, these files will be much more edit friendly than if FCP could edit AVCHD natively.

    -Russ

    Russell Lasson
    Colorist/Digital Cinema Specialist
    Color Mill
    Salt Lake City, UT
    http://www.colormill.net

  • Matt Goodfield

    July 24, 2009 at 11:18 pm

    Sorry I did miss that part

    When you suggest converting to ProRes Proxy , How am I supposed to do this ?

    At the moment I connect my camera to my iMac by a USB Cable then I open the Log and Transfer windows and it gives me the option to convert to AIC or ProRes 422

    In FCP 7 will it allow me to convert to ProRes Proxy by using the Log and transfer windows ?

    Thanks A Lot Guys

  • Bjoern Adamski

    July 25, 2009 at 1:10 pm

    Some recording formats are just not suitable for direct editing, they were optimized purely for the recording situation to deal with the available bandwidth. AVCHD is one of those, converting it is required.

    ———————
    Product Manager
    MXF4mac
    https://mxf4mac.com

  • Matt Goodfield

    July 25, 2009 at 9:33 pm

    Thanks

    But in terms of AVCHD what can I do in FCP7 that I cant do in FCP6??

  • Martti Ekstrand

    July 26, 2009 at 11:23 am

    Well the proxy addition is nice but that can be one very long conversion session for me before even starting to edit the AVCHD footage as I can have upwards of 40-20:1 ratios. I don’t worry about harddisk space but time can be of essence. AVCHD shouldn’t be that hard to edit with if tapping into modern video cards GPU power. After all my little battery powered $1500 Lumix GH1 camera can encode 50 fps AVCHD in real-time to SDHC cards but my $5000 MacPro can’t decode it well enough for basic editing from a RAID? That’s a policy decision, not a technical issue. Plus this way seem to lock me into ProRes which is not my preferred codec or have Apple added more codecs to chose from in Log & Transfer now?

    check out my shorts: https://vimeo.com/marttiekstrand

  • Tom Wolsky

    July 26, 2009 at 12:22 pm

    This is incorrect. H.264 is a highly complex codec and very difficult to decode in realtime. Much more difficult to decode than to encode. It would significantly reduce realtime capabilities for multiple tracks of video. This is a technical issue not a policy issue.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP6,” “Basic Training for FCS2” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

  • Walter Biscardi

    July 26, 2009 at 12:29 pm

    [Martti Ekstrand] ” That’s a policy decision, not a technical issue. Plus this way seem to lock me into ProRes which is not my preferred codec or have Apple added more codecs to chose from in Log & Transfer now? “

    As Tom noted, this is incorrect. Policy has nothing to do with a codec that was designed for delivery, not editing.

    Walter Biscardi, Jr.
    Editor, Colorist, Director, Writer, Consultant, Author.
    Credits include multiple Emmy, Telly, Aurora and Peabody Awards.
    Owner, Biscardi Creative Media featuring HD Post

    Biscardi Creative Media

    Creative Cow Forum Host:
    Apple Final Cut Pro, Apple Motion, Apple Color, AJA Kona, Business & Marketing, Maxx Digital.

    Read my Blog!

    Twitter!

Page 1 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy