Open a project in Premiere Elements 2022 takes a very long time in comparision to 2020

New Here ,
Dec 14, 2021 Dec 14, 2021

Copy link to clipboard

Copied

Hi,

I moved from version 2020 to 2022.

Opening of my project in with Premiere Elements 2020 took less than 30 seconds.

Opening the same project in with Premiere Elements 2022 takes about 5 minutes.

I am sure I have proper hardware (processor , RAM, SSD). OS is Windows 10

I would be happy if someone has an idea how to improve the loading performance.

Thank you.

TOPICS
Error or problem , Performance

Views

186

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 14, 2021 Dec 14, 2021

Copy link to clipboard

Copied

Are you opening the project you created in versino 2020 with version 2022? That could be the problem. Premiere Elements has never been completely backwards compatible, and opening a project created with an older version of the program can cause buggy behavior and even corruption.

 

Granted, that makes an apples to apples comparison much harder. But make sure both your new 2020 project and your new 2022 project use the same media -- and that they were both created in the programs you're opening them in.

 

Though I too have found version 2022 a bit sluggish compared to earlier versions. Slower to import media and slower to open. But not terribly so.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 22, 2021 Dec 22, 2021

Copy link to clipboard

Copied

Thank you for fast your response. Sorry for answering late.

I understand your explanation.

When I moved to 2022 I did not change anything in the project or file locations at all. I only opened the project with the new version.

If I understand you correctly I must live with this performance leak from some seconds to some minutes.

 

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Dec 22, 2021 Dec 22, 2021

Copy link to clipboard

Copied

No, Steve wrote, " a bit sluggish".   You are going from 30 seconds to 5 minutes.  That is a tenfold slowdown!  There is something wrong somewhere.  On my computer, I've found no difference.  But, I've not looked for it either.   

 

If it were me, I would initiate an online chat with Adobe techs and find what may be wrong.   https://helpx.adobe.com/contact.html?rghtup=autoOpen

 

If they can't find the issue, use the same link to get a refund under the 30 day satisfaction policy. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 24, 2021 Dec 24, 2021

Copy link to clipboard

Copied

Thank you for your tip.

I will follow up and try it.

Merry Christmas and Happy New Year

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 25, 2022 Mar 25, 2022

Copy link to clipboard

Copied

LATEST

The chat button is often not visible. Try opening the page in another browser or disabling cookies

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 02, 2022 Jan 02, 2022

Copy link to clipboard

Copied

I am back again.

I have not found any possibility to chat with the support. Even not on your link page. Could be because of the holidays.

Nevertheless I tried to continue with my project and started the audio part.

Working with PE 2022 becomes worse and worse.

Changing the volume of one or more clips and starting the preview leads directly to a system crash. Then 5 minutes to restart, there is no way to work with PE 2022 anymore at all.

I had a look in the log files and found one exception in a log file in user\<myuser>\AppData\Roaming\Adobe\CRLogs\crashlogs

 

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport serviceVersion="4.7.0" clientVersion="4.7.0" applicationName="Premiere Elements" applicationVersion="20.0" build="20210907.Git.main.abec5bc" source="Windows-Client" crashType="n/a">
<time year="2021" month="12" day="29" hour="17" minute="36" second="10" timeoffset="60" timezone="Mitteleuropäische Zeit"/>
<user guid="...."/>
<system platform="Windows 10 Pro" osversion="10.0" osbuild="19041" applicationlanguage="de-de" userlanguage="de-DE" oslanguage="de-DE" ram="32654" machine="Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz" model="Intel64 Family 6 Model 60 Stepping 3" cpuCount="8" cpuType="8664" cpuFreq="3093 MHz" processorArchitecture="9"/>
<gpu>
<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) HD Graphics 4600" description="Intel(R) HD Graphics 4600" driverDate="20171016000000.000000-000" driverVersion="20.19.15.4835" videoModeDescription="1920 x 1200 x 4294967296 Farben" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_0412&#38;SUBSYS_11E71734&#38;REV_06&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>
</gpu>
<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x00000000128072F5">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x00000000128072F5" symbolname="AF::AudioEnvelope6::processReplacing"/>
<stackStatement index="1" address="0x0000000002887461" symbolname="ML::LogAudioFilterUsage"/>
<stackStatement index="2" address="0x00000000046414A8" symbolname="AR::AudioRendererFactory::CreateTimeStretchedAudioGenerator"/>
<stackStatement index="3" address="0x0000000004658200" symbolname="AR::AudioRendererFactory::CreateTimeStretchedAudioGenerator"/>
<stackStatement index="4" address="0x0000000004656B4C" symbolname="AR::AudioRendererFactory::CreateTimeStretchedAudioGenerator"/>
<stackStatement index="5" address="0x0000000004618BFB" symbolname="AR::AudioMatrixToString"/>
<stackStatement index="6" address="0x0000000004617724" symbolname="AR::AudioMatrixToString"/>
<stackStatement index="7" address="0x000000000463624F" symbolname="AR::AudioRendererFactory::CreateTimeStretchedAudioGenerator"/>
<stackStatement index="8" address="0x00000000035251F6" symbolname="ML::LandmarkExtractor::Process"/>
<stackStatement index="9" address="0x000000000350B617" symbolname="ML::AudioSupport::Shutdown"/>
<stackStatement index="10" address="0x0000000003517121" symbolname="ML::CompilerMixer::Start"/>
<stackStatement index="11" address="0x000000000351B0C1" symbolname="ML::CompilerMixer::Start"/>
<stackStatement index="12" address="0x000000000861D74A" symbolname="dvaaudiodevice::AudioDevice::DoProcessing"/>
<stackStatement index="13" address="0x0000000008630659" symbolname="dvaaudiodevice::AudioDevicePhysicalStream::Write"/>
<stackStatement index="14" address="0x0000000008632E17" symbolname="dvaaudiodevice::AudioDevicePhysicalStream::Write"/>
<stackStatement index="15" address="0x0000000008634D5E" symbolname="dvaaudiodevice::AudioDevicePhysicalStream::Write"/>
<stackStatement index="16" address="0x000000000861D6AA" symbolname="dvaaudiodevice::AudioDevice::DoProcessing"/>
<stackStatement index="17" address="0x00000000086FC537" symbolname="dvaaudiodevice::support::GetAudioEndpointSampleRate"/>
<stackStatement index="18" address="0x00000000086FB496" symbolname="dvaaudiodevice::support::GetAudioEndpointSampleRate"/>
<stackStatement index="19" address="0x000000000870066A" symbolname="dvaaudiodevice::support::GetAudioEndpointSampleRate"/>
<stackStatement index="20" address="0x00007FF937D07034" symbolname="BaseThreadInitThunk"/>
<stackStatement index="21" address="0x00007FF938022651" symbolname="RtlUserThreadStart"/>
</thread>

 

At the moment I cannot continue my work. It seems there is no way back to an older version e.g. 2020 or 2019.

If someone can solve the problem I would be very happy.

Is there somewhere German support?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 03, 2022 Jan 03, 2022

Copy link to clipboard

Copied

Now I have contact to the support. Thx for help.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jan 24, 2022 Jan 24, 2022

Copy link to clipboard

Copied

      Can you please provide your project settings details (Aspect ratio, timebase, display format etc) and project size.

Likes

Translate

Translate

Report

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