Error code 9988 after effects

Unable to Export After Effects Composition using Adobe Media Encoder

Issue

When you add an After Effects composition created with After Effects to Adobe Media Encoder, rendering could get stuck at three seconds. It could also take around eight hours or more to render.

Workaround

You could try to use the steps listed below to resolve the issue.

Update After Effects and Adobe Media Encoder to the latest version, or make sure that both the applications are of the same version. For example, if you are using After Effects 2019, make sure to use Adobe Media Encoder 2019.

• Add the composition to Adobe Media Encoder from the After Effects Render Queue.
• Choose Composition > Add to Render Queue . From the Render Queue, click Queue in AME .

In Adobe Media Encoder, select Media Encoder CC > Preferences > General and turn off Enable Parallel Encoding .

• In Adobe Media Encoder, select Media Encoder CC > Preferences > General .
• Under Video Rendering , change the Renderer to Mercury Playback Engine Software Only , and click OK .

Reset preferences for Adobe Media Encoder. Make sure that Adobe Media Encoder and After Effects are closed in your machine (while following the steps).

macOS

• Quit Adobe Media Encoder and After Effects.
• Open the Finder , hold Option , and click Go on the menu bar.
• Click Library and navigate to Preferences > Adobe .
• Rename the Adobe Media Encoder folder to Old_Adobe Media Encoder .
• Close the window and navigate to Documents > Adobe . Rename the Adobe Media Encoder folder to Old_Adobe Media Encoder .

Windows

• Open the Run dialog ( Win+R ) and type %appdata% .
• Open the Adobe folder, and rename the Adobe Media Encoder folder to Old_Adobe Media Encoder .
• Close the window and navigate to Documents > Adobe . Rename the Adobe Media Encoder folder to Old_Adobe Media Encoder .

Clean installation for Adobe Media Encoder. For more details on how to clean installation, see Use the Creative Cloud Cleaner Tool to solve installation problems.

Источник

After Effects

• Голосовать за существующую идею ( )

117 найдены результаты

M1 Max ProRes 4444 Alpha Compressor Failing Render

Renders fail when attempting to export ProRes 4444 alpha that would otherwise not occur on Intel based macs.

Issue causes the following prompt:

After Effects error: Rendering error will writing to file «. » Compressor format error. (-1610153454).

After Effects error: An unexpected error occured while exporting a composition. Error Code: 9988

Please restart After Effects and retry the export.

Anecdotally, this is occurring on about 80% of comps I try to render. Most frequently on more complex comps with blurs and variations in the opacity levels.

Please fix this quickly, otherwise this effectively causes AE on M1 to be unusable in production/professional environments.

M1 Max AE v22 as of 2/2022

Renders fail when attempting to export ProRes 4444 alpha that would otherwise not occur on Intel based macs.

Issue causes the following prompt:

After Effects error: Rendering error will writing to file «. » Compressor format error. (-1610153454).

After Effects error: An unexpected error occured while exporting a composition. Error Code: 9988

Please restart After Effects and retry the export.

Anecdotally, this is occurring on about 80% of comps I try to render. Most frequently on more complex comps with blurs and variations in the opacity levels.

Please fix this quickly, otherwise this effectively causes AE on… Больше

BUG — The workspace is saved when quitting the program

When I quit the program, the active workspace is updated with the current configuration. In order not to change the workspaces, I always have to remember to reset my workspace before quitting the program so that it doesn’t get lost!

Can you please solve this bug?

This bug was fixed in After Effects 22.4. released on 10 May 2022.

Bring back 1, 2, 4-View Interface!

For some stupid reason. we can no longer see the 1, 2, 4-View option in the Composition Window. This feature has been changed where you MUST have 3D Track enabled in order to view this option. Whomever made that decision to update the interface with this newer work flow is an Idiot! CHANGE IT BACK! There was NO reason for this!

As of After Effects 18.2, you can change the view layout (1, 2, or 4 views) via the View menu > Switch View Layout.

If there are other changes you’d like to see regarding Composition view layouts, please let us know by filing a new request.

We need savable, cacheable roto brush propagation.

Rotobrush constantly requires re-propagation of footage.

I propagate in the footage viewer, click away, then double click the same footage in the timeline to re-open the footage that just propagated — it propagates again.

I close a project and re-open — it propagates again.

I freeze and unfreeze a mask — propagates again.

I move the same footage to a different comp, and re-open the footage viewer — propagates again.

We need savable, cacheable propagation.

Thanks for making this request. To save a currently propagated Roto Brush span, use the Freeze button in the bottom bar of the Layer panel while Roto Brush & Refine Edge is selected in the View dropdown menu ( see attached image ). This will prevent Roto Brush from re-propagating on project open and when other aspects of the project are modified.

Roto Brush should only re-propagate when there isn’t enough RAM to hold its cache or when the footage with Roto Brush applied is modified «upstream» i.e. when a mask or some other footage attribute is modified before the pixels are passed on to the Roto Brush effect. Some of the scenarios you’ve listed, like closing and re-opening a project or moving the footage to a different comp, should trigger re-propagation unless you’ve frozen the propagation as mentioned above. The other scenarios shouldn’t trigger re-propagation unless the RAM cache has also been cleared.

If possible, please file a separate report about the propagation being re-propagated in the cases where the RAM cache is not being cleared along with a screen recording of the unwanted re-propagation occurring.

Thanks again for making this report,

— John, After Effects Engineering Team

Thanks for making this request. To save a currently propagated Roto Brush span, use the Freeze button in the bottom bar of the Layer panel while Roto Brush & Refine Edge is selected in the View dropdown menu ( see attached image ). This will prevent Roto Brush from re-propagating on project open and when other aspects of the project are modified.

Roto Brush should only re-propagate when there isn’t enough RAM to hold its cache or when the footage with Roto Brush applied is modified «upstream» i.e. when a mask or some other footage attribute is modified before the pixels are passed on to the Roto Brush effect. Some of the scenarios you’ve listed, like closing and re-opening a project or moving the footage to a different comp, should trigger re-propagation unless you’ve frozen the propagation as mentioned above. The other scenarios shouldn’t trigger re-propagation unless the… Больше

add a 3D Point Control expression controller

Expressions seem to have stuck in 2D.
Please add a 3D Point Control expression controller.

Источник

Видео уроки для After Effects от AEplug

форум для общения, ваших вопросов и моих ответов

Текущие версии программ: After Effects CC 2022 v22.2.1 Premiere Pro CC 2022 v22.2

Ошибка при рендере -1609629695

Ошибка при рендере -1609629695

Сообщение #1 baimyr » 01 июл 2019, 14:36

Доброго времени суток!

Столкнулся на днях с такой проблемой, что при рендере как через энкодер, так и через ае выдаёт ошибку (-1609629695). Пробовал разные кодеки, разное разрешение, менял названия папок и файлов без кириллицы, менял место сохранения на рабочий стол и другие диски, пробовал переустанавливать QuickTime 2 раза и чистить кэш с реестром, пробовал даже видео драйвера, директ и ещё пару обновить (видимо от отчаиния), но ничего не помогает. Уже устал гуглить, потратил 3 дня и всё бестолку.. Что странно, на прошлой неделе рендерил видео и всё было в порядке, после того момента ни каких манипуляций с софтом не производилось, новые плагины и драйвера не ставил.

Не помню как, но при очередном неудачном рендере сохранился файл с логом

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264
Writing to file: \?C:UsersbaimyOneDriveDesktopUntitled Project_AMEComp 1.mp4
Writing file type: H264
Around timecode: 00:00:33:35
Rendering at offset: 33.400 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264
Writing to file: \?C:UsersbaimyOneDriveDesktopUntitled Project_AMEComp 1.mp4
Writing file type: H264
Around timecode: 00:00:33:35
Rendering at offset: 33.400 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695

Источник

Видео уроки для After Effects от AEplug

форум для общения, ваших вопросов и моих ответов

Текущие версии программ: After Effects CC 2022 v22.2.1 Premiere Pro CC 2022 v22.2

Ошибка при рендере -1609629695

Ошибка при рендере -1609629695

Сообщение #1 baimyr » 01 июл 2019, 14:36

Доброго времени суток!

Столкнулся на днях с такой проблемой, что при рендере как через энкодер, так и через ае выдаёт ошибку (-1609629695). Пробовал разные кодеки, разное разрешение, менял названия папок и файлов без кириллицы, менял место сохранения на рабочий стол и другие диски, пробовал переустанавливать QuickTime 2 раза и чистить кэш с реестром, пробовал даже видео драйвера, директ и ещё пару обновить (видимо от отчаиния), но ничего не помогает. Уже устал гуглить, потратил 3 дня и всё бестолку.. Что странно, на прошлой неделе рендерил видео и всё было в порядке, после того момента ни каких манипуляций с софтом не производилось, новые плагины и драйвера не ставил.

Не помню как, но при очередном неудачном рендере сохранился файл с логом

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264
Writing to file: \?C:UsersbaimyOneDriveDesktopUntitled Project_AMEComp 1.mp4
Writing file type: H264
Around timecode: 00:00:33:35
Rendering at offset: 33.400 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264
Writing to file: \?C:UsersbaimyOneDriveDesktopUntitled Project_AMEComp 1.mp4
Writing file type: H264
Around timecode: 00:00:33:35
Rendering at offset: 33.400 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695

Источник

How to fix the Runtime Code 512 After Effects Error 512

This article features error number Code 512, commonly known as After Effects Error 512 described as Error 512: Adobe After Effects has encountered a problem and needs to close. We are sorry for the inconvenience.

Error Information

Error name: After Effects Error 512
Error number: Code 512
Description: Error 512: Adobe After Effects has encountered a problem and needs to close. We are sorry for the inconvenience.
Software: Adobe After Effects
Developer: Adobe Systems Inc.

This repair tool can fix common computer errors like BSODs, system freezes and crashes. It can replace missing operating system files and DLLs, remove malware and fix the damage caused by it, as well as optimize your PC for maximum performance.

About Runtime Code 512

Runtime Code 512 happens when Adobe After Effects fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.

Definitions (Beta)

Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!

• Adobe — Adobe Systems is a software company headquartered in San Jose, California, USA
• Effects — Non functional enhancements of user interaction with a product most commonly visual and sound

Symptoms of Code 512 — After Effects Error 512

Runtime errors happen without warning. The error message can come up the screen anytime Adobe After Effects is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(After Effects Error 512) Repair Tool»/>
(For illustrative purposes only)

Causes of After Effects Error 512 — Code 512

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Источник

Describe the bug
Included a 4 aerender logs from different composition renders. Renders are failing as you can see from the logs. This happens at random. The biggest issue however is that a valid file (.mov ProRes 422) is still created but is cut short from where the render crashed. This is problematic as it’s then very difficult to know that a render has failed especially when working with an automated workflow.

Crash logs:
aerender-A7Gmo7C4Y1Qy90CgPYzzN.log
aerender-ejnngv8rpueXd8ki7z67s.log
aerender-KCjZ5F-7nF9n0g2zUSOQ8.log
aerender-Faoatljuiyl1fFZ8xGP_W-ahlsell-crash.log

Information about environment

• Which version of nexrender are you using? 1.37.0
• What kind of the setup do you have? (server+worker or cli) Server + worker
• Are you using pre-built binaries or globally installed npm packages? npm
• Which kind (and version) of operating system you are running it in? Windows 10
• Any additional information that might be helpful — aerender version 22.0×111

Expected behavior
Is there a way that nexrender could detect when an error is thrown within aerender and fail the render thus it can be retried?

Any help here is appreciated.

Если все перечисленное выше не помогло (или просто вам неохота возиться, пробуя все подряд), значит, скорее всего ошибка происходит из-за конкретного проекта. При возникновении ошибки или другой проблемы обратите внимание на таймкод (время) ошибки. Если баг возникает каждый раз в одном и том же месте, то есть вероятность, что он вызывается каким-нибудь конкретным эффектом или анимацией, которую придется изучить и, возможно, изменить. Например, при работе с частицами можно выбрать другой режим работы CPU/GPU в плагине (если поддержка есть), уменьшить количество частиц, для Element 3D упростить геометрию, уменьшить количество полигонов, проверить материалы, текстуры, размер и т.п.
Для уточнения проблемного слоя или эффекта мне несколько раз помогал такой способ. Вы выбираете половину слоев в композиции и удаляете их все. Рендерите видео, ну или как вы там предпочитаете проверять. Тут возможны два варианта:

• Если ошибка пропала, значит, она была в удаленных слоях композиции, отменяем удаление, и теперь удаляем только половину удаленных ранее слоев. И снова запускаем рендер.
• Если ошибка осталась, то продолжаем дальше удалять слои, упрощая проект.

Если ошибку вызывает что-то конкретное, рано или поздно мы найдем виновника таким методом. Я понимаю, что это долгий, муторный и неудобный способ, но если вы знаете лучше, то пишите мне, буду благодарен!
А если ошибка возникает каждый раз в случайных местах композиции, то можно попробовать рендерить не готовое видео, а набор кадров Image Sequence. В After Effects есть несколько пресетов для этой цели под общим названием Multi-Machine Settings/Sequence в очереди рендера Render Queue.

В таком случае каждый кадр будет отдельным изображением на диске, и если рендер оборвется, вы не потеряете уже просчитанный готовый материал. А когда вы продолжите рендер (можно продублировать задание в очереди рендера Render Queue), After Effects пропустит уже существующие на диске кадры и начнет считать со следующего места. За это отвечает отдельная настройка в Render Settings — Skip existing files (allows multi-machine rendering) («Пропустить существующие файлы (позволяет осуществлять рендеринг на нескольких компьютерах)«).

Но, естественно, звук в таком виде не получится вывести из программы After Effects и придется потом дополнительно его считать как WAV файл без видео и объединять с набором отрендеренных кадров композиции. Их, конечно же, надо предварительно импортировать в любую программу для работы с видео — After Effects, Premiere Pro, да любую. Даже мой любимый FFMPEG может это сделать, да все нормальные программы умеют делать такое. Только проверьте частоту кадров, так как куча файлов на диске не имеет такой информации, и это надо задавать руками.
Вообще, это было сделано для рендеринга по сети несколькими компьютерами одновременно, чтобы они не считали одинаковые кадры, назначенные другому After Effects. А самое интересное, что такое можно провернуть и на одной машине для ускорения рендера, ведь одна копия After Effects не задействует ресурсы процессора CPU на полную.
Уменьшение времени рендера в After Effects