A low level exception occurred in adobe premiere что это

Обновлено: 07.07.2024

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.

Adobe Support Community

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Home
Premiere Pro
Discussions
A low level exception occured in Lumetri Color (AE.

A low level exception occured in Lumetri Color (AEVideoFilter) /t5/premiere-pro-discussions/a-low-level-exception-occured-in-lumetri-color-aevideofilter/td-p/10026432 Aug 25, 2018 Aug 25, 2018

Copy link to clipboard

The error "A low level exception occured in Lumetri Color (AEVideoFilter)" keeps appearing in every projects, and it prevents me from exporting my videos (Error compiling movie). Looking at the error tab, there is a long list and the time stamp where the error occured. It's written "(AEVideoFilter:13)"

I'm using windows, Premiere pro 2018 (ver. 12.1.2).

The error doesn't appear when i use another laptop.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

That means that either you've a video driver issue or there's something "off" in the sequence at that time-stamp of the video.

As you didn't give any information on your computer . OS/CPU/RAM/GPU/vRAM . it's not something I can make a detailed guess at.

If you have your project settings for Mercury Acceleration set to anything but Software only, set that to Software only. Which is of course only an option if you have a dedicated GPU unit.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

OS : Windows 10 (64bits)

CPU : intel core i5-6198DU, 2.40GHz

GPU : Intel(R) HD Graphics 510

I can't find how much vRAM i have sorry.

I can't even change to software only, it doesn't let me click on it, it's like the option is locked.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Well . that's such a low-power computer I'm stunned PrPro is running at all. Two very slow cores, half the "minimum" RAM, that's sadly an under-powered computer for this application.

And with that setup, the reason it's locked on Software Only is you don't have a graphics card, just the onboard graphics chip. Which is a rather low-powered unit for an on-board graphics chip.

To work with Premiere Pro, a rather complex app, you'd need a fair amount more power than your current computer can provide. I don't know any way around it.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

As Neil mentions, the procedure to solve this error is to disable the GPU acceleration.

But you have an integrated graphic, and it gets a little complicated, you have only 4 gb of ram, that you will have about 3 gb of ram due to the graph, I do not know the resolution and size of the project but already the available memory is little.

You can try the following,

Update the Intel drivers.

Clean the cache folders:

Disable any unnecessary process that consumes memory, antivirus, firewall, etc.

Make sure you do not have images larger than 15% of the size of your project.

Start the program as administrator:

right click on "Run as administrator"

Test, if the problem persists, add more ram and a dedicated graph.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Hi. I am having this issue with the 2019 Pr on a 2018 MacBook Pro i9 with 32g of RAM. The video in my sequences will not play, and the app will not close without a force quit. I exported the XML's and reimported to Pr 2018 and now I am having some issues with Lumetri, but I am able to continue editing and the program runs well.

I have an older iMac (2017) that handles the seq. just fine, but there is not enough RAM to play smoothly through all the footage, so I would like to work on the i9 laptop. Any thoughts?

Could this have anything to do with the installation of Red Giant color suite? Thank you in advance.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

What is your GPU, what settings do you have in Project Settings/General/Mercury Acceleration?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Mercury playback engin GPU Acceleration (Open CL)

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Have you tried Metal? I know that Apple is moving their OS to that rather than OpenCL.

Also, software only might get you working.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Changing the Mercury playback engine did not do anything for me. I think it is strange that the only to close the program is to Force Quit. 2018 is jamming along, but I would like to get the new version up and running. Do you think it is worth trying a reinstall?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I can't see why not. Takes maybe 15-20 minutes to download the Adobe CC Cleaner Tool, use that to uninstall and remove traces of PrPro, reboot, and download/install PrPro again. And often can fix this sort of thing if it isn't a driver or hardware conflict issue.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Hello. The error ‘’a low-level exception occurred in AE.ADBE Lumetri (GPUVideoFilter::GetFrameDependencies)’’ appears every time I try to export my project and it happens exactly on 49%. The only way to close it - is to use force quite button. I have been trying to fix this error by myself for a whole month and also I changed 19version to Premier pro 20 but it does not help. I use Mercury Playback Engine GPU Acceleration (Metal).

There is some information about my computer:

MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)

Processor 1.4 GHz Quad-Core Intel Core i5

Memory 8 GB 2133 MHz LPDDR3

Graphics Intel Iris Plus Graphics 645 1536 MB

VRAM (Dynamic, Max): 1536 MB

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

So what is happening at the point in the sequence where it chunks? Have you tried exporting up to that, and after that?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Im having a issue in adobe premiere where i cant't add text to video. I have a intel i7 8 core processor with 32 gb of ram and a 1050 ti graphics card and my card is only a couple months old. I have tried cuda and mercury acceleration and nothing is working. I even rendered out the project and still cant add text in a new window

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Could give us more details of his problem.

I recommend that you see Adobe's help on titles.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

This is a very different issue and should have been a new thread.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I am having this issue as well and it has put a halt on the project as I can not even Render the timeline. I tried starting a new Project and

importing the old project. I also cleared the Cache and miss the option in the Project Preferences to clean the cache directly.

I took the LUT off the clip in question and tried to render it again but the time line still had Lumetri effects throughout.

I wonder if I need to install the LUTs directly in the Adobe Application folder as opposed to external location when using them.

I can not proceed at this point and need help, please!

A low-level exception occurred in:Lumetri Colr (AEVideoFilter:11)

Mac OS Sierra 10.12.6 Mac Pro (Mid2012)

40 GB Ram Memory

NVIDIA GeoForce GTX 6980 2048 MB

Premiere Version 12.1.2 (Build 69)

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

My issue was with windows and they said it was a windows user error so i would call adobe tech support and see what they can do since you have a mac

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

It is an error that has occurred in several versions of the program, and the cause is not known, or at least I do not know.

However, I risk suggesting the following:

Go to Edit> Preferences> Media and remove the checkbox before the item: enable Intel h.264 decoding (requires restart), or (12.1.2) Enable hardware accelerated decoding.

then restart Premiere and try, and we see the result.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Thanks for the info. there is no such checkbox on the panels mentioned on Mac for Pr CC 2018 that I can find uner Preferences or Project settings.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

So this morning I deleted all the Media Cache Files in the Common Folder and opened the copied Sequence in the new Project I created and tried to render the timeline. It FAILED again with the same Error Message. I then tried to export the Sequence using Match Sequence type and again it FAILED this time with a similar error message about Software Render Error. I had changed my Preferences earlier when opening the project to Software only eliminating Cuda and other options and still getting a failed project output. I'm pulling my hair out. never seen this difficulty before.

I could not find the checkbox in Media regarding H.264 on my Mac Premiere menus as mentioned by Juanmario. Preferenced or Project Setting did not reveal this in CC Pr 2018.

I tried contacting Adobe-Santa Monica office nearby, but no direct line. I left a voice message for Van Bedient and have not heard back at this point. I'm drowning in this project and can't get it done.

Any further suggestions will HELP!

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Same Here ! but i find that delete Luts folder (with my personnal luts) in C:\Program Files\Adobe\Common run premiere, close premiere and re-copy same luts folder in same path sometime resolve the problem….. this bug is long time ago, the other way i found is to use colorista to Apply lut and that run at 100%, thank you adobe and lumetri!

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

You're putting LUTs into the Program folder? NOT recommended, can screw you up, and doesn't work that well.

Here's the place to put your LUT folders/subfolders so that they work from the appropriate drop-down lists in Basic and Creative tabs across Ae, Pr, Me .

When you get down the folder-tree to the LUTs folder, you then need to create folders named Technical and Creative. Park your "Basic" tab LUTs in the Tech folder, your Creative tab LUTs in the Creative folder.

Relaunch Pr, and your LUTs should all appear mixed in with the included LUTs/Looks in alphanumeric order. Which is why naming your own LUTs can either group them . or move them to the top of the list for quicker access.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Thank you Neil for your answer but i know what you explained, the only right solution for me is to use Colorista IV because premiere have bugs with lumetri and luts. So i strongly recommend for everybody to use Colorista to work normally without aleatory lumetri bugs.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I work with LUTs in Pr every day .. without issue. I use them less in the Basic tab's input slot, as realistically, any tech LUT for normalizing say LOG material should be processed following the application of the tonal controls in the Basic tab . such tech LUTs are "built" carefully using the perfectly exposed, contrast, and color-balanced camera/lighting setups of precise studio work.

Real media is never that precisely and tightly controlled, so as Van Hurkman and about everyone else (including camera manufacturer's) teach, you install a tech/conversion LUT in the viewing chain, then correct the media into that LUT with corrections prior to the LUT itself.

In Pr, that means using the Creative tab slot, and using the Basic tab to make the necessary corrections to get a neutral tonal image through the LUT . and ready for further work.

This is how DaVinci Resolve works . apply a LUT to a node, and it is applied after any corrections applied to that node.

As slickly as multiple Lumetri instances work now, this isn't an issue. It's pretty easy to 'normalize' via the Creative tab's slot, use the Creative Tab's shadow/highlight "TINT" controls to do the color-balance/cast corrections, the rest of that instance to bring the clip into balance with others . especially with the shotmatching step in the Color Wheels tab.

Then use another instance of Lumetri if you need more corrections to a clip.

Then another for "Look" purposes. Perhaps using another LUT/Look applied in that instance's Creative tab, modified with the intensity and other controls of the Creative tab.

Not that Colorista isn't a particularly cool and effective tool . with a nifty interface too! .

Welcome to the Community!

We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.

Adobe Support Community

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Home
Premiere Pro
Discussions
FAQ: How to solve low-level exception error after .

FAQ: How to solve low-level exception error after updating to Premiere Pro 14.1? /t5/premiere-pro-discussions/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/td-p/11050854 Apr 15, 2020 Apr 15, 2020

Copy link to clipboard

Update: Solution: Update to Premiere Pro 14.2

Need to remain on 14.0? You may install Premiere Pro 14.0.4 from Creative Cloud Desktop app to continue using Legacy Titles with GPU Accelerated Renderer. Here is how to download the previous version of Premiere Pro.

We have identified that using GPU Accelerated Renderer might cause a low-level exception error to appear in Premiere Pro 14.1.

These errors might appear:

While using Auto Reframe with the nested clip option. Auto reframe works fine, so you can simply ignore these errors.
While using the Legacy title . To workaround this issue navigate to File > Project Settings > General and set the Renderer to Mercury Playback Engine Software Only.
Switching Renderer to Mercury Playback Engine Software Only.
While playing back the media (A low-level exception occurred in: Adobe Player (Player:5)).
In this case, try clearing the media cache and check if it's working properly. If you are still experiencing the error, switch the Renderer to Mercury Playback Engine Software Only.

Hope this helps in solving the issue. Let us know if you have any questions. To know more about the known issues you may refer to this link.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I'm having the same error, but I'm not doing using nested clips.

NVIDIA Quadro M2000M

Video Driver 26.21.14.4274 Dated 3/13/2020

I've cleared cache and changed renderer to Software only. The video now appears, but so does the error.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I'm having the same issues, but I get the error message when playing back ProRes422LT media in multicam sequences. Both the individual and multicam clips play properly, but those clips within a sequence will only play when the renderer is set to the CPU rather than GPU. (Resetting preferences and clearing the media cache make no difference.) When I uninstall 14.1 and revert to 14.0.4 everything works nominally.

Intel i9-7980XE on MSI Gaming Pro Carbon, 64GB RAM, Samsung 960PRO X 2 (One system & programs, one media.)

NVIDIA GTX1080Ti X 2

Studio drivers: 442.19 (02/03/2020)

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I started having this problem after I built a legacy title in my project. I've cleared the cache and changed the preferences, but the After Effects files I've brought in are now "missing/offline." I have many small icon animations in my timeline that I then customized in Premiere. How can I link them again without redoing the work?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Great. clearing the media cache did not work. Switching to Mercury Playback Engine Software Only worked, in that I was able to get the media files to load, but it takes more than 10x longer to render.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I had this exact same issue. 12 hours to render a 5 minute video! I switched back to previous version and rendered in 5 minutes and did not have to change the Mercury settings.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I have the same trouble and I've done clear the media cache and switch to Mercury. only.

It's just impossible to work!

Can I back to an aolder version? I can't work in this kind of speed render.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Yup, I'm having the same problem. Going back down to the previous version now, because the "Software Only" switch slows down my whole computer massively. Kind of insane a bug this massive wasn't noticed before release.

Edit: Downgrading back to 14.0.4 from Creative Cloud fixed the issue, and is a way better solution than the one pinned here.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Switch the software render from GPU Acceleration (CUDA) to playback software only. Then try scrubbing through your timeline or editing the squence to see if playback works.

I swithed from GPU to playback software and then back to CUDA and it seems to work. I still get the low-level exception error notification but at least I can see what tf I'm editing now.

Also I've had some luck with duplicating the sequence that you're working on to get playback as well

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

14.0.4 is still premiere 2020?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Yes, 14.0.4 is still premiere 2020, I did the same thing by 'downgrading' back to ver 14.0.4 and it solved both low-level exception error and slow exporting time, best solution ever.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I was looking for solutions for a whole day without being able to keep working and any of the them worked! I had to end up downgrading too, you're totally right, this is insane!

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I also did the downgrade which is working fine now. Rendering 4K film is not what you want in software only as I just bought 3 weeks ago a totally new pc with a heavy CPU for this job. I would like to use it then as well For now I just wait in this version 14.0.4 until Abobe has solved the issue as it should be working!

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Some issues as described here - and I've tried everything suggested - if I downgrade, will the project I started in 14.1 work?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Switch the software render from GPU Acceleration (CUDA) to playback software only. Then try scrubbing through your timeline or editing the squence to see if playback works.

I swithed from GPU to playback software and then back to CUDA and it seems to work. I still get the low-level exception error notification but at least I can see what tf I'm editing now.

Also I've had some luck with duplicating the sequence that you're working on to get playback as well

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

So the only fix. is to just not use GPU acceleration and accept significantly lower performance during playback? Wow.

Having the same issue with no nesting, no effects, no legacy titles, just editing with a single MOV proxy and a single music track. I've come to terms with the always-kinda-buggy nature of Premiere but this is absurd. No choice but to revert to 14.0.1 (because, of course, 14.0.3 was also giving me inexplicable errors)

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Another >>>QUICK<<< Fix is to Uninstall 14.1, and downgrade back to 14.0.4

Had the same issue as everyone else, with a legacy Title. . . had to crash our whole daily workflow with Software Rendering, and it was not fast.

Go to Apps in CC app, uninstall 14.1, then click 'Other Versions' 14.0.4 is the last version that doesn't eat itself alive.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

How do I convert my project made in the newer version to be seen in this older version?

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I upgraded last night and after that all critical projects I worked on were crashing, so it was great to find out that I can easily reinstall the 14.0.4. Switching to Software Only to resolve the issue is not feasible for my projects, even if it worked.

Well, my problems did not end here. I found out that the new Adobe Media Encoder was taking hours on a file that usually takes about an hour to export, so I had to downgrade it too. Guess what was the next problem - I lost all my predefined export settings .

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Oh, my God. Thank you. You're a genius, you're a genius, you're a genius, you're a genius. thx

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

This worked. Thank you very much lifesaver.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

I had this issue today. "Mercury Playback Engine Software Only" option slowed my Macbook Pro to unusable speeds with extremely long render times compared to the version 14.0.4. I just reinstalled the old version and my workflow is back to normal. Don't reccomend the update it was a nightmare trying to work on Software Only

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Check if you have old title graphics and delete them. The old way of making those are not available anymore and after I deleted them the error went away and I am able to work with CUDA.

Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Copy link to clipboard

Just in case anyone is wondering if the Nvidia Studio Driver update (442.92, released 4-16-2020) changed the bad behavior of Premiere Pro 14.1, it did not. I tried it on my main machine (i9-7980XE w/ 2 GTX1080ti cards) and my laptop (Dell XPS 9650 i7-7700HQ w/ GTX1050) and 14.1 was not able to playback footage with legacy titles in them. Downgrading to 14.0.4 restores nominal operation.

This has me wondering: Is Adobe treating this as a bug or program error, or will all my past projects with legacy titles be unplayable until I change all the legacy titles to the newer graphics versions? If it's the latter, that really unacceptable because I'd have to recreate hundreds (perhaps thousands) of titles.

Adobe Premiere вылетает при рендере с включенным аппаратным ускорением GPU Mercury Playback (CUDA)

Здравствуйте!
Столкнулся с такой проблемой, при рендере в Adobe Premiere с включенным аппаратным ускорением GPU Mercury Playback (CUDA) программа крашится и вылетает, может на 1% или после 90% прекратить рендер. Через Adobe Media Encoder тоже самое.
А если только с ЦП рендерить то без проблем и вылетов нет.

Процессор: AMD Ryzen 7 2700X.
Видеокарта: MSI GeForce GTX 1060 GAMING X 6G.

В предыдущей старой сборке такой проблемы не было.

На официальном сайте да, сказано что из 1*** линейки видеокарта официально поддерживается только 1080ti и старые не поддерживают, но на моей старой карте GTX 950 все отлично работало.

Подскажите, кто нибудь сталкивался с такой проблемой, особенной у кого карта GTX 1060?

------------------------------------------------------------
- Время кодирования: 00:32:33
03/13/2019 10:41:39 AM : Не удалось выполнить кодирование
------------------------------------------------------------
A low-level exception occurred in: Ускорение GPU с помощью механизма Adobe Mercury Playback (CUDA) (AcceleratedRenderer:10)

Ошибка экспорта
Ошибка компиляции фильма.

Возникло низкоуровневое исключение.

Запись с помощью средства экспорта: H.264
Запись в файл: \\?\D:\video\Эпизод.mp4
Запись типа файла: H264
По тайм-коду: 01;14;38;22
Компонент: Ускорение GPU с помощью механизма Adobe Mercury Playback (CUDA) типа AcceleratedRenderer
Инструмент выбора: 10
Код ошибки: -2147287036

Про нее можно много чего почитать в гугле, там и имена секвенций каким-то образом влияют и че только люди не выдумывают.

Последнее время мне часто пишут про какие-нибудь странные ошибки и там всегда оказывается 1060
-
ДА что тут скажешь - все как всегда: обновляй программу, обновляй дрова, обновляй винду или наоборот лучше 7 ставить. С 10 вечно танцы у кого работает у кого нет, потом обновлений и уже ни у кого не работает, жди патча. aeplug писал(а): Источник цитаты ДА что тут скажешь - все как всегда: обновляй программу, обновляй дрова, обновляй винду или наоборот лучше 7 ставить. aeplug писал(а): Источник цитаты Где это такое написано? Я вот нашел только Рекомендованные графические процессоры для Adobe Premiere Pro CC, а это немного другое. aeplug писал(а): Источник цитаты Последнее время мне часто пишут про какие-нибудь странные ошибки и там всегда оказывается 1060
Для проверки приносил gtx 1070, все тоже самое(
Я уж начал думать, может как то процессор AMD Ryzen 7 2700x не "дружит с видеокартами" при вкл аппаратным ускорением GPU Mercury Playback (CUDA).

Если просто поискать по коду 2147287036, то там упоминают утечки памяти. Попробуй последи за ресурсами на графиках. Последнее время использую Process Hacker, там и видео загрузку видно и обычную.
Чаще всего выскакивает окошко как на скрине (рис 1), и если кликнуть показать отчет об ошибке, то там огромный текст похожий на html разметку, вот начала этого текста:

<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

Okay. Less than 5 minutes after I posted this. I think I have solved the issue.

Go to: File>Project Settings>General>Video Rendering and Playback>Renderer> Change from "Mercury Playback Engine GPU Acceleration" to "Mercury Playback Engine Software Only". Hopefully this will fix it for you too!

Here are five questions to help people help you:

What operating system are you using?

What is your premiere build version?

What are your system specs?

What is the source footage format/codec?

If there is an error message, what exactly does it say?

Please reply to this with your answers. Thanks.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

i7 4770k @ 5.0GHz, 16GB ram, GTX 680, Premiere Running on SSD and Scratch on a separate SSD.

MP4/MOV H.264 4:2:0 (Full Range)

A low level exception occurred in: Adobe Player (Player: 11)

Update: Upgraded to a GTX 1080 (for other reasons as well) and still having this error.

Make sure your GPU meets or exceeds System Requirements and that it has the latest drivers.

This will be fixed in early Dec. Which is a relief for me too!
See my reply to this post:

Great! Glad other people were reporting as well keeping the case open. Put’s a little more pressure for them to fix these things in a timely manner. Too bad my current project will be mostly finished by then. Oh well, should save me time on the next one.

I have an effective workaround / solution.

Change your sequence format (this will make rendered sequence previews not crash Premiere)

Right click on the sequence in the bin and select Sequence Settings.

In Video Previews

A. Preview File Format: Quicktime

B. Codec: ProRes 422 LT (more on that below)

C. Press OK and OK to the prompt.

Transcoding can be done in two main ways.

Using Adobe Media Encoder (my suggestion).

Using Create Proxies in Premiere (make SURE you select an uncompressed format if you go this route).

Import ALL of your compressed media from your project into Adobe Media Encoder.

A. Select all in the queue.

B. Click any of the Preset settings - middle blue text column in queue.

C. Click okay to the prompt.

D. Choose the following settings

Video (all settings in here should be left to match source)

Use Maximum Render Quality (CHECK)

F. With everything still selected click any of the blue text in the Output File column in Queue - right blue text.

G. Create a NEW folder and aim your footage to that (I name it Decompressed), and make SURE you remove the "_1" after the file name.

H. Click OK then click Render (top right play button in the Queue window).

2. Replace footage in Premiere.

B. Right click and select Make Offline (DO NOT delete the originals)

C. On the still selected footage right click and select Link Media.

D. On the bottom right corner click Locate and navigate to your Decompressed folder (check Display Only Exact Name Matches to make your life easier). Then select the matching file name and press OK. Premiere will reconnect everything automatically.

Читайте также: