While I understand that you cannot comment about timeframe, can you at least verify that progress is being made to fix this problem?
I have lost (easily) 40 hours of non-billable time (and a bit of sleep) trying to isolate and work around this mess. I intend to pursue some
form of credit with Adobe in the long term, however in the short term I need to evaluate my options for the completion of my client’s project.
I have changed settings so as to not use the graphics card.
I have moved project media to an internal drive.
I have changed preview settings to DNX (instead of ProRes422).
I have created a new project and imported the sequences.
I have discarded render files, attempted to recreate render files, and restarted my PC countless times.
The media that seems to be at the root of the problem is:
UHD 23.976 XAVC mp4
My system is a:
OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Installed Physical Memory (RAM) 32.0 GB
Processor AMD Ryzen 5 1600 Six-Core Processor, 3725 Mhz, 6 Core(s), 12 Logical Processor(s)
Each tweak brought some minor gain, but has been temporary and insufficient.
While I understand that you cannot comment about timeframe, can you at least verify that progress is being made to fix this problem?
I have lost (easily) 40 hours of non-billable time (and a bit of sleep) trying to isolate and work around this mess. I intend to pursue some
form of credit with Adobe in the long term, however in the short term I need to evaluate my options for the completion of my client’s project.
I have changed settings so as to not use the graphics card.
I have moved project media to an internal drive.
I have changed preview settings to DNX (instead of ProRes422).
I have created a new project and imported the sequences.
I have discarded render files, attempted to recreate render files, and restarted my PC countless times.
The media that seems to be at the root of the problem is:
UHD 23.976 XAVC mp4
My system is a:
OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
Installed Physical Memory (RAM) 32.0 GB
Processor AMD Ryzen 5 1600 Six-Core Processor, 3725 Mhz, 6 Core(s), 12 Logical Processor(s)
Each tweak brought some minor gain, but has been temporary and insufficient.
Проблемы с рендерингом или экспортом проекта Premiere Pro? Приложение зависает, тормозит или перестает отвечать во время рендеринга или экспорта? Мы готовы помочь!
В данном документе приведены методы устранения следующих неполадок:
7 простых действий для исправления распространенных ошибок
Если проблема не устранена, выполните следующие действия.
Проблемы при рендеринге или экспорте определенного проекта?
При наличии подозрений, что проблема связана с определенным проектом, попытайтесь экспортировать другой проект и посмотрите, возможно ли это.
Если с экспортом других проектов не возникает проблем, ошибка рендеринга существующего проекта может быть вызвана наличием сторонних подключаемых модулей, переходов или LUT.
Чтобы устранить эту проблему, импортируйте необходимый проект в новый проект и повторите попытку экспорта.
Очень низкая скорость экспорта?
Чтобы увеличить скорость рендеринга необходимо убедиться, что устройство соответствует рекомендуемым системным требованиям. Дополнительные сведения см. в разделе Системные требования Premiere Pro. Кроме того, убедитесь, что используется последняя версия драйверов. Мы рекомендуем использовать драйвер NVIDIA Studio.
Для получения дополнительной информации см. документацию NVIDIA.
Premiere Pro продолжает зависать или перестает отвечать во время экспорта?
В качестве крайней меры, если решить эту проблему не удается, попробуйте вернуться к предыдущей версии приложения.
Для получения более подробной информации см. Установка предыдущих версий приложений Creative Cloud.
Hi mikkeljenson,
Sorry to hear you are having the same ERF problems as I was.
Last night I spent many hours going through all Adobes solutions, I had tried most of them already before contacting them, still, I aimed to please and went through them all again — sadly, to no avail 
I did manage to isolate and resolve what was causing my issues, it was the ‘.MXF’ format when importing into premiere pro cc 2019.
I never had the problem before CC 2019 as everything worked hunky-dory up until then, Adobe was pushing that it was my graphics card (Geforce GTX 970 4gb) but I just couldn’t accept this explanation as it was working great up until a few days ago.
I do know that on more than a few occasions GPU’s do cause issues but I was sure that here it wasn’t the case.
Another strange thing is that previous projects with the MXF incorporated seemed to work up until a few days ago but when I opened one up earlier it also started spewing out the dreaded ‘ERF’ error (Error Retrieving Frame) and it’s not funny as when you try to export the file the errors pop up every 2-5 seconds.
I will look further to see if all previous projects have this problem or if it is only isolated to new ones (projects)?
My solution was to re-download Canon’s MXF Utility install it and then run it from there so as to export each Take independently into a sequence of folders for each, then to import them into Premiere Pro CC 2019 (keeping each take sequence separately as otherwise mixing them all I was getting the same ‘ERF’ errors.
In ‘Canons, MXF Utility’ along the top panoramic media viewer I think each Icon is a separate take and this was how I was importing them. (Hope this makes sense.)
I know it’s awkward but for me, it was the only way I could get it to work.
if anyone knows a better way please let me know.
What file format are you working with? (Is it .MXF ?)
I wonder if anyone else has been having this issue as until as of yesterday I had never heard of it and there was nothing showing when I searched for a solution relating to «Error retrieving frame **** at time **:**:**:** from the file».
Hope you manage to resolve your situation.
Best.
H&M
Update
Another thing is, if you find more than one MXF file being imported into premiere pro cc 2019 (individual take) once it copies into the desktop/location folder import only the first in the sequence into Premiere as the others will contaminate the project but don’t worry all the footage is within the first MXF file (Check it and see.)
It was this that was causing the ‘ERF’ «Error retrieving frame **** at time **:**:**:** from the file.»
Which leads me to believe that it has something to do with importing MXF files and how the MXF structure does not record continuously but rather it breaks the footage into pieces and that is where the problem lays.
So I recommend using Canon XF utility to capture the MXF files (NOT Premiere Pro cc 2019,)
capturing them through the Canon MXF Utility viewing monitor as individual takes. (One icon at a time) as opposed to one continuous capture export.
This way each TAKE will have its own folder independent from the whole file and if there is more than one MXF file in each folder when importing them into Premiere Pro cc 2019 only import the first MXF in the sequence
For example, just imagine there are three MXF files you find when importing through premier from the folder where the Canon MXF Utility sent them ( AA050001, AA050002, and AA050003 )
Then only import the first in the sequence ( AA050001 ) as this contains all the information and the others just confuse it.
Remember do not import any sequential MXF’s in the shared folder as this will set off the ‘ERF’.
Hi mikkeljenson,
Sorry to hear you are having the same ERF problems as I was.
Last night I spent many hours going through all Adobes solutions, I had tried most of them already before contacting them, still, I aimed to please and went through them all again — sadly, to no avail
I did manage to isolate and resolve what was causing my issues, it was the ‘.MXF’ format when importing into premiere pro cc 2019.
I never had the problem before CC 2019 as everything worked hunky-dory up until then, Adobe was pushing that it was my graphics card (Geforce GTX 970 4gb) but I just couldn’t accept this explanation as it was working great up until a few days ago.
I do know that on more than a few occasions GPU’s do cause issues but I was sure that here it wasn’t the case.
Another strange thing is that previous projects with the MXF incorporated seemed to work up until a few days ago but when I opened one up earlier it also started spewing out the dreaded ‘ERF’ error (Error Retrieving Frame) and it’s not funny as when you try to export the file the errors pop up every 2-5 seconds.
I will look further to see if all previous projects have this problem or if it is only isolated to new ones (projects)?
My solution was to re-download Canon’s MXF Utility install it and then run it from there so as to export each Take independently into a sequence of folders for each, then to import them into Premiere Pro CC 2019 (keeping each take sequence separately as otherwise mixing them all I was getting the same ‘ERF’ errors.
In ‘Canons, MXF Utility’ along the top panoramic media viewer I think each Icon is a separate take and this was how I was importing them. (Hope this makes sense.)
I know it’s awkward but for me, it was the only way I could get it to work.
if anyone knows a better way please let me know.
What file format are you working with? (Is it .MXF ?)
I wonder if anyone else has been having this issue as until as of yesterday I had never heard of it and there was nothing showing when I searched for a solution relating to «Error retrieving frame **** at time **:**:**:** from the file».
Hope you manage to resolve your situation.
Best.
H&M
Update
Another thing is, if you find more than one MXF file being imported into premiere pro cc 2019 (individual take) once it copies into the desktop/location folder import only the first in the sequence into Premiere as the others will contaminate the project but don’t worry all the footage is within the first MXF file (Check it and see.)
It was this that was causing the ‘ERF’ «Error retrieving frame **** at time **:**:**:** from the file.»
Which leads me to believe that it has something to do with importing MXF files and how the MXF structure does not record continuously but rather it breaks the footage into pieces and that is where the problem lays.
So I recommend using Canon XF utility to capture the MXF files (NOT Premiere Pro cc 2019,)
capturing them through the Canon MXF Utility viewing monitor as individual takes. (One icon at a time) as opposed to one continuous capture export.
This way each TAKE will have its own folder independent from the whole file and if there is more than one MXF file in each folder when importing them into Premiere Pro cc 2019 only import the first MXF in the sequence
For example, just imagine there are three MXF files you find when importing through premier from the folder where the Canon MXF Utility sent them ( AA050001, AA050002, and AA050003 )
Then only import the first in the sequence ( AA050001 ) as this contains all the information and the others just confuse it.
Remember do not import any sequential MXF’s in the shared folder as this will set off the ‘ERF’.