Available Capture space

Former user wrote on 3/3/2007, 4:48 AM

I'm trying to track down a problem with Vegas under estimating available drive space on a newly installed 500 gig RAID 0 array. It appears that Vegas (I tried V3, V5 and V7) is only "seeing" a maximum of 100 gigs of the drive.

1. Could anyone out there that has 100gigs (or more) free on an AV drive confirm that Vegas Capture calculates at least 7 hours of capture space?

2. If so, is this drive a single drive or RAID array?

3. And if it is a RAID is it setup as a Simple / Dynamic drive? (this is found by right-clicking My Computer then choosing - Manage / Disk Management)

Thanks!

Jim

Comments

TheHappyFriar wrote on 3/3/2007, 5:40 AM

I don't have a RAID, but when I go to choose a folder my "D" drive has 114 free & has ~9.5 days of capture free.

dcrandall wrote on 3/3/2007, 6:33 AM

1. I am showing 976.64GB of free space. (The "Estimated capture time available" is only showing 01.33.16;11 though which is obviously incorrect)

2. I have a 2-Drive 1TB RAID0 array

3. It is setup as a Simple / Basic drive. (I was never given the choice to make a Dynamic volume .... the option was grayed out)

-Dan

Former user wrote on 3/3/2007, 6:53 AM

Thanks for the reply / info. I've been messaging tech support on and off for over a week (about a 48 hour turn around between responses) and they haven't indicated that they have ever seen this.

I have noted that as I capture footage the estimated time goes down. As a test, I created another folder on the drive (via Windows, not using Vegas) and copied about 50 gigs worth of files to the new array. Then ran Vegas Capture again and noted that Vegas now reported that now it only had half the available capture space.

So, it appears that, for some reason, Vegas can only access 100gigs of a large drive of drive array. Not only that, it can only access "the first" 100 gigs of drive space. For example: you have an empty 250 gig drive. Vegas will incorrectly report that there is only ~7 hours of available space on it (it should be ~18 hours). If I now transfer 100 gigs of files to the 250 gig drive (leaving 150 gigs free space) Vegas will report that it now has zero capture time available on it.

The only work around that I can think of is to re-partition and format the drive array into multiple drives (of ~100 gigs each). I would think that Vegas might be able to handle "them" correctly. But that's a lot of work and I run the risk of creating new problems to deal with.

I'm hoping that someone out there has dealt with this before and has a solution that gets Vegas to access the entire 500 gig array.

Thanks again.

Former user wrote on 3/3/2007, 7:45 PM

Just a bump...

Chienworks wrote on 3/3/2007, 7:51 PM

I've recently added a 250GB drive and a 300GB drive. Both are IDE ATA and neither is part of a RAID, so i didn't think my experiences would help you at all. Modern drives are so large, fast, and cheap that RAID seems kind of a pointless source of more problems these days.

For what it's worth though, the available capture time shown in VidCap seems to be correct.

dcrandall wrote on 3/3/2007, 8:17 PM

I'm not sure I understand ......on your system, is Vegas not seeing the proper amount of disk space? (Vegas correctly sees almost 1TB of space available on my RAID 0 configuration). On my system, it's only the capture time estimate that is incorrect.

Have you actually tried capturing more than what the estimate tells you is available time-wise? I'm guessing that Vegas is only incorrectly estimating the amount of capture time remaining but it will not really effect your capture.

-Dan

Former user wrote on 3/3/2007, 8:29 PM

I guess I was just assuming that when Vegas determined that there is zero time available on a drive it would no longer capture to it. But, since it sounds as if this is some sort of issue with my system, and not with Vegas, I'm sure this thread will die off pretty quickly.

Thanks for all who did reply.