The good news.
Several of you have asked me how hard it is to create a database of all your DVX video clips. Well, I’ll try to explain it--and why I haven’t simply posted one (yet).
We have the contents of hundreds of P2 cards on several Terabyte disk drives. The metadata for all of them lives in a single FileMaker database. You can type in any request you want. For example, all the clips
-- between 1-8 seconds long
-- shot by a particular person
-- shot by a particular P2 card
The last line is in case you find a corrupted clip. Which card was responsible? The database can attach the factory serial number of each card to the clip. If a clip is split across two cards, it displays the card that contains the second half of the clip. You don't need NEXTCLIP.txt, because that information is in the metadata of both clips that are split.
You can scrub through each clip right in the database--not in a separate window. In a list of clips, the icon that represents each clip is not simply the first frame in that clip; it is a frame you (or someone on your staff) designated as the representative frame. So there is no need for a separate icon jpg image.
The XML data are imported with the click of a button. You have a hundred different fields of information, such as location--down to the province, city, street where the shot was taken, but also the location of the tripod holes in case you need to recreate the shot.
It does timecode math, and it changes diapers. I wrote it over a weekend because I got tired of waiting for someone to come out with something like it. I’m not a professional programmer. I just play one on TV.
Don’t get me wrong, HD Log is great, but... ( See below).
Several of you have asked me how hard it is to create a database of all your DVX video clips. Well, I’ll try to explain it--and why I haven’t simply posted one (yet).
We have the contents of hundreds of P2 cards on several Terabyte disk drives. The metadata for all of them lives in a single FileMaker database. You can type in any request you want. For example, all the clips
-- between 1-8 seconds long
-- shot by a particular person
-- shot by a particular P2 card
The last line is in case you find a corrupted clip. Which card was responsible? The database can attach the factory serial number of each card to the clip. If a clip is split across two cards, it displays the card that contains the second half of the clip. You don't need NEXTCLIP.txt, because that information is in the metadata of both clips that are split.
You can scrub through each clip right in the database--not in a separate window. In a list of clips, the icon that represents each clip is not simply the first frame in that clip; it is a frame you (or someone on your staff) designated as the representative frame. So there is no need for a separate icon jpg image.
The XML data are imported with the click of a button. You have a hundred different fields of information, such as location--down to the province, city, street where the shot was taken, but also the location of the tripod holes in case you need to recreate the shot.
It does timecode math, and it changes diapers. I wrote it over a weekend because I got tired of waiting for someone to come out with something like it. I’m not a professional programmer. I just play one on TV.
Don’t get me wrong, HD Log is great, but... ( See below).