Walter, I have used the STABILIZATION in latest VP15 version and seemed fine. I usually set it to about HALF of the "Little" or whatever the least one is. Sorry, I dont remember the terms or numbers and can't check presently.

Walter, I have used the STABILIZATION in latest VP15 version and seemed fine. I usually set it to about HALF of the "Little" or whatever the least one is. Sorry, I dont remember the terms or numbers and can't check presently.

That is exactly, what I mean: VP15, Build 261 it worked fine for me also.
But in VP15, Build 311 I can't see any change or improvement after applying stabilization.
Please, can anybody check this?

When is this update coming to Steam? Hopefully not a month later like the last update.....

We have postponed the update for steam while we work on the fix for the UI slowdown which is plaguing many users. The steam update will come shortly after the next Vegas update.

Is there anyone out there that can confirm that internal CPU>GPU usage and Vegas RAM allocation is causing instability?

Is there anyone out there that can confirm that internal CPU>GPU usage and Vegas RAM allocation is causing instability?

Whilst your aim is admirable and potentially may/could help, I’m still not sure it would, how would one ensure that the actual process by which one would be monitoring wouldn’t ALSO be affecting the stability of the system? Simply put, monitoring could ALSO affect the result-outcome of the monitoring too. This is way above my IT Pay-Grade. I'm not an IT Guru, but I am a fully paid-up Socratian. I think?

Interesting thread.

@Grazie, I'm not attempting to build a quantum computer, but I've noticed positive (!) changes ie. no more crashes, since I disabled CPU internal intel 630 GPU and changed VP internal RAM amounts..I was wondering if that helped other sufferers too which might indicate another root problem per se..[and yes +1me too like to stimulate critical thinking..]

I disabled CPU internal intel 630 GPU and changed VP internal RAM amounts.

How would I do that? From within VP? Or some exoVP and DeepBlue approach? Has this already been discussed in this thread? If so, throw me a link.

Nothing wrong in building a Quantum PC. Give 30 minutes I’ll knock one up!

I did a few tests between editing this morning and I find AVC files play fine and it is truly the XAVC-s files that are not being read by Vegas 15 correctly whether a ram issue or anything else making it lose playback. Boris Studio Titler and XAVC-s file on lowest default viewing settings stutter and lose frames. I hope this gets some love soon. I am having to go back and forth from editing on one daw to vegas for my titles....

@david-ruby In case you haven't already done it: https://www.vegascreativesoftware.info/us/forum/new-avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

yes @Grazie it has, /edit: I just thought for once I have something working and would like to share that information; perhaps I'm barking up the wrong tree, but without someone elses's confirmation we won't know /

however, you should be able to disable your internal CPU graphics in the Bios (If you have a dedicated nVidia card); the other tweaks i've done are in [shift]preferences>internal

/add: and yes, +1 for forum tree, and bug tracking. having a multitude of issues in one thread is not going to help anyone get those issues sorted out quicksmart ;-)

@nick-hope Yes I tried this early on. Nothing changed except the loading of the screens on startup got amazingly fast. Performance no change. Thank you though.

We have postponed the update for steam while we work on the fix for the UI slowdown which is plaguing many users. The steam update will come shortly after the next Vegas update.

THANK YOU!!!

"Analysis Required" The stabilization feature will not begin to analyze the video once the lagging analyze button is selected. Clicking on any selection on any screen causes shuttering and lags. To select anything on any menu take several clicks and several seconds. Still much slower rendering than Davin**.

I observe in Build 311, that media-effect Vegas-stabilizer works much worse than in Build 261.
It also works satisfactorily in VP14.
In Build 311, I can't notice a single zoom-in after stabilize, even with strongest stabilization (1,00).
Can anybody confirm this?

I solved it by the old trick: Copying all events into a new project.
But I have no idea what the cause was.

Many thanks for trying to help!
Walter

In Build 311, I do not see any differences in stabilization from earlier. If an Audio track is inserted above the video track in timeline, the stabilization with media fx can be started, but the result is not stabilized. That was already the case in the past.

Can anybody confirm this?

In Build 311, I do not see any differences in stabilization from earlier. If an Audio track is inserted above the video track in timeline, the stabilization with media fx can be started, but the result is not stabilized. That was already the case in the past.

Can anybody confirm this?

Tested it in VP15 with new Build 321 and VP14 Build 270:
Inserted Audio-track above the video track in timeline - stabilization works OK here.

Walter

Inserted Audio-track above the video track in timeline - stabilization works OK here.

If I put the stabilization after inserting a audio track at the top, the clip is not stabilized even under build 321. If I push the track down the video track and stabilize with slightly changed values, everything works again.

I also put the audio tracks below the video tracks. Once I had an orphaned audio track as the first track. I searched for a very long time, until I found this weird connection.

Inserted Audio-track above the video track in timeline - stabilization works OK here.

If I put the stabilization after inserting a audio track at the top, the clip is not stabilized even under build 321. If I push the track down the video track and stabilize with slightly changed values, everything works again.

This video demonstrates this issue. Using build 321 with GPU acceleration OFF:

@walter-i. Could you please double check in VP15 build 321, following this procedure?

 

@walter-i. Could you please double check in VP15 build 321, following this procedure?

I have double-checked in VP15 build 321and I can confirm it!

But - if you have an other audio-file above - the stabilization works. (that was, what i ment before)

Tested it in VP15 with new Build 321 and VP14 Build 270:
Inserted Audio-track above the video track in timeline - stabilization works OK here.

Walter

Thanks for your action, Nick!

I can no longer make the timecode/time display visible by any means that I can think of.

Wouldn't loading (View>Window Layouts>)Default Layout get you started again? (It should restore the main docked areas to their default places.)

I have tried that one too, but it only brings the time display to the top of the video tracks. There's no way that I have found to "undock" it. I SERIOUSLY need that Time Display to be on the other screen, or otherwise it's useless to even edit with VP15.

There has probably been some source code change in the UI that somehow blocks the possiblity to add the Time Display to a different monitor. I wonder why cannot the Time Display window altogether be under the "View" -> "Window" -menu?! After all, all the Loudness Meters and whatnot can be brought up from there.

So, right now I either use my import from a previous VP version that has the detached Tme Display in a separate window, or I reset the track view as suggested to VP14 defaults which then enables me to do things as I've used to, but then the Time Display cannot be detached to its separate window. Please, this is one of the most crucial features in a NLE. To see the TIME.

I mean, really. What gives? And even if there was an easy solution to this it's A) not documented and B) highly illogical.

So please, dev team, fix this.

Regards,
Former Sony Vegas Pro beta tester, using VP since the times when it was still under Sonic Foundry.

Thank you.

^ P.S. And if you don't think that's a critical component, then perhaps I could sell you a car without a steering wheel or a gearbox and say it's roadworthy.

Just sayin'.

Thanks.