For me it is very stable and the new features are very welcome. It's good to see the move forward to GPU compatibility but bear in mind this also relies on NVIDIA to provide the decoding option eg at the moment it does not recognise Sony XAVC as H264 for decoding/encoding. There is one thing that would help everyone is for the crash routing to intercept a plugin failure so as to not crash the whole of Vegas ie when the legacy stabilize fails to come back with a message Plugin fail and return the user to a running Vegas rather than a dead one.
Since I’ve selected I/O Hardware for my NVIDIA and AWAY from my CPU the difference is Night ‘n Day. Thumbnails appear abruptly and I can see my GPU working and taking stress off of the CPU. But having said that, that is the major DNA change for Vegas now and I’d suggest for the future too. Knowing that the Engineers have crossed this Rubicon and planned for our futures, this is massive. Oh yeah, Colour Panes too.
For me the new VEGAS Video Stabilization FX is a godsend. I'm a hobbyist and I create a lot of home movies of my vacations with my wife. Unfortunately my hands aren't as steady as they used to be and, although my trusty Sony camcorder has a brilliant optical image stabiliser it can't cope with my incessant camera drift. I like my static shots to be, well, static, not wandering, however little. I have two presets in the preset pane, one is the default which I use on panned shots (if necessary) and the other is the Freeze Motion preset which I use on all my static shots. I don't even have to create sub-clips as I used to do with the old stabiliser. I know that I will lose a little resolution but that's a small price to pay for having my static shots rock solid. I can even adjust the Reference Frame Number slider to minimise the zoom. What's more, I can leave the User View on Basic, as I've found that all the default values work perfect for me.
That, along with all the speed improvements I'm experiencing since I upgraded my NVIDIA graphics card, results in a very pleasant editing experiencing. All I need now is someone to come up with a decent tutorial on Planar Tracking.
I haven't yet been able to take advantage of the GPU decode yet, but I'm sure it'll be one of my fav features when I can (I'm using AMD), I really like the color grading panel, especially for HDR. I only use lightroom now to process my RAW images into PSD's so Vegas can open them... or if I am doing a sunset or sunrise lapse and need to ramp setting adjustments out of the video with LRTimelapse. With the addition of Post and Image, I likely won't even need to do the RAW>PSD conversion in Lightroom anymore once I get it set up. I'm currently working on a 4K HDR all-timelapse film of my city, and it is coming out quite beautifully, far better than the same lapses did when edited in 16.
The expanded HDR support to offering HLG is nice as well, even if we can't preview it natively yet.
Slomo works nice when it works. I'm still trying to perfect the planar motion tracking, it's obvious that it is in an early form, but it does work. I was able to 3D track some text onto the edge of a sidewalk quite well, and it turned with the camera and everything.
Corner pinning/mesh warp is a feature I suggested to the team myself about a year ago. This feature makes my video projection mapping projects much easier, as I can warp video to conform to the surfaces I am projecting onto within Vegas while I'm editing, whereas before I'd have to render it out, load it into another program, then do the warping to see how it turned out. This also saves CPU power by pre-baking the warping into the video image, so my other mapping app (Resolume) doesn't have to.
Most of all, stability. I no longer get random crashes while editing just because I stopped the video or hit play at a point when Vegas wasn't ready for me to yet. No more of that annoying hanging that used to happen in 16 so frequently. The thumbnail bug is probably the worst regularly occurring bug I've seen in Vegas 17 so far, and it's easily worked around by disabling or reducing timeline thumbnail display until they can fix it.
All in all, they did a fantastic job being a small team needing to do 10 versions worth of updates over 4 years in order to catch up with the competition (and as far as HDR goes, exceed). Not to mention, they are having to build this on a foundation of code that is almost 20 years old, which brings with it a ton of challenges that makes adding these new features far more complicated than it would be if they were adding them to code they just wrote themselves recently. Slowly, but surely, Vegas is getting the complete overhaul it has deserved for so long.
For HDR it is still the only NLE that supports the direct preview by using GPUs and HDR monitors. To preview HLG - well that works if you use a Decklink 4K Extreme and a HDR monitor that can be set to HLG manually (what I do with my Atomos Sumo, but I think I could use a Sony HDR TV to since most of them can be set to PQ and/or HLG manually).
I love also the better stabilizer of VP17. Also my only use is hobbyist and I possess also Mercalli 4. Sometimes I use both to see which one isthe best and what Vegas does not so well sometimes Mercalli 4 does it a little bit better and the other way around. It was a great discovery to see my Nvidia is used very good on hardware acceleration and decoding. 3 points for the team to work on 1. The installation choice for hardware acceleration was not good on only laptop. 2. The File/IO setting was wrong on both laptop and desktop. 3. The Screencapture option on laptop gives a black frame ( I have a workaround), not on desktop and there should come more settings possible ( also with other frame- and bitrates). OBS with the right settings does a much better job with smaller filesizes.
I was just wondering if Vegas was better off to Scale HD/60/120fps footage to 4K, or use the tool directly on 4K/30fps to get the slow motion affect.
I'll have to try it out to see what looks better.
hmmm, plus and minus of both...
If you have 60p / 120p footages, decide to make slow motion to 30p, for example, better go with 'standard' Vegas tool (properties playback rate / velocity envelope) first, because Slow Motion OFX can't 'detect' the resampling setting and you will get an unwanted effect.
But if you want to make it 'slower' after being slowed down from 60p to 30p via 'standard' tool, then you will get benefit more from Slow Motion OFX (combined method (properties playback rate / velocity envelope)+Slow Motion OFX).
If you go for resolution, use 4K/30p then slowed it via Slow Motion OFX directly.