Wishlist: VS default directories

Moderator: Ken Berry

Post Reply
gordonwd
Posts: 120
Joined: Thu Dec 16, 2004 9:15 pm

Wishlist: VS default directories

Post by gordonwd »

I tend to keep pieces of my video projects in several different directories: project files, video clips, JPEGs, audio, output video files, etc. The annoyance is that VS only "remembers" the one previous directory that you've accessed. So if I insert a picture into the timeline by navigating to my directory of images, when I later insert a video clip it defaults to my image directory and I have to navigate back to my video clip directory, and so on.

What would be nice would be if it remembered the previous directories used for different purposes, such as where I last pulled a video clip from, and a different directory for where I read in an audio file, etc. I know that another Ulead product -- PhotoImpact -- works somewhat this way, as it keeps separate defaults for photo files that I'm reading in from the directory where I'm exporting JPEGs.

Maybe nit-picking on an overall fine product, but this has been bugging me since I started with VS7 (and am now up to VS10+).
BrianCee

Post by BrianCee »

so why not just set up different libraries for different sorts of videos, images, audio etc. - then when you want to find a different clip, audio or still you just flip quickly between libraries without needing to browse at all.
sjj1805
Posts: 14383
Joined: Wed Jan 26, 2005 7:20 am
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB
Location: Birmingham UK

Post by sjj1805 »

Actually you're both right.

What I would like to see is common sub-directories for things like transitions, video filters, sound clips, menus so on and so forth - shared by ALL Ulead products such as VideoStudio, MovieFactory, MediaStudio etc.

Then we would not have to worry about how to use/import menus and other things from one product in another.

I also agree that when you open something from the video library it should remember that path separately from the path used to open something in the audio library. Programmatically there are variables holding a path location, with todays large hard drive capacities a couple of extra bytes for a couple of extra variables would not be such a big deal as it was several years ago.

A few years back when hard drives RAM and so on were much smaller programmers had to find ways of keeping things small such as 2 digit year dates - eventually leading to the so called 'millenium bug'
Post Reply