Locked

Lumetri is not working

New Here ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

I tried it on adjustments and on clips, tried in different projects, tried to reinstall Premiere Pro - it's not working. Fx isn't the issue. I run out of ideas what I could do else.

Views

145

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

[Moderator moved from Using the Community (forums) to Premier Pro.]



Nancy O'Shea, Adobe Product User & Community Professional
Alt-Web Design & Publishing ~ Web : Print : Graphics : Media

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

Wild guess:

global fx mute.png

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

You haven/t given us any data to do other than guess, unfortunately.

 

" ... it isn't working" just doesn't tell us anything useful. Screen grabs, full details of every step ... what you expected, what happened ...

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

It's now resolved with Adobe specialist help. The issue was the version of Premiere. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

Still no clue what the problem was.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

Please read my previous message to find out 🙂

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

I did. "It's not working" tells us nothing. That you "tried it" on several methods tells us nothing of use. Nothing whatever.

 

What was the media? What is your hardaware? What were you using in Lumetri, and what happened instead of what you expected? With screengrabs to illustrate.

 

Then we'd know what was going on.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

You need more details than the Adobe specialist who resolved the issue 🙂 I find my description of the situation being clear. If anybody has the same issue - try to switch to another version of Premiere Pro. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

Whatever.

 

I'm guessing that whatever the issue was, is due to your hardware if a previous verion solved it. But that''s only a very wild guess, and apparently that's all we can do.

 

I never see guessing as useful in troubleshooting.

 

Now, if it IS an issue of your hardware, then telling us what it was, and specifically, would help others who may have an issue like this. But you seem to prefer to avoid helping anyone whatsoever. Sadly,

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 13, 2022 Feb 13, 2022

Copy link to clipboard

Copied

I thought I made it clear that you can't manipulate me or make me feel guilty for anything like that. But if it wasn't clear enough: please stop doing that, cause I will not do what you want that way. I am always open to help those who need help tho. If anybody needs more details of my situation, I will gladly share it. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 14, 2022 Feb 14, 2022

Copy link to clipboard

Copied

What manipulation? I've simply been trying to understand what was going wrong, that's all. It's why I'm "here". I try to help others, as others have helped me. Some of the other ACPs here have been incredibly helpful to my progression with this app. I give back.

 

And also, I do want to know about issues users are having, as that is the way that "we" can all keep track of the problems that various users may run into, and try to help each other around. Especially with the Lumetri color panel and color management, a specialty of mine. And right now, there's a number of new things, which are confusing users like crazy. And some of the new things are simply broken, awaiting a fix patch. I track these things.

 

You may also have noted that I'm about the only one offering help here. First, well ... there ain't many with more knowledge of Lumetri than me, though of course there are some. So, many of the usual volunteers here do defer to me for Lumetri issues. I'm good at sussing out what's going on, and in general, far more knowledgeable on Lumetri than most any of their typical 'help' Adobe staffers. (Some of the advice on their official help services makes many ACPs simply cringe. Though some are very good.)

 

Second ... when someone asks for help but doesn't give answers to basic troubleshooting questions, well ... there's a tendency to think they're not actually ... helpful. So a lot of the other ACPs here ... and we're all volunteers, you know? ... will tend to skip threads with an "unhelpful" poster.

 

There's no manipulation. Only a sincere and deep want to understand what problem you had. Others may have the same thing. Community knowledge in this stuff is good.

 

Back to your original post ... your post simply said ...  in it's entirety:

 

I tried it on adjustments and on clips, tried in different projects, tried to reinstall Premiere Pro - it's not working. Fx isn't the issue. I run out of ideas what I could do else.

 

Which is why I asked a number of typical, troubleshooting questions to get some information. That's all. Because "it isn't working" doesn't tell anyone what's not working. I can offhand think of a billion things that people have had when they've posted "it's not working" ...

 

Is nothing happening when you touch the controls? Is it doing something other than you expect when you move a control? Is it showing only while paused but not during playback? Is it showing on the clip but not appearing in the export? And with the new color management system, are your clips HLG/PQ or from a Phone or certain Sony & Panny cameras?

 

There's about 50 other things that people have posted here under the "it's not working" phrase over the years. And the "fix" solution you posted ... go back a version ... could also be a way around for quite a number of issues. So even the 'fix' doesn't tell us, nor anyone else coming to this thread later, what was going on and how it was resolved.

 

Neil

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 14, 2022 Feb 14, 2022

Copy link to clipboard

Copied

If you are really trying to help then why are you manipulating? If you want to know more details of my situation, you can simply ask me for it, instead of blaming me in not telling that without being even asked. You were disrespectful, which is crossing the borders, and that has even nothing to do with Adobe and stuff. If you keep sending me "blaming" messages, I'm gonna need to turn the notifications off of this post. Which means I won't even get notified when someone needs my help. Let's don't go that far please.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Feb 14, 2022 Feb 14, 2022

Copy link to clipboard

Copied

LATEST

Elena, I am distressed at your responses, as there hasn't been any intent on my part to cause issues. None. All of us "regulars" here want you and anyone else to find this place a useful tool for getting around this complicated and complex app. Please understand, I've not intended one bit of the ... it seems emotional content? ... that you seem to have taken.

 

I simply ask that you read this post, and think a bit. Could you be mistaken as to my intent? In an ideal world we'd get to sit down with a cup of beverage and learn from each other here.

 

Because, again, It's most unfortunate you are upset with me. And seriously, I have no clue whatever as to what you're calling "manipulating" ... just none. Again, I'm sorry you feel this way, but I can't find any trace in this thread. So perhaps a bit of explanation might be useful.

 

I care about clarity, and getting accurate information. That's all. And in this thread and hundreds of others I've been part of, I ask questions only because the answers might be useful. Sometimes for my sussing out a problem, and sometimes because I know, with the answer to a particular question, one of the others around here will know the solution to the problem.

 

It's all about sharing data in enough detail to help each other figure out problems. And at times, finding the right person to help with an issue. For example, I know the Lumetri system in great detail. But ... H.264/5 encoding and that sort of thing ain't my bailiwick. But there's a couple other helpers here that have amazing knowledge of those processes. I can ask a question and 'ping' their username, and probably get them to come on with an answer.

 

But I give data or ask questions, never to irritate or attack, but only to get potentially useful information. Because I do care about all users being able to find these forums a place to get answers for the problems this app can give us.

 

Reviewing this thread, I've a couple comments to add.

 

Your comment just now ...

"If you want to know more details of my situation, you can simply ask me for it, instead of blaming me in not telling that without being even asked."

 

My first post ...

 

" ... it isn't working" just doesn't tell us anything useful. Screen grabs, full details of every step ... what you expected, what happened ...

 

This seems to me, to be a rather direct, simple request. One I and many others have posted in near identical phrasings hundreds of times on this forum. There's no blaming there or criticism intended, simply direct information. I noted that the original post wasn't useful for troubleshooting, and asked for specific things that would be.

 

So it seems to me, I asked rather simply, directly, without any emotional baggage for information at the beginning. Again, I am sorry you're upset, but for the life of me, I've no idea why.

 

Several other 'regulars' here look at posts like the first one of this thread, and reply with only a link to the FAQ on how to ask for help here. So the "OP" ... original poster ... has to go to that link to see what data they should come back and add in another reply. Would that have been a better response to you?

 

And another post from me ...

 

What was the media? What is your hardaware? What were you using in Lumetri, and what happened instead of what you expected? With screengrabs to illustrate.

 

Again, these seem to me to be simple, direct and to the point questions. I can't see what was wrong with them, and would dearly love to know where you found a problem.

 

And also note ... I sign my name on every post. I don't like forums where people post anonymously as that so often allows people to go full-on nutso on each other. I go to NAB every time they hold it, and meet many other users that post here and of course staffers. So, me, personally, is "here". Publicly so.

 

And in person at NAB and Adobe MAX. In every forum I participate in, my avatar is my face. People see me at an event and know who I am. I treasure civility and collegiality, and love to meet in person everyone who I can whom I've 'met' here. It's been amazing how many people come up to me in the aisles at NAB and MAX and say ... "Neil ... I finally get to meet you!". Which is always a huge joy for me.

 

Everybody I've ever met handles video post issues differently than everyone else. It's fascinating and fun to get to know people, their workflow, and the way they do things. It doesn't matter how much or little experience you have, there's something that I can learn from you. Besides some things I can help you with.

 

Neil

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Feb 14, 2022 Feb 14, 2022

Copy link to clipboard

Copied

Hi Elena,

I am so glad you sorted out your issue and that our support staff was able to assist you. Cool!

 

FYI: these are largely user-to-user forums and there is a great deal of value in explaining a solution to your issue in detail so that others experiencing your same issue may also be able to find a solution. I think that was what your colleague was asking about and caused this misunderstanding. Of course, editors are under no obligation to provide case details. That decision is up to the individual as to whether they wish to share those with us or not. That said, your fellow editors really appreciate your input into finding solutions for various problems with editing.

 

Sorry for the issue and the misunderstanding with our forum volunteers. Good luck with your project.

 

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 14, 2022 Feb 14, 2022

Copy link to clipboard

Copied

Hi Kevin,

I am always open to help and provide more information that can be useful for others. I just need to hear the questions to know what information I should share, since my situation seems clear to me 🙂 

I think I had to mention that "not working" means the whole Lumetri Color workspace was not reacting to any of my actions. And as I mentioned before, that was fixed by installing another version of Premiere Pro. Because I had the "developer version" which has that bug (if I got the specialist correctly).

If any questions are coming up to you, feel free to ask 🙂

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines