Opening Project Takes Hours


Grazie wrote on 7/25/2016, 5:06 AM
Peter, yes, I've stopped using Media Manager in favour of Explorer. If I use use Bins now it is purely for Project-specific stuff: Graphics: Stills//Photos; Generated Media from NBTP4Uli and other Text; Audio that I want separation.
Dexcon wrote on 7/25/2016, 6:42 AM
+1 Peter

I use Windows folders for every use for which I could otherwise use Bins. And I never keep the Project Media tab as an in use window within VP13. If in use, it significantly increases the opening time of the project because it takes a long time in a big project for the basic Project Media to load all the project's events even when there are no bins created.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"


Grazie wrote on 7/25/2016, 9:11 AM
Went over the top here: 35 Bins. It is still loading after 30 mins = 1,800secs.

I killed it . . . .


Or_Toltec_Tal wrote on 7/25/2016, 11:25 AM
Thanks Guys,
Using Explorer instead of 'Project Media' can't assist you with SubClipping.

Subclip is the main reason why I use Vegas Pro, The ease of use, the transition from one subclip to another with the arrows and instant Play is heaven sent !!! Premiere Pro and Final Cut don't have it. How can you live without it, Is a total mystery to me.

If you guys want I'll make tutorial on how I use Subclips and see how efficient it is and unbelievably helpful in editing.

BTW how can I turn on the email notifications for this thread ?
Grazie wrote on 7/25/2016, 11:32 AM
Eml notifs? - none!
Or_Toltec_Tal wrote on 7/25/2016, 12:50 PM
So Grazie how were you notified that a new response was written here after a few years of non activity?
A-Scott wrote on 7/25/2016, 3:35 PM
I would guess Grazie knew because the new response caused the thread to move to the front page.

BTW, good catch on the bin issue. I'm having trouble imagining program logic that would have such behavior. Perhaps multiple thread/deadlock problem that kicks in after so many bins created.
Or_Toltec_Tal wrote on 7/25/2016, 3:54 PM
Thanks A-Scott

A professional NLE system not supposed to be limited in it's Bin folders.
We all know very often we get a Huge source material that we need to trim, subclip, and organize.

28 bins limit or 32 does not make an sense. It is purely a BUG. terrible shameful bug on Sony's Part. It need to be Fixed ASAP.
rmack350 wrote on 7/25/2016, 4:34 PM
Nick, this is something I recounted a while back. I was seeing projects bog down at around 20 bins in VP11. Maybe this coincided with the introduction of some new bin features like smart bins.

I didn't actually time it since it was just pretty obvious there was a problem.

NickHope wrote on 7/25/2016, 9:47 PM
"I'm having trouble imagining program logic that would have such behavior."

Perhaps each media bin triggers a re-scan of all the media bins (for thumbnails, codec support etc.). That would explain the approximate doubling of time for each extra bin.
NickHope wrote on 7/25/2016, 10:06 PM
Nesting bins can help. If I nest 11 of 22 empty bins into another bin, the project opens much faster than if all 22 are at the same top level. Haven't done enough testing to establish a pattern.
NickHope wrote on 7/25/2016, 10:44 PM
I submitted a support request to MAGIX, [Ticket#2016072617000806].
Grazie wrote on 7/26/2016, 3:30 AM
As I said, no eml notifs. I saw that the thread had been responded to by its appearance at the Top of the Forum listing.

rmack350 wrote on 7/26/2016, 1:48 PM
Perhaps each media bin triggers a re-scan of all the media bins (for thumbnails, codec support etc.). That would explain the approximate doubling of time for each extra bin.

That would fit in nicely with what I was seeing with Smart Bins in VP11. They would get unmanageable at around 20 bins where plain bins were still usable. Smart bins will rerun a search whenever the bin is touched.

Many years ago I had a similar experience with Dreamweaver and its site caching. I think it was attempting to run two simultaneous scans in an attempt to build a cache of a site. They never caught it because on smaller sites the effect was negligible, but there was a tipping point in the number of file objects where the scan would start to take forever. This sort of thing can happen when you've got multiple developers or a feature has been developed in bits and pieces over time.

Or_Toltec_Tal wrote on 7/26/2016, 9:24 PM
Thanks Grazie and Thank you nick for reporting to MAGIX. great job!

Nesting bins does not solve the problem. and the problem cannot be related to thumbails or media because it happens just the same with 100% EMPTY BINS, nested or un-nested.

Let's hope this Bug will get handled asap. I was amazed to read the previous post from our friend rmack350 who had encountered this problem as far as mid 2012 (VP11) !!! and reported it to SCS, still, seems that nothing had been done. very sad and alarming!
riredale wrote on 7/27/2016, 11:31 AM
Perhaps a dumb question: what is the benefit of using bins versus just regular old Windows folders?
rmack350 wrote on 7/27/2016, 12:01 PM
Bins are what is expected in most professional environments, so if you have more than one editor and they have varied backgrounds you might want to organize things in a way everyone would expect.

In addition, you can have one clips occur in many bins. It's an organizational tool but not a storage tool. If you're working in a place that has strict storage policies then bins give you some freedom from that. Also, if you regularly work with stock or library footage that is used in multiple projects (magazine shows, for example) then it may not be possible for everyone to move the media to the folder they want.

Or_Toltec_Tal wrote on 7/27/2016, 12:51 PM
Riredale - as to your question. in one word : SUBCLIPS !!!

you can trim the usable sections of your footage, put them into named Bins - and then very quickly browse them and lay them on the timeline in the order that you wish.
Vegas Pro is the only NLE that can preview subclips in realtime. which means you can move from subcllip to another with the arrow keys and the subclips play immediately (with autoplay option enabled).
This let me work very fast and find exactly what I'm looking for through switching very quickly between subclips. great for long interviews, or footage that you need to assemble in an unknown order.

Windows folders lets you sort the RAW file. but you cannot trim only the usable sections of your footage and sort them by name and folder - this is what Bins are for.

feel free to contact me if you want to know my quick method of subcliping. this workflow is the only reason I stick with sony vegas.
NickHope wrote on 9/20/2016, 3:25 AM

This bug of large numbers of media bins making Vegas open slowly has been fixed in VEGAS Pro 14.0 (Build 161). I tested with 30+ empty bins and it now opens snappily. Thanks!

[Edit: This bug returned in VP17]

Gabriel_Ahn wrote on 11/24/2016, 10:51 AM
MUTTLEY, try this.

1 - Start Vegas 12
2 - Close the "Project Media" window
3 - Open your troublesome project

Does it open much faster?

4 - Open the "Project Media" window

Does Vegas go "Not responding" for a long time?

What you're experiencing is similar to what I've seen when opening a large project started in an older version of Vegas. No amount of futzing would make it open as fast as a project started in Vegas 12. I've have no solution yet.


Holy Mother of God! I've been suffered by this issue and searched for the solution for a week and your solution works! Thank you very very much!