John, I can't recall whether I already sent this to you via email. I think I'll start posting any suggestions only here so others can pipe in if they have additional insights.
I really like the archive function, especially the ability to handle nested projects. I think a great addition would be to catalog the archives in a simple database (or even Media Manager if that is open to you). This would be a very useful way to keep track of projects that are archived to external media. Support for this information would be especially helpful:
1. Project name
2. Project description/notes to me
3. Archive media name
4. Date/time archived
5. Archive contents (e.g., veg, dar, and media file names)
6. If possible, it would also be useful to put the version of Vegas that was used to create each veg and dar. I wish SCS would include that in a metadata header.
One other suggestion - I wish the archive function gave the option of automatically including resources like fonts used in the project.
Jerry
I really like the archive function, especially the ability to handle nested projects. I think a great addition would be to catalog the archives in a simple database (or even Media Manager if that is open to you). This would be a very useful way to keep track of projects that are archived to external media. Support for this information would be especially helpful:
1. Project name
2. Project description/notes to me
3. Archive media name
4. Date/time archived
5. Archive contents (e.g., veg, dar, and media file names)
6. If possible, it would also be useful to put the version of Vegas that was used to create each veg and dar. I wish SCS would include that in a metadata header.
One other suggestion - I wish the archive function gave the option of automatically including resources like fonts used in the project.
Jerry