How to open Project File?

Sorry for this I am a newbie, I love the "Fun With" series but I don't know how to open the project files. It comes to my desktop with stuffit expander and then in text edit it looks like a mess. Please advise and thanks!

Ah - Good point, Kyriakos!
Tornlov, many of the Fun With use the Replicator, which is not available in Motion 1.0, however, many do not use the replicator. To try a project in Motion 1, first uncompress the zip file by double clicking on it, you should find a .motn file. Open it in Text Edit and change the version from 2.0 to 1.0 and save.
post back,
Patrick

Similar Messages

"Unable to Open Project File" - error

Does anyone know how to resolve an "Unable to Open Project File" - error. I accidentally shut down my computer wrong, although Final Cut wasn't open.

Welcome to the forums.
The project file might have gotten corrupted. Look for the AUTOSAVE VAULT (typically in the DOCUMENTS>FINAL CUT PRO DOCUMENTS folder) and open the most recent version. Copy it to your main project folder if it works.
If not, then try trashing your prefs with FCP Rescue.
Shane

Error Can't open project file

Was working fine on a project. Closed the project tried to access it again got this error message.
Error Cant open project file: {0}
The project is there when I check in windows explorer. Can anyone help? I have a back up so I am able to continue working but I am concerned has to how this may have happened.
Regards
Betty

Hi Betty,
The application bean might have gotten saved inadvertantly with an unnoticed / unintended change after you copied the code from it. Its a slim chance but could have just happened. If by chance it was so, then the IDE would have had difficulty in recognizing the file as a result of which that error was thrown.
In case you are sure the file was not modified could you please provide us the steps to reproduce the problem.
Cheers
Giri :-)
Creator Team

"Unable to open project file." i need help! URGENT

before the problem...
my film project and all its files were in a WD external drive. i had some problems with soundtrack pro being too slow because the files were on an external drive, so i bought 2 Internal Seagate drives. i moved all my files to the internal drives, and i changed my scratch disk to my new drive.
i have done this procedure several times before, and i never faced this problem before!
after...
so i went on to launch my FCP project, and while loading i got this message "Unable to open project file."
how can i fix it?

nope!
but here is what i did:
i reformatted it, and moved the files again... and surprisingly, it worked!
computers have a mind of their own sometimes!
but now i have another problem... i opened soundtrack pro to work on the same project, but its very slow! it keeps freezing whenever i want to make any actions.
whats the problem? and how can i fix it?

Unable to open project files can filters effect this ?

Hi Guys ! I have been a long time reader of the forums and from just observing have always learned a great deal from the discussions. Up until now I have been able to read through post and always find an answer from some of the great advice. As a relatively new Final Cut Editor I have limited knowledge but can edit and have learned enough to structure my work flow and put a project together how I would like it and complete with good results.
I have read a few post on this subject “Unable to open project file” but haven’t seen any with the specifics as my own.
Up until yesterday my files were opening all fine and working perfectly until this last night I had saved and shut down my Mac in the normal fashion. When I tried to open two specific files I was greeted with the infamous “Unable to open Project Files”. These as I can gather are the only two files that will not open and both files have used the RIVER ROCK– Chromatic Glow, or Day for Night Free downloadable Filters in the last 2 weeks could this be the reason ?
I have all the recent updates and have tried going into the Auto Vault and Render files to access the last available versions of these project files. I am able to access those but am only left with a much earlier version of the same project like a version a week earlier without vital changes.
So I would pretty much have to start again.
Any Help would be greatly appreciated
Regards
FC

Hi Tom thanks very much for your reply! , I un mounted the external drive , and reset and created a temporary scratch disk on My Hardrive to get Fce to start.
The 3 projects I have been working on which all were rendered on the 2nd of April around 3 in the afternoon. Two of the Files using the River rock filters are Not accessible from the most recent and up to date versions. The one remaining Project is able to be opened and is the only one not using the filters.
The two files accessed from the auto save vaults before April 1st up to 3pm April 2nd are working and are able to be opened with no problem. Everything after that is not opening which is a real downer as its where the project became near completion but at least I have a time frame of when things started to go wrong.
What would you suggest?

Unable to open project file. even though I just saved it.

Hi,
I just started back to work on a little FCE 2 video project after a couple of months. When I went to load the file, it said "Unable to open project file". I thought, "hmmm, I'm a beginner, maybe I'm not opening the right file." So, I made a new project with a clip and save it. Then I tried to reopen it. No go. Same message.
So, something is wrong but I can't figure it out.
My preferences are set to save the file on an external hd. The file icon shows up but says that the FCE project file has 0KB. How can that be?
I look using spotlight for the file, thinking maybe the file was saved elsewhere. It doesn't show up.
Sorry if this subject has been treated before. I searched the forum and didn't find a problem that matched my circumstances. One that was close.
Thanks for any help you can give.
Doug

Thanks for your reply Kyriakos.
Yep, I've tried the files in the AutoSave Vault and still Unable to Open Project File.
Also tried deleting the FCE preference and cache file, fixing permissions and doing a save as instead of a straight save, as outlined in the article below:
http://www.kenstone.net/fcphomepage/good_apps_gonebad.html
It only has worked on one project which is the only file that opens now.
It's driving me nuts! I'm going to start doing some major jobs soon and can't have this happen. Maybe I'll try to reinstall FCE then if no luck it's time for a refund.
Would upgrading from FCE 1 to HD have anything to do with it?
Have you had any luck, Doug?
Pat

HOW TO OPEN WINDAT FILES

How to open windat files which come along with E mails from microsoft users ?

That is priceless, "you can ignore winmail.dat...." No I can't. They are often a drawing or purchase order I require for a job.
I am running outlook on my mac and I still can't open them. All my other devices open these attachments no problem (none of them are apple). The people sending me these attachments are using macs. The only thing that has changed since I started encountering this problem is my hardware. I still use outlook, I have the same email address. The PDF attachments are being sent by the same people in the same way. When I had an iphone they opened on there too. Why do all the people on this forum keep blaming microsoft. Why can't macs read microsoft RTF, much like gmail or yahoo manage to do.
I cannot go asking busy project managers to send me attachments in a different format simply because I bought what I thought to be a decent computer.

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

How to open project from an earlier version (RH x3) using RoboHelp 6.

Hello everyone, I need your help. I have recently upgraded
from RH x3 to RH V6. I have just completed the installation of RH6
after spending long time with Adobe customer support as it took
them long time to figure out how to provide me the unlocking key to
install RH v6.
BTW I have only installed RoboHelp 6 by itself. I did not
install their Source Control because we already have Visual Source
Safe which we have been using in our company.
Also, since I had Adobe Reader 8 installed on my PC, I did
not install Acrobat Element 7 either. As I suppose if Acrobat 7 or
higher is installed RH v6 was not going to install Acrobat Element
7.
Well, now after I have installed RH v6, my first step is to
find out how to open project from an earlier version (RH x3) using
RoboHelp 6.
RH x3 is installed on my old PC and I am working on my new PC
where I have installed RH V6.
Sorry, for providing you too many details, the purpose is
only to give you a clear picture.
Please, give me your feedback if I am doing everything
correct and how should I open the project from an earlier version.
Thanks

Hi Peter,
Thank you so much for the response. Actually, after I posted
the question on Forum we had lost internet connection for some time
and I just went ahead and tried it by myself.
This is what I did – since we use MS Visual Source
Safe, my all files were in the working folder of VSS in my c drive.
I just clicked the Open tab/More Files in RoboHelp Starter and
located the RoboHelp HTML Project File. It opened without any
problem. Everything looks alright.
Is there anything specific I should be checking to make sure
if it is working fine in this version of RH. Because I did not
create this project, somebody else did and I have never used this
tool before this is the first time I will be using.
I found your site pretty helpful though and it did have some
information about Source Safe. I still have one question related to
Visual Source Safe that Is RoboHelp v6 linked to VSS automatically
and check the files out from it automatically whenever a project is
opened or we have to manually set the link between the RH6 &
VSS.
In RH x3 whenever I would open a project it would prompt a
message that in order to open this project the following files need
to be writable, would you like to make them writable, selecting
that option would checkout all the files from the VSS to make them
writable. However, in RH V6 I opened an existing project and it
opened without checking out the project files from VSS. Do you have
any idea what’s happening?
Ps: Do you recommend any book on RH 6 for starters or any
other recommendation?
Your help is always appreciated

"Unable to open project file" Error Message

I pulled an all-nighter (13 hours of editing) last night to create a critical project in FCE 3.5.1 on my Intel iMac running 10.4.11 then left this afternoon for a few hours and shut down my machine. Came back tonight and tried to open the project (which I saved on my Maxtor 1 TB external drive along with all of the scratch disk files). To my absolute panic, it won't open the file now with an error message that simply says, "Unable to open project file". HELP!!!! Anyone have any suggestions?!?!

In the past I found (and reported to Apple Feedback) the same bug Steve reports here, but I should recall that the problem:
- only appeared in PAL projects (probably not the case for kscritch) - never heard of it in NTSC
- was consistent in FCE 3.x, not so in FCE 4
I made tests importing .psd images with transparency into PAL projects using FCE 4, and I had various behaviours: sometimes the project worked, sometimes I couldn't open the project again (as in FCE 3), sometimes I had error messages with inconsistent behaviour (msg like "file error", but the project opened and file was there...), etc. so I decided to do without.
Now I only import .tif or .png images when I need transparency
Piero

'Unable to open project File' Please help....

Help. Since yesterday, Final Cut Pro has been crashing every time I have tried to render something. I have used the FSC Maintenance Pack that has been recommended and ran Crash Analyser and Corrupt Clip Finder. No corrupt clips were found and the Crash Analyser fixed the problem for a while and I was able to work for a couple of hours. (prior to this I also removed some Motion files and that also temporarily stopped the crashing). I began working on my project again today, and the same thing started to happen. I kept having to turn everything off at the source until finally I gave up! Just before I turned it off I started running Autosave Cleaner but it seemed to freeze too so I Force Quit it. I have just turned it all back on again and to my horror, my project is not even opening. My other FCP projects are opening but not the one I am working on. I have no idea what to do. Final Cut opens and the message is 'Unable to open Project File'. I am so upset and really hope that someone out there can help.
I run 10.5.8, I have 10 GB memory. All my clips are imported as XDCAM EX 720p25 (original format MPEG HD) but I have been working in this project for weeks without a problem.
Thanks in advance
Gill

I don't know why it is set to the internal disk, but that is the default. That is not project related. It is system related (hence System Settings). So probably you started fcp one without the external disk attached. FCP forces you then to choose another scratch-, waveform-, thumbnail-, autosave location.
Probably you've set it all to the internal disk then.
Next time when the external disk was there again you might have only reset the scratch disk, but not your Autosave location... Just a thought.
That is, IMHO, the disadvantage of system orientated scratch disk settings...
Rienk

Unable to open project file

Hello!
I'm in desperate need of a miracle here. I've already read over other solutions to this problem, but perhaps someone can come up with something I haven't. I'm using Final Cut Pro 7.0.3, and I finished a project last month that took a lot of editing work. After the project finished, I cleaned up my folders as usual, copying over all the media and the FCP project file over to my network external hard drive. I then made the horrific mistake of deleting my autosave files. Little did I know I'd want to access the project later, and instead of opening and having to reconnect my media, it just comes up with the error of "unable to open project file".
I've tried copying the project file I saved in November back to my local computer and opening it. I tried dismounting the network external hard drive and opening my local project file. I tried adding a .fcp to the end of the file's name. And I downloaded Pro Maintenance Tools in a hope that it could fix the corrupted file, it said it was fixed, but I still can't seem to open it. All my other FCP files are opening just fine.
I'm also interested if anyone knows whether my deleting everything FCP created except for the project file might be why it crashed?
Thank you in advance to anyone who even reads this hoping they can help.

Sorry, I'm out of ideas. Perhaps someone else with greater tech skills will chime in on this and be able to suggest a solution. Deleting or changing the location of the files you mentioned earlier in the thread can certainly complicate and add time to a new edit but should not have caused the problem you've encountered in getting the project file to open.
Good luck.
Russ

"Unable to open project file" message in final cut express 3.5.1

I have (well had now) a project with 3 video clips and multiple .psd files as stills. When the project contains just the 3 video clips and a couple of transitions I can save the project and quit Final Cut Express and relaunch FCE and when I try to re-open the same project, it opens just fine, without any problems and just the way I expected it to be. After editing the same project for a couple of hours and saving along the way (this has happened twice now and I don't think the length of time of editing matters) and adding multiple still images to the 3 video clips (this part is new in my working with FCE); I save and quit. When I return to open the same project I get the message "Unable to open project file" and click the OK button, which is my only option and I am given a new blank project. So where did my work go???

Thank you for the response, but it hasn't worked yet...
I read the link. I am working off my internal drive.
I re-named the Capture Scratch folder, and any Render folders and then launched FCE. I was presented with a window that reads "To preserve the integrity of the data used by Final Cut Express HD, it is necessary to ensure the existance of the following path(s)" The path in the box below is where my project file and support files are. My 3 options are Quit, Check again and Reset Scratch disk. I choose the Reset Scratch Disk button and it took me to the Scratch Disk window and I Set/Created a new folder and clicked Choose and then OK back at the Scratch Disk window and Continue at the initial window... the Reset Scratch disk button is now labeled Continue. I am given a new Untitled Project work space. I tried to open my project file and once again with the message "Unable to open project file".
Where did I go wrong???

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

"unable to open project file" on external hard drive

I see other users had this same issue, but I read all the relevant posts and they haven't helped me. basically, I created and saved a project (along with all scratch disks) on an external hard drive. then, when I closed the project and re-opened it, it was "unable to open project file." however, it looks like all the project files are still on the hard drive (capture scratch, autosave vault, etc.) so seems like this should be redeemable. what can I do?
thank you in advance, you are angellic!

What is the exact message? Try copying it to your computers system drive and opening it? What about in the Autosave vault? Look in there for the last backup, try opening that.
Shane

How to open Project File?

Similar Messages

Maybe you are looking for