Forum Replies Created

Page 7 of 126
  • Jeff Kirkland

    August 7, 2019 at 7:24 pm in reply to: replacing media file

    what happened when you tried to relink the missing file from inside fcpx? Messing around in the finder is never a good idea.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • Jeff Kirkland

    July 27, 2019 at 4:33 am in reply to: Green Screen Export Anomaly or Something Wrong?

    Great! Well, not great but at least it’s solved ☺

    It could be that the LUT file is damaged or just not created properly to start with. Install a replacement, override the camera LUT in the inspector, and you should be good to go.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • Jeff Kirkland

    July 26, 2019 at 10:11 pm in reply to: Green Screen Export Anomaly or Something Wrong?

    Is the LUT one of the built in ones or one you added? Even if it looks wrong, it could be worth trying applying a different LUT to see if the issue is just with that particular LUT file.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • Jeff Kirkland

    July 26, 2019 at 9:58 pm in reply to: Green Screen Export Anomaly or Something Wrong?

    Compressor had the same auto LUT applied? Sounds like you’ve found a bug with the LUT system. Maybe apply the LUT to that clip manually and see what it does?

    I’ve never used FCPX’s built in LUTs which could be why I’ve never seen it happen. Surprised nobody else has come across it if that’s the case though.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • Jeff Kirkland

    July 24, 2019 at 9:35 pm in reply to: Green Screen Export Anomaly or Something Wrong?

    No clue about that one. Have you tries deleting your render files? Maybe FCPX is pulling something from there…

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • From memory, and its been a very long time, The DSR 45 is SD only so if you have any 1080 tapes (which I assume are HDV) it won’t be able to play them.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • What Neat Video works on, depends on where you put it in the effects chain. so if you make your colour correction changes pre Neat Video then it’s working with whatever you’ve done to the image so far. There’s no way (that I’m aware of) for any plugin to bypass the other plugins that came before it and just access the unadjusted image.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • [Bret Williams] “Or record the screen in QT.”

    Doh! Some days my brain just isn’t in gear…

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • So he’s gone from the HD to SD then back to HD in his MKV and now wants to go back to SD. I suspect it’s going to be difficult. I remember researching it a couple of years ago and even Matroska themselves saying that it was very difficult to go from an MKV container to DVD without losing an unacceptable amount of quality. Can’t remember the why though.

    You might try EditReady to get from MKV to something like ProRes and then try burning from there.

    Alternatively, if the MKV is playing back ok, maybe it’s worth trying a direct capture? Play out the MKV into a capture device and see if that works.

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

  • Jeff Kirkland

    June 12, 2019 at 12:40 am in reply to: Seq header duplication

    Now that’s stretching my memory. It’s been a long time since I even saw DVD Studio, let alone actually used it but….

    What type of role are you starting from? ProRes or MPEG2? If it’s MPEG2 then it’s possible there’s an error in the mpeg encoding. Try re-encoding it.

    I’ve seen that error happen because there was a corruption in the DVDSP project and rebuilding it from scratch has fixed the issue.

    I’ve also seen the issue happen because there were spaces in the filename. If there are spaces, try deleting the asset, then renaming it in the finder and reimporting it.

    That’s all I can think of off the top of my head but it’s been a long time. Maybe something there will help…

    —-
    Jeff Kirkland | Video Producer & Cinematographer
    Hobart, Tasmania | Twitter: @jeffkirkland

Page 7 of 126

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