Skip to main content
R
RG500
Participant
December 30, 2022
Answered

Selected luts not applied to Media encoder

  • December 30, 2022
  • 2 replies
  • 5109 views

I have added a LUT to the drop down menu of Lumetri basic. You can select this and the lut is applied. If you quick export within Premiere the LUT is applied to the export. If however you send the export to Media encoder, the export does not apply the LUT. Can't imagine why this happens. If I apply the LUT from an external source rather than the drop down menu the LUT is applied when exporting via Media Encoder.

PP 23 and latest version of Media Encoder.

    This topic has been closed for replies.
    Correct answer R Neil Haugen

    Do NOT put LUTs in the program's internal LUT folders ... that's not only not recommended, it will lead to really screwy behavior.

     

    There are the two user-added LUT storage locations ... they do publish that in the help documentation. Not that it's a fantastic help file, this is there.

     

    The Program{package} files/Adobe/Common/LUTs folder is the easiest for me. With subfolders I created as above.

     

    After adding any LUTs to the subfolders, you have to relaunch Premiere, or any other of the three apps Ae, Me, or Pr. They only scan those folders for contents on program launch. 

     

    And if they are not seeing them on re-launch, it's normally 1) the LUT type isn't usable, like many Resolve created LUTs; 2) there's a name issue or some other file header issue;  3) nearly all other problems are a folder permissions issue between the OS and Premiere.

     

    Some LUTs can be made usable if you know how to open them in a text editor, and simply remove some extra unneeded verbiage in the file header. There's one line typically added by Resolve that gunks Premiere, but I can't remember which it is at the moment.

    2 replies

    R Neil Haugen
    R Neil Haugen
    Legend
    September 5, 2023

    If you put them in with the program's own LUTs, then ... you must have the identical LUTs in every program.

     

    Because they do not use LUTs from their internal folders by LUT name, but by the relative positions of the LUTs in the folders in a computerese alphanumeric sort process.

     

    Ergo ... fifth LUT down, not Albany_Blue ...

     

    Whereas, if  you correctly place them in folders that Premiere, AfterEffects, and MediaEncoder are all designed to look ... then they work across all apps.

     

    I can access and get applied the many LUTs I've created by all three apps. Across version series, since prior to 2019 versions, from the one set of folders.

     

    You can't do that in your process. You will have to ensure that every folder has precisely the same number and name of LUTs in them across all apps. A ton of work there.

    Everyone's mileage always varies ...
    M
    McKian
    Known Participant
    September 5, 2023

    Ah, I'll check that out. Weird that it works that way. It really is a failure on Adobe's part to not have the LUT's in there already.

    R Neil Haugen
    R Neil Haugen
    Legend
    September 6, 2023

    That's like comparing that you have to learn how to adjust your seat in a new car to having to dig beneath the hood and replace part of your wiring. It is no where near the same thing and Adobe should have fixed this years ago. If Adobe doesn't know how to actually make a program the works consistently than they have a lot to learn.


    Human perceptions are fascinating, as we are all different from each other. We are all diverse, because the reality is we don't know how to be otherwise.

     

    To me, your analogy is backwards. Messing in the program folder is going under the hood. I don't know other apps where one adds things into the program files folders.  And this has been set like this, and included in all the help and tutorial stuff, since 2017 at the least

     

    There is a rather large difference ... to me, at least ... between something that works very consistently if different than some expects, and one that work inconsistently.

     

    The things like user keyboard settings, presets, all of that, are outside the program files. Which might not be what you expect, but is how the entire app is written.

     

    And is entirely consistent with the behavior for other user added things.

     

    Understand, I've complained repeatedly about the plethora of places user stuff is stored. Sort of all other the drive. THAT I would like to see modified, down to one folder where all user things are stored.

     

    Neil

    Everyone's mileage always varies ...
      R Neil Haugen
      R Neil Haugen
      Legend
      December 30, 2022

      Because you added the LUT to the ones included with the app. Users should never, ever! add LUTs to the Premiere, AfterEffects, or MediaEncoder internal folders!

       

      Because you then get exactly what you just got.

       

      There are two different paths users can use to add LUTs in such a way that you add them once, and all three apps access them. Search the help for user LUT locations.

       

      I prefer the location:

       

      Program [Package on Macs] files/Adobe/Common/LUTs ...

       

      ... and then use the appropriate subfolders so they show on the drop-down list where you expect to use them. You may need to create these subfolders before adding the LUTs.

       

      • Input (for Interpret Footage color management Input LUT slot)
      • Technical (for Lumetri Basic tab Input LUT slot)
      • Creative (for Creative tab Look input LUT slot)

      Neil

      Everyone's mileage always varies ...
        M
        McKian
        Known Participant
        September 5, 2023

        This is frustrating to me because this entry pops up in google as the first solution for this issue and it doesn't feel like it actually solves the issue for me. I'm not sure how to get Media encoder to link up to the same LUT's now that I've moved them to the Common Folder.

        For me I just moved the luts to the internal folder of Media Encoder and restarted my computer and it started working again. It's not ideal since I have to do it every time Adobe updates their software but there doesn't appear to be a better solution coming from Adobe.

        R Neil Haugen
        R Neil HaugenCorrect answer
        Legend
        September 5, 2023

        Do NOT put LUTs in the program's internal LUT folders ... that's not only not recommended, it will lead to really screwy behavior.

         

        There are the two user-added LUT storage locations ... they do publish that in the help documentation. Not that it's a fantastic help file, this is there.

         

        The Program{package} files/Adobe/Common/LUTs folder is the easiest for me. With subfolders I created as above.

         

        After adding any LUTs to the subfolders, you have to relaunch Premiere, or any other of the three apps Ae, Me, or Pr. They only scan those folders for contents on program launch. 

         

        And if they are not seeing them on re-launch, it's normally 1) the LUT type isn't usable, like many Resolve created LUTs; 2) there's a name issue or some other file header issue;  3) nearly all other problems are a folder permissions issue between the OS and Premiere.

         

        Some LUTs can be made usable if you know how to open them in a text editor, and simply remove some extra unneeded verbiage in the file header. There's one line typically added by Resolve that gunks Premiere, but I can't remember which it is at the moment.

        Everyone's mileage always varies ...
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices