Copy link to clipboard
Copied
I have a lot of CS6 projects that I'm going back and reworking in Premiere Pro 2024. This worked fine for a while, but starting a couple of months ago an annoying glitch popped up.
When I specifiy the destination folder and tell it to create the new version of the project, it does its thing, pops up the warning about the Legacy Titler no longer being supported, and creates the project. However, when it does so, the Project window - the one that lets me see and organize all the sequences, bins and media in the project(!) - is missing from its usual place in my workspace.
If I go to the Windows menu, Projects> and select the project name, an error pops up that says "Matrix Cannot Be Inverted."
So in order to work around this, I have to start a brand new PP 24 project, then import the main sequence and its accompanying media from the CS6 project. This works, but seems unnecessarily kludgy and time-consuming especiall for something that used to work fine.
Update: Today, for the first time in 6 months; I had an old CS6 project *not* go stupid on me in this manner when opened/resaved in Premiere Pro 24. I was actually able to pull up my sequences, tweak them and re-export the final product without having to take that extra step of first creating a new version of the project and importing the sequences into it. I didn't change anything on my end; I wonder if Adobe updated something under the hood or a recent Windows update perhaps could have unknowi
...Copy link to clipboard
Copied
I've recently started evaluating old projects also. (circa 2014) I am encountering the same error under the same circumstances. Thanks for the workaround. At least I know the project isn't gone forever.
Copy link to clipboard
Copied
Update: Today, for the first time in 6 months; I had an old CS6 project *not* go stupid on me in this manner when opened/resaved in Premiere Pro 24. I was actually able to pull up my sequences, tweak them and re-export the final product without having to take that extra step of first creating a new version of the project and importing the sequences into it. I didn't change anything on my end; I wonder if Adobe updated something under the hood or a recent Windows update perhaps could have unknowingly solved the issue?