Importerquicktime prm premiere pro ошибка
Обновлено: 03.07.2024
Здравствуйте. У меня 4 года ноут Lenovo G500 и только недавно, когда стало нужно делать монтаж в Adobe Premiere Pro CC 2018 сильно тормозит предпросмотр проделанной работы в окне видео. Думаю из-за того что не переключается на видеокарту ATI, а работает постоянно на Intel. Сделал все манипуляции, чтоб максимально разгрузить и облегчить нагрузку, но не помогло. Потом вспомнил про переключение видеокарт т.к. у меня Intel и ATI. Но Catalyst Control Center, где можно настроить параметры switchable graphics для каждой программы или отдельного случая, не запускается, хотя с первых дней всё работало, но за все годы только сейчас реально понадобилась дискретная карта, а тут. В BIOS я ещё давно проверял и была включена "switchable graphics".
Сделал всё как писал Turok123, но теперь в Диспетчере Задач у обоих видеокарт восклицательный знак ((
Что делать? Прошу вашей помощи. Спасибо!
Заметил такую вещь. Когда проделал все пункты от Turok123 и начал ставить родной драйвер AMD Video Driver для 32- и 64-разрядной версии Windows 7 — Lenovo G400, G500 версии 8.0.911.0 появилось это окно
Так у всех или почему мне предложило удалить старые компоненты, если ничего не осталось?! Я проверил и нажал на удалить, но появилось окно "компонентов не обнаружено". Вот текст из файла отчёта по установке
Диспетчер установки Catalyst™
Отчет об установке
11/18/18 21:38:41
Информация об оборудовании
Имя AMD Radeon Graphics Processor
Изготовитель Advanced Micro Devices, Inc.
Идент-тор устройства 0x6663
Идент-тор поставщика 0x1002
Код класса 0x038000
Идентификатор редакции 0x00
Идентификатор подсистемы 0x3800
Идентификатор поставщика подсистемы 0x17aa
Другое оборудование
Существующие пакеты
Устанавливаемые пакеты
Обновление профиля PXКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 1.00.1
Размер: 1 Мбайт
Профили приложения OEMКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 1.00.0000
Размер: 1 Мбайт
Диспетчер установки AMD CatalystКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 8.0.911.0
Размер: 20 Мбайт
AMD APP SDK RuntimeКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 10.0.1124.2
Размер: 90 Мбайт
Драйвер дисплея AMDКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 12.100.14.0000
Размер: 90 Мбайт
Enable AeroКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 1.00.0000
Размер: 1 Мбайт
AMD Accelerated Video TranscodingКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 12.10.100.30204
Размер: 3 Мбайт
Catalyst Control CenterКонечное состояние: Оп-ция вып. успеш.
Версия элемента: 2013.0204.1539.28035
Размер: 150 Мбайт
Другие обнаруженные устройства
Нажимая на десктоп правой кнопкой мауса есть пункт в меню "Catalyst Control Center", но при выборе выдаёт
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
- ImporterQuickTime.prm
Copy link to clipboard
After I install windows 10 my premiere don't start.
The loading stops in "ImporterQuickTime.prm"
Somebody help me?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more1 Correct answer
Thanks Jeff.In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.Copy link to clipboard
Same thing here but with media Encoder 2015
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Same thing here.
Given that I'm actually paying for Premiere and I need it, it bugs me quite a lot.
NVIDIA drivers up to date (355.82) GeForce GTX750
Windows 10 Pro, DirectX 12, 16GB RAM
Quicktime 7.7.6 installed (but it crashed before also)
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Create a new user account and try starting Pr again from the new account. If it launches successfully, then go back to your original account and launch Pr while holding down the Shift+Alt keys. That should reset your plug-in cache and preferences. Doing that will often fix startup and other crashes in Pr.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Good news -- and good troubleshooting!
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Which folders exactly need to be accessed by admin? Why does starting up premiere as admin not fix this?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
Which folders exactly need to be accessed by admin? Why does starting up premiere as admin not fix this?
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
I tried, but it did not help. I've commented also in this thread about the same issue: loading importerquicktime.prm - crush
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn moreCopy link to clipboard
joaocverde wrote
Thanks Jeff.
In my case I discovered short before your answer that somehow, the folders where Premiere keeps some files (on my Libraries) required administrator privileges to be accessed. I had to access those in Windows Explorer with elevated permissions beforehand, and after that Premiere (and Media Encoder too, curiously AE did not have any errors) would run OK, and since then I have rebooted and Premiere continues to launch successfully.
This did NOT work for me, but after a very long and annoying back and forth in another thread, the problem was isolated to a file in User App Data that needed to be force deleted. Here's what I did to fix it for me:
I can confirm that deleting this file on the user account that's preventing Adobe Premiere Pro will work to fix the problem:
C:\Users\YOUR USER FOLDER\AppData\Roaming\Adobe\Common\Essential Sound/SharedTags
If you can't get there, go to any open folder and at the top under View;check show hidden files.
This file will NOT delete just by right clicking and deleting it. It will say it cannot be deleted because it's in use. Even with closing all Adobe related files in task manager, it still was unable to be deleted because 'System' is using it.
This is a perfect example of how Adobe loves to introduce new features (Essential Sound) that causes conflicts with other parts of Premiere that used to work perfect. In this case, the new feature wouldn't even let Premiere start up.
Adobe, can we please all agree that you seriously need to do FULL testing before new features are introduced?
Я запускаю Adobe Premiere Elements 12 на 64-разрядной версии Windows 7 Home Premium, и недавно он начал висеть при запуске, показывая Loading ExporterQuicktimeHost.prm .
это поведение началось недавно (он работал нормально, по крайней мере, до января), без изменений в Premiere Elements с тех пор (я полагаю, это было вызвано некоторым обновлением windows).
согласно собственным инструкциям Adobe, я попытался (без какого-либо успеха):
- переустановка quicktime и Premiere Элементы
- удаление всех сторонних кодеков
- убедитесь, что " Adobe QT32 Server.exe", " dynamiclinkmanager.exe " и " adobe premiere elements.exe " были занесены в белый список на брандмауэре
я обнаружил, что убийство dynamiclinkmanager.exe процесс, когда запуск застрял разблокирует Premiere элементы, но это должно быть сделано каждый раз, когда я начинаю его.
в чем проблема? Есть ли постоянное решение?
вы можете попробовать следующее: При открытии Premiere и когда он зависает на сервере QT32, попробуйте убить процесс в диспетчере задач и убить процесс premiere, затем проверьте, не работает ли процесс QT, а также проверьте, не работает ли процесс динамической компоновки. Если они просто перезапустить премьеру.
Если процесс QT не может быть остановлен, то у вас есть проблема с вашим программным обеспечением брандмауэра. Есть некоторые сторонние приложения брандмауэра, которые могут вызвать сбой создания экземпляра QT server, например Comodo брандмауэр у меня был плохой опыт с ним.
также есть еще одна возможность, что вы добавили некоторые новые кодеки, которые конфликтуют со старыми, особенно в отношении быстрого времени, как, например, DNxHD QT кодеков или аналогичных от Avid.
эти данные не могут быть найдены на Adobe или, по крайней мере, я не нашел его там.
надеюсь, что это будет работать для вас, или по крайней мере дать вам идею, как найти решение.
У меня есть чистая установка, и эта проблема будет со мной, когда премьера зависает и вылетает.
в то время как премьера застрял на экране заставки, перейдите в Диспетчер задач и убивает "Adobe QT32 Server.процесс exe". Теперь он откроется корректно, но я советую вам перезапустить его!
START HERE! Here are solutions to some common problems:
Choppy/Laggy Playback | Poor Export Quality
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?
If your issue is resolved, please take a moment to change your post flair to Support (Solved). Thank you!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
Premier Pro latest version (14.4)
Intel i5 8GB Ram 64-bit with Intel (R) HD Graphics 4600
Had the same problem today..
Hope that helps you.
I’m having the exact same issue and Adobe support hasn’t been very helpful! All their suggestions haven’t worked. I also can’t find the json file
My issue was the recent September Windows 10 update. Roll back that update if you recently updated your PC. Solved my problem.
Adobe Care gave me a solution that fixed the error:
“Thanks for confirming that. Could you please try these steps and check if it helps.
Navigate to C:\Users\username\AppData\Roaming\Adobe
Rename the folders named Premiere Pro & Common to OldPremiere Pro & Oldcommon respectively
Navigate to C:\Users\username\Documents\Adobe
Rename the folder named Premiere Pro to OldPremiere Pro (This will reset the app settings)
Right-click on the icon for Premiere Pro and select Run as administrator Let us know if it helps. Thanks! SKC”
Nothing else had been working but this instantly worked for me!
Update 10/1/20: I decided to back up my computer and rest it because this was too frustrating. I found an option to roll back the recent (September) Windows 10 update on the same settings page to reset the PC. I opted to try that first. It solved my problem.
I have been having this problem since morning (12/11/2020). In fact, it has robbed me of 80% of my active time today.
So, I went on a hunt for a viable solution.
After many trials, uninstalling Premiere, searching for an elusive %Appdata% folder, and almost giving a thought of starting afresh my computer, I found one solution that led me to the finding I will share in this thread. The solution has to do with the idea of creating another user account.
After my analysis, it seems like this is a Windows 10 sort of a problem.
Another similarity is that the culprit is Adobe Premiere or Adobe Media Encoder or both hugging or cruising at the final stage of the loading AEXD.aex or importerquicktime.prm plugins.
This is the same problem I encountered with my Camtasia. However, Camtasia resolved it by suggesting a new location. That went on smoothly. I didn’t even think there is a huge problem lying beneath.
So, to fix this, once I was in the second user account, I noticed when load Premiere Pro, I got this notification from my Windows 10 defender to allow Premiere Pro to have access to My Document.
It is obvious by default, this folder is accessible to these apps, right?
However, with the revamped Windows Security, the Ransomware protection is super active to watch which apps access certain paths in your computer.
So, with these two plugins in need to access the Adobe folder in my Documents (I hope that’s the case here), the windows defender sees it as a threat. As a result, it prevents them from accessing the folder.
This is the reason Adobe Premiere Pro and Adobe Media Encoder are the two most affected apps from the creative suite. That is, for Windows 10 users who are using Windows security as their default antivirus.
Option 1:
Open your Windows 10 Security App (Windows Defender for win 10)
Click Virus & threat protection
Click on Protection history (Wait a little bit to load the history)
Toggle the histories from "Protected folder access blocked" - you will require administration rights here.
Click on Actions Button and select Allow on device.
Option 2:
Open your Windows 10 Security App (Windows Defender for win 10)
Click Virus & threat protection
Click on Ransomware Protection
Then, on Manage ransomware protection.
Next, on Block History
Toggle the histories from "Protected folder access blocked" - you will require administration rights here.
Click on Actions Button and select Allow on device.
One thing to note, you cannot remove the Documents path from the list of protected folders.
Читайте также: