Vegas starts to hang after the 20th bin...

rmack350 wrote on 6/19/2012, 11:05 AM
Yesterday I was going through a project containing about 300 named clips, using the project media window's search tool to search for specific things, and then saving the search results as bins. Around the 20th bin, Vegas started to get unresponsive while creating the bin. Both cores would run at 50% while Vegas spent a few minutes trying to create the bin. Each successive bin took longer to create, until the last one I tried, maybe the 24th, took about 10 minutes to create. Vegas would remain unresponsive during this time.

The solution was to split into two projects and delete half the bins but that wouldn't work for everyone. Once half the bins were deleted new bins could be created again without any hang time.

A side curiosity was that FileIOSurrogate was running at about 900MB of memory usage, but that didn't change when I split the project. I don't think it's relevant but it caught my eye since that's a lot of memory usage.

There were only a handful of clips on the timeline at any moment. They were DVCProHD quicktime files using Raylight Decoder. I was exporting stills, so jpeg images were being added to the media pool automatically.

I'm using VP11-64, latest build, on Win7-64 with a Core i5 2500 and 6GB of RAM. Project and media are on an external USB drive. I think only the Vegas version and the RAM are relevant, though.

Anyone ever had a similar experience?

Rob

Comments

Former user wrote on 6/19/2012, 11:40 AM
All of the thumbnails created in the bins are stored in memory (notice that it has to redraw each time you open a project). In the past I know this can tie up a lot of memory and as such, it is sometimes recommended to turn thumbnails off on large projects to conserve memory.

Dave T2
rmack350 wrote on 6/19/2012, 11:51 AM
Thanks Dave.

I always use Details view in the project media window. And if I watch the task manager I don't see any page file activity. Just Vegas11 happily running along at 50% CPU on all two cores.

So, I assume that my thumbnails are as off as they can get.

If I had some time I could try making bins with AVI files. However, since the bin creation process goes from immediate to interminable with just a few more bins I think it's a Vegas problem. Sometimes code will seem to work fine because it finishes quickly but if you load it up it'll do it's job slowly enough to see a problem.

BTW, I reported this to SCS yesterday.

Rob
JJKizak wrote on 6/19/2012, 12:48 PM
My next rebuild will have as much memory as I can stuff into the case.
JJK
rmack350 wrote on 6/19/2012, 2:45 PM
JJK sez My next rebuild will have as much memory as I can stuff into the case.

Sure, but I'm not seeing any shortage of memory while this happens. The page file doesn't grow, Vegas is using a little over a gigabyte out of the available 6 GB. I don't believe this is strictly a memory issue, or if it is then it wouldn't matter if I had more RAM installed since it's a management issue rather than a quantity issue.

Just curious if anyone else has had the same experience. I could try the same project on my home computer which is a little more powerful than the one at work, and I could try to do the same thing with AVI files instead of quicktime...but I think it's a flaw in the way Vegas deals with bins. Bins have always seemed like a back-burner feature of Vegas that has never gotten much attention since they were introduced.

Rob
rmack350 wrote on 6/20/2012, 4:58 PM
A follow-up on this. I haven't had time to swap out for other types of media but it occurred to me that maybe this hanging was strictly linked to creating a Bin from Search Results.

Sure enough, I can create a new empty bin without any sort of hang or delay. I can search the Project media for clips with a certain word in their name. No problem there either. And I can select the results and drag them into my new empty bin. No problem.

The only time its a problem is if there are lots of bins (around 20), I do a search of the project media, and then right click on the search result (under the bins) and select "Save as Bin". Then I get a 5 or 10 minute hang.

Rob