Skip to main content
L
LoboAdobe
Participant
March 8, 2018
Answered

sharing LUT on different work station

  • March 8, 2018
  • 2 replies
  • 2917 views

Hello everyone,

I am having a problem which is clearly related to my special kind of workflow, but would like to ask for help on this anyways, as it got me stuck.

My workflow isspecial because I have to deliver projects in whole to my clients, meaning project file, raw material and any media used in the project.

Now I started liking the possibility of working with Lumetri and custom LUTs.

And this causes the problems I, or actually my clients have.

As my computer knows where my custom LUTs are stored I do not have the problem, but my clients open my projects and they have to

choose and reactivated the LUT on each clip/edit in the timeline if I just give them my LUT directory, as obviously on their ,machines the path to the LUT is different.

I then thought I could work arround that by adding the LUT to Premieres own LUT folder, which worked fine as long as the clients added it there as well.

BUT, whenever I add a LUT to this directory, or the client adds one it seems to mess up the structure and Premiere opens the projects with using a different

LUT then was actually used on the footage.

It seems a bit as if Premiere locates the LUT not by its name, but by "place" in the folder, something like "use 7th LUT from top". which seems odd.

Is there any way to make it possible to interchange a whole project between different work stations with Lumetri and using custom LUTs?

Thank you for any advice in advance.

Best regards

Petra

      This topic has been closed for replies.
      Correct answer francis-crossman10980533

      What Jim Simon states is absolutely true - do not open the application package to install your own LUT files.  It will cause all sorts of problems including the ones you have already run into.  You'll get burned - don't do it. 

      You should apply LUTs by using the "Browse" button in the drop-down and navigate to the LUT files on disk.  Using this method, Premiere is supposed to actually embed the LUT file into the project file so you can share the project with your client without having to worry about the LUTs.  This will not install the LUTs onto your clients' system for use in other projects, but the project you gave them should work correctly.  If this is not working, that is a bug.  BTW we are aware of the frustration surrounding using custom LUTs and we are working on a fix to make this easier for you.

      2 replies

      francis-crossman10980533
      Adobe Employee
      francis-crossman10980533Correct answer
      Adobe Employee
      March 12, 2018

      What Jim Simon states is absolutely true - do not open the application package to install your own LUT files.  It will cause all sorts of problems including the ones you have already run into.  You'll get burned - don't do it. 

      You should apply LUTs by using the "Browse" button in the drop-down and navigate to the LUT files on disk.  Using this method, Premiere is supposed to actually embed the LUT file into the project file so you can share the project with your client without having to worry about the LUTs.  This will not install the LUTs onto your clients' system for use in other projects, but the project you gave them should work correctly.  If this is not working, that is a bug.  BTW we are aware of the frustration surrounding using custom LUTs and we are working on a fix to make this easier for you.

        L
        LoboAdobeAuthor
        Participant
        March 13, 2018

        Hello Jim, hello Francis,

        thank you so much for your answers. It helped a lot. I reinstalled Premiere and now the LUT embedment worked fine across all our platforms as well as at the clients.

        Thank you!

        all the best

        Petra

          E
          excited_Genie16B8
          Legend
          March 8, 2018

          Adobe recommends not tampering with the program files and folders.  That means the client will need to Browse to the various LUTs used in the project.

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices