Still getting instant crashes when trying to open an existing project from the File menu of another open project (no nested anything - just "close this and open that")

I trialed V17 on the last update and quickly decided I wouldn't be able to use it due to crashes/performance issues.

Worked w/ V17 on Update 2 over the weekend and had zero problems. It was snappier than the last version of V16 I generally use. No crashes. Faster rendering.

Honestly I was a little skeptical, but yes I think this update was awesome. Performance/crashing issues are fixed on my side. Can now consider an upgrade.

Thank you!

I spoke too soon, render as crash for complex projects is still there. First time I tried from a fresh open, the render as dialog appeared as it should have. Upon loading the project again, doing some editing, then clicking render as, it crashed.

Hey @fr0sty Try deinstalling all magix software, then reboot en run Ccleaner (cleaner + reg-cleaner), reboot en install the latest version of Vegas. After that, the Render As.. crash disapears. At least, this did it for me!

Cheers!

I will check this out. Thanks for the tip!

@ngjb stable enough I would assume looking at the (rather few) items they fixed in this second patch, and the fact that this second patch took a while to release, but not unplanned I assume. Just saying, if stability was a drama, and blocking, quick fixes would have come sooner I guess.

Okay thanks for the feedback. I assume you are using Version 17 without all the crashes other people are reporting.

To users who are experiencing problems with this build, please make a thread about it, as if we try to help you in here, it's only a matter of time before yours and our posts get buried under other users posting about the update. Separate threads keep everything organized and easy for us to help you.

for when support for Flash Video (FLV)

--- Korean input problem ---
"Titles & Text" is now entered correctly.
However, "(legacy) Text" is still not fixed.
Do you have a plan?
Thank you.

--- Korean input problem ---
However, "(legacy) Text" is still not fixed.

When your problem is that you don't see that, maybe this screenshot helps you.

Here is my report. Update went well, no issues here. Rendered a 19 second intro that included TP7 and some Boris FX (3D Extruded EPS animated 3D logo) and (Particle Emitter 3D), no issues. Thank you Vegas team.

--- Korean input problem ---
However, "(legacy) Text" is still not fixed.

When your problem is that you don't see that, maybe this screenshot helps you.

 

 

I think his issue is with entering text, not finding the titler. I had issues with some Japanese fonts in the past, so maybe a similar issue.

It takes several minutes to open a large project.

What happened to the AMD decoding update that was "so important" to Magix?

My guess: AMD's framework is either really hard to work with, not 100% stable, or both. Other NLE's have same issues.

What happened to the AMD decoding update that was "so important" to Magix?

We are working on it. Understand that work like this does take time to get working right. The amount of time it has taken to get AMD docoding support is on par with the time it took for NVDEC. And the time table is fairly consistent with the time table we had for the encoding side for VP 15.

With this new update, it doesn't help remove the vp15 blacklist. 2-3fps. Simply, the videos from the YI camera cannot be edited again. I don't get it anymore ... Is that a punishment?
https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-1-build-321-general-discussion--117239/?page=7

When editing or importing a large project with vegas 17 the committed ram for me will climb to the max amount than crash. As for Vegas 16 stays at like 10% of what 17 uses.

Here is the same exact project imported with 16 vs 17.

\

When editing or importing a large project with vegas 17 the committed ram for me will climb to the max amount than crash. As for Vegas 16 stays at like 10% of what 17 uses.

Here is the same exact project imported with 16 vs 17.

\

@LongIslanderrr Please compare the numbers in Options->Preferences...->Video->Dynamic RAM for Preview max:

Please, what should I do to make YI camera videos editable? I have several of these cameras and after a new update my records are useless in Vegas For Anger.
Thank you!

When editing or importing a large project with vegas 17 the committed ram for me will climb to the max amount than crash. As for Vegas 16 stays at like 10% of what 17 uses.

Here is the same exact project imported with 16 vs 17.

\

@LongIslanderrr Please compare the numbers in Options->Preferences...->Video->Dynamic RAM for Preview max:

Set to 0 on both.

AFAIK committed RAM is mostly process-private virtual address space, and some of this can be in RAM and some in the pagefile. Sometimes commited RAM is larger then physical RAM of your motherboard (because of Pagefile on HD.....). Used RAM counts and that is quite equal 4.x GB in your screenshots.

Maybe there is an issue by allocated RAM with VP17, users in our forum reported problems with large objects, but it should solved by build 353, else they should test and report again

The bezier motion tracking is far way better then before. But, its hard to place the points on the preview window when Curve is selected in bezier masking. The problem is I cant tell which pixels am I placing at. And I wish there is special dedicated window that zoom in 300+ into the clip so I can do more precision tracking. Something like Pan/Crop window?

I also wish a special assign key like hold shift while placing the points so that the line will be straight instead of being curvy every time I placed a 2nd point & so on. If I did something wrong, I wish it can be undo by just Ctrl + Z. but it reset the whole 1 keyframe instead undoing to the previous adjustment in the bezier masking/preview mask that I do.

Adding text still kinda nuisances as I have to "Guess" the X & Y placement of the text before click OK. if I want to adjust the text position must be done with Pan/Crop not from the media it self. I hope the X & Y thingy is replaced with something else like 50% opacity of the "Placement Text" onto the preview window so user can adjust directly where they want it to be.

I hope the data from the bezier masking is not strictly for PiP/text. I hope it can assign to other FX like lens flares etc.

You can adjust text directly in the preview window... you can move or resize it. There's also another window that lets you adjust coordinates, where 50 is the center. I usually manually center my text and then use those numbers to make sure I'm on actual center.

1000% agree we need a preview zoom function, though, as bezier masking is broken without it. I won't even attempt to use it anymore, I use the old masking system still.