Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FCP Renders on PowerPC Mac, unable to link on Intel Mac



Ben Media V wrote:

We are not using any ACLs or Open Directory in this setup.
Starting with 10.5 the OS changed the way it handles Umask scripts. All files and folder that are created by the finder follow umask rules but application, such as FCP do not.

There are only 1 admin user on every FCP system so the users are 501 by default.
I need to verifiy this thou.
You really shouldn't have all admin users with same uid. On small installs you can manual enter all users in each computer with unique uid's. On 10.5 you can use the guest user, on 10.4 you can go into the netinfo and set up users without home directories. Also note that the default group changed between some os releases.


May I know whats your workaround for now?

Even if you had ACL's on you san, you don't 'really' want them turn on for your capture scratch. If you have your users share one capture scratch set your perms for the default folders to be R/W. Let each project's render and capture folder be read only to the group. If you move a project from one system to another, then you get group reads, and need to do a 'save as' on the project file to render or capture. This could be a good think. It forces users to version the project every time a new starts working on it.

If you use project folders (an idea that I have seen, tried, and hate) then you need to start with project scratch templates files with the correct perm. ie ProjectTEMPLATE/Render With the Render / Capture / AudioRender folders all set to Group Read/Write. Then FCP will make render files with R only and you user needs to rename the Sequences to render. Again, not a bad idea.

If you use user folder then you should have read access to everything and renders are sent to the users R/W folder.

For Project files without ACL's, start out with a Template folder. Don't open FCP and create a new project. Start with a folder with all your user files. IE audio, projects files, graphics, edls, scripts. If you duplicate your Template folder on the finder, then it keeps the R/W perms. You get to set up your projects with slates and the like. That will keep the issues level 'down' and make users duplicated a version of the projects. It also allows you to save a step for any folder that need permissions changes. The parent template folder is always r/w so if a project file gets made in FCP then you can just get info on the template folder and populate the perms down in one step instead of two.

You 'should' be able to change application perms with a launchd instead of umask, but my attempt when bust. You can also run a nightly script to adjust all your perm on Project files.

Hope this helps.

-Phil


Cheers,

Ben Cheng | Application Engineer | The Media Village Pte Ltd

On 5/14/2008 9:31 AM, TechTalk wrote:
On 13-May-08, at 6:35 AM, Ben Media V wrote:

The workaround is to re-apply the user permissions on the FCP project file,
- "Get Info"
- The owner's permission is already Read/Write, but select it as Read/Write and apply it again


I am finding that FCP does not listen to perms set (i.e. umask) and editors who are admins and in the same group still can't open each other's project files without some teeth gnashing.. This is with 10.5.2 and Xsan 1.4.2

:)

Mat X
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/email@hidden



This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xsan-Users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xsan-users/email@hidden

This email sent to email@hidden
References: 
 >FCP Renders on PowerPC Mac, unable to link on Intel Mac (From: Ben Media V <email@hidden>)
 >Re: FCP Renders on PowerPC Mac, unable to link on Intel Mac (From: TechTalk <email@hidden>)
 >Re: FCP Renders on PowerPC Mac, unable to link on Intel Mac (From: Ben Media V <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.