Skip to main content
R
rony5E1D
Participant
November 5, 2021
Pregunta

Premiere Pro v.22 - Crashing, Exporting, Proxies, Previous Projects Don't Work

  • November 5, 2021
  • 5 respuestas
  • 2150 visualizaciones

his is by far the worst update ever.....nothing works ADOBE just waisting people time and money at this point ...

issues are

1 crashing without saving or warning

2 exporting issues

3 proxy dont work with media encoder (freeze PREMIERE}

4 all previous Projects no longer work

 

Mod note: Changed the title to reflect your actual issue.

 

    Este tema ha sido cerrado para respuestas.

    5 respuestas

    S
    stephenh71804362
    Known Participant
    July 18, 2022

    Identical issues with CPU maxing out in activity monitor at 2000% and crashing AME 2022 while making canon 4K proxies - at first I thought it was my machine slowly dying but when I use AME 2020 it just takes 600% CPU in activity monitor while executing the exact same tasks... I will uninstall 2022 version and wait for a fix...

    Kevin-Monahan
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    July 19, 2022

    Hey there, stephenh. 

    Sorry to hear about your troubles. It sounds like your project was corrupted in the new version. You can sometimes work around that by importing the old project into a new one. You can try that if rolling back did not help your situation. Let us know if we can help.

     

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    S
    stephenh71804362
    Known Participant
    July 19, 2022

    Thanks Kevin,

    here is my main thoughts on this problem. 10bit Sony FX3 4K files work perfectly in the "create proxy" AME putting no heavy usage on cpu however Canon mxf 4K files seem to push the AME cpu % consistently above 2000% and then the error appears media encoder cannot continue.

    the new 22.5 version of pr pro works perfectly. When I tried to export Canon mxf UHD 4K files in AME using create proxies it would work for a while then an error message media encoder had to quit due to a problem. In the activity monitor the cpu usage % was upwards of 2000% for AME while AME was executing these proxy encodes, I can't see how this has anything to do with PP file being corrupted. Anyway on rolling back a version all is well... the cpu % is 600% ish while encoding and the gpu is purring along fine as well.

    once I have a bit of clear air I will try again.

    my system is Catalina OS, MacPro 12core 48g ram areca blackmagic 4k extreme 

    my belief if that 22.5 AME on my system  is having compatibility issues with the canon mxf 4K files due to they work perfectly in AME 22.4

    anyway thanks again Steve

    B
    BillScurry
    Known Participant
    November 5, 2021

    Keyboard shortcuts are greyed out, meaning that the configuration is frozen on the factory Premiere default -- but I've used the Final Cut config since day one.

    R Neil Haugen
    R Neil Haugen
    Legend
    November 5, 2021

    You've got a permssions issue there probably, PrPro is having trouble accessing stored user data.

     

    Neil

    Everyone's mileage always varies ...
      T
      terrences88725115
      Participant
      November 5, 2021

      It want let me place a clip on the time line

      R Neil Haugen
      R Neil Haugen
      Legend
      November 5, 2021

      Do you have track targeting set? This trips up a lot of people. Just in case ... the two left blue blocks there in V1 and A1 are for clips coming in from the Source monitor. The two right-side blue blocks are Track targets for work done within the sequence.

       

      You enable/disable them by clicking on them.

       

      Neil

       

       

      Everyone's mileage always varies ...
      R Neil Haugen
      R Neil Haugen
      Legend
      November 5, 2021

      Hey, it's a pain to be a user hammered with a new version. Been there, done that ... one version it took something like three or more months before I could use it. The best advice is NEVER start working your client projects in a new major version until you've tested it on your machine with your media/effects/workflow and it works.

       

      In this case, that would be continuing to work work in 2021 (15.x) while installing and only testing 2022.

       

      That said ... anyone assuming their experience is universal is perhaps not ... necessarily accurate. You and some others are certainly not getting work in 2022 out ... you mention some things, others are having a real pain with Ae/Pr dynamic links.

       

      But then most users are actually not having issues. Like ... my rig is eating Pr2022 like candy right now.

       

      Some things that might have an effect for some of your issues. First, many people simply install the new version and 'open' old-version project files in the new version. Not normally the best way to migrate.

       

      First ... dump all cache files. Then in the new version, create new project files. Use MediaBrowser to select old project files, and import the assets from them into the new project file.

       

      This does two things: you have a clean new project file which has a better chance of working without issues, and your old project file is untouched and available for work in the old version still.

       

      The above process might have gotten you past the problem with old projects. I say might ... as it works for many things but of course not all. No guarantee.

       

      And you might do better at this point in using the CC Desktop app to uninstall any 2022 CC apps ... Pr, Me, Ae ... reboot the computer. Use the CC Desktop app to reinstall starting with Pr, then Me, then Ae.

       

      But whatever you do, you can keep working your deadline-facing projects in 2021 without issues.

       

      Neil

      Everyone's mileage always varies ...
      J
      jmmccray
      Participant
      November 5, 2021

      I'm also having exporting issues!

        Términos y condicionesAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices