Forum Replies Created

Page 1 of 43
  • Hey, thanks for the reply. Yeah I also feel like there must be an easier way / plug-in to do this. I just wasn’t sure if I was missing something obvious in AE

    Thanks

  • Michael Duff

    February 10, 2020 at 12:56 pm in reply to: 23.976 footage is interpreting as Drop-frame TC

    Just tried in Davinci and the TC is being read correctly. Tried on another Premiere computer with the same problem. So seems like some weird bug in these files that Premiere doesn’t like but MC and Davinci are fine with

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 10, 2020 at 11:18 am in reply to: 23.976 footage is interpreting as Drop-frame TC

    23.976 …

    but as shown above if it is even showing drop frame TC on the source footage window not just the sequence

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 5, 2020 at 10:41 am in reply to: 23.976 footage is interpreting as Drop-frame TC

    I’m not actually changing the interpreting of the footage. I mean, all footage is interpreted by Premiere when you import it as whatever it is meant to be. I’m not re-interpreting it. I just opened that window to show that the interpretation was correct …. 23.976

    But yeah … something wacky. I have upgraded to Catalina a couple weeks back and someone said that could be bugging it out?

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 4, 2020 at 9:08 pm in reply to: 23.976 footage is interpreting as Drop-frame TC

    Thanks – hopefully the screenshot links below are working now.

    The TC is source timecode and each clip has been exported from Media Composer with this TC written into the file. The TC is also burnt in as reference on the screen. The TC in Media Composer and when I open the clips in Quicktime match between the file TC and the burnt in.

    But, when I import into Premiere the TC does not match up. The start TC does not match up and for some reason Premiere is showing dropframe timecode (; instead of :).

    I’m not interpreting the footage as anything other than what it is. I was only saying that it is being interpreted into Premiere as it should be. Footage was shot at 23.976, exported from Media Composer at 23.976, and is importing to Premiere at 23.976. But this weird thing is happening where Premiere is reading the TC incorrectly – for some reason as dropframe – and therefor all the timecodes are out.

    Does that make sense?

    screenshot2020-02-03at8.54.00pm.jpg

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 4, 2020 at 10:52 am in reply to: 23.976 footage is interpreting as Drop-frame TC

    Also, when I open the files in Quicktime the TC is correct and matches the burnt in TC from Media Composer. But as soon as it comes into PP it is incorrectly interpreted. See screenshot:



    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    February 4, 2020 at 7:49 am in reply to: 23.976 footage is interpreting as Drop-frame TC

    Thanks for the reply.

    The footage is 23.976 from Media Composer and has TC burnt in. Importing into PP and interpreting at 23.976. In the source monitor the timecode does not match what is burnt in and the timecode is show semi-colons (;).

    The burnt in TC is definitely correct in Media Composer but for some reason it seems it isn’t interpreting correctly in premiere or something ..?

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    January 6, 2020 at 8:50 pm in reply to: Relinking LUTS

    Thanks for the reply … in this case he would need to reapply the preset to each clip?

    We have a 2hr program with different LUTs and grades throughout … I was hoping he could just open my project – reconnect the media – hit render – so that I don’t have to upload a 2hr prores files. Possible?

  • Michael Duff

    January 5, 2020 at 7:46 pm in reply to: Modify a Lumetri preset “globally”

    Thanks for the reply. Unfortunately master clips don’t make the process any faster as I’m working on a project that has been “project managed” so every clip has its own master clip.

    I’m just a bit confused because I did have an effect applied on various clips across the project and somehow I shifted the colour temp and now every instance of that effect the colour temp is very cool. Now even just to fix that I need to find every single instance (hundreds of them) and correct the colour temp. I’m 99.9% sure this is what happened as I can;t think of another way that all these effects had their colour temp changed.

    Anyway, thanks for the reply… I’ll settle in for a long night of modifying effects…

    Michael Duff –
    Bearcage Productions, Australia
    http://www.bearcage.com.au

  • Michael Duff

    January 2, 2020 at 10:50 pm in reply to: Modify a Lumetri preset “globally”

    Any ideas? I think I must be missing something obvious here. Surely there is a way to adjust an effect and have it apply to all instances throughout a project….? I understand I could use adjustment layers but this is a massive project and even with adjustment layers I’d still need to manually update the effect on every adjustment layer that contains the effect.

    If anyone has an idea appreciate the help. Thanks

Page 1 of 43

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