Andrew Richards
Forum Replies Created
-
[Craig Alan] “We will be buying more. What do you recommend? Right now I have 9 computers and nine g-raid firewire drives.”
It depends on how you anticipate the students using the stations. Will they only work on an assigned station during class? Or will they be coming in for lab time as well? When I was in school, the students who had their clips local to a given Mac were forced to book particular machines vs the ones with a FireWire drive who could use any machine.
Smaller, more numerous portable drives would make for a more flexible lab environment if students are competing for seat time in the lab. If you don’t need that flexibility, what you are doing is fine. The material you are predominantly working with (HDV, DVCPRO-HD) is a low enough bitrate to work from FW800 G-RAIDs. You would only need the Pegasus RAIDs for something like multicam ProRes. Having some Pegasi for the big complex projects is good.
[Craig Alan] “For the projects themselves, I have as many as 5 teams per period plus some students doing independent projects. However, some assignments I have all students write and direct his/her own. So with enough stations I could also have them write, direct, and edit his/her project. So we could have everyone editing at once. “
This is why I wonder about how much you want to be tying particular students to particular Macs. If the students are going to get the seat time they need on the system they loaded their footage onto, then immobile RAIDs are fine. I’m assuming there are multiple classes using the lab.
The other thing to consider is what happens if (when?) a piece of storage fails. If it is a Pegasus, then you have a number of students with blown work. With more numerous smaller drives, you have only one student/team affected. Students are very skilled at blowing up storage, so if you have a number of students from a number of classes all depending on a Pegasus, and something happens and the RAID is gone, you’ll have many more panicked students to deal with than if it was just one student’s/team’s G-RAID.
[Craig Alan] “I ordered ARD for the teacher station. Is it better on a dedicated Mac just for that purpose or will the teacher station, used for a wide variety of things, be fine?”
If you ordered the box with a disc in it, see if you can return it. The version of ARD on the Mac App Store is $79 and is exactly the same as the $499 unlimited version in the box. It is handy to have ARD on a dedicated server since it can act as a task server for scheduling automated administrative tasks. Just a nice-to-have thing; a copy for your own use is the most important.
[Craig Alan] “I have another 38 grand to add to these. I’m thinking nine more computers. That would give us 27 computers and classes are between 25-35 (+). I’m trying to have enough stations so I can teach editing with each student at a computer.”
Spend your budget on workstations, not reaching for shared storage. Your students get much more benefit from a workstation they don’t have to share as much. Shared storage is great for a lot of applications, but in your case I think it is more risk than reward, especially with respect to FCPX. Keep your eyes on Small Tree though. They are working on an iSCSI-based (i.e. no fiber) Xsan hardware package that would be a significantly smaller investment.
Best,
Andy -
[Craig Alan] “That would mean each user would create a sparse disk image of each project? It seems like a great way to keep projects in a container that could be backed up, moved to another computer, archived, etc.”
You as admin would create them and then assign permissions to them. The permissions on the .sparseimage file become the permissions of the mounted disk image.
[Craig Alan] “The only thing I didn’t follow from the link is how do you clean up at the end of a session? Do you quit FCP X then unmount the sparse image? “
Yes, you’d quit FCPX and unmount the image. Not a big deal since you are also logging the user anyway.
[Craig Alan] “If these images are kept on the raid 0 drives will we be loosing any speed from this set up?”
Negligible, if any.
[Craig Alan] “Could I simply have two sets of folders on the root level (one with admin permission access only) and move projects into the properly named one for FCP X, restart into the right user account and be good to go? With or without Project Manager X?”
Yes, though this is probably more hassle than using sparse images. FCPX only sees what is in those two root folders, Projects and Events moved outside them are essentially offline.
[Craig Alan] “Xsan: not necessarily out of my budget. The software is $1000. No biggie.”
Actually, on Lion, Xsan (the software) is included in OS X at no cost.
HOWEVER!
Xsan is not the least bit trivial to set up and manage, and the big costs are hardware and help. It requires switched Fibre Channel (FC) storage (though you can also use switched SAS or iSCSI but these are not supported by Apple). At minimum, you’re looking at a $15K-$30K RAID, a $10K FC switch, running optical cables to each client, a $800 SANlink FC adapter for each client, and a bunch of expensive hours from a qualified installer.
[Craig Alan] “Wish I knew this was the best option before my last order went through.”
It is not the best solution for you, it is just the only way to have FCPX point to a certain folder instead of the root of a filesystem.
[Craig Alan] “I have asked the company if they could be daisy chained together and work with xsan. I will also be meeting with another possible funding source to discuss finishing this post lab with all this in mind. “
I can answer that. There is presently no way to use Thunderbolt RAIDs with Xsan. They can’t be networked, and Xsan only works with networked storage.
[Craig Alan] “So if we were to use xsan and centralized storage: how easy will it be to assign permission to certain projects?”
Don’t do it. You’d be in way over your head. Based on what I’ve seen of your situation in this thread, I recommend going with the sparse image method. It gives you a nice, tidy way to do what you want to do and gives you the ability to cap the storage any given student can use for any given project. You can limit access based on login credentials, and no matter how messy the students get inside their sparse image, they aren’t making a mess of the RAID and its filesystem (which you can make read-only).
I also recommend getting a Mac mini Server (if you don’t already have one) and setting up Open Directory to centrally manage the accounts for your lab (if you haven’t already done so). Also get a copy of Apple Remote Desktop for that server, it is inexpensive from the App Store and very useful for administering a bunch of Macs.
[Craig Alan] “Thank you for your continued patience. I’m catching on but a bit baffled at how all this feels like a “work around”. For any institution, a must.”
It is a workaround. If you hadn’t already bought 10 RAIDs, I would be recommending different storage. But you’ve got what you’ve got, and I think my recommendation above is the best way to work with what you’ve got.
It never came up- what are your students shooting on, and how much will they typically be shooting for a project?
Best,
Andy -
[Craig Alan] “The raids will be raid 0. Media drives, exclusively.”
In that case, don’t remove any drives while the RAID is running or you will destroy the RAID set. Make sure your students understand this and lock the drives if possible.
[Craig Alan] “Is FCP X so much faster and more efficient that the old rule of using external drives or separate internal drives (MAC PRO) as media drives no longer applies? “
Nope, that rule still applies. No amount of software optimization can overcome physics, and physics are what makes storing media on a device other than your boot volume preferred. You create an I/O bottleneck by using the boot volume for media storage since the OS and the app are constantly reading and writing small files on the boot volume. True for FCP7, true for FCPX, true for pretty much any app that has a high demand on storage I/O.
[Craig Alan] “If a user account has two FCP X folders on the root level of the attached media raid, can’t another user have two other folders on the root level of the raid? “
No. FCPX puts the folders there, and if they already exist, it uses them. If it does not have access to read and write, it won’t work. The path to the folders is the key, and if the user running FCPX doesn’t have appropriate permissions on /Volumes/RAID/Final Cut Events and /Volumes/RAID/Final Cut Projects, it just won’t work. If you have any experience with Avid, the same issue arises.
[Craig Alan] “Two different user accounts do not share the same folders even on an attached drive do they? This would defeat the purpose of user accounts and permissions.”
DAS presents its filesystem(s) to the host and subsequently to the user logged in. User access to the directories and files on the DAS are controlled via permissions just like they are on the boot volume. So you can configure a directory to be shared amongst a number of user accounts or to limit access to only one user account. FCPX needs to have read and write access to /Volumes/RAID/Final Cut Events and /Volumes/RAID/Final Cut Projects to work, and the permissions of the current user are the permissions that FCPX is granted for that user.
Basically, if you have more than one user targeting DAS for FCPX, you either disable permissions for the DAS and let everyone see everything, or you have to work around it by partitioning or using the sparse disk image workaround I linked to previously that also works around the NAS limitations imposed by FCPX.
Best,
Andy -
Personally, I’m more interested in Google Maps for the NES.
https://www.youtube.com/watch?v=rznYifPHxDg
Best,
AndySome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Craig Alan] “Why can’t the “current user’s Movies folder” be on an attached drive as opposed to the system drive which is never recommended for any editing program. “
FCPX does not let you set scratch locations like FCP7 does. On the boot drive it writes to Movies for the current user or it can write to the root of any DAS. That’s it.
I suppose you could try doing a symbolic link from ~/Users/username/Movies/ to a particular directory on the DAS, but I’m not sure how FCPX would take that.
[Craig Alan] “Actually this is quite possible since the thunderbolt raids have removable drives. However, wouldn’t carving up a raid into partitions undermine much of the speed advantage of the raid?”
Hot swap drives have nothing to do with partitioning. Hot swap drives are only for replacing failed HDDs so the RAID can rebuild itself (assuming it isn’t RAID-0). The RAID aggregates and presents the physical drives as a single logical entity that the OS sees the same as a single disk. With a RAID, you do not have any control over which data goes to which HDD in the array. That is the RAID controller’s job.
Partitioning is carving up the logical entity, not the physical entity. I/O on a partition of a RAID volume is going to spread across the RAID’s physical disks the same as for a single volume. Technically, a “volume” in OS X is a partition, so all drives have one or more partitions once they are formatted.
[Craig Alan] “Also why can’t a folder on the raid be given access to only one user account as opposed to an entire partition? “
It can, but remember FCPX addresses two folders (FCP Projects and FCP Events) at the root of the volume, and those cannot be defined elsewhere on the volume (except when using SAN locations with Xsan). This means that if you can’t really have managed permissions for FCPX DAS, hence the partitioning idea.
[Craig Alan] “I assume Apple wants FCP X in institutions. This can’t be a unique concern of mine. If you were sharing a computer why would you want your media available to everyone?”
My read on it is that Apple designed FCPX for sneakernet with drives moving from Mac to Mac and/or user to user. For a lab setting, I would recommend assigning an external drive to a user or team to share that can move from Mac to Mac, or you can test the partitioning or sparse disk image methods (FCPX has a 30 day free trial you can test with).
Best,
Andy -
[Craig Alan] “We’re not going to use thumb drives. The media and projects stay in class. Everything is done in teams and kids can be absent. Lower income. Can’t require thumb drives. We will have fast firewire and faster thunderbolt raids.”
Fixed direct-attached storage (DAS) is more difficult to mesh with your environment. FCPX stores Event and Project scratch by default in the current user’s Movies folder (so that is cordoned off from others already) or it can store Event and Project scratch at the root of any DAS. If you have a fixed DAS, you aren’t going to be able to restrict user access to FCPX scratch unless you do the sparse disk image workaround that is necessary for storing Event and Project scratch on NAS. The exception is Xsan, but you didn’t mention it and it is probably out of your budget from what you’ve related.
One thing you could do with DAS is carve it into partitions, one per student or team of students, and then apply permissions to them appropriately. That could get unwieldy though if your environment can’t tolerate wiping the DAS clean periodically to carve out new partitions.
Best,
Andy -
I’d be concerned about the speed. I suppose a very fast 32 GB or larger thumb drive could maybe support light native h.264 work but higher bitrate material could choke the pipe.
Best,
Andy -
[Bill Davis] “I thought you could do this via Thumb Drives, but I was wrong. Appears X only recognizes drives, not memory sticks.”
FCPX will address any direct-attached storage in terms of form factor, but it is limited in terms of the filesystem used (how the drive is formatted). The pic above is my ExFAT USB thumb drive. HFS+ is the standard, of course. Most thumb drives come formatted FAT32 so they can support the broadest range of OSes, but FAT32 will not work with FCPX (nor would you want it to).
Best,
Andy -
[Kevin Christopher] “This really points out to me how simple the hfs file system really is.”
HFS+ is arguably the single most significant liability in OS X today. It’s really a shame the effort to integrate ZFS into 10.5 and 10.6 got scuttled. ZFS is awesome!
Best,
Andy -
[John-Michael Seng-Wheeler] “Last time, the new Xeons were released in march and the new MacPro using said Xeons didn’t come until July.”
Didn’t know that. Good point.
[John-Michael Seng-Wheeler] “I’m hoping the fact that it’s two years old and doesn’t have Thunderbolt will make Apple pick up their heels a little more this time.”
I’m hoping Intel’s delayed launch of the E5s did not preclude them delivering development units to partners so they could be ready when they shipped in volume.
Either way, if HP ships in April and Apple takes months more to do the same (assuming they are doing a new Mac Pro at all), it would seem like another bad omen.
Best,
Andy
