Cornico,

I wasn't talking about this particular thing, but the crashing in almost every session, and problems opening files. I need a stable program in my work.

vegardbell.
I don't see any in your 8 comments and 2 post.
The problems you mentioned were solved, what are your crash problems and problems to open files you did not tell us.
Mention them and give us information about your workflow included hard- and software used. I hope they fit the System Requirements needed for Vegas Pro 14.

I have more than enough computer power to run Vegas (or other video editing software). I have used After Effects next to Vegas 11 and 13 for some years because of the motion tracking features in AE, and it ran flamlessly.

These crashes are random, and probably hard to diagnose. They happen to all kinds of files, and they happen at different operations. Anyway, I'm always hitting "send" on the feedback dialog box that pops up on a crash.

I had the same problem (Windows 7 64 bit SP1 Ultimate) with animation as well as frequent crash of the video editor
during the automatic or manual save of the project or writing temporary files, etc.
The installation "Microsoft.NET 4.6.2" at that time did not solve the problem.

I found that the problem appeared (at least for me), after installing updates "KB4012215" from Microsoft.
I restored Windows from a backup created before the big Microsoft update on March 2017.
After that:

I deleted ALL versions of "Microsoft.NET" and replaced them with ONE version, the latest (4.6.2).

I reinstalled the required for me MS Visual Studio C++ versions.

I reinstalled the required for me MSXML versions.

After that i installed Vegas Pro 14 build 244.

Most of the problems were solved for me.

By the way, here's what Microsoft writes about this version:
https://www.microsoft.com/en-us/download/details.aspx?id=53344

"The Microsoft .NET Framework 4.6.2 is a highly compatible, in-place update to the Microsoft .NET Framework 4/4.5/4.5.1/4.5.2/4.6/4.6.1.
The offline package can be used in situations where the web installer cannot be used due to lack of internet connectivity.

Thanks for this message Alexander.
It shows once and for all that only users of Windows 7 are having those problems, most of them since the new build 244.
Users who did not see these problems are all users of Windows 10.

Maybe time for the W7 users to upgrade to the latest Windows version before complaining and accusing this Vegas version?

Maybe time for the W7 users to upgrade to the latest Windows version before complaining and accusing this Vegas version?

Unfortunately I have quite a lot of licensed software that is not compatible with Windows 10. Moreover, Windows 10 does not suit me for several reasons.

Maybe time for the W7 users to upgrade to the latest Windows version before complaining and accusing this Vegas version?

Or, maybe time for MAGIX to confirm that this inter-build of Version VEGAS14 only works with Microsoft Windows 10 and that they have QA-ed this inter-build 244 will only work with MS10. An official comment on this will staunch any further heartache and stop us from chasing our IT tails.

The feedback from MAGIX, thus far, is that "bugs" in this build are being addressed. Up to now nothing from MAGIX has been stated that this inter-build of version VEGAS14 is requiring Microsoft Windows 10.

I also have Win 10 (been using it since last summer), and the thing that worked was installing .NET version 4.6.2.

Thanks for this message Alexander.
It shows once and for all that only users of Windows 7 are having those problems, most of them since the new build 244.
Users who did not see these problems are all users of Windows 10.

...Short memory, yeah? Forgotten are the "marvels" brought by Win-10 updates.

Maybe time for the W7 users to upgrade to the latest Windows version before complaining and accusing this Vegas version?

Maybe it's time for you to refrain from broadcasting your manners and competience...

We're getting close to an install saying it needs the version of NET to operate correctly. Oh, BTW, I can confirm I have Net 4.6.2 installed and has been since Nov last year. And yes, I'm on W7.

new update.

Who wants to try?

...Short memory, yeah?

Maybe, maybe not.😇
I'm sure my short memory tells me I never had any problem with W10 because from the beginning I switched off Windows Update and switched it on only when I knew it was save to do so.😑

new update.

Who wants to try?

I did it ---- unfortunately the Vp14 UHDp30 Intel HEVC output is still stuttering as with other builds. 😰

"Old" customized MC AVC rendertemplates render fine again with this new build

Selecting FHD 10Bit in the Intel HEVC template on an i7-6700k system still returns an error when starting to render.

Peter, no problem on laptop from signature

Peter, no problem on laptop from signature

Resolution is still not correct. should be 1080 not 1088...

Do you have quicksync enable?

Do you have quicksync enable?

I have no idea where to enable that in a HEVC template.
Can you point me out?

Do you have quicksync enable?

I have no idea where to enable that in a HEVC template.
Can you point me out?

 

You can not enable Intel QuickSync within the Vp14 render template. First of all, you need to have a Skylake or Kaby Lake CPU with the GPUs that support the Intel Encoder. And the internal GPU mut be enabled within the BIOS to allow for QSV.

Selecting FHD 10Bit in the Intel HEVC template on an i7-6700k system still returns an error when starting to render.

Can you show the screenshot of encoder settings?

Vegas is known to be picky on bitrates.
I have just rendered a test FHD 10bit Intel HEVC MOV with Variable bit rate where the Maximum was 24mbps and Average was 12mbps.

This all resulted in 1920x1088 file with 4 extra black lines added (not being masked on decoding) either at the top and the bottom.

 

Vegas is known to be picky on bitrates.
I have just rendered a test FHD 10bit Intel HEVC MOV with Variable bit rate where the Maximum was 24mbps and Average was 12mbps.

On what type of system/CPU ?

It's not a matter of bitrates in this case. Same error happens on my system, tested with a big range of bitrates and it only happens when trying to render to HEVC 10 bit (and in this case it always happens).
I didn't test with build 252 yet, but I doubt this issue is solved from 244 to 252.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 *2
OS on SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF