Copy link to clipboard
Copied
I'm suddenly unable to import .srt files into Premiere Pro; I get "the importer reported a generic error." I've tried these things:
I've had this error with more than one .srt file and in more than one project. I'm on a PC, Windows 10; Premiere is up to date.
I found an old thread where someone said that they solved the problem by deleting .xmp files but there was no explanation of how to do that and haven't been able to find an answer on Google.
I am on Mac and PPCC 23.1.0
created my own SRT with ScriptEditor, got the same "generic error". in my case the line breaks were the problem too.
SOLUTION:
downloaded BBEdit on the App Store (free for Evaluation)
imported file, clicked Text > Normalize Line Endings
saved the File with "save as..." with Line breaks: Unix (LF), Encoding: Unicode (UTF-8)
Thanks to everyone in this thread, especially @Stan Jones , I couldn't have solved this without the community!!!
Copy link to clipboard
Copied
I encountered a similar issue and discovered a straightforward solution. I modified the file's extension from .srt to .txt, saved the changes, and subsequently reverted it back to .srt. Afterward, I successfully re-uploaded the file to Premiere Pro. This method proved effective.
I hope this does the trick for you!
Elke Fleurackers
Copy link to clipboard
Copied
i give it to chat gpt and he fix it
try that if you had that problem now
Copy link to clipboard
Copied
Hello. I had the same "generic error" message trying to import a .srt file with Ukrainian fonts. I work on Adobe Premiere Pro 2024 and a MacBook Pro 2018 OS 12.7.6. I eventally found a work around that coud probably be useful to others. I duplicated another .srt document in English with latin fonts working fine and kept only the first line. Then I copied-paste the text from the ukrainian document without the first line and it seems to be OK. Probably the new document kept the original category of fonts in English and used it for the new ukrainian ones.
Copy link to clipboard
Copied
Thanks for reporting your workaround. Always amazing options.
I suspect the actual fix for some of the workarounds is a change in the UTF encoding.
Stan
Find more inspiration, events, and resources on the new Adobe Community
Explore Now