Pro 10 Bugs?

Kimberly wrote on 4/16/2011, 12:06 AM
Hello All:

I have been struggling with a couple of Pro 10b issues.

Issue No. 1
When I choose File/Exit, I receive the Windows error message "Vegas Pro has stopped working." I am using Pro 10b with Vista. This happens about 50% of the time and I cannot isolate the root cause.

Issue No. 2
When I preview my project to the end of the timeline, Vegas stops responding if I don't wait an appropriate amount of time after the preview concludes before clicking "Save" or whatever. What is an appropriate amount of time? Maybe 30 seconds, maybe 60 seconds. I save frequently anyway, but the only workaround I have found is to save prior to previewing, then let the computer lock-up, then restart. This seems to happen about 75% of the time.

Has anyone else experienced these issues? Any workarounds?

Regards,

Kimberly


Comments

Kimberly wrote on 4/16/2011, 1:18 AM
Hello TLF:

No reason except that 10c came out a couple days before I left the USA for an extended period. I didn't want to risk heading off with a total unknown and little to no access to Internet for support or Forum advice.

I'm planning to switch to 10c when I go home in June. Overall 10b has worked for what I'm doing except for those few annoying things.
amendegw wrote on 4/16/2011, 2:00 AM
I would seriously doubt that 10.0c alone would solve these problems as the only fixes that came with the 10.0b -> 10.0c upgrade were "Notable fixes/changes in Version 10.0c: Fixed problems that could occur when rendering to Sony AVC format." see: Release Notes

That said, the mere fact of reinstalling Vegas (this time the 10.0c version) may fix the problem.

On rare occassions, I've seen similar funkiness (a technical term) with Vegas operation. The workaround I've used is to exit Vegas completely, then reopen my project and it seems to work fine. If that doesn't work, a reboot, then start Vegas with no other programs running has never failed me.

Now, that's not a permanent fix (lucky for me it rarely happens), but let's hope the Vegas re-install fixes your issues.

...Jerry

System Model:     Alienware M18 R1
System:           Windows 11 Pro
Processor:        13th Gen Intel(R) Core(TM) i9-13980HX, 2200 Mhz, 24 Core(s), 32 Logical Processor(s)

Installed Memory: 64.0 GB
Display Adapter:  NVIDIA GeForce RTX 4090 Laptop GPU (16GB), Nvidia Studio Driver 566.14 Nov 2024
Overclock Off

Display:          1920x1200 240 hertz
Storage (8TB Total):
    OS Drive:       NVMe KIOXIA 4096GB
        Data Drive:     NVMe Samsung SSD 990 PRO 4TB
        Data Drive:     Glyph Blackbox Pro 14TB

Vegas Pro 22 Build 239

Cameras:
Canon R5 Mark II
Canon R3
Sony A9

farss wrote on 4/16/2011, 2:23 AM
"Has anyone else experienced these issues?"

Yes.

"Any workarounds?"

Not exactly a workaround. Open Task Manager, check for ErrorReportLauncher process. Also check for Vegas100 still running as a process when you've exited Vegas.

I've seen this happening in previous versions of Vegas as well. It would seem as though Vegas looses the plot then tries to do a graceful crash and the whole thing gets tied up in a knot.

Bob.
Kimberly wrote on 4/16/2011, 2:49 AM
Thanks for the ideas!

I've also noticed that two of my plug-ins, Mayhem and Ultimate S Pro4, don't always show up in my customized toolbar. They are added to my customized toolbar, but they are not always visible in the toolbar across the top of my screen. My fix here is to choose Options/Customize Toolbar, remove them, and then re-add them. Then I exist Vegas and, voila, they appear in the toolbar. Weird, huh?