P: Label colours appear to have inverted in Premiere Pro

[Molly32590422poa9]

I have opened Premiere Pro today to find all the label colours in my timeline appear to be inverted. The lighter colour is now the main body of the clip and the darker colour is now the waveform. I have tried to go through all the different label group styles. I have also tried uninstalling and reinstalling the application. Does anyone know how to get this back to the default colours. 

I have attached an image of what it should look like and what it looks like now.

[Jcampanale]

One of the most powerful qualities of Premiere is the ability to customize UI, and a HUGE advantage over Resolve. I hope Adobe continues to embrace this advantage and allow us to revert the waveforms in a future build.    

[MyerPj]

I was turning over and over worried about how @alex82lu would 'adapt somehow', and his aversion to 'trial and error' OK, I like the Vibrant color scheme (and the rest) in the new update. But we can't have Big Al going thru trial and error, so here's how to get inverted/non-inverted waveforms. I changed one setting in the Label Color Preferences, from... hang on... Dark Green to... wait for it.... Green!!.

[alex82lu]

@MyerPj  Hey thanks for your comment. So did you manage to revert with "the manual color labeling" that the audio label is not inverted? This is how my waveforms look like - darker background, brigher foreground (the waveform) and currently it is the other way around which I feel hard to work with. I just feel it is better on the eyes this way or at least I would prefer this option but of course it is also a habit. 

 

 

[Glass Amoeba]

Hi,
No unfortunately, the inverted waveform color / 'invisible' selection color issues are still problems even with my original Pantone label color choices restored.  Adobe needs to restore the previous look, at least as an option in a future update. I think that's the only solution. It is indeed very hard to look at. That's why they designed it the other way in the first place over 20 years ago. Mystifying...






Joshua Fong
Leisure Hive Productions
(323) 650-5854
WWW.HAJIRAN.COM

[MyerPj]

@alex82lu , did you see this post:

https://community.adobe.com/t5/premiere-pro-discussions/p-label-colours-appear-to-have-inverted-in-p...

[Glass Amoeba]

Thanks for sending. I did notice that you could change it to light waveform on dark background by altering the colors but I still feel like this is a bandaid solution Adobe is forcing on us.

1) I already have a longstanding color scheme that I use to rapidly identify and differentiate things across projects both old and new. Global changes confuse an established workflow.

2) Though we have a workaround, it limits our palette we can choose from.  I use these colors for things throughout the interface, changing them might help the audio, but make it harder to differentiate folders and clips elsewhere.

It's a good solution for people who aren't married to the colors they have been using but I feel like the best solution in the long run is for Adobe to just recode the interface to let it look the way it used to. 

[R Neil Haugen]

I agree ... but I'm first and foremost practical. So ... posit for a better system, and fix your screen as you can now. Tis Life. Sigh.

[MyerPj]

Well said.

🙂

[Jcampanale]

Is there any change to UI customization in 24.6? 

[Jcampanale]

Selections being harder to discern, and inverted waveforms are the biggets issues for me. Any new customization of those in 24.6?  

[ashearer66]

It'd be nice for users who don't care about the unfixable change to stop
saying "just adapt." That's not how a service should work when you've been
paying for it for years. So if you don't mind the change, stop posting on
this thread.

Instead, it'd be useful for Adobe to offer an option of a TRUE FIX. Bottom
line: the unnecessary new version makes it hard to work. Many of us would
still like the original version exactly as it was. Not a halfway solution.

Looking forward to Adobe getting their act together and actually fix a
change thousands of users are still upset about after months of inquiry.

[R Neil Haugen]

I'd recommend actually reading the other posts here. Without assumptions?

Most of us posting do not like the new changes. Don't make up stuff saying we do. But read the rest of the post. I don't like them anymore than you do. OK?

That said ... first, there are several million daily users of Premiere. Most of whom seem to be ok with, or even like, the changes ... no, I don't undertand that, but then we are all different. In everything.

I'm on several forums, and on one for pro editors ... you have to have your credits & whatnot to get accepted ... a number of the totally outraged folks over this went to try the "vivid" option, as total proof of how flippin' awful and stuuuuupid this whole thing was.

And ... instead found they loved it. Kinda ticking me off because I don't, but then ... again, we're all different.

Would a good chunk of us, like you, want an option for the old look? Exactly ... especially the audio tracks?

Heck yes.

Can you make it not quite so bad, in the meantime?

Yup.

So like I said above this, advocate for change, and try to set your own system so it's less objectionable.  And ... be polite, and respect that all others will disagree with you on most things. As that's Life among humans.

[PG73]

My main issue with the changes is the waveform height, which I don't see anyone else mentioning. As can be seen by comparing the red circles in the image below, the waveform used to go to the top of the track with any text covering the waveform. Now the text is given its own space at the top of the track, squashing the waveform below. This makes it
incredibly hard to see the waveform in detail at the same size it was previously. 

[LuisJaime25]

Yeah this is a good point too.

[R Neil Haugen]

It may not have been mentioned in this thread, but I'd bet if one carefully went through it, you'd find several mentions.

As yes, this is one of the majorly annoying things ... waveforms are smaller on many timelines even IF the track height is the same. I totally agree, an "unfortunate" choice, being polite in public.

[tommy_9536]

Hello, how can I create a new thread about this topic?

[tommy_9536]

Hello, I still have this problem too in the latest version which is 24.6.1.

[DJP2014]

Full height waveforms are still available if you click the wrench icon in the timeline and turn off Show Audio Names.

Obviously audio names can be pretty useful so i've made it a shortcut.

EDIT : You also need Show FX Badges turned off as well.

[MyerPj]

@DJP2014 Looks like and also Show Audio Type Badges.

[tommy_9536]

Since I updated from 24.3 to 24.4.1, the audio waveform label color is inverted and it looks darker. The problem is it is very hard to see and it is very annoying. I became too lazy to edit and did not want to use the Premiere Pro. This is a very big problem because it is still a bug in the 24.6.1 version and needs to be fixed immediately. Please Adobe team fix this bug/issue as fast as possible. Please see the screenshot that I sent below.

[Carlos Ziade]

you can revert back to Classic from Preferences

[MyerPj]

I'm glad my screenshot is working for you! 🙂

[D. Kroll]

I don't use Premiere intensively, I mainly use it for some base audio editing and normally I don't bother with feedback.

But this update is absolutely atrocious. Not only did I have to revert the colours myself, instead of the "new" colours being an other option, but now forcing the new colour upon everyone. Besides this the colours on the work bar are now invertered. 

Before it was easy recognizable if there was an effect on a layer with the green and yellow tick each smartly indicating what happened to the layer. And now, there is nothing!!!

I do not want to spend hours researching how to do the setting correct when they shouldn't have been changed in the first place!!!

And don't get me started on the weird boxes around the Essential Graphics, and the dark colour of Media Encoder.

CHANGE IT BACK!!! Or at least give an easy option to change it back without having to use older versions.

If it isn't broken, don't fix it.