Comments

Eugenia wrote on 4/21/2011, 2:18 PM
It's a known bug, you must always kill it from the task manager, otherwise it's eating CPU out.
msavard wrote on 4/22/2011, 10:45 AM
This is a known bug?!?! Surely they are planning on releasing a fix soon, like today!?!? This is very disappointing.

I had version 6 of this program and finally upgraded to version 10 and now find out that In some respects I am worse off than before? Version 6 had better performance in previewing (on my machine at least), added clips to the timeline faster and it didn't have bugs like the programming not closing all the way? To top it off, I didn't get the upgrade version, but bought the full version because I had a gift card at Frys, so with the rebate they were offering, I could get it cheaper than the upgrade. But the processing company said they never got my UPC so I didn't even get the rebate!!! I do have a nice hole in my box from where I cut the UPC symbol out of the box before putting it in the envelope though. :)

I have touted this program as being the best among other competitors and even recommended it to a friend, but now I'm not so sure. Dang...

(whew, I feel better now)
Birk Binnard wrote on 4/22/2011, 11:19 AM
Interesting observation for sure. I've been running VMS10 since it's been released and never had that problem. My system is Win7-64 SP1 so maybe it's a 32-bit issue? Can you give the name of the process(es) left active when Vegas ends? And some info about which OS you are running.
msavard wrote on 4/22/2011, 11:31 AM
Movie Studio 10 build 179

Processes left active:

ErrorReportingLauncher.exe
VegasMovieStudioPE100.exe

Interesting thing though. When I just tried it, I opened up VMS 10 with no project, no nothing and then closed it everything went fine. But if I add something to the timeline, whether I save the project or not, and then close it, I get those two processes left open. If VMS opens a previous project when I start it up, it also leaves those processes running if I close it.

System: Windows XP Home 32-bit SP 3
Memory: 3 gb
Processor: Intel Core2-Duo E6750
Eugenia wrote on 4/22/2011, 11:38 AM
It's reproducible 100% on my XP machine too.
Markk655 wrote on 4/22/2011, 12:29 PM
Running Vista 32, processes close out just fine using the recipe from above.
Birk Binnard wrote on 4/22/2011, 12:56 PM
That makes me think it is XP related. Try setting the Properties/Compatability to XP 32-bit mode for VegasMovieStudioPE100.exe. Of course that's just a guess.

I could not find a copy of ErrorReportingLauncher anywhere on my C: drive. But whatever it is you likely don't need it running. Try searching for it and change the name to ErrorReportingLauncher-x or something like that.
GaryDZ wrote on 4/22/2011, 1:12 PM
No open processes with Win 7 Pro 64 bit, Intel i7, 12GB RAM. (I have not installed SP1 yet)
drguitar0001 wrote on 4/22/2011, 1:22 PM
Add this to the list of known issues with VMS 10. Sony is not planning to update the program with any fixes. I have been told (by Eric of Sony Support) that the fixes for VMS 10 will come in the release of VMS 11.
msavard wrote on 4/22/2011, 1:56 PM
ErrorReportingLauncher.exe is in the Vegas Home Studio folder.

Another wrinkle here. It seems to only happen when I add video to the timeline. If I open it up, add a picture, then close down (without saving) then the process stops fine. If I open it up again and add a video to the timeline, then close down (not saving) then the process doesn't stop.
Birk Binnard wrote on 4/22/2011, 5:19 PM
My system does not have a Vegas Home Studio folder.

What I did find, however, is a file called PRSConfig.exe in the same folder as the Vegas program. If you rub this it puts up a dialog box that says it is the Problem Reporting Service Configuration, and it lets you set options for Detection Level and Reporting Level. It looks like if you set Detection Level to Disabled and Reporting Level to Manual you won't get that other piece of software launched automatically.
Eugenia wrote on 6/8/2011, 12:43 PM
Bug still exists on Platinum 11, on Windows XP.
msavard wrote on 6/8/2011, 1:44 PM
Did you ever install the lightworks video editing program and the matrox codecs? Once I uninstalled the matrox codecs, VMS closes all the way. It works faster as well.

(http://lightworksbeta.com/)

Eugenia wrote on 6/8/2011, 1:52 PM
That seems to be it, thanks. Matrox AVI also crashes projects with cineform if installed. This bug didn't happen on Vegas pre-v9 (pro/platinum), so it's still Sony's bug in my opinion.
PalKat wrote on 6/11/2011, 12:40 PM
How do I check the Task Manager (where is it located)? To see if VMS 10 is still running in my CPU?
Thanks
msavard wrote on 6/12/2011, 8:35 PM
press CTRL+ALT+DEL and choose the processes tab. You can sort the list by clicking on the Image Name column. Then look for something like VegasMovieStudio. Click on it and then click the end process button and that will close it.

You can also right click on the task bat at the bottom of the screen and choose task manager and do the same thing.