Earlier, VP17 (demo) was hanging for me in many circumstances, with white screen & option to report to Microsoft. That problem is gone now that I updated the Intel graphics driver for the onboard UHD 630 (I7 8700K). I have no separate video card. Suggestions were made to update graphics drivers for Nvidea; also applies to Intel.

Earlier, VP17 (demo) was hanging for me in many circumstances, ... I updated the Intel graphics driver for the onboard UHD 630 (I7 8700K)...

Same for me @bvideo. Updating i7-7700K & Z270 graphics and chipset drivers seems to have solved lots of random crashes while adding or working in video FX on DV clips in VP17. The update was simple using Intel's Driver & Support Assistant (https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.html). This included updates newer than what ASUS offers on the downloads page for my motherboard (ASUS PRIME Z270-A).

zdogg

And, BTW, how about an option to "save" when the Vegas "has to shut down" warning comes up?

You could enable 'Live Save' which saves your project every time you make an edit, then you can retrieve it if the worst happens.

@Jack S

I think you're not getting my point, it is about just getting back to work quickly when you re-open the program, anytime, whether that was because of a crash or you just quit the program and came back to it later. You have to re-orientate yourself to where you were, and it is not always easy to just "go" to that place, especially with complex timeline.

@paul-marshall The lens database comes with VEGAS 17. You can add your own unknown lens by using the automatic estimation of PTLens (use the estimated parameters in VP17).

@VEGASPascal or Robert Johnson  “You can add your own unknown lens by using the automatic estimation of PTLens (use the estimated parameters in VP17).”

Not sure what this means PTlens? Can you clarify, thanks?

@Former user  Unfortunately the help text is not correctly linked to the plugin. If you search for "Lens Correction" within the VEGAS Help (F1) you will find the corresponding help text and how to determine lens distortion parameter.

@Vegas_Sebastian Thanks for the clarification, works as you say, help file needs fixing. This is a great additional tool to VP. One thing I noticed is that if I add a new preset, say mytestlens then selecting X delete doesn't remove it immediately. You need to toggle back to say default, then you find it’s gone.

I had searched in the manual pdf and assumed that when it wasn’t there it wouldn’t be in VP help either.

Just curious, does the module within VP do CA removal etc or is just a cut down version doing only distortion correction? On the PTlens web site it says … "PTLens is software that corrects lens pincushion/barrel distortion, vignetting, chromatic aberration, and perspective."

zdogg

And, BTW, how about an option to "save" when the Vegas "has to shut down" warning comes up?

You could enable 'Live Save' which saves your project every time you make an edit, then you can retrieve it if the worst happens.

@Jack S

I think you're not getting my point, it is about just getting back to work quickly when you re-open the program, anytime, whether that was because of a crash or you just quit the program and came back to it later. You have to re-orientate yourself to where you were, and it is not always easy to just "go" to that place, especially with complex timeline.

What I usually do is set a marker at the playhead position. Then exit. I know, it's not a cure, but it surely is a band aid. 🙂

That's what I do if, I have a lot of markers already, I just take a note on paper, say no 42.

So I was brave enough to edit a wedding on Vegas 17. I loaded roughly 1,200 clips from sony a6500, Panasonic HCX1 and an old camcorder. Nice to say that nothing crashed during my workflow. I did notice that it does take about 30 seconds extra (compared to V16) to open the project. Seems stable to me.

I'm a bit late to the "first impressions" party, having had to sort out an upgrade to my Boris BCC effects (from v10, which crashed Vegas 17, to the oddly-titled 2019.5 aka V12) but now that Vegas is working I have to say first impressions are excellent.

Timeline playback is *much* smoother than it was before (4K XAVC-S 100Mbps 25p files from a Sony AX53 camcorder) and, crucially, playback on cut transitions is much better. Still not totally smooth, which is frustrating - after all, the simple cut is the mainstay of editing and it really needs to play back totally smoothly so you can preview your edits - but it is much, much improved. Should mention this is on Draft-Full quality.

I like the new colour grading effect, particularly in combination with the Bezier masking thing because previously any effect that was masked using pan/crop meant the mask affected everything (including, I note, the colour grading tool); using the Bezier effect gets round that provided you line up the effects in the right order.

One tiny request, nothing to do with v17 as such: is there any way to make the default choice of filetypes when you press "Open.." to be "Vegas Projects" rather than "Projects and media". I know I can change the dropdown with a simple click, but I'd love the default to be Projects only. I never open media using the File..Open command.

I should also add that I was one of the doom-mongers who briefly flirted with DaVinci Resolve because I was getting so frustrated with Vegas (13, having seen no good reason to upgrade to 14 or 15, though I did eventually get 16 which was certainly better) - but having used Resolve, I came back to Vegas. Resolve is powerful but oh, so clunky. And buggy (that was the Studio 15 version).

My love affair with Vegas Pro continues...

Regards

David

I was the one who started the "is Vegas 16 good enough not to upgrade to 17", well except for the Capture Screen issues (now solved for the time being with ReLive that I've had with my AMD utility but never even knew about it), I am loving 17. Seriously the added things bring real value to program and I hope that we see a more very cool additions in the coming versions. Thank you Magix for working hard for the vegas users.

Everyone, I know there are frustrations with certain pieces of VP17, as with any other software. And I know some of those have been expressed on these pages. But I want to thank you for not only the good comments (I particularly love the honesty of "I was one of the doom-mongers who briefly flirted with..."), but also for your respectful presentation of your frustrations.

I have been spending too much time dealing with the ugliness on our Facebook pages and I begin to lose my ability to be civil with some of those people. What is it about Facebook in general that makes people think that horrible comments are somehow OK? Coming back to these forums where things are communicated in a generally mature and professional manner is a breath of fresh air. You don't know how grateful I am for that!

What is it about Facebook in general that makes people think that horrible comments are somehow OK?

It's the anonymity that allows people to be rude without consequences?

@gary-rebholz - Come here for some R&R, put yah feet up and have have a cuppa joe.

My first impressions needed me to know about I/O Hardware selection of my spanking new NVIDIA card.

^Something tells me if they get that sorted to auto-choose the best GPU to use, there will be a lot of vegas 17 users pleasantly surprised after updating, just like you were. Maybe it can run a brief test the first time you run it?

Not auto-chosen, but maybe a hint?

Not auto-chosen, but maybe a hint?

@vkmast - A most splendid idea. He likes it.

Did I miss something about this? Optimal?

Maybe that the program thinks what's the best?

SMART SPLIT showing Black Flash

I saw Gary's Smart Split tutorial and liked it. But I'm getting a black flash at the Smart Split transition. Any ideas what I'm doing wrong or wrong setting? I get the same black flash whether I use Smart Split or just the Warp Flow transition. Punchline: It IS a proxy 4K clip for an HD project. Any ideas?

Tested a bit today. As my previous "first impressions", still the same horrible interface/icons, still the same missing functions as forever. Still need to use a plugin to have Studio>PC levels on the preview window, still no proper exposure adjustment (Even with the new shinny "Color Grading"). like, WTH???

I liked the event length extension info, and all the new features. I imagine that for most people, that is the goal, they will be pleased.

But to me, all the enhancements are "shadowed" by the weakness. Will keep, again, with the v14. :(

What do you mean by "proper exposure adjustment?" I assume there is some math here that you don't like. Would be good for dev's to understand specifically what you mean.

Personally I think the new Color panel does a great job. End results are the same for me as the "other NLE famous for it's color."

nVidia users, be sure you have latest nVidia Creator drivers installed, if your card supports it; this helped me a lot stabilizing the crashes so far.

Also make sure if you want to use nVidia HW acceleration, your IO is set properly (I noticed this to default to Inter QSV initially which I have disabled):

Dynamic RAM was growing like a cancer during NVenc render, thus crashing. Disable for Happiness ;-)