Rolf Howarth
Forum Replies Created
-
Apologies for the delay replying. This is first we’ve heard of excessive times saving catalogs onto a Windows network share but that could just be because, as Matt says, that’s not a typical use case. Most standalone users save catalogs to a local drive, most network users save them to the CatDV Server (which is specifically designed for sharing catalogs, of course). Anything more than a second or two or so to save a 3MB catalog file is excessive though, so we’ll do some tests and investigate.
-
You should be able to import an ALE file (not AAF) into CatDV. You say “CatDV indicates that either the file is corrupt or the codec to read the media the missing” but I don’t recognise that message in the context of the ALE importer, so perhaps you could send a copy of the ALE file and a screenshot of the error to support@squarebox.com? Thanks,
-Rolf -
Apologies for missing this thread earlier. I can’t immediately reproduce this issue, so I suspect it depends on the type of media you’re dealing with. If you have an example that fails could you mail the following to support@squarebox.co.uk so we can investigate please: a screenshot of the clip in FCP, a screenshot after importing it into CatDV, and a copy of the XML file from Final Cut? Thanks.
-
Weird, the forum automatically turns YouTube links into embedded video, which may not work in all browsers. If you have problems, go to YouTube and search for “CatDV and Cache-A”
-Rolf
-
Some 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.
-
Ok, but the way CatDV sees things the whole file path is the “name”. Thus a tape-based preview such as /Volumes/Raid Set/CatDV Previews/ADH02/3000,27584,28777,96c.mov includes the the reel name ADH02. On the other hand, a path based preview such as “FS02 John Smith.mov” will be called whatever the original hires file has called (possibly with the extension changed to .mov, .mp4 or .jpg). The original file might be called Clip1.mov, Sunset.mp4, DSC01234.jpg, Train.wav, or whatever. Some applications might include the reel name there but by no means all.
-
I’m still confused. You say “path-based files have the original reel name as part of the file name”. The reel name isn’t added by CatDV, it just uses whatever the original file name was. How the files are named depends on what software you use to capture them and how you name your clips. CatDV will work with any kind of files placed on any volume with any kind of folder structure and any kind of file name, so file-based previews won’t in general have the reel name in them unless you or your software put it there.
-
I’m not sure I know what you mean by path-based previews looking like tape-based ones.
If the original file path has the reel name in there somewhere then the corresponding path-based preview will too, but if the original doesn’t then the preview won’t.
Unless the old Mac Classic way of doing things, CatDV always accesses files via Unix-style file paths. We use the term “original” to mean the original path to the full res media that CatDV saw when the file was originally imported, ie. what’s stored in the CatDV Media Path field. If the file has moved, or was imported on a Mac and the catalog is being view on a PC, or if the original file is offline and you only have a proxy available, then CatDV uses “path mapping” to automatically construct a new file path from the original file path (ie. the path as stored in the catalog).
-
PS. You could also set up equivalent directories for the full res media, so even if you import the file on one machine (so that’s the path that’s stored in your catalog) CatDV will automatically locate the hi-res media file on the other machine, even though it’s mounted differently.
-
Don’t use catalog archives! That’s an obsolete feature that only worked with tape-based previews and will be removed in a future version of CatDV.
I’ve just seen your comment about “naming the RAIDs the same”. That’s another more likely explanation of why you’re seeing RAIDSet and RAIDSet-1, if you have two volumes with the same name mounted at the same time.
I would strongly recommend you don’t name them the same. If you have two different files with the same path name, how can the system tell the files apart?
Note that that isn’t the same thing as saying that the same file can’t have two different paths. This happens all the time and is something that CatDV copes with well, especially in mixed environments. For example /Volumes/Media and the M:\ drive might be the shared volume on Mac and Windows, so if you configure them as being equivalent paths then CatDV will automatically find the file even if it encounters the “wrong” path.
Yes, “original” refers to the original full res media that the proxy relates to. Let’s say you have a disk which is sometimes mounted as /Volumes/RAID_ONE and sometimes as /Volumes/FCP Edit 2/RAID_ONE but the contents are the same in each case. (I’ve made up a new name to make it clear that each volume needs to have its own unique name, for example RAID_ONE and RAID_TWO). Let’s further assume you have a separate volume which we’ll call PROXY where you want to store your proxies. (If you mount and unmount your main volumes, I assume the proxies will be on a separate volume that is always available?)
You could then set up paths such as the following
Tape-based previews:
/Volumes/PROXY/TAPE/Path-based previews:
/Volumes/PROXY/ONE (/Volumes/RAID_ONE)
/Volumes/PROXY/ONE (/Volumes/FCP Edit 2/RAID_ONE)
/Volumes/PROXY/TWO (/Volumes/RAID_TWO)
/Volumes/PROXY/TWO (/Volumes/FCP Edit 2/RAID_TWO)If you do that, your PROXY volume will contain three top-level directories: TAPE (all your tape-based previews), ONE (proxies for all the original files on RAID_ONE), TWO (proxies for all the original hi-res files on RAID_TWO), and CatDV will find the proxies regardless of which machine you imported the media and built the previews on.