Vegas Pro 17: first impressions ?

Comments

VEGASPascal wrote on 8/6/2019, 10:51 AM

I think this is just a different naming between the localized versions.

"TimeWarp" was the first (fancy) name in the first beta of VEGAS Pro 17. It is only cached in your plugin manager. You should delete the temporary folder in "C:\Users\<your user name>\AppData\Local\VEGAS Pro\17.0". VP17 will recreate this folder by the next start.

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

I think this is just a different naming between the localized versions.

@Marco. Well, I was told by the Magix chap here that I should CHOOSE Optical Flow to get GPU. There something not correct here?

 

Marco. wrote on 8/6/2019, 10:54 AM

"You should delete the temporary folder in "C:\Users\<your user name>\AppData\Local\VEGAS Pro\17.0". VP17 will recreate this folder by the next start."

Yes, that did it, thanks.

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

@VEGASPascal - Thanks.

Marco. wrote on 8/6/2019, 11:01 AM

"Well, I was told by the Magix chap here that I should CHOOSE Optical Flow to get GPU. "

I see, sorry.

If you applied the Slow Motion FX, start the analyze process. After this is done further adjustments will pop up, one of it is "Method". Its dropdown menu allows to select either "Morph" or "Optical Flow".

Grazie wrote on 8/6/2019, 11:02 AM

@VEGASPascal - I don't have a Temp Folder in that: "C:\Users\<your user name>\AppData\Local\VEGAS Pro\17.0"

Please advise.

Marco. wrote on 8/6/2019, 11:06 AM

That "17.0" actually is the temp folder.

Grazie wrote on 8/6/2019, 11:11 AM

@Marco. I did apply SloMo. I then had to wait for the Analysis to happen. It was v e r y s l o w indeed. I stopped it and came here and asked if I could make it faster and was inormed that Optical Flow uses GPU. The next thing was to find OF. I could not see this in the Tutorials and so I came back here. And now I hear that I need to do the CPU Analysis prior to reach Optical Flow - eh?

TWIXTOR& is a one shot progressive process. If somebody would care to input here?

Grazie wrote on 8/6/2019, 11:14 AM

That "17.0" actually is the temp folder.

@Marco. I wish I had been told that and NOT to look for a TEMP folder IN that Path.

Marco. wrote on 8/6/2019, 11:18 AM

Yes, Slow Motion is a 2-step-process. Like MagixPascal said, it's based on analyzing as the first step (CPU) and then selecting the slomo method where Optical Flow is GPU accelerated.

"I wish I had been told that and NOT to look for a TEMP folder IN that Path."

But you needn't look at it (and delete it). It was me who had to do this because my labeling went wrong.

"TWIXTOR& is a one shot progressive process. If somebody would care to input here?"

I find the VP17 slomo is easier to use while it sometimes gives me even better results than Twixtor does (I only have the Twixtor demo version available).

bryan-quarrie wrote on 8/6/2019, 11:34 AM

I am enjoying this new version of Vegas Pro! :)

It seems a bit more stable than 16 (my computer is based on an AMD Ryzen 7 CPU, has 32GB RAM and has 2 USB 3.0 external drives attached to it where I store my video clips etc.).

Sometimes after playing a large multi-cam project (4 cameras, full-HD), and then pressing SPACE to stop, Version 16 would freeze and then would crash for no apparent reason. I haven't encountered this on 17 yet (fingers crossed!).

 

My favourite features so far are:

 

Slow-mo effect,

Working with greater-than-4K projects,

The new NewBlueFX transitions and effects,

...and more besides! :)

 

 

Because I have a load of third-party plugins that I bought when I used 16, I am hoping that the manufacturer's of those plugins will keep up as I have PluralEyes, Neatvideo, Mercalli 4.0 and Titler Pro.

Apart from that, Well done, Magix!

Former user wrote on 8/6/2019, 12:38 PM

I've asked this elsewhere, I suspect no one knows, maybe someone here. Where is the new Intermediate lossless codec, render template?

fr0sty wrote on 8/6/2019, 12:55 PM

I've heard nothing of a new intermediate, only that the previous magix intermediate was updated to 10 bit and they added support for ProRes 4:4:4:4 (with alpha) on import.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Marco. wrote on 8/6/2019, 1:29 PM

The lossless NVIDIA intermediates are mentioned in the "What's New" section of the VP17 web site.

fr0sty wrote on 8/6/2019, 1:30 PM

Interesting... yet another feature I wasn't expecting. JN, IIRC that codec requires specific hardware from Nvidia, only certain GPUs do it. Are you sure your GPU is an Nvidia card with the required hardware?

Last changed by fr0sty on 8/6/2019, 1:32 PM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Marco. wrote on 8/6/2019, 1:35 PM

Mine? I'm sure it is not. Intel only here. But probably you meant JN_.

Norbert wrote on 8/6/2019, 2:06 PM

It's a joke. Redesigned UI for color correction effects and BS with laggy timeline preview with X AVC L files.

Marco. wrote on 8/6/2019, 2:26 PM

The Color Grading panel is much more than just a redesign. Neither Lift/Gamma/Gain Color Wheels nor Lift/Gamma/Gain Channels equal the Low/Mid/High concept of the legacy Color Corrector or any other legacy CC tool. None of this has been in Vegas Pro before. LUT concept with both input and output LUT as well as LUT export is brand new. Exposure is new. Color Curves are implemented in a different way which affects signal flow, preserves out of range data and offer a better R, G, B and color balance handling. The whole Grading package offers quite different workflows and is to be used in a different way. There's been lots of positive feedback to that new panel and I'm sure this will be a useful toolset.

Of course once an NLE is equiped with any kind of a RGB or YUV level adjustment tool (like curves), any further CC tool could be blamed to be nothing else than a redesign … 😄

Former user wrote on 8/6/2019, 2:28 PM

@Norbert I'm not the type of person to go around knocking heads every time someone finds something wrong, in their view, with VP, the thought police will probably be coming to you shortly, close the door and pull down the blinds.

FWIW I think that despite that initially I couldn’t even get into VP on my PC, and couldn’t initially even render out a project, I really love all of the new VP17 features, and absolutely and especially the colour correction, easy luts import, export etc it’s brilliant.

Marco types faster😂

zdogg wrote on 8/6/2019, 3:22 PM

@Norbert While I wouldn't say that all my expectations are met, (some actually exceeded) this upgrade is nothing to scoff at. And the still new relatationship with Magix has shown a direction that may not be perfect, but certainly shows promise and positive movement. Why the snide remark? I mean, that UI design idea would be my first thought as well, (skeptical) but I certainly wouldn't "pounce" without really knowing that facts, makes one look like a crank. (no thought police, honest broker).

Mohammed_Anis wrote on 8/6/2019, 3:32 PM

Can anyone help me figure out how to do the Audio Synchronization feature? I can't seem to find it.

I realize its optimized for multi-cam editing, but shouldn't the option be visible at least in a greyed out fashion? The documentation doesn't say much about the how-to.

Marco. wrote on 8/6/2019, 3:49 PM

Select all audio events, then use Tools/Multicamera/Synchronize Audio to Align Events. Wait until the analyze process is done.

It sometimes works fine for me and sometimes it completely fails.

fr0sty wrote on 8/6/2019, 3:49 PM

Go to Tools>Multicamera>Sync Audio to Align Events. You may have to select the events you want to align first, so try that if it doesn't work.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Radeon VII

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Mohammed_Anis wrote on 8/6/2019, 4:49 PM

Select all audio events, then use Tools/Multicamera/Synchronize Audio to Align Events. Wait until the analyze process is done.

It sometimes works fine for me and sometimes it completely fails.

Premiere Pro's autosync feature gave me some hard time in certain instances as well.

 

Go to Tools>Multicamera>Sync Audio to Align Events. You may have to select the events you want to align first, so try that if it doesn't work.


Thank you!

One thing to note is that once its done and for whatever reason you want to redo it, you need to delete the events., re-import them to from project panel to timeline and then sync again.

Either way, I'm happy with this feature. Finally. At long last, vegas. At long last!