Forum Replies Created
-
Bryson didn’t go into that level of detail. But I believe that his description of their workflow details how they put your level (and mine too) of detail into CatDV rather than trying to create it in either directory structure or file names. I mean after all, that’s what CatDV is there for. If you’re going to do all the work, why have it.
I don’t have the Worker node. I create my first level of organization when I capture the footage using FCP 7. So far we rarely see file-based footage, though I’d like to get there. And I like long pieces of footage filled will shots and interview. The worst thing in the world for productivity is thousands of individual shots. I can’t imagine what it would be like if an interview came in a word at a time.
Non-linear: all the time and nothing but.
-
Here’s what the directory structure looks like on one of my proxy drives.
I do like having the reel name as the prefix to every file name. Oh, and I window burn all the proxies and put the reel name on all of them. That works great when they’re being referenced by someone who isn’t used to dealing with footage.
Non-linear: all the time and nothing but.
-
Ok, there are some semantics that we have to be careful of here. It’s EASIER if your paths are consistent. That MEANS: if you put them in one place, it’s hard for CatDV to find them if you move them.
Translation: Don’t keep changing where you store them. It doesn’t mean you can’t store them in multiple places. CatDV keeps track of where everything is. If you move them it doesn’t know where to look. However, if you move them you CAN tell CatDV where to look and all will be fine.
So, best thing to do is put them in a place, read them into CatDV and then let CatDV make the proxies. But because you are using paths (and not tape names) you can use other software, like Compressor, MpegStream Clip or something else to make the proxies. You just store them on your proxy drive(s) using the same structure: Volumes/Archive 1/Paris becomes for the proxies: Proxy Drive A/Volumes/Archive 1/Paris
you don’t want to have too deep a directory structure because you’ll run out of space for the OS to deal with it. I’d have to look up what the limits are (someone chime in here if you know), plus it gets very complicated to manage. You keep it simple and let CatDV do the heavy lifting. When you go to the workgroup version you’ll see how easy life becomes because you don’t have to deal with all these separate catalogs. All becomes as one (grasshopper). You just to a query and CatDV finds all the shots/clips for you. I do a LOT of drag and drop from CatDV to FCP directly. Works wonders and cuts down hugely on edit prep. Everything is already loaded and ready to go, as proxies.
Holding up? Each file name says what it is. The shooting location is already defined. After than I need the specifics of the shot itself and the other information is pretty much in the way. Again, CatDV does the heavy lifting.
And in triplicate: well your file name already has the date/country/city/broll and more, and yet you have directories that repeat the information. Actually if they’re all in the same directory a simple directory sort will give you all you need. CatDV isn’t going to die or blow up or something. Or at least it’s not likely. I do keep copies of catalogs locally in a DropBox folder and those are backed up six ways to Sunday. My date fields INSIDE of CatDV are what are important. If I tried to put the same degree of information in the directory structure and then duplicate it in the file name, well, talk about a plate of spaghetti. Start simple. You can always get more complicated later (inside of CatDV).
Look at what Bryson put up about how NASCAR uses the system. You’re not going to see that kind of directory structure.
Non-linear: all the time and nothing but.
-
Well from my perspective you’re over thinking it.
I’m in pretty much the same situation. about 16 years of footage, dating from the time we switched from film to video. For the last 13 or so years we’ve created a great deal of derivative product from all the different material we’ve shot and continue to shoot. It’s all documentary in style. Not a spoken word is scripted. Lots of interviews and lots of transcripts. We create video-based products that are sold all over the world.
A few years ago we even changed the way our accounting works to match the way we actually create product. Whenever we shoot it’s research towards making an at-the-time-undetermined project. Product creation doesn’t begin until we sit down to put together a project in edit. The best way for us to work this way, and keep footage somehow compartmentalized and still make some sense of it all, was to separate it out by shooting location. So we have this factory, or that office site, or that hospital or school. Reel names (we shoot HDCam on a 750) use as two or three letter designator for the shooting location. So I can see a note or a line out of an EDL, or a tape case and know immediately what “shoot” it came from.
Ok. So the majority of the time I’m using FCP to load the footage. The project goes under the location name, say “Unity Hospital.” What become important later is the path to the directory Unity Hospital. Doesn’t matter how or where that footage goes later. I just need to find it. I use FCP to mark sections to load and label them such as: UN07 cafeteria cover 1.mov or UN10 Lacy Darcy interview part 2.mov {Note that I’m using ProRes for my files). When the shots are captured I bring them into CatDV, which will remember just exactly where the footage is. I can then parse them out even further with all sorts of key identifiers and markers and transcripts. I also create proxy movies of everything that live on a separate drive attached to one of my systems. Because I’m using “paths,” the structure is the same as the original footage.
Lately I’ve been moving footage off onto external drives for storage, and to clean out my systems. I’m sure some lucky souls get to use CacheA but for now we’re using raw external drives. It’s quick and easy and I can mount a drive using an eSata dock directly to one of the systems and edit from the raw drive when I need to. But the real change has been moving the original footage off to one of my archive drives FIRST and then bringing the footage into CatDV and making proxies from there. I’m doing the vast majority of my editing using the proxy movies, NOT the originals. As a result I have 100 of my footage from ALL shoots available ALL the time. Originals don’t come into play until I’m working on finishing. Then I can mount archive drives and conform/consolidate/relink or do whatever. It’s been quite slick. And by moving the originals to an archive drive first I’m not reconfiguring CatDV all the time to find the footage for both the originals and the proxies. I also have a portable clone of the proxy drive for working offsite (I used to just call that home). Because we’re using “paths” for proxies CatDV (and Final Cut) always thinks it knows where to look for a shot.
Sure, you can do what you suggest, but I think you’re adding a layer of complexity that’s not really going to help you that much and it will eat up even more prep time. Takes me back to the days when I setup the table of accounts for my old company’s accounting system in Quickbooks. I had everything parsed out to the Nth degree. I could have told you how much black gaffer’s tape was used on training projects versus commercials on any named Thursday. Of course I never did, nor did I ever actually need that level of detail. In the end it was a big lesson learned. One of the big lessons with CatDV is that you can add fields and descriptions later without messing up everything you already have. Are you willing to go back and redo your directory structure if someone suddenly decides if they want to know if shots were done under cloudy or sunny skies? Ouch.
Non-linear: all the time and nothing but.
-
Looking at your proposed directory structure and file name you have everything in triplicate. Just as it is you could drop four levels of directories.
Non-linear: all the time and nothing but.
-
Well from my perspective you’re over thinking it.
I’m in pretty much the same situation. about 16 years of footage, dating from the time we switched from film to video. For the last 13 or so years we’ve created a great deal of derivative product from all the different material we’ve shot and continue to shoot. It’s all documentary in style. Not a spoken word is scripted. Lots of interviews and lots of transcripts. We create video-based products that are sold all over the world.
A few years ago we even changed the way our accounting works to match the way we actually create product. Whenever we shoot it’s research towards making an at-the-time-undetermined project. Product creation doesn’t begin until we sit down to put together a project in edit. The best way for us to work this way, and keep footage somehow compartmentalized and still make some sense of it all, was to separate it out by shooting location. So we have this factory, or that office site, or that hospital or school. Reel names (we shoot HDCam on a 750) use as two or three letter designator for the shooting location. So I can see a note or a line out of an EDL, or a tape case and know immediately what “shoot” it came from.
Ok. So the majority of the time I’m using FCP to load the footage. The project goes under the location name, say “Unity Hospital.” What become important later is the path to the directory Unity Hospital. Doesn’t matter how or where that footage goes later. I just need to find it. I use FCP to mark sections to load and label them such as: UN07 cafeteria cover 1.mov or UN10 Lacy Darcy interview part 2.mov {Note that I’m using ProRes for my files). When the shots are captured I bring them into CatDV, which will remember just exactly where the footage is. I can then parse them out even further with all sorts of key identifiers and markers and transcripts. I also create proxy movies of everything that live on a separate drive attached to one of my systems. Because I’m using “paths,” the structure is the same as the original footage.
Lately I’ve been moving footage off onto external drives for storage, and to clean out my systems. I’m sure some lucky souls get to use CacheA but for now we’re using raw external drives. It’s quick and easy and I can mount a drive using an eSata dock directly to one of the systems and edit from the raw drive when I need to. But the real change has been moving the original footage off to one of my archive drives FIRST and then bringing the footage into CatDV and making proxies from there. I’m doing the vast majority of my editing using the proxy movies, NOT the originals. As a result I have 100 of my footage from ALL shoots available ALL the time. Originals don’t come into play until I’m working on finishing. Then I can mount archive drives and conform/consolidate/relink or do whatever. It’s been quite slick. And by moving the originals to an archive drive first I’m not reconfiguring CatDV all the time to find the footage for both the originals and the proxies. I also have a portable clone of the proxy drive for working offsite (I used to just call that home). Because we’re using “paths” for proxies CatDV (and Final Cut) always thinks it knows where to look for a shot.
Sure, you can do what you suggest, but I think you’re adding a layer of complexity that’s not really going to help you that much and it will eat up even more prep time. Takes me back to the days when I setup the table of accounts for my old company’s accounting system in Quickbooks. I had everything parsed out to the Nth degree. I could have told you how much black gaffer’s tape was used on training projects versus commercials on any named Thursday. Of course I never did, nor did I ever actually need that level of detail. In the end it was a big lesson learned. One of the big lessons with CatDV is that you can add fields and descriptions later without messing up everything you already have. Are you willing to go back and redo your directory structure if someone suddenly decides if they want to know if shots were done under cloudy or sunny skies? Ouch.
Non-linear: all the time and nothing but.
-
oh great. That means we have to do some. 🙂
Need to catch up. . .Non-linear: all the time and nothing but.
-
Robb Harriss
April 23, 2012 at 5:15 pm in reply to: CatDV for small operation with RAID and bags of external disksKind of a tall order because it’s so open, if you know what you mean.
For starters just put all your proxies in one place. I have a single G-tech drive that’s holding all of them right now. All the machines simply point to it. You can carry that with you, or as I do, clone it over to a smaller buss-powered portable firewire drive. The only thing that changes, and it’s per machine, is pointing to the drive holding the proxies. In the windows world just give it the same drive letter all the time. Easy enough.
Is that what you’re looking for?Non-linear: all the time and nothing but.
-
I just set the audio to whatever the original is, in my case 48K and leave it uncompressed. I don’t believe that it takes any more time do deal with. Are you dealing with lots of different audio tracks? There is a function to select a track for playback if more than one is available.
Non-linear: all the time and nothing but.
-
Robb Harriss
April 7, 2012 at 12:31 am in reply to: Maximizing the Potential of Metadata: FCP7, Premiere Pro, FCPx, and CatDVThat’s not all that much footage :-), at least in my house. But think of this: transcripts. In my care little is more important than what people say. I send everything of for transcription. If you can’t afford it, do it yourself. Time consuming, you say? You’re the one with 60 hours of footage. The more time spent in prep, the less spent in edit. In the “olde days” we tried to keep people out of the edit suite until they were ready.Contrary to current practice, an edit suite is not for the purposes of viewing, reviewing footage. It’s for editing. It’s cheaper to work outside the room than inside the room. The room keeps busy and your can manage more than one project simultaneously.
A system like CatDV allows you to integrate the transcripts right into your logs. Yeah, that’s what we used to call them. Log your footage. It’s all about knowing where everything is. Transcripts do that for the most difficult parts. Time coding the transcript allows you to hop right to the quote with a click. Cover footage is much easier. And you want to lock down your search terms. You don’t want people to use multiple words for the same thing, e.g. Kid, child, boy, girl, youngster, Infant. You want to limit the terms or you’ll be searching forever. None of the NLE systems lefmyoumlog, work at this level. Yet CatDV let’s you work with all of them. It even allows a user to cobble together a cuts only version sof a sequence that you can open fully populated with footage. It also let’s you carry around all the footage for a project (or many projects) in you pocket. Many of our pieces are culled from hundreds of hours of footage shot over the years. I can sit there with it all loaded all the time. Yet none of it is in the edit system (yet) clogging it up.Non-linear: all the time and nothing but.
