A few weeks ago I posted asking what sort of project management features people could envision for Vegas. I don't think there were many responses and I didn't have anything on my mind at the time. Now I do, because I'm recatpuring 10 or 12 clips spread across several tapes shot over the last two years. There are maybe 50 tapes in this project. Here's what comes to mind:
1: Vidcap really bogs down if you've got too many clips in a vidcap file. It needs to be able to handle much, much bigger catalogs of tapes and shots.
2: Vidcap doesn't keep track of media that's been moved. It should. It would either allow you to search for media or it would get the info from the current project whenever that project has to find offline media.
3: vidcap files need to be more "Project Based". Users should be encouraged to use Vidcap as a project database, and vidcap should be useful as a project database.
4: Vidcap files could also keep track of what veg files are using the media files. Much like edit details, vidcap should show you where and how many times a media file is used within a project, assuming that a project encompasses many veg files.
5: Vidcap needs to be more integrated with the main Vegas program. Definitely when Vegas has to find media Vidcap should also know the media was moved.
6: If vidcap fails for some reason in the middle of a batch capture, it would be nice if the files already captured were usable. Currently, you have to wait until Vidcap successfully finishes the batch job before the media files have names applied and are added to the current media pool.
I guess what I'm saying here is that Vidcap could become an overall project management tool, coordinating itself with all of the Veg files associated with it. In the Vegas project you would specify the vidcap database to associate with the project. You should be able to specify "none" if you like.
Rob Mack
1: Vidcap really bogs down if you've got too many clips in a vidcap file. It needs to be able to handle much, much bigger catalogs of tapes and shots.
2: Vidcap doesn't keep track of media that's been moved. It should. It would either allow you to search for media or it would get the info from the current project whenever that project has to find offline media.
3: vidcap files need to be more "Project Based". Users should be encouraged to use Vidcap as a project database, and vidcap should be useful as a project database.
4: Vidcap files could also keep track of what veg files are using the media files. Much like edit details, vidcap should show you where and how many times a media file is used within a project, assuming that a project encompasses many veg files.
5: Vidcap needs to be more integrated with the main Vegas program. Definitely when Vegas has to find media Vidcap should also know the media was moved.
6: If vidcap fails for some reason in the middle of a batch capture, it would be nice if the files already captured were usable. Currently, you have to wait until Vidcap successfully finishes the batch job before the media files have names applied and are added to the current media pool.
I guess what I'm saying here is that Vidcap could become an overall project management tool, coordinating itself with all of the Veg files associated with it. In the Vegas project you would specify the vidcap database to associate with the project. You should be able to specify "none" if you like.
Rob Mack