Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Export Out, Import In- Why Now Needs Render???

  • Export Out, Import In- Why Now Needs Render???

    Posted by Bill Bilowit on May 23, 2007 at 12:37 am

    Music video project, DVCProHD 720 23.98, edit going swell. But tonight, a bad workflow anomaly. I am stumped.

    Please see my profile for system/version details.

    Some scenes have several layers and effects so I set In and Out points, select my timeline in Browser, right-click to Export>Quicktime Movie>Current Settings>Self Contained, with or without audio, save in the RAID.

    I import the newly single-layer clip into a Browser bin, drag it into the same timeline, plays fine, render bar grey. Just like always, several years of doing this through 3 upgrades.

    “All of a sudden” my exports brought back in have a red render bar when placed into the SAME timeline it was rendered out from. And for added mystery, playing the imported clip from the Browser in the Viewer the external display will not play all frames. (Video Playback> AJA Kona 720p 59.94 8 bit 1280×720, it’s the setting I always use with 720 23.98 as there is no Kona playback 720p 23.98 setting here.)

    Timeline’s Easy Setup-
    –AJA Kona 2 720p 23.98 DVCProHD Varicam
    –After problem I tried DVCPRO HD – 720p24
    All original clips play fine on sequences created from either setup. It’s the export out / import in that’s a problem, either setup.

    Original clips shot on HVX200, imported no problem to RAID, item properties format:
    Rate: 23.98, Frame Size: 960×720, Compressor: DCVPROHD 720p60, Pixel Aspect: HD (960×720)

    Newly imported clip item properties format:
    Same as above BUT Frame Size: 1280×720, Pixel Aspect: Square.

    Export/import always worked fine, never needed to check item properties before whether editing 720, 1080, or SD. I trashed prefs already, no fix.
    What could I have done here???

    Bill Bilowit replied 18 years, 11 months ago 2 Members · 3 Replies
  • 3 Replies
  • Jeremy Garchow

    May 23, 2007 at 4:08 am

    Try exporting from the file menu. File > Export > Quicktime Movie. Current settings, don’t recompress, and make self contained (if you need that).

    You or FCP has obviously goofed up the settings somewhere as your footage should be 960 not 1280.

    Jeremy

  • Bill Bilowit

    May 23, 2007 at 6:56 am

    Thanks for the suggestion… tried it, and same problem. Then I opened an old 720 project, that one in 29.97, and exported a segment of the timeline and brought it back in, and same problem– it comes back as 1280×720 needing a render for that timeline it came from.

    I clearly don’t know as much as I need to about differences in capture vs. edit vs. playback formats, but I can’t figure out where the problem could be. Since this procedure worked for years and now it doesn’t, where could the goof-up be?

  • Bill Bilowit

    May 23, 2007 at 5:08 pm

    Okay, now I tried using Quicktime Conversion as an export, selecting DCVCPRO HD 720p60, and it successfully imports back in and into the timeline with no render necessary. Great, BUT– the image quality has suffered.

    With the 720 preset, quality can only be “Medium”. If I choose “None” uinder compression and Quality slide to Best and Colors to Millions+, in addition to really long render, the new clip will NOT play in the timeline without a render, even though it is 960×720.

    Within Quickitme Conversion export settings is also Frame Size, checking that reveals “Current Size” is 628×353, “Compressor Native” is 960×720. So what is the DVCPRO HD 720 frame size supposed to be in its correct incarnations?

    Suddenly all is chaotic with this issue and stopping this job dead in its tracks. I have trashed prefs and used FCP Rescue and opened brand new projects using the original camera clips. It seems my Export capabilities are broken or corrupted now.
    What could this be?

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