P: Transcription Crashing Premiere version 25.1.0 build 73

[rachelcenter]

transcription still crashing latest version of premiere version 25.1.0 build 73. Can this be fixed? This was happening on the first release of pemiere 2025 and i think a really late version of premiere 2024.  Mac os sequoia 15.1.1, Apple M2 Ultra, 128gb ram.

mod edit title for clarity

[rachelcenter]

transcription keeps crashing Premiere 25.0.0 Build 61. does anyone else have this problem? I had this issue too right before I upgraded to version 25.0.0 (build 61). I'm on mac Os seq 15.0.1.

apparently it crashes beta as well.

[Kevin-Monahan]

Have you tried a brand new project, @rachelcenter?

Thanks,
Kevin

[rachelcenter]

no because I'm working off of a project that someone did the 3 hour footage sync for me. if I take this entire project and drag it into a new project, does that count as a new project? because I can try that

[rachelcenter]

so far so good

[Kevin-Monahan]

Yes, it's roughly the same as trying it with a new project. For sure delete the media cache since it's a new version.

Thanks,
Kevin

[rachelcenter]

nevermind it just crashed again

[Kevin-Monahan]

Did you delete the media cache?

[rachelcenter]

Yup! over an hour or so ago when you told me to.

[Stan Jones]

@rachelcenter,

Sorry you did not get a response to your earlier post. Since you were getting this issue in the previous version, I would start with a brand new test project with one clip from the previous project.

Also, when updating any version of PR, but especially a new point release (i.e. 25 over 24), I completely wipe the preferences and caches. If you reset preferences without being prepared, you can lose customization. See this page to avoid those problems:
https://helpx.adobe.com/premiere-pro/using/reset-preferences.html

When you start PR, hold the shift key down and reset preferences and cache.

To test your transcription issue:
• Create a new test project,
• In the create new project screen, be sure that "auto-transcription" is turned OFF.
• Add one clip,
• In the Project Panel, right-click and pick Transcribe
• Click Transcribe
What happens?

Stan

[rachelcenter]

I will try to troubleshoot this if i can find a free moment this week, it may be another week til I have freetime. Adobe should offer a button that lucid link offers, called generate diagnostic report, where I can send a report to your team to see the code in order to figure out why its crashing.

[Stan Jones]

Are you getting a crash report that allows you to put your email address in? If so, do that and staff can look up the report from your email address. If not, there may still be log files that staff can point you to that may be useful.

Stan

[rachelcenter]

yes i've filled out my email address plenty of in the past few days but I never hear back.

[Stan Jones]

Staff are more likely to ask when they are working with you on troubleshooting an issue.

I can't look up some of the information at the moment. I am displaced because of the hurricane affecting Western North Carolina, and I forgot to bring my laptop back when I went home today briefly. One more thing to add to feeling out of sorts!

Stan

[rachelcenter]

stan, wiping the preferences is such an ordeal. I did it a week or two ago when I had other premiere issues, and it's such a pain to put everything back to how I had it. I don't have auto transcription turned on. I dont have the free time right now to do the clip one by one, but I suspect that LONGER transcriptions could possibly be crashing it.

[Stan Jones]

I totally understand. The point of the single clip project is a test, not a suggestion that you do it this way for your regular project.

Skip resetting the preferences, but close all projects, close premier, create a new project, set it to captions and graphics workspace, and if that is what you use, reset to the saved layout. Then add the one clip and transcribe.

Part of the goal here, is to simply determine whether it is all transcriptions or only some that are the issue. Completing a single clip transcription does not rule out a bug, but gives us some direction on what sort of problem maybe involved.

Stan

[stevenprobets]

Yup same here! Really frustrating

[stevenprobets]

I have this issue. Latest 25.1 version. I cleared caches and made a new project and it's still happening. Mac OS 15.1.1 64Gb RAM M1 Max.

[Kevin-Monahan]

Thanks for writing in, @rachelcenter. Thank you, @stevenprobets, for alerting us about the bug, as well. I hope an engineer will respond shortly. Sorry for the frustration.

I wonder if anyone else in the community has seen this bug. @Stan Jones, have you come across this one yet? Sorry folks, I hope they can get this fixed for you soon.

Cheers,
Kevin

[Stan Jones]

@rachelcenter and @stevenprobets,

Thanks for the responses in the old thread:

https://community.adobe.com/t5/premiere-pro-bugs/transcription-keeps-crashing-premiere-25-0-0-build-...

I am back home, but I am still stumped by your problem. I am not experiencing this with 25.0.0 (or previous) and not in Beta 25.2.0.44. (I am on a project and have not updated to 25.1.0 yet.)

I am still unclear what exactly happens and when, and whether it happens every time or only sometimes.

Rachel,  you got bug reports and sent them back with your email address; Steven did you?

Steven, is it an actual crash for you? And for both of you, when does it happen: immediately on hitting transcribe in the transcribe dialogue, or only after some time of processing?

@Kerstin Ebert @alexander-riss 

Stan

[rachelcenter]

"I am not experiencing this with 25.0.0 (or previous)", stan is your experience on a mac or pc?

[Stan Jones]

@rachelcenter,

Sorry; meant to say. Win10.

Stan

[rachelcenter]

please test it on a mac. i've had adobe confirm known bugs that were only
showing up on mac not pc

[Stan Jones]

> i've had adobe confirm known bugs that were only showing up on mac not pc 

I'm PC only; staff or another helper will test on Mac I'm sure. This is a bug that has been hard to replicate, so I report what I'm seeing to help rule in/out issues. And my apologies again for not noting that I was testing on Win 10.

Stan

[rachelcenter]

but we cant rule out the bug if testing is only done on PC and issue is on Mac.

[Stan Jones]

> but we cant rule out the bug if testing is only done on PC and issue is on Mac.

Totally true. But we don't know that it is Mac only. If I replicated the problem on Windows, that would be helpful information. Of course, we can't completely rule it out on Windows just because I couldn't replicate it. 

But it points to Mac.

Stan