Is this a known bug?

Vliegvisser wrote on 4/27/2018, 5:32 PM

When I close my Vegas 15 latest build project and try in the same Windows instance to open Vegas pro 15 again it hangs on this .

I can wait for hours but Vegas will not start, unless I close in the taskmanager this Vegas remain in the backgroundprocesses of the taskmanager that was added there at the moment I closed the former instance or saved & close.

Is this a known bug and knows any one how to overcome this extra step to open Vegas again?

I'm working on laptop Windows 10 latest builds and enough good memory with more versions of Vegas Pro and Vegas Movie Studio, but nowhere else I see this behaviour.

Comments

max8 wrote on 4/27/2018, 6:00 PM

This happened to me also once.

Rainer wrote on 4/27/2018, 6:27 PM

Yes, well known issue that's been around forever. Vegas takes a while to clear out of memory, though usually a minute rather than hours. Long-time impatient users know to kill the process tree in task manager before re-loading Vegas. I now regard it as more of an annoyance rather than a bug, since you don't lose any work.

Vliegvisser wrote on 4/28/2018, 12:07 AM

Yes, well known issue that's been around forever.

To me it is a bug because I see this since the last update of Vegas Pro 15 to build 321.
When I do the same with Pro 13, 14 or VMS 14, 15 it is not happening.

It also happens only on my laptop not on desktop.
Laptop is Asus ROG Strix GL503VD-FY208T
Do I have to look for this problem after the type of memory maybe?

Vliegvisser wrote on 4/28/2018, 4:03 AM

In the meantime I did a lot of testing and figured out that my problem shows up at the builds 261,311 and 321, but not at the initial Pro 15 build 216.

So I'm back at build 216 and the problems I had are gone.

Vliegvisser wrote on 5/3/2018, 10:22 AM

Because I was not satisfied to go back to that early build, I tried to figure out what was causing this problem on my laptop.
I figured out after a lot of tests and trials that the cause seems to be a combination of

- using videofiles from my Samsung smartphone and

- starting on the laptop Vegas Pro with the integrated Intel 630

This wil happen in that case

To overcome this I found two ways

1. Starting Vegas with the Nvidia card Geforce 1050 or

2. Going back to Vegas Pro build 216

I now use option 1, but there I got the problem that Fx's are not showing the result realtime but only after closing the FX window.
For "normal" FX use I had to reïnstall the older Geforce driver 382.53-notebook-win10-64bit-international-whql. Hoping not to discover negative behaviour of the older driver on my workflow, which I did not see until now.

Vliegvisser wrote on 5/4/2018, 11:09 AM

Somewhere I saw that sometimes the latest Windows update (1803) not good was installed.
So, curious as I am, today a I tried again to update Windows.
My two problems
- FX not realtime showing the changes in preview with Nvidia as start GPU and the newer drivers
- this "kind of memory" problem by using my smartphonefiles
are gone.

What stays?
Rendering with also my laptop to Intel HEVC goes very slow and I have to change there the GPU to start the program with the Intell to get very fast rendering to UHD 50p HEVC ( activity Intel GPU 75-95% in the taskmanager)