Skip to main content
ryano1391910
Known Participant
April 8, 2018
Question

Media Encoder 12.1: custom lut is broken

  • April 8, 2018
  • 17 replies
  • 6857 views

in 12.1 (171), in the "effects" tab on the "export settings" window, when "lumetri look/lut" is checked, I can't choose "select" from the drop down menu. when I click it, nothing happens. !

This topic has been closed for replies.

17 replies

goguvarra
Known Participant
November 4, 2022

So, 

As of 2022 this is still not fixed.

The LUT is applied but it shows as NONE. I can live with that but is there a filed BUG complaint about this where we can vote? 

Writing on the forums doesn't solve anything as the devs are not looking here.

Participant
September 16, 2019

I have to say that LUT's are one of the most annoying things I have had to deal with since our TV production company started using Premiere / Encoder back in 2014. There always seems to be issues with the user interface with them. Anyway I got a fix for this stupid issue which works at least with Media Encoder 2019 / Versio 13.1.3 (Build 45).

 

So the problem seems to be in the User Interface of Media Encoder. When you enable Lumetri Look / LUT in the Effects window and from the dropdown menu click Select and tell Media Encoder where your LUT is located it just shows Applied LUT as None. But the thing is that IF you actually have a working LUT (I have tested this with .cube LUT) it does apply it, only the user interface shows it as None.

 

Here is what you can do:

 

1. Create a new user preset.

2. Apply the LUT by going to Effects --> Lumetri Look / LUT --> Select.

3. The LUT will look like "Applied: None" but it is actually working.

4. Save the preset.

5. Apply it to all the clips that need to be transcoded. They all transcode with applied LUT even though it says that there is no LUT applied.

 

I just tested this with few different clips and LUTs. It is awfully confusing but at least it works.

 

Gotta say that I absolutely hate having to come up with these kind of random fixes to known issues that dont seem to get fixed. Adobe, come on!

Participant
October 16, 2019
what you say is true (vs 13.1.5 - build 35). In fact you only see the .itx files, and when you load a .cube or .look it doesn't seem to be loaded. However the .cube or .look files are not interpreted in the same way as Premiere giving a different result. So I haven't found a way to use LUT correctly in AME .....
estebanf93
Participant
March 29, 2019

Im still having this issue in 2019,

I am able to select a LUT, however when I press open it simply doesn't apply it it disappears?

LeCrapo
Participant
April 15, 2019

same here and very annoying =/

Inspiring
November 17, 2018

Still isn't fixed... why...

Being able to bake a cube lut into a proxy file to get Rec709 out of log footage for offline editing would be nice. Please actually work on this?...

also, I can't seem to roll back to 12.0.0 it's only giving me the option to go back to 11.1.4  ?? super frustrating

rowanb11828946
Participant
October 16, 2018

Still broken, even in the 2019 versions! Incredibly frustrating...

Participating Frequently
September 25, 2018

I also have the same problem. Just updated to the newest version of AME and PP, 2018 still does not work, where as 2017 works fine.

Participant
July 9, 2018

Looks like this is fixed in an upcoming patch release expected very soon. Also little known that you can now store custom or imported LUT"s in your system to be recalled in the Lumetri Panel  - just create this folder and place any LUT"s into this directory in this location -  /Users/USERNAME/Library/Application Support/Adobe/Common/LUTs/Technical

Roei Tzoref
Legend
July 17, 2018
Looks like this is fixed in an upcoming patch release expected very soon. Also little known that you can now store custom or imported LUT"s in your system to be recalled in the Lumetri Panel

bedient can it also be recalled by the effects panel in AME to apply the LUT? because I don't see it there.

Known Participant
July 19, 2018

staff: bedient, 12.1.2 (latest version from a few days ago) does NOT fix this issue !

Known Participant
June 14, 2018

So, it's over two months since topic start and no fix, even no Adobe's member showed up here. Terrific!

Participant
May 10, 2018

Got the same problem on 12.1.1 need to rollback..

collideentertainment
Known Participant
April 26, 2018

Yes. Broken for me too.

V 12.0.0 works though.