Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Media Manager does hidden & mandatory deinterlacing when HDVi50 -> prores?

  • Media Manager does hidden & mandatory deinterlacing when HDVi50 -> prores?

    Posted by Toke on September 3, 2008 at 4:25 pm

    I’m mastering a sports documentary which is mainly shot in 1080i50 hdv with Canon XLH1.
    I need to do lots of graphics and cc’ing and also lots of slow motion.
    I had EDL from premierePro, which I recaptured in HDV and then Media Managered to APRhq.
    Slow motioned footage looked bad in FCP, so I tried to separate fields in After Effects and do slow motion there, but it didn’t work with APRhq’ed footage.
    I tried to do same thing with original HDV material and slow motion looked good.

    So Media Manager somehow deinterlaced the footage when it was converted to APRhq.
    I checked apr & hdv footage in QTplayer and hdv shows noticeable interlacing but apr does not.

    After that I did a test:
    Opened a new project with hdv1080i50 sequence.
    Imported one hdv1080i50 clip.
    Shortened it a bit in timeline and chose MM.
    There I selected recompress proresHQ 50i.
    MMed project had deinterlaced clip.
    I even confirmed this in After Effects.
    So in this way MM is broken.

    Similiar experiences?
    Would it be worthwhile to report this to Apple?
    Do they have “report a bug” somewhere?

    Owen Smithyman replied 15 years, 10 months ago 3 Members · 6 Replies
  • 6 Replies
  • Toke

    September 22, 2008 at 6:17 pm

    Don’t know if there’s anybody interested about this, but I did another test and found out that deinterlacing happens only when there’s scaling involved.
    When I did a test with hdv1440i50->proresHq1440x1080i50 there was no deinterlacing.
    So, with hdv1440i50->proresHq1920x1080i50 there is some quick and dirty deinterlace which produces pretty ugly quality.
    I reported the problem to Apple before, but got no answer, so maybe they are not so interested about this solution either…

  • Kumpanija Lajthaws

    January 19, 2009 at 12:47 pm

    We’ve experienced the same exact problem, on FCP 6.0.5.

    We work with HDV almost exclusively, but CC in Color. So for short 30 sec work, we used to export each clip to ProRes HQ, and then import those clips into Color.

    However, for long projects, we found it made more sense, obviously, to go thru Media Manager, and automatically re-encode the clips in Prores HQ.

    And yet we’ve hit the same stumbling block that Toke has written here about, only that in our case we’re finding that each and every clip gets deinterlaced, irrespective of whether we’ve applied basic motion to it, or not.

    Any takers?

    k

  • Toke

    January 19, 2009 at 1:22 pm

    I noticed back then, that if the resolution (1440×1080) is not changed (to 1920×1080), media manager does not do any altering to video.
    Can Color handle well 1440×1080 proresHQ or does it have to be 1920×1080?

  • Toke

    June 3, 2010 at 9:46 pm

    [toke lahti] “Can Color handle well 1440×1080 proresHQ or does it have to be 1920×1080?”
    Pretty old thread, but the problem came up again recently, so can anybody clarify?
    Is there any decrease in performance in Color if you’re using non-square pixels like 1440×1080 with prores?

    Or have anybody noticed if this “Hidden & mandatory deinterlacing in Media Manager” bug is removed in FCP7?

  • Kumpanija Lajthaws

    June 4, 2010 at 7:39 am

    Hi Toke

    Can only answer on the first part of the post: yes, although I have no hard evidence by way of statistics, it does seem to us that Color crashes far more frequently with 1440×1080 footage than it does with 1920×1080.

    k

  • Owen Smithyman

    July 8, 2010 at 9:41 pm

    Man, I’ve been searching for info about this issue for weeks now! Unfortunately, the issue persists in FCP 7. Right now I’m dealing with converting DVCPRO HD footage to ProRes 422, and Media Manager deinterlaces it just as you describe! Very annoying, because there’s no way to make it stop other than exporting each clip manually from the timeline. Anyone else out there experiencing this and have any insight??

    GRRR!

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