Cannot open Project files from previous FCPX versions

Hello,
I'm currently on 10.0.8, and have not upgraded to 10.1.1. Here is my issue:
A documentary project I've been working on since 10.0.1 is not showing up in 10.0.8, and I'm wondering how to "manually" update the Project. I upgraded FCPX versions a few times while working on this Project (I think all the way up to 10.0.4), but then I stopped as I noticed it was negatively affecting parts of my project and making the application run slow (and Apple recommends you don't update versions while in the middle of a project). I finished that project, but now fast forward and I'm in 10.0.8 and I need to revisit that Project to make a few changes, but FCPX won't even recognize it. It successfully updated and recognizes the Events I used for this particular Project, but not the Project itself.
Any help/suggestions would be great.
Thank you!

Thanks Russ. After all this time, I actually solved the problem myself. I forgot that back 6 months ago, I renamed my Project file, from the default "CurrentVersion". I just came across another post that said you're not supposed to do that, so I changed my Project file back to "CurrentVersion" and now FCPX recognizes it. After all that toil, the answer was just too simple!!
Thanks.

Similar Messages

I cannot open pdf files from one supplier when using Adobe Reader but I can using another Viewer

I cannot open pdf files from one supplier when using Adobe Reader but I can open it if using Google PDF viewer or another viewer. The Adobe reader gives the error "There was an error opening this document. The file is damaged and could not be repaired" when I try to open the file. The version of Adobe Reader is 10.1.7, however I have tried other versions and they all fail the same way. I have tested on a number of different PC's in different networks and all fail using Adobe Reader but work using alternate viewer. Also the PC's will open a PDF from any other source.

Newer Reader versions are more strict than older versions (and other PDF viewers). If certain minimum requirements are not met, Reader will tell you that the PDF is damaged. This can happen when a document was created with software that does not adhere to PDF standards, or when the file was damaged during a download or email transmission.
You should contact the creator of these PDFs.

I cannot open a file from LR5 into CC2014 unless it is a smart object. also will not save back to LR at all it gives me an error message "Line: 1 - photoshop.notifyLightroomDocClosed ('lightroom-2.0', 'B53AFA39-A49B-4709-A9BD-0B6467C175C3', 'Macintosh H

I cannot open a file from lightroom into CC2014 unless I open it as a smart object. CC opens, just will not display my image. i am given an error code when I save an image, and can only save to my desktop or other locations, not automatically back into my lightroom.
I am using LR5 latest update, as well as CC2014
Below is the error message:
Line: 1 -> photoshop.notifyLightroomDocClosed ('lightroom-2.0', 'B53AFA39-A49B-4709-A9BD-0B6467C175C3', 'Macintosh HD:Users:BPexposures:Desktop:_DSC5962 as Smart Object-1.psd');

I was also having this issue, and I did some more searching and found this answer in the Adobe forums: Re: Photos from Lightroom 5 to Photoshop CC (2014) and back.... The issue appears to be caused by having not updated Lightroom to the latest version prior to having CC2014 installed (wow that's stupid). The trick seems to be to uninstall Photoshop CC2014 and to then reinstall it after having upgraded to Lightroom 5.5.

Mac OS X cannot open pdf files from online sites.

Mac OS X cannot open pdf files from online sites.

The problem is definitely between my safari and Adobe.
I can open documents in emails. But not something like this.
Your Folk Project newsletter for the coming month is available for download at:
http://folkproject.org/enl/eNewsletterDownload.shtml
Kathryn Weidener
Storyteller
908 369-7571
[email protected]

LR4.4: Cannot open Raw files from Olympus OM-D E-M1 [was:Adobe lightroom.]

Just bought a new cámara olympus OM E-1 and find that I can not download my fotos with
Lightroom 4.4. Lightroom does not accept the format ORF. any help please!

Thanks John you have been a great help! I will see what suits me best!
Enviado desde mi iPad margaret.
El 09/11/2013, a las 07:33, John Waller <[email protected]> escribió:
Re: LR4.4: Cannot open Raw files from Olympus OM E-1 was:Adobe lightroom.
created by John Waller in Photoshop Lightroom - View the full discussion
DNG Converter.
Read all about it here
http://www.adobe.com/products/photoshop/extend.displayTab2.html
It's a way of opening the Raw files from your OM-D EM-1 without having to upgrade to LR5.
In short, you open the Raw files from the camera uing the DNG converter, convert the Raw files to DNGs. Then you edit the DNG files in LR4.4.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5828160#5828160
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5828160#5828160
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5828160#5828160. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Lightroom at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

I just began month trial of cs6 & cannot open raw files from nikon 600?

I just began month trial of cs6 & cannot open raw files from nikon 600?

Have you updated your Photoshop to get the latest Camera Raw update patch? If not go to:
Help >> Updates
This should get you the necessary updates for your camera assuming it is not "too recent".
Good luck and post back.

Cannot open project file with write access...

I have seen that this problem has been reported before but have yet to find a solution.
I have my project file in an external hard drive. When I plug the hard drive to another computer and want to save it I get this message:
"Cannot open project file with write access. The file may be locked or you don't have permission to write to this location. Select Save As..."
I don't want to Save As because other projects make reference to this file and also my Encore file will be messed up.
FYI both computers use Windows 7.
Any solutions?

Right click on the folder in Question and select properties. Then select the security tab. Make sure you add everyone to the user list. You do that by selecting edit and then add. Type in everyone in the object section and hit ok. Then select the everyone user and checkmark the Full control. Hit Apply and it will adjust the permissions for the folder and subfolders and files.
Eric
ADK

Unable to open project file - from one 6.0.2 to another 6.0.3.

Hi
We're at a time-critical stage of finishing our movie, and we need to get the color-corrected sequence from the post-house to our studio so we can make some picture changes and get it back to them. They can open the project file just fine (it was created in 6.0.2, but they since updated their system to 6.0.3), and we have just updated to 6.0.3 also. Quicktime is 7.4.5 (which matches their version). However, they've FTP'd it to us, and we cannot open it here. FCP gives the error "Unable to open project file". It's not the "older version" message which I've seen before, it just ... fails to open it. Almost as if the file were corrupt. However, the post house can re-download the file from FTP and open it there, so this confuses me. I've also tried the file on a FCP 6.0 system (which I can't update because it's an Avid system locked to a certain version of Quicktime) and the same error message.
Would anyone be willing to test the file and see if they can, at least, open it?
Many thanks.
Matt

Have them zip the file... Project files via email often don't open if they aren't zipped..
Jerry

LV RTE cannot open project files that have .lvlib references in Dependencies

I'm writing a LabVIEW DLL to inspect LabVIEW project files, and I've noticed that if a project has a .lvlib reference in its Dependencies, then the Run-Time Engine contradicts itself about whether or not it can find the project file:
Project.Open returns error 7 (file not found)
Project.GetFileLVVersion is successful
Here are snippets from my G and C code that exercise this behavior:
int openStatus = StatusSuccess;
char* projectVersion = createStringWithLength(VersionStringLength);
printf("Analyzing %s\n", pathString);
OpenProject(pathString, &openStatus, projectVersion, VersionStringLength);
printf(" Project written in LabVIEW %s\n", projectVersion);
if (openStatus == StatusSuccess)
printf(" Opened project file.\n");
else
printf("Error: Could not find project file, or file was not a project file (error code %i).\n", openStatus);
However, when running in the development environment, both methods succeed.
Is this a bug, and if so, is it fixed in LabVIEW 2014?
Here is how you can reproduce it:
Prerequisites:
LabVIEW 2013 SP1 32-bit
ConEmu for a good console -- https://code.google.com/p/conemu-maximus5/wiki/Downloads
minGW for compiling a program to use the LabVIEW DLL -- http://sourceforge.net/projects/mingw/files
.lvlib reference in Dependencies breaks Project.Open in LV RTE
Unzip the attachment into a temporary directory (eg c:\xtra\temp)
Open "OpenProject.lvproj" in LabVIEW.
Build "Open Project Library".
Using ConEmu with a bash prompt, navigate to the temporary directory.
Type make
$ make
patching file `builds/platdefines.h'
gcc -std=c99 -g OpenProject.c -o OpenProject.exe -lOpenProject -Lbuilds
6. Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Analyzing c:\xtra\temp\OpenProject.lvproj
Project written in LabVIEW 13.0
Opened project file.
7. Notice that both invoke nodes execute correctly.
8. Type OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
Analyzing c:\xtra\temp\OpenProjectWithLvlibDep.lvproj
Project written in LabVIEW 13.0
Error: Could not find project file, or file was not a project file (error code 7).
9. Notice that the version node succeeded while the open one failed.
10. Type diff OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
$ diff -u OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
--- OpenProject.lvproj Tue Nov 4 11:28:28 2014
+++ OpenProjectWithLvlibDep.lvproj Tue Nov 4 11:32:37 2014
@@ -13,7 +13,11 @@
<Property Name="server.vi.propertiesEnabled" Type="Bool">true</Property>
<Property Name="specify.custom.address" Type="Bool">false</Property>
<Item Name="OpenProject.vi" Type="VI" URL="../OpenProject.vi"/>
- <Item Name="Dependencies" Type="Dependencies"/>
+ <Item Name="Dependencies" Type="Dependencies">
+ <Item Name="vi.lib" Type="Folder">
+ <Item Name="NI_MABase.lvlib" Type="Library" URL="/<vilib>/measure/NI_MABase.lvlib"/>
+ </Item>
+ </Item>
<Item Name="Build Specifications" Type="Build">
<Item Name="Open Project Library" Type="DLL">
<Property Name="App_copyErrors" Type="Bool">true</Property>
Here is another way to trigger this behavior, which also shows that LabVIEW only sometimes tidies the Dependencies item:
Open "OpenProject.lvproj" in LabVIEW.
Add a new VI to the project and place the "Application Directory" file path constant its block diagram.
Select "File » Save All (this Project)" and use the default name for the new VI.
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Remove the "Application Directory" file path constant.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice the problem is gone, as is expected.
Re-add the "Application Directory" file path constant to the block diagram.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is no problem, which is surprising as there should be an error since the Dependencies item hasn't been tidied.
Close the new VI and remove it from the project.
Select "File » Save All (this Project)"
Open "OpenProject.lvproj" in a text editor.
Notice the Dependencies item has been tidied.
Re-add the VI back to the project.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Solved!
Go to Solution.
Attachments:
LVRTE_OpenProject.zip ‏10 KB

NInjaneer_wow wrote:
The same behavior occurs in LabVIEW RTE: a new project with an Application Directory constant in a blank vi will return error 7 - file not found, but still return the correct version of LabVIEW in which the project was created.
I've been experimenting with workarounds for this behavior, and I found one.
When I provide the LabVIEW path for libdir in my executable's ini file, the run-time is able to load and inspect the project file.
libdir="C:\Program Files\National Instruments\LabVIEW 2013"
While it's expected that a stand-alone executable may be placed on a system that doesn't have the LabVIEW IDE, it's still surprising to me that the Run-Time Engine cannot find LabVIEW's standard library without some explicit guidance. What other considerations contribute to that behavior?
References:
LabVIEW configuration file/Paths -- http://labviewwiki.org/LabVIEW_configuration_file/Paths

Unable to open project files from 2001

I have a .fcp file and a .fcm file from 2001 that I am unable to get FCP 5 to recognize. For the .fcp it gives the error "Unable to open project file." For the .fcm it says "File error: Wrong type." I don't remember which version of FCP they were made on (perhaps even FCP 1?) but I'm really worried about not being able to open them anymore. Any suggestions, please?

Oh no! I am really in trouble, because this is a very complex project with about a million cuts. What you're basically saying is I should just start over? What other options to I have? There must be some way to convert an old FCP file, no?

Cannot open NEF files from D200 in Camera Raw 4.1

I am using Photoshop CS3 with Windows XP. I have downloaded the latest Camera Raw update (4.1) and installed as directed.
I am able to open Raw files from Nikon D70 in camera raw but unable to open files from D200 - I am getting the message that it is an invalid file.
When I revert back the the previous version of camera raw I can open these files with no problem.
Can amyone advise please.
Thanks
J

Janet,
> I am not using Photoshop 6, where did you get that from?
We are referring to Trevor in post #2, not you.
As to your issue, just a general comment, as I don't do Windows:
Even though it sounds too obvious, make sure you have properly uncompressed (unzipped) the downloaded ACR 4.1 and that you have installed it according to the instructions.
>I have downloaded the latest Camera Raw update (4.1) and installed as directed.
Note that you didn't say "unzipped", so forgive me for bringing it up.

CC cannot open a file created in latest version

I subscribe to CC. I tried to open a file from a client. I got a message saying I couldn't open it "because it was saved with a newer version of Adobe InDesign CC (9.1)". I hit the update button in InDesign multiple times and no updates for InDesign appear. I check my (PC) version and it is 8.0.2. My question is whether since my client uses a Mac is it possible that Adobe has a newer version(9.1)available for Mac which then cannot be opened on the newest PC (8.0.2) version?
If that guess is wrong, does anyone have any idea what might be the problem?

version 8.x is CS6... download the CS6 CC exchange app.
wait a min: thats something else
G

Trying to open a file from an older version to a new version of indesign

I'm on am mac and i am trying to open a file from the 2014 indesign with 2015 software, i am getting this error:
what i don't understand is why a newer version can't read the file of an older version

That is exactly the opposition of what you are trying to tell us.
Correct is:
You have Adobe CS6, version 8.x.
You get a file from someone else, who has Adobe CC 2014, version 10.x.
You are trying to open that file on your computer.
But because that file was created in a later version, you get this message.
Either ask to get an IDML file (with a PDF), tell them, they should go to File > Package… and check IDML and PDF export.
Better would be, if you also subscribe to the Creative Cloud to be up to date with the latest version.
But what you should do anyway, update your InDesign CS6, as there are updates available which will correct this error message, as from CS7 upwards no CS exists anymore.

Photoshop Elements 9 and cannot open Raw files from my Canon EOS 1000D camera.

I am using Photoshop Elements 9 on a Windows 7 based PC and would like to know why I cannot open Raw files produced by my Canon EOS 1000D camera.
I have checked the version of the plug in as 6.5 for raw files which is supposed to open .cr2 files and should be compatible according to Adobe site info.
any ideas for next move.
Mick

Hi,
According to all of Adobe's charts, the Canon 1000D should be supported by the basic PSE 9 even without updates. When you said you checked the camera raw version in PSE, did you do that by going to the Help menu and selecting About plugins -> Camera raw?
The Canon 1200D requires ACR 8.4 which is only compatible with PSE 12 - so for PSE 10 your brother would need the DNG converter.
I can't find a sample raw file to try (I do have PSE 9). If you want to upload a sample file to dropbox and give me access, I could try it on my system.
Have you tried opening one of your files on your brothers system?
Nrian

Cannot open raw files from my Nikon D3200 in Elements 11

After I found I could not open raw files from my new Nikon D3200 in Elements 10, and did a couple hours of searching the web site, I upgraded to Elements 11. Elements 11 also will not open the raw files from the D3200

I found the solution in a Light Room forum. The problem was I was using an older version of View NX2 to transfer the files. I uninstalled that version and installed the version supplied with the D3200. The files now load into Elements 11 with no problem. Apparently the old version affects the content of the NEF files, as Elements was not able to recognize them, and gave an error message that the files were from an unsupported camera.
Thanks for looking into this, Don Rieser

Cannot open Project files from previous FCPX versions

Similar Messages

Maybe you are looking for