Just to clarify: Changing the file name didn't work. Exporting to GoPro Cineform didn't work. Is that correct? ... View more

Mo and Neil gave you good info, if a bit unpleasant.  Before you wipe your system, though, try this: Launch Pr from a shortcut (Taskbar, Start Menu, Desktop) while holding down the Shift+Alt keys.  Alt resets prefs and Shift clears plugin cache. Keep the keys pressed until the main program window appears. Before trying to open any project or starting a new one, go to Preferences>Media Cache and delete *all* your media cache files. Now try opening your problem project or starting a new one and then importing the old one into it. Try selecting just one sequence in the Project panel (what you called the "media bin") and then trying the XML export again using File>Export>Final Cut Pro XML.   You should also try setting your default audio input to none in Preferences>Audio Hardware. ... View more

There may be a problem with your file name as well. Too long or too many non-alphanumeric characters.  Try a test export using a short file  name like "TestExport01" without the quote marks.  ... View more

Thanks for posting back with your results! ... View more

I'm sorry you're having to go through all this. It's not normal behavior for Pr.   It was a good idea to try a different selection in the Project panel for FCP XML export, but I'd like you to try one more. Pick a sequence, just one, in the Project panel and try to export an XML file. What happens?   Are you running Pr as an administrator? Are all of your folder permissions correct?   Finally, it may help us if you gave very detailed information about your editing rig, including type and number of monitors. https://community.adobe.com/t5/premiere-pro/faq-what-information-should-i-provide-when-asking-a-question-on-this-forum/td-p/3929027?page=1   For what it's worth, there is something major that's wrong with your system or with your Pr installation or with this particular project. What I hope is that it's solvable to some degree and you can get your system to either work or let you move on. ... View more

Please post a zoomed-in screenshot of your timeline before the delete operation and a screenshot of your timeline after the delete operation. ... View more

I don't think the tracks underneath are being ignored, they just may not be visible if the track above doesn't have an alpha channel, either as part of the clip or created by a track matte or keying. ... View more

Try changing Mercury Playback Engine to software only in your Project settings. ... View more

Are all of the imported illustrations the exact same frame size? Posting screenshots here of your illustration properties, your sequence settings and your export settings might be helpful. ... View more

See my answer in your color grading topic:   https://community.adobe.com/t5/premiere-pro-discussions/premiere-changed-all-of-my-color-correction-grading-dramatically/m-p/12869286#M404689 ... View more

@defaultxevn64n09qqn wrote: I opened it in 2021 and it's still messed up.  I don't know what you mean by "reseeting your workspace" or "changing to a default workspace".  I've never done this.  I don't know what this means or how I would do that.           ... View more

You can export your project as an FCP xml file. Go to File>Export>Final Cut Pro XML.   EDIT: Pr only exports FCP 7 format XML files. FCPX won't read FCP 7 XML files. Why Apple doesn't have that backward capability is puzzling. Why Adobe doesn't create XML files that can be used in FCPX is also puzzling. To bridge that gap you need a $20 utility called SendToX. Detailed instructions and things that get lost in translation are on their web site. ... View more

If you can get any version of Pr 2021 to run, try importing one of your old 2021 projects into a *new* 2021 project. If that works and the color grade looks like you want, then try saving that new 2021 project and importing it into a brand-new, empty, 2022 project. If this is just a problem of a slightly corrupted project file, then the project import step should fix that.   Also try resetting your workspace, or changing to a default workspace and resetting that.   All this is done in the hope that the grading information you need is still in those project files and you just need Pr to get at it. ... View more

Are you able to change Mercury playback engine to software only? It may be dimmed on your M1, however. ... View more

Do you have a saved version from before the upgrade to 2022? If so, save a copy of that project file somewhere safe and try opening the saved version in 2021, then in 2022. (This assumes that it worked as expected in 2021). You should also try importing the problem project into a new 2022 project. ... View more

Two thoughts: 1. Graphics drivers 2. Set Mecury playback to software only. ... View more

And with all the nonsense software Dell loads up on its computers, there may well be a software conflict. Anti-virus and other system-level background processes can wreak havoc on Pr because Pr needs low-level hardware and OS access. There may also be so much bloatware and adware launching at system startup that Pr can't grab the resources it needs. ... View more

The OP is 2 years old so I think Mike may have moved on by now. ... View more

I have a 2019 MacBook Pro running Monterey 12.3.1 The GPU is separate from the CPU. Your M1 Max, as I understand it, has graphics integrated in the CPU, so there is no way to exclude the GPU part of the CPU from being used. If that is correct, then the option being grayed out makes sense. I assume you're running the Apple silicon native version of Pr? You may want to try running the Intel version under Rosetta to see if you can get better results. ... View more

I can't set the default duration to 1 frame, but I can set it to 0.03 seconds, which is the 1 frame equivalent for a 30 fps sequence.  The only annoying thing is that you have to change the time duration for each sequence based on frame rate.   Unless 0.03 or 0.04 secs is close enough and prevents the bleed between clips no matter the frame rate. ... View more

Check for system overheating. If you are working from an external drive make sure it's a fast drive and that no other hardware or software is using the same bus as the drive. Check for software conflicts like antivirus and other system monitoring apps.   EDIT: I just your post above. Try disabling the onboard Intel graphics either through the Nvidia control panel or system bios. ... View more

I'm not sure exactly what you are trying to do here.   Are you trying to get the top disc to look like it is spinning above the bottom disc while the bottom disc also spins?   You may have to adjust the anchor point for each layer to get it to look right if that's what you're trying to do. ... View more

@M.23772777hgxe wrote: If you reset settings then you can open project.   It may be worth spending some time to discover which setting is getting changed that causes the project not to open.   You should also try resetting your workspace(s) once you get a project to open. ... View more

Please try running Pr under Rosetta. There may be a conflict between displays that the built-in graphics of the M1 chip can't handle natively. ... View more

Try these steps, please, in order. Even though you've reset preferences, please try it again as part of these steps: Launch Pr from a shortcut (Dock, Launchpad, Desktop) while holding down the Shift+Opt keys.  Opt resets prefs and Shift clears plugin cache. Keep the keys pressed until the main program window appears. Before trying to open any project or starting a new one, go to Preferences>Media Cache and delete *all* your media cache files. Now try opening a project or starting a new one. ... View more

How does Pr perform if you temporarily use just the MBP screen and not the LG screens? How does it perform if you use the MBP screen and just one of the LG screens? Have you tried running Pr under Rosetta? Or natively if you are already using Rosetta? ... View more

Thanks for posting back! ... View more

@Andy 1968    At the risk of being called a fanboy, sycophant, apologist or similar derogatory term, if you're going to call somebody out by name, you should at least do them the courtesy of spelling their name correctly.  It's Monahan, not Monohan.  Why would I bother to post this irrelevant bit of tripe? Because I've put up with people mispronouncing and misspelling my name my whole life. Kevin deserves to have more care taken than that.   ... View more