@wwaag If you need the sample source.mxf file that I use to test UHD I can make it available via a dropbox link. I use a smaller sized source.mp4 file for FHD, but that works ok now.

@JN-

Send me the link.

@wwaag Done.

Just for kicks I checked that this doesn't work in HOS RenderPlus:

vceencc64 -i <inAVS>  --codec h264  --lossless -o <outFile>.mp4

It doesn't.

I also tried h264-vce with crf 0 and slow preset. It stutters in Resolve and the quality loss is too much for me.

I've added the results for that, along with the UT Video Codec results, to my previous table.

@NickHope

"Just for kicks I checked that this doesn't work in HOS RenderPlus:"

It does work. However, you first need to set the the Color Matrix to "None" in the Avisynth Settings dialog. This will ensure that the render from Vegas is direct RGB and not converted to yuv prior to beginning the render in Nvenc.

Here's the result.

If added as an option to HOS, this could be automatically set and not require the user to make such changes. That's always a potential pitfall of using direct command lines.

...Nvenc lossless is 99.9% lossless (SSIM of 0.9999)...

Are you referring to AVC NVENC set to Lossless? (Again, I'm using Movie Studio Platinum 16 & 17 so may be missing some features that are obvious to Vegas Pro users.)

@wwaag The disappearing file issue came back to FHD as well as previously UHD.

After a lot of time, including using Nicks crf = 0 testing, I made progress, I was able to create HOS Nvenc lossless files in both FHD and UHD. What I did was I deleted the .ccl template file thats saved and loaded from C:\ProgramData\HappyOtterScripts\Magix Vegas Pro\RenderPlus\Custom CommandLines\ with the command line given by GJeffrey. I then made it up again, same command line as given on previous page. Maybe the original file was corrupted. Maybe the moon was in the wrong phase, who knows.

From what I can see happens is this ...

1) The output file gets rendered out to the named output file, say x.mp4

2) Upon render finish this large file x.mp4 is now renamed to tempOut.mp4

3) tempOut.mp4 is now copied to x.mp4

4) tempOut.mp4 is now deleted

What was happening earlier today was item 1) took place.

I wonder if then x.mp4 got deleted instead of tempOut.mp4, wrong variable names? Or maybe it's just that time of year.

@JN-

Just downloaded and rendered the mxf file without issue using the CommandLine in HOS. It worked, but produced a huge file that V17 did not like for playback when brought back to the timeline.

The above process you describe is exactly what happens for GPU-supported renders since audio is rendered separately, thus requiring a remux of the rendered file. Again, you need to provide me information contained within the R+ folder if such an error occurs again.

@wwaag

If I set Color Matrix to none (I.e. RGB), the rendered file has a luminance shift.

With Nvencc, you can keep a RGB-->YUV colormatrix (YUV420 - PC HD in my case) and it works with the lossless option

"Just for kicks I checked that this doesn't work in HOS RenderPlus:"

It does work. However, you first need to set the the Color Matrix to "None" in the Avisynth Settings dialog. This will ensure that the render from Vegas is direct RGB and not converted to yuv prior to beginning the render in Nvenc.

Here's the result.

If added as an option to HOS, this could be automatically set and not require the user to make such changes. That's always a potential pitfall of using direct command lines.

@wwaag I changed the color matrix to none but unfortunately it's still not working for me.

Just to clarify, in case you overlooked it, my "just-in-case-it-might-work-despite-what-wwaag-said" ccl started with "vceencc64", not "nvencc64".

@wwaag Ok. “The above process you describe is exactly what happens for GPU-supported renders since audio is rendered separately, thus requiring a remux of the rendered file.”

While try to get it working, going in circles really, but got there eventually, I discovered that the file I had successfully rendered earlier in the day (Nvenc lossless using HOS) had no audio. So assuming that I didn’t select to not add audio, it may be pointing to an issue re: remuxing.

Anyway, its working again using GJeffreys suggestion.

@GJeffrey As far as getting this lossless working in Magix only, not with HOS assistance, I suspect that maybe you and Magix got lucky with your choice of source file?

I'm going to work through a good number of the ~20 Mbps and ~35 Mbps files in my FHD table posted on the previous page, used now as source files. I’ll see which do and don’t render out successfully. This testing will be in VP not HOS.

I'll leave it at that then, because without a doubt, within Magix its just at best flaky, I already tested three of the ~20 Mbps files yesterday and only 1 worked, plus of course your sample file, thanks again for the HOS command line at least I now have entries, to be added, for UHD and FHD Nvenc lossless.

@JN-

Please share a sample file which doesn't work for you. I can test on my system.

HOS works flawlessly for me but I only have 2.7K video files up to 30p.

@GJeffrey Will do. It’ll take a little while to go through my samples. At this stage I'm only going to test them in Magix VP 17 452. Maybe you were thinking of HOS? If you mean to test them in VP let me know, thanks.

I just edited my earlier post, it wasn’t clear in that regard.

FWIW these are the results of rendering out the smaller FHD files using VP17 452 Nvenc lossless codec.

I didn't get a single file tested from that table that rendered without issue.

The number below is the files item no. in the table. All files have a single video and audio stream, 25 fps

13 Never finishes, render reaches 100% but I have to use Task Manager to close VP
14 Never finishes, render reaches 100% but I have to use Task Manager to close VP
15 Artifacts at ~ the 3 seconds position
16 Never finishes, render reaches 100% but I have to us Task Manager to close VP
17 No video stream but 2 audio streams
18 zero byte file
19 Artifacts at ~ the 3 seconds position
20 No video stream but 2 audio streams
21 Artifacts at ~ the 3 seconds position
22 Artifacts at ~ the 3 seconds position
23 zero byte file
24 Artifacts at ~ the 3 seconds position
25 zero byte file
26 Artifacts at ~ the 3 seconds position
27 Artifacts at ~ the 3 seconds position

I tested maybe half a dozen random files, (straight out of camera), FHD, from different cameras,, GH3 GH5 etc and had only one problem file, well two, see below

I tested another SOOC GX800 UHD file and got a zero byte file rendering to UHD.
This same file produced really comical and substantial artifacts rendering to FHD.

@NickHope

"Just to clarify, in case you overlooked it, my "just-in-case-it-might-work-despite-what-wwaag-said" ccl started with "vceencc64", not "nvencc64".

Oops!! You're absolutely right. My bad. It does NOT work in using VCE or QSV--only Nvenc.

These 2 tables, FHD and UHD do have the Nvenc lossless examples, item's no. 3, but generated in VP17 via HOS.

I have installed the GV HQX codecs correctly as far as I know. I have enabled the QT codecs in deprecated features. But I am not able to use GV HQX.mov files. VP17 is telling me "unsupported codec". I have read all over the forum and do not see how to get VP17 to recognized the codec in .mov. A lot of the info is over my head. Do I need to manually install them in a specific location? this codec in mov is one of the primary file forms I receive for editing? My VP17 will recognize the HQX.avi just not the HQX.mov? any instruction? Please, Thank You