For the last hour I have been continiously end task, restart, etc. trying to get Vegas to load without Media Manager crashing freezing the system. Is there anyway to turn off MM outside of Vegas???
Sony please get to bottom of this! My workflow has come to a standstill.
A trick I learned is that when you install the Vegas software, just whack cancel as soon as you see the Media Manager installer popup. You'll get an error when you run Vegas that says MM cannot be started, but can get rid of that easily by checking a box in the Vegas options.
" Why don't they just fix the damn MM? Hello? 6.0c anyone?"
Probably because (if I recall) the database engine is a Microsoft product - installed with XP, and I suspect that this is where the problems are coming from.
"I have no problem with MM loading correctly. I suspect that 99% of Vegas 6 users don't either. Why not fix your computer?"
Come on let's get real here. I suspect you have not been reading the posts on people having troubles with Media Manager. Also have you used it for a large project like 1900 clips? My system and Vegas runs perfectly without MM enabled. Common sense tells me that it's a software problem when Vegas will not start half the time only when MM is enabled and actually crashes while trying to load MM.
I have not had any issues with MM, not sure why some folks have had terrible experiences. Check your Microsoft products, registry, services and ortrojans/spyware, etc. i suspect it may be with some windows file that is corrupt or missing. Perhaps re install Windows.
the microsoft forums are flooded with people that have problems with SQL components .. even MS suggests to not use it sometimes ... I believe it is more a MS issue (in interaction w/ vegas) than sonys problem .. though of course they are on the firing line here ..
Shifting the blame to Microsoft is not the right answer. I'm using a Sony product and by virtue of that Sony has the responsibility to make it work. Or don't sell it as such.
I could be wrong here but looking at the error logs that some have posted it does look like Vegas asking the SQL Server to do something wrong (create a duplicate relationship).
Thing I don't get is why so much development effort was poured into the MM when it's not something that's going to generate a single sale even if it did work 100% right. A quick browse of these forums would give a pretty decent list of where to spend the development dollar on things that would create sales. Better still, they should take a tour of any networks edit suites, speak to real world editors, the ones that turn out 60 minutes of content per day. After two years of development effort I still can only think of one new feature (and it's still only sort of working) that'd attract a production editor to Vegas. I can think of quite a few shortcomings that'd make them look elsewhere though.
Bob.
Better still, they should take a tour of any networks edit suites, speak to real world editors, the ones that turn out 60 minutes of content per day. After two years of development effort I still can only think of one new feature (and it's still only sort of working) that'd attract a production editor to Vegas. I can think of quite a few shortcomings that'd make them look elsewhere though.
I could be wrong here but looking at the error logs that some have posted it does look like Vegas asking the SQL Server to do something wrong (create a duplicate relationship).
Are you referring to duplicate keys or one-to-many or something else? It's not obvious to me why the system should croak because of even an illegal request.
Thing I don't get is why so much development effort was poured into the MM when it's not something that's going to generate a single sale...
Look at Adobe's Creative Suite 2. Many are hailing Adobe Bridge as a great asset that really saves time for professionals. How is that so different from MM? Seems like much of the same idea except they didn't bother with a whole gigantic SQL infrastructure.
We need to figure out which component creates the problems. If it is the MS SQL server, this can be quickly replaced with for example a free MySQL Windows server providing the identical WIndows service.
Unless of course MS SQL as used here is really "SQL+", with some unnecessary proprietary SQL feature added to preclude the use of somebody else's server.
But MS would never do such a thing, would they? :O)