Sam Steti wrote:I also think he uses a LUT as a "look"
That was my impression -- in a lexicon/jargon-loaded work environment, sometimes its hard to sort out what the real intent is for interpreting the language being used. To directly address the issue at hand, if a user is using a LUT as a PowerGrade, the absolutely easiest way to implement trading the look in and out of a correction is to have it in directly addressable memory as a still, Mem, or PowerGrade with the last the most universally accessible across all users and projects.
There are those who use the term "font" when they are referring to a graphic element in a timeline -- whether its a chapter title, lower-third, or whatever... and when they send a revision note something to the effect that "the font at time code such-and-such needs to be changed", I know its probably the wording that needs to be addressed and we're not going to change the letter style, because, you know, text like "Later the rebels returned and massacred every man, woman and child" would read so much better in Zapf Chancery than Helvetica Neue Bold. Not that adding the text "... starting with the youngest." doesn't have a different impact... Yes, we were "fonting" that scene.
LUT as a term has been co-opted, I feel, in the same way and LUTting a grade is a buzz term that does not recognize the correct technical implementation or intent for why the LookUpTable matrix was invented. Originally, it was to transform between display spaces so that working in a native space would translate to multiple release media in a predictable way. But in practice someone will grow fond of any correction applied to anything because its a unique, eye-catching treatment, but whatever floats yer boat.
jPo