Vegas Pro 17: first impressions ?

Comments

vkmast wrote on 8/10/2019, 2:52 AM

@AVsupport maybe enough to see which is V17 (until the next version?)

bvideo wrote on 8/10/2019, 9:48 AM

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.

Douglas Clark wrote on 8/13/2019, 6:25 AM

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 wrote on 8/13/2019, 12:24 PM

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.

sebastianS wrote on 8/14/2019, 8:01 AM

@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).

@MagixPascal 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?


@JN_  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.

JN_ wrote on 8/14/2019, 8:34 AM

@sebastianS 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."

Last changed by JN_ on 8/14/2019, 9:10 AM, changed a total of 2 times.

 

Desktop and Laptop basic specs ...

Both run Win 10 ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4 Nov. '18.

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

adis-a3097 wrote on 8/14/2019, 10:29 AM

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. 🙂

JN_ wrote on 8/14/2019, 11:14 AM

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

 

Desktop and Laptop basic specs ...

Both run Win 10 ...

Running latest ver. of Vegas Pro with latest updates.

VP13 B453 also.

Vegaseur and Pluraleyes installed on both ...

Quicktime 7.79.80.95

PC ...

i9 9900K, Intel Graphics 630. Nov 2018.

Mem. 32gb DDR4 Nov. '18.

Graphics card .. Nvidia Rtx 2080 Ti

Nvidia Graphics driver .. latest Studio driver.

Latest Intel Graphics driver

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..16GB DDR4 

Graphics card .. Nvidia GTX 1070, latest Studio driver.

Julius_ wrote on 8/14/2019, 11:54 AM

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.

David Johns wrote on 8/15/2019, 8:56 AM

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

D7K wrote on 8/15/2019, 9:41 AM

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.

gary-rebholz wrote on 8/15/2019, 10:14 AM

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!

OldSmoke wrote on 8/15/2019, 10:32 AM

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?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Grazie wrote on 8/15/2019, 10:54 AM

@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.

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

fr0sty wrote on 8/15/2019, 11:10 AM

^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?

vkmast wrote on 8/15/2019, 11:18 AM

Not auto-chosen, but maybe a hint?

Grazie wrote on 8/15/2019, 12:17 PM

Not auto-chosen, but maybe a hint?

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

Grazie

PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti

PC 10 64-bit 64gb * Intel® Core™i9 - 3.3GHz * 40Gb NVIDIA  GeForce RTX 2070

Cameras: Canon XF300 + PowerShot SX60HS Bridge

RonB_USA wrote on 8/15/2019, 1:35 PM

Did I miss something about this? Optimal?

j-v wrote on 8/15/2019, 1:39 PM

Maybe that the program thinks what's the best?

met vriendelijke groet
Jan

Camera : Pan X900,GoPro Hero7 Hero Black
Desktop :AsRock Z270 Pro4, W10 , i7 7700K 4.2Ghz,16 DDR4 GB RAM, Gef. GTX 1050 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 10,12,13,14,15,16,17 and VMS PL 10,13,14,15,16 are installed
Both Nvidia GPU's have driver version 431.70 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

RonB_USA wrote on 8/15/2019, 3:56 PM

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?

malowz wrote on 8/15/2019, 6:05 PM

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. :(

 

Kinvermark wrote on 8/15/2019, 7:32 PM

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."

 

AVsupport wrote on 8/15/2019, 7:41 PM

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 ;-)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

fr0sty wrote on 8/15/2019, 11:57 PM

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???

Did you not see the exposure controls in the color grading panel?