Enhance Speech crashes on some Macs with Intel chips / AMD GPUs

[David Polk]

The below is a fix that is working for some users.

Update: 
To fix the issue described below, upgrade your Mac’s OS to the latest version: Sequoia (15.0).
Go to Settings -> General -> Software Update
More information about Sequoia available here.

This issue effected some users with Mac Intel computers using AMD Radeon GPUs. The bug involved a crash when using Enhance Speech, particularly with longer audio clips. We do not see evidence that this was effecting other configurations.

We are continuing to work on a fix for remaining users still experiencing this issue. Thank you for your patience.

[Michael Grenadier]

derekc87147135,  unfortunately it's not simple.  Webcams usually record heavily compressed and probably a nonstandard sampling rate and bit depth.  Use adobe media encoder to convert the audio to 48k 16 bit aiff (which I think is a standard preset) and I bet your problem will disappear...  bwdik...  Please let us know if that works.  If you need help figuring out the specs on the source file, post back... Happy to help.

[MunchyBugs]

This is not just a Mac or Intel issue. I have a Puget Systems machine with a Threadripper 3970X processor, 128GB RAM, and an Nvidia RTX3090. I have seen this issue several times. No need to involve your partnerns at Apple; its not an Apple issue. It is another Adobe issue with Premiere. That's okay, though, there are still issues from CS6 that crop up so we can all just write this off to Premiere being shoddy.

[55878965]

Thanks, was about to post a bug report. But this sums it up.

[raffi2]

i get the same crash since 3 month no change 

it'z look like latest Beta is hanging this properly now !!

[raffi2]

i fact all crash beta and latest : soon has you clic on enhence audio this crash : a shame 

[raffi2]

It's appenning since several month and accros all the updates …

i lade it work once with goo result, and on the latest beta i was able to make it work once on a fresh account, but it's not htesame good result : very wierd 

[raffi2]

with online enhance speech we get an other translation language which donésent exist !!!!!!!!

[Michael Grenadier]

James5D31, Unfortunately most iphone footage is variable frame rate which can cause intermittent and unpredictable issues..  And is heavily compressed which can also cause problems.  

use mediainfo to determine whether your source is variable or constant frame rate
https://mediaarea.net/en/MediaInfo/Download
if it's variable use handbrake to convert to constant frame rate setting the quality slider in the video panel to maximum or use shutter encoder https://www.shutterencoder.com/en/ which allows you to transcode directly to prores or other mezzanine formats, "First choose a video codec.
Then in the "Advanced features" section check the box "Conform by:" and set your frame rate in images/seconds." from ShutterEncoders FAQ. You want to figure out what the original target frame rate of the smartphone or screen recording was and set to that in the conform dialog.

And I strongle recommend setting your target format to an all iframe format like prores.  Not only will each video frame be discreet, the audio will be uncompressed which will probably hel

Post back if you have any questions

[David Polk]

What is your chip configuration? If it's different from above, then Enhance Speech is re-rendering whenever you make a change, which is normal, for now. If you have longer clips that need to be enhanced, I would suggest considering doing that at the end. Or you can use the "render and replace" feature so that it doesn't re-render. We are working on figuring out a way to make re-rendering unnecessary with this technology.

[Patrick25446950wgnm]

I've found that if I open Premiere, delete all media cache, then open the project I'm trying to complete, it seems to help avoid the crash. That's onluy partially effective, but I was able to deliver some finished work that needed the benefit of the enhanced audio.

[FPS_Fish]

Working away in PremierePro Beta.

Imported some rendered QT footage from Resolve.

Put it in my timeline (as I've done hundreds of times)

Clicked on a clip and ...crash.

Weird. My system is very stable.

Opened project,  clicked on same clip - crash

Opened project,  clicked on different clip - crash

Opened project,  clicked on same clip - crash

Opened project,  deleted imported media, clicked on any clip - crash.

Opened different project - all is fine.

Opened auto-saved project,  clicked on any clip - crash

Tried to open project in non-Beta version - nope. Won't open.

Uh oh.

On an Intel Mac Pro 2019 and read the bug reports about enhanced audio.

Deleted all enhanced audio audio, clicked on any clip - crash

Opened project, got rid of all Resolve media, click on clip...ok!...until the last clip and then crash.

Opened project, managed to delete last clip in timeline, removed all enhanced audio - now all clips are fine.

Everything plays back.

Ah ha! Great. 

Reimport resolve Quicktimes and click on clip  and then crash.

WTF?

[Michael Grenadier]

BrownFish, what is the format of the resolve clips?   

[FPS_Fish]

Quicktime ProRes 422.

[MunchyBugs]

BrownFish, welcome to Premiere Life, aka Crash Life. When projects begin to get beyond the scope of YouTube Shorts, Premiere seems to inevedibally crash and break. Unfortunatly, this has been an issue for over a decade and it doesn't seem to ever get resolved. Once a project starts doing this, Adobe will tell you the project file is corrupted and the only way to "fix" it is to re-import that project file into a new project. They will start by having you clear preferences, clear cache, delete peak files, proxies, etc. After all that, you'll re-import the project file. You'll lose a bunch of work but at least you should still have your timelines. The likelyhoood of it continuing to be unusable decreases, in my experience, from 98% to 55%.

[Michael Grenadier]

MunchyBugs, besides editing primarily long form documentaries, I also provide support for other editors...  I rarely have had any issues on my own projects or while editing for clients.  The only time I can remember serious issues was when working on a client's first generation apple M1 macbookpro a few years ago..  I was able to workaround and the problems that were caused by too early adoption of new technology with the help of people on this forum...     However, I have had to deal with many issues because support clients have dug themselves very deep holes for which they rarely were willing to take responsiblity for...   I've been accused of being an adobe apologist...  but I'm just being a realist as to what's required to be a working professional with extremely complex technology which involves NOT just the software and hardware but also constantly evolving formats...  which can present unanticipated issues.  For example a couple of years ago, sony changed the way their cameras handled colorspace...  Some of the issues my client was having with constant crashes were caused by this...  Both civilian participants here and adobe employees were quickly able to help me discover the problem and the solution.  

I have worked extensively on avid and apple fcp 1-7 before moving primarily to premiere with occasional forays into Davinci Resolve for difficult color correction tasks.   All NLE's have issues and Premiere has been as stable if not more so than any other alternatives...     

[Michael Grenadier]

BrownFish, how much ram do you have on your system?  And what are your sequence settings?   Never easy to diagnose issues from a distance but happy to help and try and solve your problem...

[FPS_Fish]

Ok. I agree that it does seem like a corrupt project.

But I've been using PP for 4 years now and, again, my system is rock solid.

Be it Beta or non-Beta versions, I have rarely had a crash - like once every six months. And they never repeated.

However, I'm in no-way saying your problems are imaginary.

As for this post, I'm just contributing to this bug report in the hopes it might help solve the problem.

[FPS_Fish]

Thanks for asking: 96gig RAM, MacPro 2019 Intel.

UHD 23.976

Nothing out of the ordinary here.

This isn't a new sequence. Or a new project.

I've been working on the for a couple of months now with no issues at all.

I don't easily blame things on bugs in software, but I think it's pointing to a Beta issue.

[Michael Grenadier]

brownfish, so this is only happening with Beta version?  Never a good idea (and not recommended) to use the beta for real work...   Theoretically, you may be able to open the premeire pro project in the latest release version...  but no promises...

[David Polk]

This post has been updated to communicate a fix available in the latest Mac OS (Sequoia) update.

[Richard32672607bxp9]

I'd like to be the first to report that this hogwash and the issue is NOT fixed. I am running Sequoia 15.0, tried enhance speech, and it crashed my computer as before. I urge you to remove your update, change the status from fixed, and ACTUALLY FIX THIS. It's absurd.

[David Polk]

@Richard32672607bxp9 could you please tell us which hardware setup / version of Premiere you're using?

[raffi2]

Sorry but nothing is sorted sequoia doens't adress this issue and it's still crashing for the hundred of times !!!

[Richard32672607bxp9]

Premiere 24.6.1 (Build 2)

3.8 GHz 8-Core Intel Core i7

AMD Radeon Pro 5700 8 GB

64 GB 2667 MHz DDR 4

[mstegner]

@Richard32672607bxp9 

What model Mac is this?  I.E. a Mac Pro 7.1?  Can you post the model number so I can attempt to locate one to test on?