I am actually using the Magix HEVC encoder - Intel HEVC doesn't show up for me - did you have to do something to enable it? In VP 15 I used Intel HEVC, just assumed it had been replaced in 16 by the Magix encoder

These are mine HEVC render options

I think it depend on your installed hardware and it's updated drivers.

ok so I have two problems at least instead of one ;( First, I don't have the same Intel HEVC encoder option I had in Vpro 15 and second, when using the Intel Quicksync option of the Magix encoder, it garbles my 2704x1520 video...

I just did a reinstall, reinstalled the intel graphics driver - Intel 8700k on the latest version of windows 10. Same results

Which driverversion?

The 23.20.16.4849 ?

nov 5th driver: 25.20.100.6373. My prior version was 24.20.100.6136

I have i7 7700 with HD Grafics 630 and a Geforce GTX 1050

Here no problem with the same source files with 50p, look

but why you don't use the Magix HEVC with QSV, more than 10 times faster render with equal result.

Did you try that same test using Magix HEVC with qsv?

also, I think you should have rendered to 59.94 fp even if you only have 50p file to try and better replicate the encode.

My failed render is using Magix HEVC with qsv at 59.94 fps

also, I think you should have rendered to 59.94 fp even if you only have 50p file to try and better replicate the encode.

No why should I?
Normally I never use the QSV options in OBS nor Vegas because it is not reliable, it has always many bad frames and sometimes bad total renders.
That I said here many times.
I always use NVENC with very good results.

BTW

Besides that, I try always not to use strange framerates for me because they give me a lot of troubles at export or editing, f.i. also with Prodad stabilizer for stabilizing 29.97 frames from my smartphone. When I set the projectproperties and export to my default 25 or 50p, I never have troubles.

also, I think you should have rendered to 59.94 fp even if you only have 50p file to try and better replicate the encode.

No why should I?

The gentleman has a problem with Magic HEVC (qsv) encoding 2704x1520 59.94 fps, so you post a video of encoding with intel HEVC (not qsv) encoding at 2704x1520 at 50fps. That's not very helpful. The idea is to replicate the encode to see if it's a bug with vegas16 that the user simply can't fix.

Ken, what CPU and GPU do you have?

The gentleman has a problem with Magic HEVC (qsv) encoding 2704x1520 59.94 fps, so you post a video of encoding with intel HEVC (not qsv) encoding at 2704x1520 at 50fps.

That did he first tell us after my video. I was reacting at his opening question where he was speaking about the Intel HEVC (look at the title of the question).
How should I then have known that he was meaning the Magix one?

I know, you went to such effort, even making the video which I'm sure was appreciated, but after the misunderstanding you've lost interest. I like the gpu related problems, but I don't have vp16 to assist.

I did not lost my interest but always try to help other users.

Maybe this helps you and the OP.
This morning when sitting behind my laptop (reading your comment) I switched my GOPro settings to NTSC and made from where I was sitting a testfile in order to help others.
The made file has this MediaInfo

I loaded that file into my VPro 16 build 307 and exported it with Magix AVC with the settings that I show in the video I made with OBS from my screen during that render and exported file-play. Look

So what exactly is the difference between Intel HEVC encoder and Magix HEVC using Intel QSV? I had assumed they would be the same thing. But you are saying you can successfully render Gopro 2.7k/59.94 using Magix/Intel QSV?

So what exactly is the difference between Intel HEVC encoder and Magix HEVC using Intel QSV? I had assumed they would be the same thing.

I see no difference, only the time to export to Intel HEVC takes much longer with me and this says MediaInfo about both types with my average bitrate of 20 Mbs

But you are saying you can successfully render Gopro 2.7k/59.94 using Magix/Intel QSV?

Yess I say that and I proved it in the video above.

Well this is incredibly bizarre. I also have Mavic air 2.7k/59fps - it is 2720x1530 (vs GoPros 2704x1520 ) - and the Mavic air video renders. And unfortunately I have determined I can render GoPro's footage at 2720x1530 just fine - so there is a queer problem with my system at 2704x1520. Suggestions? I'm using original clips from each device so havent introduced anything into the video. I do not have the gopro software loaded - I'm starting to think there is some software conflict but no idea how to track it down.

Perhaps there is some insight to be gained from this site. 

If this is a final render, shouldn't you select pixel dimensions that will fit on to a screen? 2560x1440. Software renderers can be loosey-goosey, but hardware may be more constrained.

Have you tried 2704x1521? 2688x1512?

Well I dont want to introduce artifacting which is why I always keep the final render the same resolution as the source

An admirable goal. But, you let the monitor create the artifacts. Cameras use these pixel dimensions to allow for stabilization and cropping.

Well this is incredibly bizarre. I also have Mavic air 2.7k/59fps - it is 2720x1530 (vs GoPros 2704x1520 ) - and the Mavic air video renders. And unfortunately I have determined I can render GoPro's footage at 2720x1530 just fine - so there is a queer problem with my system at 2704x1520. Suggestions?

Traditionally the width and height should be divisible by 16, and that's true of all standardised resolutions, It's also true of 2704x1520, your problem resolution. If you think about hardware encoding being a simpler more rule based approach than software encoding, then something like a measurement not divisible by 16 could be an issue, but looking at the mavic resolution of 2720x1530, that 1530 height is not divisible by 16,8 or 4 yet it's hardware encoded just fine.

A strange vegas Pro bug?