Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

Audio In/Out points not visually showing on waveform in Source Monitor — still not fixed

New Here ,
Apr 29, 2025 Apr 29, 2025

I’m beyond frustrated.

This bug has existed for months, and it’s STILL not fixed.
Here’s the issue:

  • In the Source Monitor, when I set In and Out points on an audio clip, they do NOT show up visually on the waveform.

  • The lower bar (time ruler) shows the In/Out points correctly.

  • But the waveform itself — which used to highlight the selected area — shows NOTHING.

  • However, if I reopen an older clip that already had In/Out points saved before, the highlighted area DOES appear.

What does that mean?
The In/Out points ARE being set, but the waveform UI refuses to update.
This is clearly a visual bug with the overlay layer, not a shortcut or user issue.

I’ve tried literally everything:

  • GPU renderer → software-only mode

  • Reinstalled Premiere

  • Reset preferences

  • Deleted media cache

  • Used WAV instead of MP3

  • Updated NVIDIA Studio driver

  • Used NVIDIA Control Panel to force Premiere to use the dedicated GPU

  • Even created a new Windows user account

  • Downgraded from Premiere 2025 to 2024

  • Tested on Premiere Beta

Nothing worked.

Yet when I load an old clip with In/Out already saved, it shows the highlighted area just fine.
This proves the problem is NOT my system. It’s Adobe’s.

I'm using Windows 11 with an RTX 3060. Many others are reporting the same issue online (Reddit, Adobe Forums), and there's STILL no fix or even acknowledgment.

I'm wasting hours of time — this is not a minor annoyance.
This is a core editing feature, and it's broken.

Please escalate this. It’s unacceptable.

739
Translate
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

correct answers 1 Correct answer

Adobe Employee , May 28, 2025 May 28, 2025

Hi everyone, 

This issue has been fixed in the latest Premiere Pro Beta release. Would you mind trying the latest Beta to see if it helps? Please refer to this link to learn more about the Creative Cloud Beta program.

 

Thanks,

Sumeet

Translate
Community Expert ,
May 01, 2025 May 01, 2025

did you try to log out/in creative cloud app? (might be syncing issues)

can you describe your workflow?

are you in production mode? 

are you working on a local machine with local drives?

what if you start a fresh new project with one single audio file to try?

Translate
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
Community Expert ,
May 01, 2025 May 01, 2025

Known issue.

Translate
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
Contributor ,
May 01, 2025 May 01, 2025

Just started having this issue as well. Just updated to Premiere Pro 25.2.3, and problem persists.

 

Working on M1 Mac Studio with Sequoia 15.4.1

Translate
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 ,
May 28, 2025 May 28, 2025

Any fix for this yet?  Also having this issue.

Translate
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 ,
May 28, 2025 May 28, 2025

Hi everyone, 

This issue has been fixed in the latest Premiere Pro Beta release. Would you mind trying the latest Beta to see if it helps? Please refer to this link to learn more about the Creative Cloud Beta program.

 

Thanks,

Sumeet

Translate
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 ,
Jun 11, 2025 Jun 11, 2025

@Sumeet Kumar Choubey The issue is still in the version 25.3.0

Translate
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 ,
Jul 31, 2025 Jul 31, 2025

Just chiming in, also have the same issue. Going to try the beta now, but I find that usually the Betas are even MORE bugged. 

Translate
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 ,
Jul 31, 2025 Jul 31, 2025

Beta solved it for me, but still, not excited about being forced to use unfinished software. 

 

 

Translate
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 ,
Aug 08, 2025 Aug 08, 2025

Thanks for taking the time to share that this issue is fixed in beta! Sorry for any frustration. We'll get it shipped to the official version as soon as possible.

 

Caroline

Translate
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
Engaged ,
Aug 14, 2025 Aug 14, 2025
LATEST

@caroline_editsany reason this fix didn't make its way into 25.4? it's been fixed in the beta versions for months now and was fixed in the 25.4 betas..? I downgraded, then reupdated and now they're working again ignore me I guess lmao. software funkiness

Translate
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