-
1. Re: Issues opening CS6 projects in Premiere Pro CC
monstremoi Jul 9, 2013 2:17 PM (in response to pilgrim_)How long does CS6 take to locate the same files with the project file, verses PPRO CC with the same files and project from CS6?
-
2. Re: Issues opening CS6 projects in Premiere Pro CC
pilgrim_ Jul 9, 2013 2:26 PM (in response to monstremoi)I don't know how long it takes CS6 I only have PPRO CC.
-
3. Re: Issues opening CS6 projects in Premiere Pro CC
JSS1138 Jul 9, 2013 3:22 PM (in response to pilgrim_)There are reports of some oddities, including slow downs, with projects created in earlier versions. You should ideally finish a project in the same version it was started in.
If you have CC7, then you're a Creative Cloud subscriber and have access to CS6 as well.
-
4. Re: Issues opening CS6 projects in Premiere Pro CC
pilgrim_ Jul 9, 2013 4:14 PM (in response to JSS1138)Right now I'm using the CS7 trial so CS6 isn't even an option. This makes manipulating old projects a real bother to do in CS7, but I guess there isn't any way around it.
After the yellow bar is finally full it takes me back to the link media page, asking me to locate offline media. I'll hit cancel and everything is still offline. I end up repeating this process until eventually it decides to find media.
-
5. Re: Issues opening CS6 projects in Premiere Pro CC
JSS1138 Jul 9, 2013 4:33 PM (in response to pilgrim_)I guess there isn't any way around it.
There is one. Pay money for the software, then you get the version you need.
-
6. Re: Issues opening CS6 projects in Premiere Pro CC
pilgrim_ Jul 9, 2013 4:35 PM (in response to JSS1138)That doesn't help CS7 work, it just means I have to use CS6, which is kind of lame.
-
7. Re: Issues opening CS6 projects in Premiere Pro CC
PaulM-Aus Jul 9, 2013 4:51 PM (in response to pilgrim_)I opened a large CS6 project in CC for the first time this morning and the process took a good 15 minutes to locate the media. It found all the media without fault but nothing had been moved since saving it in CS6. If you're bouncing a project around suites or drives that could explain why it threw up the offline errors. From my limited experience updating about a dozen CS6 projects into CC the wait time is normal and depends on the size and complexity of the project. How long is it taking on your system to open pilgrim, and can you give us a rough idea of how much content is sitting in the project?
-
8. Re: Issues opening CS6 projects in Premiere Pro CC
pilgrim_ Jul 9, 2013 5:45 PM (in response to PaulM-Aus)The project size is 508 GB. There is lots and lots of media from lots of different cameras, there is a bunch of RED footage too. I've linked media in a project of similar size in CS6 on the same computer with the same hard drive setup and didn't take anywhere near as long. It took closer to 4 hours to locate 70% of my project using CS7.
-
9. Re: Issues opening CS6 projects in Premiere Pro CC
JSS1138 Jul 10, 2013 6:26 PM (in response to pilgrim_)That doesn't help CS7 work, it just means I have to use CS6
Well, it's not that it "doesn't help CC7 work", as such, it just means you may not be able to squeak another month out of Adobe using the software for free. You may actually have to pay for it.
-
10. Re: Issues opening CS6 projects in Premiere Pro CC
Zach Powers Aug 5, 2013 11:30 AM (in response to pilgrim_)You should file a bug report with Adobe. I just did. I am experiencing the same issue on multiple machines with Creative Cloud licenses. I waited to upgrade until I was finished with my major active projects in CS6, but I'm not recalling projects from last year for a couple of clients, and I have to wait around for hours to re-link just a couple of files at a time. If I didn't need a few hundred markers and other project-specific things from those old projects, I would just re-edit the sequences based on my EDLs because that would be much faster than waiting for the re-link. Premiere CC supports backwards compatibility with CS6 project files (mine are just fine once I go through the hours of re-linking), and I never experienced a similar issue after upgrading from CS5.5 to CS6 early last year, so I think it's a bug.




