After effects error source file has no importable streams что делать

Работа над ошибками

11. При открытии mov файла в программе After Effects СС получаем ошибку. Это происходит на платформе Mac OS X когда компонент DVCPROHDVideoOutput QuickTime конфликтует с программой After Effects CC (12.0). Ошибка также может возникнуть при просмотре, визуализации и экспорте видео. Встречаются следующие варианты ошибок:
— «After Effects error: file ‘file name.mov’ cannot be imported — this ‘Mov file is damaged or unsupported.’»
— «After Effects: One of the output modules could not be imported. It has been reset to use the default setting for the selected file format.»
— “Error reading frame from file ‘[file path and name].mov’. (86 :: 2)”
— “[file path and name].mov”. An output module failed. The file may be damaged or corrupted. (-1610153464)”
Решение проблемы: это происходит потому что, для воспроизведения и экспорта Adobe After Effects СС использует QT32 Server. И с этим процессом происходит сбой из-за плохого взаимодействия с QuickTime video out, при установленном компоненте DVCPROHDVideoOutput QuickTime component. Поэтому идем в [OS Drive]/Library/QuickTime делаем резервную копию DVCPROHDVideoOutput.component перетащив его на рабочий стол. Теперь удаляем DVCPROHDVideoOutput.component из папки Library/QuickTime перетащив его в корзину. И соответственно не забываем очистить корзину. Также как вариант, можно попробовать установить последнююю сборку кодеков Apple ProApps QuickTime Codecs 1.0.x update.
*При открытии проекта в версии программы Adobe After Effects CC 2020 появляются следующие сообщения об ошибках:
«After Effects error: The source compression type is not supported. (86 :: 1)»
Нажимаем на кнопку ОК и появится ещё одно сообщение:
«After Effects error: file ‘file name.mov’ cannot be imported — this ‘.mov’ file is damaged or unsupported.»
Проблема в том, что версия программы Adobe After Effects CC 2020 не поддерживает связанное с проектом видео в контейнере MOV. Т.е. не поддерживается кодек которым пожато видео в контейнере MOV.
12. После запуска программы на плфтформе Mac OS X Maverics появляется сообщение: You can’t use this version of the application “Adobe After Effects CC” with this version of OS X. You have “Adobe After Effects CC” 12.0. Или: Данная версия программы “Adobe After Effects CC” не может быть использована с этой версией OS X. Вы используете “Adobe After Effects CC” 12.0.

Необходимо установить обновление Adobe After Effects CC (12.1) Update и выше, при установке обновления 12.2 и выше необходимо использовать следующую методику.
Если при попытке поставить или скачать обновление, получаем ошибку: The most likely causes for this failure are an inability to connect to the internet or being logged in as a non-administrative user. То вот следующие методы решения проблемы: удалить или переименовать, файл в следующих директориях:
Mac OS X / Library / Application Support/Adobe/AAMUpdaterInventory/1.0/AdobeUpdaterAdminPrefs.dat. Или / Library / Application Support/Adobe/AAMUpdater/1.0/ AdobeUpdaterAdminPrefs.dat.
Windows C:Program files(x86)common filesadobeAAMUpdaterInventory1.0AdobeUpdaterAdminPrefs.dat.
Или искать файл в этой папке: C:Program DataAdobeAAMUpdater1.0AdobeUpdaterAdminPrefs.dat.
И далее вручную ставим скачанное обновление.
13. Ошибка при загрузке программы: «After Effects warning: An unknown Adobe Player Engine error has occurred. Scripting will be disabled.«. Вариант решения проблемы: попробовать поставить последнее обновление, переустановить или если есть ошибки в работе Adobe Media Encoder, переустановить и его.

14. Ошибка при загрузке программы: «After Effects can’t continue: The Common Extensibility Platform (CEP) suite couldn’t be loaded. You may need to reinstall.«. / After Effects продолжение невозможно: Не удалось загрузить пакет CEP (Common Extensibility Platform). Возможно, требуется переустановка.
Как исправить? Попробовать запустить приложение от имени администратора. Нажимаем на AfterFX.exe правую кнопку мыши и выбираем: Запуск от имени администратора.

15. Ошибка при проигрывании таймлайна композиции: After Effects error: Cached Preview needs 2 or more frames to playback / After-Effects Fehler: Wiedergabe einer Cache-Vorschau benotigt mindestens 2 Frames. Данная ошибка связана с недостатком памяти.

Несколько вариантов решения проблемы:
— Чистим память командой: Edit > Purge > All Memory & Cache.
— Перезагружаем программу Adobe After Effects CC 2017.
— Включаем Enable Disk Cache, если данная опция включена, то чистим ее содердимое нажав на кнопки: Empty Disk Cache и Clean Database & Cache, в настройках программы: Edit > Preferences > Media & Disk Cache.
— Снижаем качество предварительного просмотра в окне композиции с Full на Quarter.
— Проверяем наличие свободной памяти в Диспетчере задач. Т.е. память может быть занята какими-то процессами, или наоборот, для превью используется только часть свободной памяти, выделенной для Adobe After Effects CC 2017.
— Снимаем галку перед пунктом Reduce Cache Size when system is low on memory (this will shorten cached preview) в настройках Edit > Preferences > Memory.
— Также стоит обратить внимание на размер файла подкачки и чтобы достаточно памяти было выделено для операционной системы: RAM reserved for other applications.

— Проверяем, чтобы рабочая область (Work Area) не находилась в следующем положении:

16. Ошибка: After Effects warning: Unspecified drawing error. Решение: сбрасываем рабочее пространство до дефолтного (делаем его по-умолчанию).

Источник

Image Import Failure in After Effects & Premiere

This is an old problem. And I bet anyone who reads this has experienced this one.

After Effects Error: The source file has bad header. Please check that it is a valid file. (86::1)

The solution is usually simple, open the image in Photoshop or something that lets you export the image and I save it as another format, usually a png. Several times I saved the jpg over top of itself and the error persisted, but a quick export as a png works every time for me.

Even Premiere has this problem..

Error Message The file cannot be opened because of a header error.

So you might ask me – why am I writing this?

Well, what I don’t understand here is why Photoshop, Illustrator, Photos on Windows, Preview on Mac, Paint, Firefox, Chrome, and even Outlook can all open this file without a problem? And I am sure many other programs can open this file as well… At least the error messages are useful and tell me something I can understand.

But, if Photoshop and Illustrator can open this file why not AE or Premiere? Adobe some your programs have the ability to open this image. Why not use that same logic, or code, or whatever it is in all of your programs?

Makes no sense at all to me as a user. And it’s just another one of those inconsistent behaviors between your programs Adobe that I just do not understand. It is also another small, but annoying, waste of my time. It adds an unnecessary step in my workflow. It gets in the way of creativity when I am on a roll creatively and must make a turn in that creative process to handle something so stupid as this.

Maybe I am too demanding as a user?

I want things to work consistently.

I want the programs I use to NOT get in the way of my work and creativity.

I want those programs to NOT piss me off.

I just want them to work. Seems simple to me. Maybe it’s not that simple?

Источник

3 Common After Effects Errors and How to Fix Them

Spending hours to solve an error in After Effects can be a frustrating waste of time. To save you the stress, here are 3 common After Effects errors and how you can fix them.

Few things are as discouraging as pouring over endless forum threads in hope of discovering a solution to a stubborn error within a program. Sometimes the solution is surprisingly simple, but you can often find yourself desperately entering places in your computer you didn’t even know existed in search of answers. Here are a few After Effects errors, both simple and complex, that we found most frequently troubled AE users in the past few years.

1. “Files Are Missing Since You Last Saved the Project”

This is by far the most prevalent error message in After Effects. Luckily, it’s a simple issue with a simple solution. If files imported into your project have changed location on your computer, or the project file has been moved, After Effects will often lose track of their location.

Relocate Your Missing Files:

To relocate your files, navigate to the Project tab and type in the search term “Missing.” This will show all the files that are currently missing, as indicated by a Television Color Bars thumbnail. Right click on each file, and select “Replace Footage > File.” Select the file from its new location, and it will instantly be restored to the project.

Repeat this process for each missing file. If there are multiple missing files in the same location, you will only need to replace one of them. The rest will automatically update once After Effects recognizes the new location.

Prevent Lost Files with “Collect Files” Feature:

This issue tends to occur most often when opening a project on a new computer. To prevent this from occuring, you can save your project as a folder that includes all necessary files with the project file.

Just go to File > Dependencies > Collect Files.

Make sure the “Collect Source Files” dropdown menu is set to “All” and that the “Generate Report Only” checkbox is not checked, then click “Collect.”

2. “Output Module Failed” [H.264]

Before delving into this rather common problem, it helps to understand how various media file types work. Video and Audio files can be exported to and played in a number of different file types, otherwise known as Containers, Wrappers, or Formats.

Some video examples you might be familiar with are the .AVI, .MOV, and .WMV, amongst others, whereas some audio examples would be the .MP3, .WAV, and .AIFF. Each of these formats can be exported using a variety of codecs. A codec is the algorithm used to compress data into a smaller, more efficient file. Some codecs maximize quality, while others may be designed to export fast or playback smoothly.

While h.264 is one of the most popular codecs to export with due to its balance of quality and speed, it can often produce the “Output Module Failed” error within After Effects, especially when using a Quicktime format. Unfortunately, this error has a plethora of possible causes, so I thought we would investigate as many as we could find. We’ve placed them in order of complexity, so that you can start with the easy solutions and work your way down if your situation is more complicated.

Use Adobe Media Encoder

In a best case scenario, you can simply export using Adobe Media Encoder instead of using the built-in After Effects Render Queue. Adobe Media Encoder is much more reliable and provides a much better workflow as well. Instead of normally clicking “File > Create Proxy > Movie…”, you would select “File > Export > Add to Media Encoder Queue”.

Avoid Exporting With a Quicktime Format

If this error persists, try exporting in H.264 in an .MP4 wrapper instead of a Quicktime .MOV. Sometimes issues within Quicktime itself can cause your render to fail, so avoiding it altogether may be another easy fix.

Purge Memory & Disk Cache

After Effects constantly stores the files that are used to preview render in a folder on your hard drive, so that they can be easily accessed in the future without having to re-render each time. This folder is known as the Disk Cache, and as it grows full over time, it can cause problems within the program. Output Module Failure is no exception.

To empty or purge your Disk Cache, navigate to “Edit > Purge > All Memory & Disk Cache.” The only consequence of this is that you will need to wait for any previously rendered previews to re-render if you access them again. With any issues you stumble upon, purging the disk cache is a good place to start.

Disable or Limit Multiprocessing

Multiprocessing is a feature that was designed to maximize the use of your computer’s processing power, and though it was recently removed for CC 2015, it often causes multiple problems in older iterations of After Effects, including this one.

You can access multiprocessing options by navigating to “Preferences > Memory & Multiprocessing.”

Once there, try lowering the number of available processor cores. If this fails, you may need to disable multiprocessing altogether. Your render times will suffer, but at least you can export what you need. Don’t hesitate to try this with other errors, as the multiprocessing feature has been the culprit behind many issues in the past.

Manually Purge Disk Cache

On rare occasion, After Effects may fail to completely clear the Disk Cache. You can find your Cache Folder by navigating to “Preferences > Media & Disk Cache,” where its location is displayed. Open this folder and ensure its contents are deleted.

Reset Flash Memory

On a few occasions, users found that resetting their computer’s flash memory solved their Output Module Failure. This is a rather unlikely cause, but entirely worth the effort if you’re out of options. On a Mac, this is as easy as holding “CTRL+CMD+P+R” during boot up. For PC users, the process to do depends on the motherboard brand. More often than not, the option to do so can be found in the motherboard’s BIOS settings, which can be accessed by clicking the key displayed in the BIOS Access Prompt (usually the first thing on-screen during startup.)

3. “RAM Preview Needs 2 or More Frames to Playback”

This maddening RAM preview error became widespread around 2013, and has plagued many users since. Though Adobe is aware of this error, it has not been entirely fixed, and it still frequently appears from various causes. Currently, the error is most commonly a result of a conflict between Adobe’s Dynamic Link Manager and System Firewalls. Most other causes have been patched in recent iterations of After Effects.

Allow Dynamic Link Manager Access Through Your Firewall [Mac]

Navigate to the folder “/Library/Application Support/Adobe/Common/” and click “File > Get Info.” Make sure the Lock icon is not activated, and enter your administrator name and password if necessary. Scroll down to “Sharing & Permissions” and grant your current account Read & Write Privileges. Below this, click the small Settings icon and select “Apply to enclosed items.” Re-lock the folder and you’re done!

Allow Dynamic Link Manager Access Through Your Firewall [PC]

Navigate to the folder “ C:Users AppDataRoamingAdobe” and right-click it to access its “Properties” menu. Choose the “Security” tab and allow your current user “Full Control” of the folder. Click OK and you’re good to go!

We can’t guarantee that these solutions will work in every instance, but hopefully they’ll help save you some time down the road. What are the most painful After Effects errors you’ve experienced? Let us know in the comments below!

Источник

Just FYI this is a complete nightmare.

I’m at a clients studio, they’ve promised to build these spots around 2 templates. Load the templates in they contain references to video footage encoded as Quicktime.Mov’s probably as photo jpeg or h264 etc as that’s quite common.

I cannot import these elements. I’m on the ducking clock buddy, people are paying for my time to sit here and muck around with this nonsense.

I once worked around this by converting the mov file in quicktime to a prores.mov and then life carried on, but this stupid quicktime X isn’t even giving me sophisticated options for export, Media Encoder won’t import it either.

Long story short not only am I ducked right now, so is my producer/boss/client who promised spots to one of our higher end clients, shot a bunch of footage on RED with this client, and right here right now we’re ducked.

I pay my subscription fee to you guys in the hope you will be smart enough to make it so I don’t wind up in binds like this. Just saying we’re taking away support for normal workflows, for no apparent good reason is mind bogglingly irresponsible.

I would say more, but I need to go back to solving this problem (instead of applying my creativity to the project — which is what I’m being paid to do, and the reason why we pay for your software to begin with).

Just FYI this is a complete nightmare.

I’m at a clients studio, they’ve promised to build these spots around 2 templates. Load the templates in they contain references to video footage encoded as Quicktime.Mov’s probably as photo jpeg or h264 etc as that’s quite common.

I cannot import these elements. I’m on the ducking clock buddy, people are paying for my time to sit here and muck around with this nonsense.

I once worked around this by converting the mov file in quicktime to a prores.mov and then life carried on, but this stupid quicktime X isn’t even giving me sophisticated options for export, Media Encoder won’t import it either.

Long story short not only am I ducked right now, so is my producer/boss/client who promised spots to one of our higher end clients, shot a bunch of footage on RED with this client, and right here right now we’re ducked.

I pay my subscription fee to you guys in the hope you will be smart enough to make it so I don’t wind up in binds like this. Just saying we’re taking away support for normal workflows, for no apparent good reason is mind bogglingly irresponsible.

I would say more, but I need to go back to solving this problem (instead of applying my creativity to the project — which is what I’m being paid to do, and the reason why we pay for your software to begin with).

Just FYI this is a complete nightmare.

I’m at a clients studio, they’ve promised to build these spots around 2 templates. Load the templates in they contain references to video footage encoded as Quicktime.Mov’s probably as photo jpeg or h264 etc as that’s quite common.

I cannot import these elements. I’m on the ducking clock buddy, people are paying for my time to sit here and muck around with this nonsense.

I once worked around this by converting the mov file in quicktime to a prores.mov and then life carried on, but this stupid quicktime X isn’t even giving me sophisticated options for export, Media Encoder won’t import it either.

Long story short not only am I ducked right now, so is my producer/boss/client who promised spots to one of our higher end clients, shot a bunch of footage on RED with this client, and right here right now we’re ducked.

I pay my subscription fee to you guys in the hope you will be smart enough to make it so I don’t wind up in binds like this. Just saying we’re taking away support for normal workflows, for no apparent good reason is mind bogglingly irresponsible.

I would say more, but I need to go back to solving this problem (instead of applying my creativity to the project — which is what I’m being paid to do, and the reason why we pay for your software to begin with).

Just FYI this is a complete nightmare.

I’m at a clients studio, they’ve promised to build these spots around 2 templates. Load the templates in they contain references to video footage encoded as Quicktime.Mov’s probably as photo jpeg or h264 etc as that’s quite common.

I cannot import these elements. I’m on the ducking clock buddy, people are paying for my time to sit here and muck around with this nonsense.

I once worked around this by converting the mov file in quicktime to a prores.mov and then life carried on, but this stupid quicktime X isn’t even giving me sophisticated options for export, Media Encoder won’t import it either.

Long story short not only am I ducked right now, so is my producer/boss/client who promised spots to one of our higher end clients, shot a bunch of footage on RED with this client, and right here right now we’re ducked.

I pay my subscription fee to you guys in the hope you will be smart enough to make it so I don’t wind up in binds like this. Just saying we’re taking away support for normal workflows, for no apparent good reason is mind bogglingly irresponsible.

I would say more, but I need to go back to solving this problem (instead of applying my creativity to the project — which is what I’m being paid to do, and the reason why we pay for your software to begin with).

Just FYI this is a complete nightmare.

I’m at a clients studio, they’ve promised to build these spots around 2 templates. Load the templates in they contain references to video footage encoded as Quicktime.Mov’s probably as photo jpeg or h264 etc as that’s quite common.

I cannot import these elements. I’m on the ducking clock buddy, people are paying for my time to sit here and muck around with this nonsense.

I once worked around this by converting the mov file in quicktime to a prores.mov and then life carried on, but this stupid quicktime X isn’t even giving me sophisticated options for export, Media Encoder won’t import it either.

Long story short not only am I ducked right now, so is my producer/boss/client who promised spots to one of our higher end clients, shot a bunch of footage on RED with this client, and right here right now we’re ducked.

I pay my subscription fee to you guys in the hope you will be smart enough to make it so I don’t wind up in binds like this. Just saying we’re taking away support for normal workflows, for no apparent good reason is mind bogglingly irresponsible.

I would say more, but I need to go back to solving this problem (instead of applying my creativity to the project — which is what I’m being paid to do, and the reason why we pay for your software to begin with).