One thing why isn't that space in the middle that seperates the timeline (upperhalf) and the rest of the bins (lowerhalf) not better utilized.

You got a screen grab of this - I'm interested.

"name of current clip", that's there "Show Event Name" clips in Vegas are called Events. Something I piked up from reading here and the manuals
"date of caught on camera (for those of us who like to keep events in chronological order). " Well, eh kinda yeah. But the progressive Event NUMBER will indicate chronological order too?

Is this the length of clip you referred to? "There are many times that I just want to know how long is that edited clip." Double click on it and you get the readout in the bottom right hand corner of the T/L. Yeah?

"Creating a loop setting seems to be the quickest way and it may not be accurate if you don't set it correctly at both ends." Don;t follow?

"The way I see it here lies some precious realestate completely unused." - Sure! Anything for improvement.

Back to your "cross-post". I believe Bob and others were referring to the SFVidCap file and where that gets placed. That can be a pain. But You can ALWAYS setup your capture folders and drives.

You should REALLY try out Scenealyzer.

I think what Thom is asking for is the display of tape metadata.
There's a whole world of stuff recorded by most cameras and a stack more that the camera operator can log onto the tape as well as into the memory chips on tapes. Take a look at a MiniDV or DVCAM tape. On the back edge of the tape you'll see five or so indents, that's where a set of contacts can go and if you buy the slightly more expensive tapes there's contacts there that connect to a flash memory chip. Once you've got that and the right camera all manner of usefull things can be written into that memory chip.

Sony VCRs will read that data back for you and display it.
Even without the memory chip there's a lot of data on the tape that we're denied access to.

Re the capture issue.

What's being referred to is not just the SFVidCap file. Rather it's the issue of where Vegas captures clips to. Logically when starting a new project one would specify a root directory for the project and then the NLE creates folders (bins?) where it stores things. This way you and the program know where things are. You go to capture a tape and without thinking about it the capture puts the clips in there, let's say a bin named 'Capture', which is also a folder called 'Capture' under the project root. It saves itself into a 'Projects' folder.

The advantage of this is when you run multiple projects everything ends up in a logical place instead of the current annoying, conterproductive way Vegas does things at the moment. The one that really bugs me is when I render something out and then go to save a new copy of the project by default it wants to save the project into the folder I just rendered to.

Perhaps all of this could be solved simply if the Vegas project file used XML. Everything could be stored, the project would remember what mpeg-2 encoder settings were used, what mp3 tag data was used, where the assets were, the saving in user time could be huge and as new things are added all it takes is a revision to the schema and it wouldn't be too hard to repair a corrupted project file.

Problem at the moment seems to be that the project file is only an inliner record set which is very inflexible.

Bob.