Locked motion tutorial project files

Hi I have just received 'Motion Graphics and Effects in Final Cut Studio 2' book for xmas but am finding all the lesson media files are locked ( appear with a padlock ) both on the dvd and once copied over to my hard drive.
on get info its says i can read and write
in terminal it says drwxr-xr-x
any ideas?
thanks chris

No - i mean the files are locked all the project files that u need to open to work on are locked they wont open at all.
the only files i can open from the dvd are the video files and the pdf.
i just put in a similar dvd for fcp and none of the files r locked.

Similar Messages

Can't open motion 4 project with motion 5 !

When I open a Motion 4 project with Motion 5 I get the followwing message : Le document « origine.motn » n’a pas pu être ouvert.
meaning the document can't be open ! Any ideas ?

There is something wrong with the file. Normally Motion 5 can open Motion 4 project files. Open in Motion 4, Save As, try again.

Would working from a locked project file cause problems?

Hi all.
working in FCP 4.5 on numerous Dual G5s (2.0 & 1.8 GHz) with sufficient RAM (4 GB+).
I'm working on a large project with a number of editors and I've created projects that each editor can use as references to the material. I lock the reference projects so that if they inadvertantly make changes to them, they will be reminded that the changes will be lost when they close out of the project. A theory has arisen that we are seeing performance degredation due to conflicts with Autosave. By performance degredation, I mean that responsiveness decreases, and an occasional crash occurs. I'm just wondering if the concern is valid. I'm just wondering if the concern is valid. My feeling is that it's too intermittent to be autosave's fault. Has anyone come across this?
thanks,
jack

nothing is written to the project file between saves, so it seems unlikely that your issues are related to their lock status. autosave only requires that a project has a pre-existing project file in order to work, so again, the issue would sem to be unrelated
... ok, so much for logic. the real resolution is likely only to come with be some controlled trial and error. see how you get on with unlocked project files and see if the performance issues disappear.

FCP opening anamorphic motion project files as 4:3

I have a 720x480 anamorphic motion template which I need to place in a 720x480 anamorphic FCP sequence. FCP is automatically distorting the template, when I open it in the viewer (prior to dropping it into the timeline). It looks 4:3.
When I drop it in the timeline, it is squished. The distort value is 33%. Anamorphic is unchecked in the browser. I know how to fix it once it's already in the sequence, but seeing as I have several hundred of these templates to use, I'd prefer to have FCP open it correctly.
It does the same thing with motion project files, not just the templates.
Anyone know a way to correct this in FCP?

Ok, but for my workflow, I need to use motion templates, not project files. There is no way to correct this in the browser for a template. I need it to just come in 16:9.
If I want SD footage in a 16:9 format (pillarboxed) what size do I make the sequence? Should it be some custom size that is not anamorphic, yet still much wider than tall?
I need to standardize all my sequences (whether they are 16:9 footage or not), so that I can use one set of motion templates, which will be 16:9. Should the motion templates then be created in this same custom size?

Can't lock a Project File

If I use Get Info on any DVD SP project file, the check box "Lock" in the Get Info dialogue box is inoperative, so I can't lock the file. All other Mac files can be locked but not my DVD SP project files. The manual does not help.
Any suggestions please?

Well, that's the mystery. I am using 10.3.9; the files involved are single DVD SP project files - not in a folder; I am the owner; and I have Read and Write access (as shown in Get Info); and I am repeatedly saving and loading that project file and other project files!

•TIP - Open Motion Project File In QT Pro

Not sure if everyone already knows this but you can open a motion project file in QT Pro.
For this one project I had to export QT files from Motion. It was taking forever and was playing around and discovered that if you open the motion file from QT player and did an export it was much faster.
The export from motion took 54 min...when using the QT method it took 5 min.
Why?
Who cares, it was faster and looked great.
If you already know this trick..great, if you dont I suggest giving it a try if you need a faster solution.
Cheers!

I've tried that. I think there might be a bug in QT Pro (PC) or for some reason my QT Pro can't handle an .ac3 file. I just upgraded QT Pro to 7.5.5 and now I get different behavior. Basically, I'm getting no audio at all even though I've chosen "Add to Movie" properly. I think the problem might be that QT Pro isn't able to recognize my .ac3 file. If I playback the .ac3 file in QT by itself, I don't hear anything at all. I don't have a 5.1 sound card in my computer, but shouldn't I at least be able to hear two channels? Do I need anything special installed (hardware or software codecs) to playback an .ac3 file with QT Pro?

HT201108 Transferring Motion 4 files to Motion 5 Project

I have recently purchased FCPX and Motion 5 having used FCP Studio for several years. My first attempt to transfer a FCP7 project to FCPX using "7 to X Final Cut Pro" was partialy successful however, none of the Motion 4 files in the project would transfer.
Can't find information in the Motion 5 manual so I'm hoping someone can point me in the right direction.
Ray B.

FCPX unlike FCP Studio does not allow you to open Motion Projects whether they are from Motion 4 or 5. In other words there is no round tripping in FCPX. You can open your Motion 4 projects in Motion 4 and save them as a Quicktime movie and import that to FCPX. Motion 5 will open some Motion 4 projects but not all since Motion 5 doesn't have all the same behaviors, filters image units etc.If the Motion 4 project opens in 5 you may still have to make some editing adjustments.Motion 5 has templates for transitions, titles, effects and generators that allow you to create those types of projects and publish them to FCPX and they will appear in the appropriate tab in FCPX effects browser. So if some of your Motion 4 projects fall in one of those categories then you might try that approach. Other wise save them as Quicktime movie and import to FCPX.

Motion crashing upon open of certain project files (fine otherwise)

I am a fair newbie to Motion and am working through the Apple Pro training book (Motion Graphics and Effects in Final Cut Studio 2). All included project files open fine on my Mac Pro, (leading me to think the project files are fine) but crash Motion on the iMac I'm using. Projects I create from scratch open with no problem on the iMac.
Both Mac's are using the latest OS and application updates.
Below is a copy of the crash report for the crashed thread. Any ideas are gratly appreciated.
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000004
Thread 0 Crashed:
0 Ozone 0x0133bcd3 -[OZTimelineViewForViewer numberOfRows] + 13
1 Ozone 0x0133b65f -[OZTimelineViewForViewer rowsInRect:] + 35
2 Ozone 0x0133b33a -[OZTimelineViewForViewer drawBackground:] + 366
3 Ozone 0x011d7706 -[OZTimelineView drawRect:] + 806
4 com.apple.AppKit 0x932f13b1 -[NSView _drawRect:clip:] + 3228
5 com.apple.AppKit 0x932f040b -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 614
6 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
7 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
8 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
9 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
10 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
11 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
12 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
13 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
14 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
15 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
16 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
17 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
18 com.apple.AppKit 0x9330236f _recursiveDisplayInRect2 + 149
19 com.apple.CoreFoundation 0x9083eb30 CFArrayApplyFunction + 307
20 com.apple.AppKit 0x932f0613 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1134
21 com.apple.AppKit 0x932ef473 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 217
22 com.apple.AppKit 0x932eeb78 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 290
23 com.apple.prokit 0x959abd9d -[NSProWindowFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 101
24 com.apple.AppKit 0x932ee362 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 523
25 com.apple.AppKit 0x932edc8e -[NSView displayIfNeeded] + 439
26 com.apple.AppKit 0x932eda32 -[NSWindow displayIfNeeded] + 168
27 Ozone 0x012d95af -[OZDocumentWindow displayIfNeeded] + 71
28 com.apple.AppKit 0x9333dd6c _handleWindowNeedsDisplay + 206
29 com.apple.CoreFoundation 0x9082dd6e __CFRunLoopDoObservers + 342
30 com.apple.CoreFoundation 0x9082ce10 CFRunLoopRunSpecific + 827
31 com.apple.CoreFoundation 0x9082cace CFRunLoopRunInMode + 61
32 com.apple.HIToolbox 0x92dec8d8 RunCurrentEventLoopInMode + 285
33 com.apple.HIToolbox 0x92debf19 ReceiveNextEventCommon + 184
34 com.apple.HIToolbox 0x92debe39 BlockUntilNextEventMatchingListInMode + 81
35 com.apple.AppKit 0x93272465 _DPSNextEvent + 572
36 com.apple.AppKit 0x93272056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
37 com.apple.AppKit 0x9326bddb -[NSApplication run] + 512
38 com.apple.prokit 0x9598881d NSProApplicationMain + 324
39 com.apple.motion 0x00005ab8 0x1000 + 19128
40 com.apple.motion 0x0000317e 0x1000 + 8574
41 com.apple.motion 0x000030a5 0x1000 + 8357
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x0133b64a ecx: 0xa0a57184 edx: 0x00000001
edi: 0x11767570 esi: 0x117760a0 ebp: 0xbfffdab8 esp: 0xbfffda80
ss: 0x0000001f efl: 0x00010282 eip: 0x0133bcd3 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
iMac 1.83 GHz Intel Core Duo Mac OS X (10.4.10) 1.5 GB RAM
Mac Pro Mac OS X (10.4.10)
Mac Pro Mac OS X (10.4.10)

Looks like a font issue. Try this:
Create a "virgin" account from the accounts preference panel. Try opening it there.
If it crashes, try again with Console (Application -> Utilities -> Console) open and see if it outputs anything useful when it crashes.

GB Creating Corrupt Project Files

Hi. I've been working with GB and GPO (Garritan Personal Orchestra) for a video project. A had a Project open (a fairly large one) and was frequently "saving" to the project on the Mac HD. I have encountered problems with GB crashing and the project files being used becoming corrupted in the past week. But I can't figure out what's causing the problem. This time I saved the project, opened up a track volume control for one track (Out of the 20 or so tracks) and clicked on one point and the big picture in the Software Instrument went black and GB crashed. The Relaunch dialog window came up. At that point, the project was corrupted. I now have two .band files that don't have a thumbnail preview when looking at them in the finder. GB says "Read Error: Illegal format of file. Abort" when I try to open them. Any help on more of what's causing this problem rather than how to fix the corrupted files (Even though that would be fantastic) would be appreciated.
Thanks
Lojimek

Sorry I don't have any insight as to possible causes (do you Lock as many tracks as possible)? but here's HangTime's tutorial on rescuing corrupted files:
http://www.bulletsandbones.com/GB/Tutorials/RescuingFiles.html

Error reading project file : no protocol

I have followed the instructions exactly as in the j2ee tutiorial ,but, when I run asant , an error occurs:
: Error reading project file : no protocol: ../../common/targets.xml
Urgent!

Could you please provide a bit more detail such as which sample you are using? Also are you using the latest version of the tutorial and have you configured your build.properties in the samples/common directory?

'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 - 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

How do I save Icon templates with the Project files?

My project files are stored in a folder, say, "My Documents\LabVIEW\My Project", and this folder, in turn, is saved under (Sub)Version Control. I'd like to include a sub-folder called "Icon Templates" that could contain the icon templates I'm using in this project, but they seem to be "forced" into "My Documents\LabVIEW Data\Icon Templates" (almost the same, but the "owning folder" is different).
Is there any way to change, preferably on a Project-by-Project basis, the default location for Icon Editor templates? I tried to figure this out, and saw that one could change where "3rd Party" templates were stored, but that didn't seem to do anything (maybe because I don't understand the concept of a "3rd Party"?).
An important (to me!) reason to accomplish this is that I want to commit my new icons when I commit the rest of the Project, and have them appear when I checkout the project on another machine (or do an update from the Repository).
Suggestions welcomed ...
Bob Schor

Well, I thought of this as well. I did change Default Data Documents (which seems to be where Icon Editor expects to find its Templates file) to My Documents\LabVIEW (instead of LabVIEW Data), and that worked (sort of). But that still doesn't solve my problem. I have multiple projects -- My Docs\LabVIEW\Project 1, say, and My Docs\LabVIEW\Project 2, and want to have a specific set of icon templates for each stored, say, as Project 1\Icon Templates and Project 2\Icon Templates.
My problem is two-fold. First, there is a setting in Icon Editors, Tools, that seems to be designed to let you designate where your "special" templates are located, which I've set to, for example, My Docs\LabVIEW\Project 1\Icon Templates. However, when using the Icon editor, these templates never appear! It's as though it's still "locked" into the "3rd Party" sub-folder of the parent Icon Templates folder. Second, even if this worked (which it doesn't), is there a way to "embed" this setting as part of Project so that the settings "stay with the Project" (and can thereby be customized)? One important reason to do this is to simplify organizing Projects and folders on disk -- I keep them "together" (use the same structure for both, so a Project is contained, on disk, inside a single set of nested folders), which greatly simplifies and facilitates using Version Control to manage development.
Thanks for the reference. I didn't know about all of the symbolic names. It does appear that they are only used in the VI Search Path entry, correct?
Bob Schor

Re-interpreted footage metadata is lost when moving Premiere Pro CC 2014 project file to different computer

Hi guys,
I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
Looking forward to a resolution to this problem.
Daniel Lichtenberg
[ad/link removed by moderator]

Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
I came across this thread
Premiere Pro CC error message and crash
which had the suggestion -
"Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

How to open V1 files in V2 with no project file

I have an swf output file from a tutorial created in
Captivate version 1. I have no project file, so when I opened V2,
and tried to import the swf as an animation, I receive an error
that it is looking for something called 'root'. I have a link from
my Robohelp project file to these captivate 1 tutorials and nothing
happens when you click on the looks, the tutorials are not
launching. So, I thought I would try to republish these tutorials
in v2, to see if that was the problem.
Any ideas?

Hi Teresa
First off, a major change occurred between Captivate 1 and
Captivate 2. I've attempted to describe how to work with these and
RoboHelp at
the
link you see by clicking here.
Secondly, don't sweat the "root" message. It's a red herring.
Cheers... Rick

Locked motion tutorial project files

Similar Messages

Maybe you are looking for