Forum Replies Created

Page 1 of 2
  • That did it. Thanks Jeremy. That is so strange that it sees a timeline in the bin and knows to make individual clips with the setting chosen, but won’t make an XML for the trimmed media that it transcodes in that same batch.

  • Here is the entire process thus far:

    1. Ingest footage using RCX Pro to ProRes proxies.
    2. Edit in FCP.
    3. Export XML > import to RCX Pro. (All media is reconnected fine and things going smoothly so far)
    4. Grade Timeline in RCX Pro.
    5. Attempt to export a folder of media + correlating XML from RCX Pro in order to finish the big batch of short timelines that are sitting in FCP waiting for this process to be figured out…

    Step 5 generates a folder of media that all looks great, but no XML anywhere.

  • Here are one of the setting combos used. This one is prores4444 3840×2160. I have the ‘Generate FCP XML’ checked so I can hopefully get an XML, but it hasn’t worked yet…

    Does this clear anything up?

  • It was set up as part of the transcode operation. No XML was generated. I’ve tried multiple times using the FCP XML option (also tried all the other options) as part of the export preset. I’ve tried it on multiple computers as well and with multiple types of transcoded media (ProRes4444, DPX, QT wrapper, etc) None of them generate a matching XML (or EDL).

    Any ideas outside of the obvious that I might be overlooking?

  • I’m having the same issue. Tried checking all of the boxes in the export settings, yet nothing is generated in the directory or anywhere else on the computer. It doesn’t seem to be generating any kind of XML at all. If I try to do an export (shallow) XML, it links to the R3D’s rather than the rendered out ProRes or DPX files.

  • Brandon Mcfarland

    August 25, 2011 at 7:57 pm in reply to: Expression for Digital 24 Hours clock

    That works. Thanks! Now I just have to find a fixed width font that looks decent so it doesn’t look like it’s jumping around as much.

  • Brandon Mcfarland

    August 25, 2011 at 7:08 pm in reply to: Expression for Digital 24 Hours clock

    I’m trying to modify this to make a 48 hour countdown. I’ve got the numbers correct, but I want to try and get the numbers under 10 to display with a zero in front of them. Any tips for that? I tried just changing the begin values, but that didn’t work at all (it didn’t mess up the expression at all though, so I left it).
    Thanks.

    beginHr = 48;
    beginMin = 00;
    beginSec = 00;
    beginHun = 00;

    beginTime = (beginHr*60 + beginMin)*60 + beginSec + beginHun/100;

    function digits(myVal,myNumDigits){
    var s = myVal.toString();
    while (s.length) return s;
    }

    currTime = beginTime - time;

    hr = digits(Math.floor(currTime/3600),2);
    min = digits(Math.floor((currTime%3600)/60),2);
    sec = digits(Math.floor(currTime)%60,2);
    hun = digits(Math.floor(currTime%1*100),2);
    hr + ":" + min + ":" + sec + "." + hun

  • Brandon Mcfarland

    February 19, 2011 at 5:44 am in reply to: Exporting frames to retouch and re-import

    When you said:
    “I’ve tried using PSD, TIFF, and PNG, saving both with and without a color profile”
    Was that exporting from FCP? Or is that just saving from PS? What options have you tried from FCP?

    The method I use is this:
    1: Make freeze frame (Shift-N)
    2: Drag from viewer into bin to make independent clip
    3: right click on that file and export using quicktime conversion
    4: choose still frame in the pull down
    5: use PNG or TIF
    6: edit in PS and then save as TIF or PNG.

    I don’t get any gamma shift using this method. Hope this helps.

  • Brandon Mcfarland

    February 19, 2011 at 5:36 am in reply to: FCP sees AE ProRes renders as interlaced

    Yep. Been there done that. I’ve been making non-interlaced material since it was an option. Final Cut Pro seems to not like/understand when other applications make their own codec… All signs point to these files being progressive (even compressor) but as soon as I drag them into an FCP bin, they are all of a sudden upper field first.

    Side note: I have also seen this with Animation codec and on multiple systems running similar versions of AE and FCP, so I’m pretty sure it’s not a single system issue. Anyone else experiencing this issue since the last ProKit Update?

  • Awesome! That works perfectly.

Page 1 of 2

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