by mikeryan » Thu May 13, 2004 5:06 pm
The inconsistency wouldn't bother me any - if you think of the filesize field as "the number of bytes that will be transferred (or whatever) if I use the file", it's not really inconsistent at all. I wouldn't be bothered by stale filesize data when removing tracks from the VCD either, I really have no interest in what the size on the external disk is. Of course, you could clear that field (or update it if the original disk happens to be mounted), but I don't think it's a big enough deal to squeeze in for 2.2. Assuming VCD data is kept in its own DB table (I have Access 97, it won't open the MM DB for me to poke around myself), I'd think the ideal solution would be to save the VCD filesize there and keep the original disk size in the main table, but of course you don't want to make metadata changes at this stage of development.
As long as size-limited autoplaylists work right, I'll be happy... I've been managing my player contents and playlists by hand on fairly complicated criteria, and MM 2.2 will be very close to letting me fully automate it. I've been looking for a media database app for a while (even sketched out a design for building it myself, including the VCD concept), I really appreciate you doing the work for me - thanks!
The inconsistency wouldn't bother me any - if you think of the filesize field as "the number of bytes that will be transferred (or whatever) if I use the file", it's not really inconsistent at all. I wouldn't be bothered by stale filesize data when removing tracks from the VCD either, I really have no interest in what the size on the external disk is. Of course, you could clear that field (or update it if the original disk happens to be mounted), but I don't think it's a big enough deal to squeeze in for 2.2. Assuming VCD data is kept in its own DB table (I have Access 97, it won't open the MM DB for me to poke around myself), I'd think the ideal solution would be to save the VCD filesize there and keep the original disk size in the main table, but of course you don't want to make metadata changes at this stage of development.
As long as size-limited autoplaylists work right, I'll be happy... I've been managing my player contents and playlists by hand on fairly complicated criteria, and MM 2.2 will be very close to letting me fully automate it. I've been looking for a media database app for a while (even sketched out a design for building it myself, including the VCD concept), I really appreciate you doing the work for me - thanks!