FCP X is network blind?

This is crazy. The file access thing is pretty fundamental. It's as if the intent is to force all data access to the iCloud. So as long as you're editing your iPhone footage for theatrical release on iTunes, you're golden, but as soon as you'd like to do anything that smacks of a professional utilization of the product you're screwed.
 
Does upgrading to Lion Server changes these networking issues? It is my undertanding that in Lion Server you can create case-insensitive Xsan volumes that act like traditional HFS+ volumes.
 
Solved!

Solved!

Wanted to share this tidbit - network logins WILL work, but with a couple tweaks.

The outstanding issue is this: FCX will not allow network logins to create the first initial project/event (1st time FCX launches) because it is looking to create the first project on the Local/user/movies folder, which doesn't exist for network logins. It WILL, however, allow a network login to create additional projects/events, if one already exists. This is bizarre, and I have to assume this is a design flaw.

The work around involves the disk image technique described in other threads. A default disk image with a default event / project needs to already be set up before the network login can use it. And this disk image has to be created on a local hard drive (using a local login). Once the directory structure is created in the disk image, then network login can mount the disk image on their desktop, and use that to create their events / projects.

I don't understand why Apple decided this, but this is the way it is.

I'm tickled pink that this works. We're going to deploy to our labs. I've been testing all after noon, and I'm astonished at how easy media management is now. Now I'm understanding why others are saying this is perhaps a superior way of working. If I decide to share a project with another user, I can simply give them a copy of the project sans media, or copy the project with references to events, or copy off a project with only the media.

But all of this involves using disk images in a network environment. Once its set up, it's ridiculously easy to use (easier than FCP 7 media / scratch disks).

Dillon
 
Summary of the procedure as I understand it.

Summary of the procedure as I understand it.

Hi, I was facing this issue yesterday after installing a Buffalo Linkstation NAS unit. I didn't really understand the solution from the previous posts, but through experiment figured it out. In case it clarifies things (this ought to work with other configurations as well), here's my procedure:

Create a dedicated folder on the NAS if you want, using that device's configuration utility or webaccess (I did this for convenience, don't think it's required, though).

Open Apple's hard disk utility (it's "Festplattendienstprogramm" on my system, I don't remember the english name :Drogar-Happy(DBG):). Click on "Create new disk image."

In the pop-up, select a LOCAL folder (doesn't matter if that drive has the space you will specify for the disk image); at "save under", name your new image (this will become the name of the sparse image), the other settings (below that):

Name: of the partition you're creating, what will show up as the "drive"
Size: own setting, maximum free space you have or want to use on your NAS (you could create several of these for archiving purposes as described elsewhere in this thread)
Format: Mac OS Extended (default)
Security (or whatever that's called in english): none (default)
Partitions: Apple partition (default)
Image-Format: scalable (?) bundle image

Create the image. Unmount it. drag, move or copy it to the NAS folder. Mount it again.

Start FCP X. The new "disk" should be in the events & project lists, but empty. Create a new event and a new project on the new "disk".

Now you can use it as you would any other attached drive. If you copy existing events & projects over, you might have to start them the first time by double-clicking on the "CurrentVersion" file within the events directory to get FCP X to recognize them, I'm not sure.

If I run into any problems with this approach, I'll keep you posted, but that's it as far as I know.

I think this is essentially what Time Machine does to prep a drive for backup.

Note that I was using OS X Lion, so I don't know if it's exactly the same under 10.6.

Cheers and good luck,

Goesta :thumbup:
 
Last edited:
You must log in or register to reply here.
Back
Top