Skip to main content
Participating Frequently
May 3, 2026

The Properties panel only displays the first applied adjustment

  • May 3, 2026
  • 2 replies
  • 57 views

Dear Adobe Premiere Pro Team,

I would like to report a behavior observed in the current Beta version of Adobe Premiere Pro within the Color workspace, specifically in the Analysis panel and its interaction with the Properties panel.

When applying multiple “Adjust” instances within a single clip (e.g., Adjust 1, Adjust 2, Adjust 3), only the first adjustment is exposed in the Properties panel. The remaining adjustments remain active and visually affect the clip, but are not displayed or accessible within Properties unless the first adjustment is removed.

Observed behavior:

  • Multiple Adjustments can be applied and are all active in the clip.
  • The Properties panel only displays the first applied adjustment.
  • Subsequent adjustments are not listed, inspected, or made available in the UI.
  • Removing the first adjustment causes the next adjustment in the stack to become visible in Properties.

Expected behavior:

  • The Properties panel should reflect all active adjustments applied within the clip.
  • Alternatively, a structured stack or list view should allow inspection and selection of each individual adjustment.
  • Consistent representation between applied effects and UI visibility is expected for accurate editing control.

Impact:

This behavior reduces transparency and traceability of active adjustments, making it difficult to audit or manage multiple applied corrections within a single clip, especially in complex grading workflows.

Best regards,
Rodrigo Negrão

 

 

 

Steps to reproduce:

    1. ...

 

Result: ...

Expected: ...

 

System info

    Application: Premiere Pro (Beta) v26.3.0.61

    OS: macOS v26.4.1, RAM: 18,00 GB GB, CPUs (logical): 12

2 replies

R Neil Haugen
Legend
May 4, 2026

First, note my tag line: everyone’s mileage always varies  as we are all different from one another. And so naturally will not agree on things … but should listen to each other.

 

I read through your post and thought about your comments. I understand I think why you might think about this as you do. All very valid points to discuss.

 

Yet, I actually agree with the intended design. Because?

 

In my experience, I believer you should not be doing any major color work outside the Color Mode. Period.

 

Again, why?

 

Because within the Color Mode, you have the new (and amazing) scopes and a clear view of the entire image manipulation chain ...which you do not have in the ECP. Even if all operations were listed at once.

 

Doing any major messing with the image should be done where you can see the full results and implications of your steps. Just working in the ECP, you can’t.

Everyone's mileage always varies ...
Participating Frequently
May 4, 2026

Thanks for your thoughtful reply — I agree with your point about doing color work within Color Mode, and I fully share that approach.

Just to clarify, the behavior I’m describing is actually happening inside Color Mode, specifically within the Analysis panel — not in Edit Mode or the standard ECP workflow.

So this is not about doing color work in the wrong place, but rather about how adjustments are represented within the correct environment.

Even within Color Mode, it’s possible to apply multiple Adjust instances to a clip, while only one is exposed in the Properties panel. The others remain active but undiscoverable unless the first is removed.

This creates a disconnect between the actual image processing chain and what is visible in the UI — even in the context where full control and visibility are expected.

That’s the core concern: not where color work happens, but how reliably the system reflects what has been applied.

Would be great to hear your thoughts considering this specific context within the Analysis panel.

Best regards,

Rodrigo Negrão

R Neil Haugen
Legend
May 5, 2026

I can certainly understand your preference here! So yea, I’d be happy to see them give us the option for this at least.

 

As a matter of the way I work, it wouldn’t be something I’d use ... but then, none of us uses probably more than 10% of the capabilities of any of these apps. And we all use them differently. So setting the UI to allow for the differences is most often a Good Thing.

Everyone's mileage always varies ...
mattchristensen1
Community Manager
Community Manager
May 4, 2026

@Negrão Filmes thank you for trying out Color Mode and sharing your feedback. What you describe is intentional. The idea is that the color controls in the Properties panel in Edit Mode are for quick adjustments while you edit. Anything more complex means you need to switch to Color Mode where the interface is able to display the full complexity.

Participating Frequently
May 4, 2026

Dear team,

Thank you for the clarification regarding the intended simplification of the Properties panel in Edit Mode. I understand the goal of providing a streamlined interface for quick adjustments.

However, I would like to raise a design concern that goes beyond complexity and touches on a fundamental UX principle: state visibility.

In the current implementation, multiple Adjust instances can be active within a clip while only the first is exposed in the Properties panel. This creates a discrepancy between the actual state of the clip and what is represented in the UI.

From a design perspective, this introduces a “hidden state” condition, where:

  • Active modifications are not discoverable
  • The user cannot reliably audit what has been applied
  • The system behavior becomes non-transparent and potentially misleading

This is particularly critical in color workflows, where trust in the image pipeline is essential. Even in a simplified editing context, users need to maintain awareness of all active transformations affecting a clip.

The issue is not the absence of full controls in Edit Mode, but rather the absence of structural awareness.

A simplified UI should reduce interaction cost — not reduce visibility of state.

Potential directions that could preserve simplicity while addressing this:

  • A minimal indicator of multiple adjustments (e.g., count or badge)
  • A collapsed stack representation
  • A clear signal that additional hidden adjustments exist

Currently, the behavior creates an implicit stack without any explicit representation, which can lead to confusion, especially when revisiting timelines or collaborating.

In its current form, this feels less like intentional simplification and more like a break in UI-state consistency.

I believe addressing this would significantly improve reliability and user trust, without compromising the intended simplicity of Edit Mode.

Best regards,

Rodrigo Negrão