Reinstalled VP17 B353 . . with trepidation . . .

Grazie wrote on 11/24/2019, 12:49 AM

OK, what I'm going to say sounds totally daft, but please hold fast:

Scubbing with Contour Shuttle Pro (CSP) at the highest speed x20 freaks out both B321 and B353 and I get crashes and whiteouts. However I can Grab Cursor with Mouse and go even greater than x20 without issues. GO figure? So I have reproducible separation of issues. I needed to directly observe what is happening. And the only way I know how to do this is via M$ Task Manager. Well, viewing TM I can see TWO distinctly different Observations:

Observation 1: Mouse Scrubbing >x20 Power Usage goes VERY HIGH but within 2 seconds reverts to VERY LOW - Mouse Scrubbing Power Usage goes VERY HIGH but within 2 seconds REVERTS to VERY LOW. This indicates to me that there are VP process that have/are working as they should and close down so not to consume POWER. This is a good thing - yes?

Observation 2: CSP x20 Scrubbing, the Power Usage goes VERY HIGH however REMAINS very high. No matter how long I wait VP17 Power Usage will not revert to LOW. It's stuck VERY HIGH. Which, in turn indicates to me that there are still VP Processes still active and not closing down as they should. Then I come along and add FURTHER demands on VP, either by just clicking on another command or activating a further process, until I get crashes. This is a bad thing - yes?

Now, here's the REAL Kicker: None of the LOW/HIGH Power Usage issues are apprent in VP16. I can FULL Speed my CSP and Power Usage once I stopped scrubbing reverts to VERY LOW.

Conclusions:

A] As I said, I'm using B353 "with trepidation" and I have a Weather Eye on Power Usage in TM as this is the only indicator to me that there aren't any closing-down processes issues apparent.

B] None of this happens in VP16.

Whilst writing this I'm watching VP17 B353 Power Usage:

And from this VP Power Status "Very Low" I repeated my Crash Test Dummy process of NB ColorFast2 and HOS Render As Take and got this:

However, that VERY HIGH POWER USAGE reverted within 2 seconds to VERY LOW. And again, this in turn implies that ANY B353 Processes had been carefully closed down, thusly releasing and allowing further Commands/demands made by me.

I'd like your comments on my findings especially @VEGASDerek .

For the moment B353 is also Holding Fast!

Comments

Grazie wrote on 11/24/2019, 5:17 PM

@Steve_Rhoden - You'll be happy for me that I've been able to remove the Wrench and Place it back in the Tool Box. 😉

Grazie wrote on 11/25/2019, 2:54 AM

As long as I wait until VegasPro wipes its feet smartly and gets back to "Very Low" Power Usage, VP17 B353 is behaving as it should - and some.

@VEGASDerek & @VEGAS_EricD what processes am I waiting for? Is there anything you or I can do to hasten/rush the processes along? Maybe I'm too quick for VP17 now? I know my PC is up to Muster for this.

fr0sty wrote on 11/25/2019, 7:58 AM

Power usage isn't a very good indicator to use. That can be affected by a number of things outside of Vegas, such as windows power settings which can be affected by windows updates, etc. Being that Vegas is an app that is designed for high performance computing, I doubt much consideration is put into how much power it draws at any given time. As for when processes end, I imagine that is a bit more complicated than you're making it out to be. A process may need to remain open for various reasons, even if it isn't receiving any input from you. How things get handled can change from one version to the next that may require more or less processes to achieve them. So, I can't help but feel like you are barking up the wrong tree with your methodology here.

Grazie wrote on 11/25/2019, 9:02 AM

Power usage isn't a very good indicator to use.

@fr0sty - I’m sure it isn’t. But, and until I get a better offer, it’s the one that’s got me going again and flagging just when I can go forward.

As for when processes end, I imagine that is a bit more complicated than you're making it out to be.

@fr0sty - Without a doubt. And yet, it’s the only indicator I can go by to get onto my next creation.

So, I can't help but feel like you are barking up the wrong tree with your methodology here.

@fr0sty - Agreed. And until that time that the real experts, I’m definitely ain’t one of the them, can make head and tail out of this fandanglement it’s whats I need to do to be able to move on.

fred-w wrote on 11/25/2019, 3:10 PM

@Grazie Have you tried Process Lasso, will automatically sets and keeps your Vegas170.exe to "high priority" each time you open Vegas. There is a free version. It has some other features/benefits I've not explored. Seems to work well, I've had it for about three months. https://bitsum.com

Grazie wrote on 11/25/2019, 8:39 PM

@fred-w - Thank you. No I hadn’t. I’m reading what it could do. I don’t understand much of it. If @fr0sty is making an argument that what is happening, is happening externally to VP, what Lassoo would be doing would be to speed up something that is being hobbled by another process. Thinking about this, and using my bad analogy it would be like putting my foot on the Gas pedal to go faster, not realising that I had had the Handbrake applied. I’m guessing @fr0sty would argue - I couldn’t disagree - it’d be better to release the Handbrake! 😏

As I said somewhere up there, somewhere, that I’m using the Power consumption as my Speedometer Indicator. Why? Because I’ve neither the depth of knowledge nor IT wisdom to make things better. I’m wholly dependant on MAGIX to improve matters. What MAGIX is dependant on are Users, me, saying when and where it’s hurting.

fred-w wrote on 11/27/2019, 4:18 AM

Just as you can manually set the priority and affinity of each active "process" in the Task Manager processes page, (Real time, high, above normal, normal, low...I think those are the settings anyway) Process Lasso will simply do that automatically, each time you open Vegas, for example. Just a time saver, somewhat a pain to manually set. And you might tend to forget about that, as well.