New Audio Speed/Duration is good, but rendering required files on playback very flaky, buggy, keeps crashing more often than not

​@Heiko-Brantsch Thanks for sending us a test project with that WAV. I didn’t run into trouble changing its speed in your sequence, either with the media online or offline.

Offline media is still represented by clips in the sequence, with their speed settings and other timeline relationships intact. So taking media offline isn’t the same as removing those clips from the audio-render path. If you relink the media, those sequence settings are still there. So while it seems odd, it’s intentional.

When I opened the project, Premiere reported a missing video filter called Renoiser, and a missing audio filter: 3:cd4ca2f2 9849ac 439bb9 1cb96a. The audio filter could be relevant trigger, but we can’t identify it from that ID. On my system it wasn’t available, so my test won’t have the exact same audio processing as yours.

1) Could you tell us the filter’s name and version, and whether it’s applied to the voice clip, an audio track, the master, or a nested sequence?

2) In a copy of the project, could you bypass just that audio filter and test the same speed change in the main sequence? You could even SHIFT launch Premiere and just have it temporarily disable plugins

3) Also, in a duplicate of that sequence, remove the other audio clips, not just take their media offline, while keeping the affected WAV and its speed settings. If that avoids the crash, add the other audio clips back in groups to see which may trigger it and what might be on that.

4) When all media is offline, what exact action or progress indicator shows that audio is rendering? A short screen recording of that state, with the Progress panel visible if possible, would help. Please also share the exact Premiere build you tested.

5) Fully close Premiere and relaunch cleanly, and open the project again with out opening the crashed project from your recording. If that doesn’t work, can you send us the project that is listed  (project: P&G-Cube-ONE-Edit-4-86741748-0ab4-a019-858a-6
 

Thanks for helping us narrow it down,
Katie

Sometime instead of a full-on crash I get this error: 

wow first of all thank you for the very fast response!

no unfortunately I wasn’t patient enough to type my work email in every single time, but I will do so, then you can track all the necessary information. Or I can upload you my crash logs, to a drop box, I already did so for a separate unrelated issue.

Both versions of Premiere I have installed each are the newest built as I tried reinstalling both today.

Mac OS Tahoe 26.7.2 on MacBook Pro with M4max CPU.

The file that was causing the crash with the speed change was a .wav 48khz.

I recall that I never had this problem in Premiere 2026 but I do have it in both 2027 and the current beta to varying degrees.

specifically this project I’m currently working on still has the export failure that I worked around via xml export after many failed attempts so it’s still reproducible anytime on this machine.

Everything is run from the internal SSD. 

The Macbook is MCM managed by my company.

Hope that helps narrow it down a bit?

Hi ​@Heiko-Brantsch 

Thanks for stopping by the Premiere forums and giving us those details about the crashing with speed change on clips in both v27 and Beta Premiere. Appreciate that screen recording as it was helpful to see exactly what was going on.

If you are getting crashes with the crash report dialog box popping up, you can enter your same Adobe related email in the blank before sending, then let us know what that was in a DM, so our engineers can look up that specific report. Let us know if that’s happened already, or keep an eye out if it should crash again.

We ran a few quick tests in both versions of Premiere and were currently unable to recreate the issue, so wondering what else might be missing from the equation. We’d like to get some additional details about your setup to help better troubleshoot.

Noting you’re using both the latest 27.1 Beta Premiere and v27 recently released Premiere with this issue. If able, it might be helpful if you tell us which build precisely they both are by going to Help > About Premiere or Premiere > About Premiere.

For those versions, there is now an ability to change ‘Mode:’ as rendered medium, high, or legacy. I see yours was on High, and does changing that affect the outcome or same crash type issue? I tried out all the modes, just in case, but all 3 were working as expected.

Questions about your setup:

• Setup/OS: Please specify Windows 11/10 or Mac, plus what macOS, along with driver version/build.
  • GPU Driver version/build(Windows only): We recommend updating to the most recent version; for NVIDIA users, we strongly recommend the Studio version of the driver.
  • Mac Chip (Mac Only): what M-series chip? If Intel, please include GPU.
• Media Files: video, images, etc. and what types (can check under Media Properties)
• Project Size: About how big is your project file? Is it in a Production or Multicam? Approximately how many clips are involved in a rough estimate
• Media Storage: Are your Scratch Disks set to your Documents folder or the same as project, and is this the same as the Media drive?

Also, please let us know the following for helpful context:

• Does it affect all projects or only some? What about new projects with a few sample clips?
• Do you recall which Premiere this was last working in, when It started, and what might have changed? Any plugins, OS update, drivers, etc.
• Are you also using third party plugins and/or extensions, and if so, which ones and are they currently up to date?

Let’s start there and hopefully we can narrow this down to see what else might be happening.
Sorry for those troubles, and we do hope to help!
Katie