Forum Replies Created

Page 2 of 3
  • Sean Cole

    August 22, 2011 at 4:07 pm in reply to: Twixtor?

    Hi John,
    Goto your Master Seq and use Cmd-0 (zero) to bring up the seq settings. Make a note of the compressor, the frame rate, and so on.
    No jump to your SloMoClipSeq and do Cmd-0 again. Provided there are no clips in it you will be able to adjust its frame rate. You can also adjust it’s codec at any time.
    I will do a search for a video. I’ve not needed them myself as Twixtor has always been simple enough to understand from it’s included documentation.

    Sean
    Pi Digital

  • Sean Cole

    August 22, 2011 at 2:56 pm in reply to: Multiclip FCP

    Hi Alessandro

    My option would be to choose the best of my three native formats and convert the other two to match it. Or use your final output format (assuming it’s a format easy to edit with). Failing that I choose ProRes.

    All the best

    Sean
    Pi Digital

  • Sean Cole

    August 22, 2011 at 2:52 pm in reply to: red levels are high

    Hi Ismael,

    A couple of things you could do. The simplest is to add an effect to the shot which is Effects>ColorCorrection>BroadcastSafe. In its settings change the mode to Very Conservative. Disable the luminance limiting then adjust the Saturation Max Out to something like 100 and it’s start threshold to 95. If it is still too high tweak the RGB output.

    Alternatively, add a Simple Color Corrector (not the 3-way) In it’s Visual settings open the ‘Limit Effects’ section, use the eye dropper to select the red then use the Saturation control to reduce the red levels. Adjust the Limiters Saturation and Hue softness widths to blend it in better.

    Hope these help

    Sean
    Pi Digital

  • Sean Cole

    August 22, 2011 at 2:40 pm in reply to: Twixtor?

    Hi John,

    The Twixtor in FCP workflow is as follows.

  • First create a sequence (Which we will call SloMoClipSeq from now on) and make its settings identical to the Master Sequence.
  • Next add your clip to be slomo’d to the SloMoClipSeq. If it asks to change the seq settings say No.
  • Then add a Slug after the clip with the same duration. If you are going to slo by 50% add 1 of these slugs. If 25% add 3 of them, etc.
  • Back in your Master Seq, add the new SloMoClipSeq to the timeline.
  • With the SloMoClipSeq clip selected add the Twixtor effect and adjust its settings accordingly
  • That’s it in simple terms as I remember. Hope it helps.

    Sean
    Pi Digital

  • Sean Cole

    August 21, 2011 at 6:32 pm in reply to: Exporting out of FCP X problems

    Ok, good. What settings are you using for export to email?

    It is interesting so far as it is saying that the background run of Compressor has first created a deinterlace then deleted it. 3 and a half minutes after. Is it sitting there all that time before it tells you -50? But it’s only providing info, but not errors.

    I’m guessing that your edit has media from various sources, some interlaced and others not and at some point it’s reaching a clip that’s upsetting the Quicktime export component.

    I’ll wait for your settings info first though.

    Sean
    Pi Digital

  • Sean Cole

    August 20, 2011 at 10:14 pm in reply to: Exporting out of FCP X problems

    Hi Jordan,

    The -50 is a quicktime error and is a known issue (for 2 years+ now). Compressor would likely have the same problem – after all, the system employed by FCPX is the same as Compressor to export, i.e., Quicktime.

    So, solutions. There is no single solution as yet. Some say use a smaller file. Some say create a smaller file. Some have found corrupt files. Some have found nothing to solve it and scream.

    Here’s my way. Open your Console. Clear the contents (this is only temporary to help you see what happens next), then try the export again. If it all goes wrong again for you, take a look back at the console and see what it says. Post it here if you can’t fathom it yourself. I’m confident I can.

    All the best.

    Sean
    Pi Digital

  • Sorry Andreas, you too have slightly misunderstood me. My fault I suppose though. I know only full well that xml is used for lots of things, not least databases and in HTML for providing plenty other information. I also use the EX3 which also has XMLs on it’s cards for metadata. So yes, XMLs DO resemble XMPs in this one regard.

    However, what I was specifically talking about was it’s use for FCP exports. In a similar way to how Avid, Premiere Pro, After Effects, Motion, Soundtrack Pro, Grass Valley, and crap loads of other software use it 😛 for sending edit and effects information to each other – or anything potentially in fact.

    So, Tell me please how XMP is like that? It’s not. It’s extended metadata. That’s it. It can’t transfer edit information over to FCP, After Effects, Avid. It could, but it doesn’t. Not yet anyway. – But of course you don’t need me to tell you that (forgive my apparent insolence. It wasn’t meant for your benefit, it’s for anyone else who may stumble across this thread in search of valid information).

    FCP’s XML interchange protocol is to address this (the transfer of edit/sequence AND clip specific information) and is what the Original Poster was writing about when he spoke of the API’s Apple were going to release.

    Who’s AXEL by the way? :/ Is he/they creating a new solution for data interchange.

    What do you think about the Alexa when working with Prores, what is the XML on the card for? Data or metadata.
    P2? Canon 5D/7D?

    Que? Oh, sarcasm. I see 😀 Like it

    So to sum up, when I said ‘XMP is metadata, whereas XML is for data transfer through a packaged markup language’ what I should have added (for those who couldn’t be bothered to link it with the rest of the post) was ‘from Final Cut Pro to some other edit or sequence based application – because obviously if I wanted to send just a clip I would export a quicktime with a crap load of metadata’ 😉

    Sean
    Pi Digital

  • Sean Cole

    August 19, 2011 at 3:41 pm in reply to: I’m annoyed about FCPX and I want to vent

    Walking and Pointing is EPIC! 😀 Watch the making of, it’s hilarious

    Sean
    Pi Digital

  • He he he. I wasn’t offended at all. It’s all too easy to find offence in something we read cause you can read it with an angry voice or a funny one. Imagine me with a Peewee Herman voice and it won’t be nearly as offensive – just annoying. Which is how most people find me. Nevertheless useful when they need a difficult job done. They can lock me away in a dark room somewhere and just know it’s getting done without having to bear my sarcasm and twisted humour.

    Now, XMP is metadata, whereas XML is for data transfer through a packaged markup language. So two completely different things, but I can see where it might be confused. XMP is VERY useful when storing extra info about a clip and FCPX, while it creates info about a clip like Shot angle, faces, etc, you can’t export that data with a clip. So perhaps what you would like is a way to get clips from FCPX to export with XMP data. That would be cool, eh!

    Pi

    BTW, thanks for acknowledging my true identity as owner of this entire forum 😛

    Sean
    Pi Digital

  • Skip off is the broadcast model dead. Maybe where you live. Here it’s very much alive – and kicking me to death :P. Most of the work I do is for Broadcast in one form or another. I work freelance for them but most of the production teams I’m working with are staff – especially the BBC. I’m like you, glad to have my own company where I can do my own projects in my own time and others for others. Wonderful!
    I still dream of the day, however, when all the broadcasters ONLY broadcast in HD widescreen so we can do away with all this 14:9 and 4:3 rubbish.

    Back on track though, Joseph. As a digital only distributor what uses would you have with XML from FCPX? Do you use EDLs or need interchange with other software – If so, which?

    Sean
    Pi Digital

  • Page 2 of 3

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