Skip to main content
ThioJoe
Community Expert
Community Expert
November 30, 2025

Audio cuts out for short period when beginning shuttling in v25.6.2

  • November 30, 2025
  • 2 replies
  • 267 views

Since updating to Premiere 25.6.2 last week, I immediately noticed that shuttling (playing at 2x+ speed) causes the playback audio to cut out for a short period.

 

To reproduce (at least on my system), specifically while playing back at normal speed, upon pressing the shuttle right hotkey to play faster, that is when it cuts out. It will also cut out if the shuttle key is pressed again while already shuttling to further speed it up.

 

It does NOT happen when:

  • Beginning normal playback at normal speed, even if the 'shuttle right' key is used to start playing (pressing the shuttle key from a stopped position just plays regular speed). It's only if transitioning into true 'shuttle' speeds.
  • It also does not happen when "maintain pitch while shuttling" is disabled

 

Some notes:

  • I do not recall this happening prior to 25.6.2, and I would have noticed it because it's quite obtrustive to my workflow where I use shuttling extensively.
  • It also happens in the 26.0 Beta
  • I tried it in a virtual machine with a more fresh installation of Premiere 25.6.2 and it still does it.
  • I recorded the system audio to see how long it cuts out for, and it seems to cut out for exactly 125ms every time.

 

These are my audio settings:
866964iEC6338E3B41741B1.png

866965iAF74A67334F3BBF6.png

 

I also tried changing the latency but it doesn't seem to have any effect. But again this didn't happen in prior versions so I doubt it's just down to my settings.

 

I'm using "MME" device class in the audio settings as you can see in the screenshots. I tried switching to ASIO to see if that would help but I couldn't figure out how to get that to work at all (it was not outputting any audio) so I gave up on that.

 

Windows System Info:

  • Premiere Pro Version: 25.6.2 (Build 1)
  • Windows Version: Windows 11 Enterprise 25H2 (Build 26200.7296)

 

System Hardware:

  • CPU: Intel 13900KS
  • GPU: Nvidia 5090 FE
  • GPU Driver Version: 581.57
  • RAM: 128GB
  • Storage: NVMe SSD - Optane 905P 1.5TB

2 replies

Community Manager
December 18, 2025

Hi @ThioJoe , thanks for letting us know. We introduced a fix for a long standing bug where you could hear a loud "pop" noise while playing via JKL. There is in fact a 100 ms ramp (fade) to prevent this issue. We will share the feedback with the team and keep this thread updated. Thank you!

ThioJoe
Community Expert
ThioJoeCommunity ExpertAuthor
Community Expert
June 8, 2026

@Adolfo H.  Appreciate the insight. I think then there might actually be a bug in the intended fade/ramp you describe.

 

I used Audacity to generate a constant sine wave file to be able to more exactly see the times involved. As you can see the fade/ramp in fact only lasts about 5 milliseconds, the rest of the gap is silence and lasts exactly 123 ms every time, on my system at least.

 

(There also seems to be some kind of almost-zero audio for 42ms after the 5ms fade out, and and for 5ms before the 5ms fade-in, not sure that’s relevant.)

 

So basically it fades out over exactly 5 milliseconds, has a huge 123ms gap of silence (which is the obtrusive part), and then fades back in over 5ms again. As opposed to a ramp that lasts 100ms which I assume is what was intended (which seems rather long in the first place, I'd imagine even 5ms ramp would be sufficient, without the huge gap of course).

 

And to be clear I didn't stop and start playback here, the gap occurred when I was playing the video normally, and then pressed the shuttle key once to make it play faster.

 

Additional Troubleshooting:

The timeline FPS doesn’t seem to make a difference. I tested it on a 59.94 fps timeline and a 1000fps timeline, and it’s the same 5ms ramp and 123ms silent gap. I also tested changing the device sample rate from 48 KHz to 44.1 KHz which made no difference in the gap or ramp time.

 

However I did notice a difference when I changed the “Latency” value in the Audio Hardware settings (I am using Windows MME). Setting the latency to 30ms it became a 111ms gap of silence. At 500ms it is a 158 ms gap. Same 5ms ramp for both. So it could be related to how the ramp and delayed speed change interact with Windows’ audio buffers.

 

Also for what it’s worth, I never really experienced the pop when shuttling before. And like I mentioned, I personally think a 100ms ramp (assuming it were working as intended) is unnecessarily long. Probably only a few milliseconds would be sufficient.

Community Manager
June 8, 2026

Thank you for this info!!! I’m sending the post to one of our QE’s to take a look. Really appreciate the amazing and thorough feedback. I’ll keep you posted once I hear back from our engineering team.

Cheers! 

Community Manager
December 1, 2025

Hi @ThioJoe

 

Thank you for reporting a problem and for all the information provided. 

 

I can reproduce on my end and will let the team know. 

 

Sorry for the frustration, 

Dani