No matter how many percent the enlarged image is. On a large monitor without zooming there are artifacts and noise in the Prores codecs. In Vegas Pro zoom preview is less detailed. I recommend saving the image from Vegas and opening it in an image viewer or graphics program. There are many programs without ProRes certificates that convert to ProRes codecs and the image is the same as the source. Vegas Pro costs money and is licensed for Prores codecs but does not render the same as the source image. It should not be like that.
No matter how many percent the enlarged image is. On a large monitor without zooming there are artifacts and noise in the Prores codecs. In Vegas Pro zoom preview is less detailed. I recommend saving the image from Vegas and opening it in an image viewer or graphics program. There are many programs without ProRes certificates that convert to ProRes codecs and the image is the same as the source. Vegas Pro costs money and is licensed for Prores codecs but does not render the same as the source image. It should not be like that.
I'm not so sure about that, Apple themselves have looked at the code in VEGAS' ProRes encoder and approved it (it's part of the process of licensing their codecs). I don't think they would be doing that if there was such a quality discrepancy. I'd like to see some signal analysis from apps designed to do quality comparisons, not just someone's eye on a system that may or may not be configured correctly.
As someone with a correctly configured system there appears to be an issue.
Here's a different video where I saved a frame from the original file in Vegas and then did the same with MPC Black for the renders. I then made a TIFF of them all in Photoshop (and downscaled the original UHD frame in Photoshop to the same pixel dimensions so it is more detailed but you get the idea). Download. The ProRes file looks rougher than I'd expect.
At 100% in Vegas on a 27" screen 6 inches in front of me playing back they look different as well (ProRes KS vs Vegas ProRes vs the original).
No matter how many percent the enlarged image is. On a large monitor without zooming there are artifacts and noise in the Prores codecs. In Vegas Pro zoom preview is less detailed. I recommend saving the image from Vegas and opening it in an image viewer or graphics program. There are many programs without ProRes certificates that convert to ProRes codecs and the image is the same as the source. Vegas Pro costs money and is licensed for Prores codecs but does not render the same as the source image. It should not be like that.
I'm not so sure about that, Apple themselves have looked at the code in VEGAS' ProRes encoder and approved it (it's part of the process of licensing their codecs). I don't think they would be doing that if there was such a quality discrepancy. I'd like to see some signal analysis from apps designed to do quality comparisons, not just someone's eye on a system that may or may not be configured correctly.
If apple did the right thing export ProRes in Vegas Pro. Why not certified free or paid converters like Intertake 2, Avdshare Video Converter 7, Acrok Video Converter Ultimate, MacX HD Video Converter, Bigasoft ProRes Converter, Shutter Encoder, etc. have better image quality than Vegas Pro even in Prores LT codec after converting MP4 or photos or graphics. The image is identical to the source. In Vegas Pro, no. I am using Windows 10
I don't see any of those on the Apple Prores Authorized Products list. Where did you see them? Looks to me like most of these (all?) are FFMPEG implementations; which are NOT authorized, although they may be acceptable for most purposes.
As someone with a correctly configured system there appears to be an issue.
Here's a different video where I saved a frame from the original file in Vegas and then did the same with MPC Black for the renders. I then made a TIFF of them all in Photoshop (and downscaled the original UHD frame in Photoshop to the same pixel dimensions so it is more detailed but you get the idea). Download. The ProRes file looks rougher than I'd expect.
At 100% in Vegas on a 27" screen 6 inches in front of me playing back they look different as well (ProRes KS vs Vegas ProRes vs the original).
I see the OP was specifically talking about downsampling to 1080p... that's probably where the problem lies, not in the ProRes code... but rather in the process of downsampling it before it gets encoded... if I had to guess. I'm no programmer, but it doesn't seem like there would be such obvious flaws in the code that apple inspected themselves to make sure there wasn't flaws in it. I guess the way to test that would be to compare 1080p downsamples using other codecs.
I see the OP was specifically talking about downsampling to 1080p... that's probably where the problem lies, not in the ProRes code... but rather in the process of downsampling it before it gets encoded... if I had to guess. I'm no programmer, but it doesn't seem like there would be such obvious flaws in the code that apple inspected themselves to make sure there wasn't flaws in it. I guess the way to test that would be to compare 1080p downsamples using other codecs.
I am in complete agreement. My Difference Composite test above supports fr0sty's impression, but the message seems to have fallen short of its original mark. Vegas uses Bicubic downscaling, which is as good as anything in the destructive process of 4:1 synthesis and decimation. You cannot simultaneously preserve and destroy the same data.
I'd like to see some signal analysis from apps designed to do quality comparisons, not just someone's eye on a system that may or may not be configured correctly.
Yes, that would seem important.
The 422 and HQ ProRes encoders are the same at all resolutions. Scaling occurs in the processing engine, before the encoder. Comparing pixels is one thing; what does the math say about the image?
"I'd like to see some signal analysis from apps designed to do quality comparisons..."
In my spare time, I've been running actual analysis on rendering from XAVC to FHD and UHD with ProResHQ in Vegas 18-20. Since I don't give a rats ass about perceptual analysis, the next and only comment from me on this subject will include data. It's a long process.
Nie widzę żadnego z nich na liście autoryzowanych produktów Apple Prores. Gdzie je widziałeś? Wydaje mi się, że większość z nich (wszystkie?) to implementacje FFMPEG; które NIE są autoryzowane, chociaż mogą być akceptowalne w większości celów.
I wrote that other programs are not certified for ProRes codecs that properly export the image as source. They even have better source image quality in 4K or full hd in ProRes LT codec than ProRes HQ in Vegas Pro. I know these programs use ffmpeg.
I shot ~ 23 seconds of the same visually complex scene with my Sony RX10-IV in FHD and UHD. There was little motion in the video, but much fine detail. No camera setting was changed except for the pixel dimensions. In two separate Vegas Pro 18 projects (one for FHD and one for UHD), I trimmed each file to 20 seconds and rendered to Apple ProRes HQ at FHD and UHD to match the pixel dimensions of the source media. There was no rescaling for any of the renders. File/IO and Preview Acceleration settings were "as found". I did not change them. I used Wayne Waag's RenderQualityMetricsV2 application to measure how faithfully the rendered files matched the original files. These tests were repeated for Vegas Pro 19-550, and Vegas 20-214. Two different machines were used with three different Windows 10 boot images.
This table presents the results:
I used Shutter Encoder to render ProResHQ from the original source files and ran the same comparisons in Vegas 20-214 without trimming the video in order to maintain frame alignment.
This table presents the results:
Observations:
Vegas Pro does slightly better encoding UHD from the sample files than FHD.
The results were surprisingly consistent from Vegas version to Vegas version except for a slight dip in Vegas 20-214 FHD.
Shutter Encoder does a better job encoding to ProResHQ than Vegas
FHD Source Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\FHD.MP4 Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 116 MiB Duration : 23 s 25 ms Overall bit rate mode : Variable Overall bit rate : 42.3 Mb/s Encoded date : UTC 2022-12-16 20:15:50 Tagged date : UTC 2022-12-16 20:15:50 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L4.1 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 23 s 23 ms Bit rate mode : Variable Bit rate : 39.8 Mb/s Maximum bit rate : 60.0 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.640 Stream size : 109 MiB (94%) Encoded date : UTC 2022-12-16 20:15:50 Tagged date : UTC 2022-12-16 20:15:50 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Metas : 3 Codec configuration box : avcC Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 23 s 25 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 4.22 MiB (4%) Encoded date : UTC 2022-12-16 20:15:50 Tagged date : UTC 2022-12-16 20:15:50
UHD Source Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\UHD.MP4 Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 272 MiB Duration : 23 s 525 ms Overall bit rate mode : Variable Overall bit rate : 97.0 Mb/s Encoded date : UTC 2022-12-16 20:14:18 Tagged date : UTC 2022-12-16 20:14:18 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.1 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 23 s 524 ms Bit rate mode : Variable Bit rate : 94.4 Mb/s Maximum bit rate : 100.0 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.380 Stream size : 265 MiB (97%) Encoded date : UTC 2022-12-16 20:14:18 Tagged date : UTC 2022-12-16 20:14:18 Color range : Limited Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Metas : 3 Codec configuration box : avcC Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 23 s 525 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 4.31 MiB (2%) Encoded date : UTC 2022-12-16 20:14:18 Tagged date : UTC 2022-12-16 20:14:18
Vegas 20-214 FHD Rendered File Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\Rendered Output\Vegas 20-214\FHD.mov Format : QuickTime Format/Info : Original Apple specifications File size : 594 MiB Duration : 20 s 20 ms Overall bit rate mode : Constant Overall bit rate : 249 Mb/s Encoded date : UTC 2022-12-17 01:11:44 Tagged date : UTC 2022-12-17 01:11:44 Writing library : Apple QuickTime Video ID : 1 Format : ProRes Format version : Version 0 Format profile : 422 HQ Codec ID : apch Duration : 20 s 20 ms Bit rate mode : Constant Bit rate : 247 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Scan type : Progressive Bits/(Pixel*Frame) : 3.982 Stream size : 591 MiB (99%) Writing library : magx Language : English Encoded date : UTC 2022-12-17 01:11:44 Tagged date : UTC 2022-12-17 01:11:44 Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 20 s 20 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 3.67 MiB (1%) Language : English Encoded date : UTC 2022-12-17 01:11:44 Tagged date : UTC 2022-12-17 01:11:44
Vegas 20-214 UHD Rendered File Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\Rendered Output\Vegas 20-214\UHD.mov Format : QuickTime Format/Info : Original Apple specifications File size : 2.32 GiB Duration : 20 s 20 ms Overall bit rate mode : Constant Overall bit rate : 995 Mb/s Encoded date : UTC 2022-12-17 01:09:14 Tagged date : UTC 2022-12-17 01:09:14 Writing library : Apple QuickTime Video ID : 1 Format : ProRes Format version : Version 0 Format profile : 422 HQ Codec ID : apch Duration : 20 s 20 ms Bit rate mode : Constant Bit rate : 994 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Scan type : Progressive Bits/(Pixel*Frame) : 3.998 Stream size : 2.32 GiB (100%) Writing library : magx Language : English Encoded date : UTC 2022-12-17 01:09:14 Tagged date : UTC 2022-12-17 01:09:14 Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 20 s 20 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 3.67 MiB (0%) Language : English Encoded date : UTC 2022-12-17 01:09:14 Tagged date : UTC 2022-12-17 01:09:14
Shutter Encoder FHD Rendered File Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\Rendered Output\Shutter Encoder\FHD_Apple_ProRes_422_HQ.mov Format : MPEG-4 Format profile : QuickTime Codec ID : qt 0000.02 (qt ) File size : 1 024 MiB Duration : 23 s 25 ms Overall bit rate mode : Variable Overall bit rate : 373 Mb/s Encoded date : UTC 2022-12-17 05:59:26 Tagged date : UTC 2022-12-17 05:59:26 Writing application : Lavf59.30.100 Video ID : 1 Format : ProRes Format version : Version 0 Format profile : 422 HQ Codec ID : apch Duration : 23 s 23 ms Bit rate mode : Variable Bit rate : 371 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Scan type : Progressive Bits/(Pixel*Frame) : 5.977 Stream size : 1 020 MiB (100%) Writing library : Apple Encoded date : UTC 2022-12-17 05:59:26 Tagged date : UTC 2022-12-17 05:59:26 Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Gamma : 1.961 Audio ID : 2 Format : PCM Format settings : Little / Signed Codec ID : sowt Duration : 23 s 25 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 4.22 MiB (0%) Default : Yes Alternate group : 1 Encoded date : UTC 2022-12-17 05:59:26 Tagged date : UTC 2022-12-17 05:59:26 Other ID : 3 Type : Time code Format : QuickTime TC Duration : 23 s 23 ms Frame rate : 29.970 (30000/1001) FPS Time code of first frame : 00:50:44:15 Time code of last frame : 00:51:07:14 Time code, stripped : Yes Language : English Default : No Encoded date : UTC 2022-12-17 05:59:26 Tagged date : UTC 2022-12-17 05:59:26
Shutter Encoder UHD Rendered File Specs
General Complete name : C:\Users\John\Desktop\Render\2022-12-16 ProRes Test\Rendered Output\Shutter Encoder\UHD_Apple_ProRes_422_HQ.mov Format : MPEG-4 Format profile : QuickTime Codec ID : qt 0000.02 (qt ) File size : 3.76 GiB Duration : 23 s 525 ms Overall bit rate mode : Variable Overall bit rate : 1 373 Mb/s Encoded date : UTC 2022-12-17 06:00:07 Tagged date : UTC 2022-12-17 06:00:07 Writing application : Lavf59.30.100 Video ID : 1 Format : ProRes Format version : Version 0 Format profile : 422 HQ Codec ID : apch Duration : 23 s 524 ms Bit rate mode : Variable Bit rate : 1 372 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 29.970 (30000/1001) FPS Color space : YUV Chroma subsampling : 4:2:2 Scan type : Progressive Bits/(Pixel*Frame) : 5.519 Stream size : 3.76 GiB (100%) Writing library : Apple Encoded date : UTC 2022-12-17 06:00:07 Tagged date : UTC 2022-12-17 06:00:07 Color primaries : BT.709 Transfer characteristics : BT.709 Matrix coefficients : BT.709 Gamma : 1.961 Audio ID : 2 Format : PCM Format settings : Little / Signed Codec ID : sowt Duration : 23 s 525 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 4.31 MiB (0%) Default : Yes Alternate group : 1 Encoded date : UTC 2022-12-17 06:00:07 Tagged date : UTC 2022-12-17 06:00:07 Other ID : 3 Type : Time code Format : QuickTime TC Duration : 23 s 524 ms Frame rate : 29.970 (30000/1001) FPS Time code of first frame : 00:50:21:00 Time code of last frame : 00:50:44:15 Time code, stripped : Yes Language : English Default : No Encoded date : UTC 2022-12-17 06:00:07 Tagged date : UTC 2022-12-17 06:00:07
Here is a multi-layer .tif file that others and analyze with their eyes.
Change Log
2022-12-17 0801 Fixed typo in header.
2022-12-17 1500 Added files saved from the Vegas Pro 20-214 Preview for a typical FHD ProResHQ render.
Thanks for the test. This is the image on the left Shutter Encoder Fullhd ProRes 422 and on the right Vegas Pro 20 Fullhd ProRes 422.
Does it make a difference if you render from a 32bit Vegas project?
Czy robisz różnicę, jeśli renderujesz z 32-bitowego projektu Vegas?
I also rendered in a 32 bit project. The image is still as in the screenshot on the right. The more details an image has, the more pixelated with artifacts. In ProRes codecs.
@john_dennis Did you also try comparing quality as op did visually? The 4k xavc clip rendered to ProRes fhd. Also, shutter encoder lists Lavf59.30.100 as the writing app so it's probably ffmpeg prores_ks. Another thought. Maybe the problem is downsampling in the same operation as upscaling the chroma sub-sampling... rendering to 4k 422 ProRes first and downsampling that might give different results.
The real acid test, however, would be comparing renders made by a true-blue Apple system to eliminate their libs as a suspect... if anyone has an m2 running fcp, that would do it.
I compared Prores 422 on Premiere Pro using an animated title video, Prores versions are both officially licensed with Apple. Titles shown are what was transcoded from 4K to 1080P Prores4 22.
First thing of note, Vegas is 275 Mbit/s no matter if you're recording a black screen or a room full of falling confetti, it has no rate control. In example shown Premiere encodes at 22 Mbit/s for black screen, and 367 Mbit/s for peak activity, while Vegas keeps to 275 Mbit/s.
Shutter Encoder has correct VBR rate control for it's non official Prores , it only peaks at 262 Mbit/s with black screen at 16 Mbit/s but doesn't look bad like the Vegas version. So not sure if it's only about a lack of bitrate
Just tried to replicate the problem and everything looks fine to me. I'm using a 25p xavc Sony test clip someone posted here with this mediainfo...
General Complete name : D:\MISC\test ProRes Renders\test_ax33uhd_xavc-s_20200803092856_C0007.mp4 Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 127 MiB Duration : 11 s 40 ms Overall bit rate mode : Variable Overall bit rate : 96.6 Mb/s Encoded date : UTC 2020-08-03 13:28:43 Tagged date : UTC 2020-08-03 13:28:43 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.1 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 11 s 40 ms Bit rate mode : Variable Bit rate : 94.9 Mb/s Maximum bit rate : 100.0 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.458 Stream size : 125 MiB (98%) Encoded date : UTC 2020-08-03 13:28:43 Tagged date : UTC 2020-08-03 13:28:43 Color range : Limited Color primaries : BT.709 Transfer characteristics : xvYCC Matrix coefficients : BT.709 Metas : 3 Codec configuration box : avcC Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 11 s 40 ms Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 2.02 MiB (2%) Encoded date : UTC 2020-08-03 13:28:43 Tagged date : UTC 2020-08-03 13:28:43
Project properties I used are:
Got the best 4k render using ProRes422HQ with a reasonable drop in measured quality rendering HD with the same ProRes422HQ. Could not see artifacts as described in the HD render. Ffmetrics comparisons to the source xavc clip I used yielded these measurements:
Just out of curiosity, how are you taking the snapshots of the VEGAS ProRes clips in your comparison? Are you using the VEGAS snapshot save feature in the preview monitor? If so, that is dependent upon the quality setting you have the preview monitor set to. Also, if saving as a JPEG, that introduces noise... if your preview quality isn't set to Best, you aren't getting the best snapshot either...
So ideally, when making comparison snapshots, you'd want Best (Full) as your preview window quality, and PNG as the format you save it to.
You can easily check in Vegas Pro. Plain detailed image without artifacts. After rendering FullHD ProRes 422 in HQ, the image is pixelated with artifacts. It's the same with movies.
https://drive.google.com/file/d/1NYfI3A9jOzyYQ1MB_jmYb_HeVq8oSLBK/view?usp=share_link
I also did a 4K image rendering test. On the left is the source image in 4K. On the right render to 4K ProRes 422, the same is also with HQ. And there is also pixelosis and artifacts. I am sharing a detailed source image.
https://drive.google.com/file/d/1cXAE4y2tNMf7JHbHh8UM1fPJRUZgIrF-/view?usp=share_link
"You can easily check in Vegas Pro. Plain detailed image without artifacts. After rendering FullHD ProRes 422 in HQ, the image is pixelated with artifacts."
I can't easily see it with a still image rendered in FHD.
I think you need to
You still didn't answer how you were acquiring these images... are you saving snapshots from the VEGAS timeline?
„Możesz łatwo sprawdzić w Vegas Pro. Czysty, uszkodzony obraz bez artefaktów. Po wyrenderowaniu FullHD ProRes 422 w HQ obraz jest pojedynczy na pikselach z artefaktami”.
Nie mogę tego łatwo zobaczyć na nieruchomym obrazie renderowanym w FHD.
Myślę, że muszę
- sprawdź swój przepływ pracy
- Znajdź sobie inny powód do zmartwień
Your photo has too little detail and information in the image, therefore there are no artifacts. I recommend checking the render on my photo. I have provided downloads and tests before.
Nadal nie odpowiedziałeś, w jaki sposób zdobywasz te obrazy… czy zapisujesz migawki z osi czasu VEGAS?
You still didn't answer how you were acquiring these images... are you saving snapshots from the VEGAS timeline?
Imports an XAVC movie into Vegas Pro. It renders to the ProRes 422 codec. Then it imports the ProRes movie into Vegas Pro and saves the images to Tiff or Jpg. And I also showed earlier examples of how Prores codecs compress the image with artifacts.
In an earlier post RogerS also confirmed the problem with ProRes codecs.
This artifact problem occurs with detailed images like landscapes.
"Your photo has too little detail and information in the image, therefore there are no artifacts. I recommend checking the render on my photo."
My photo has exactly the number of pixels in a FHD render.
General Complete name : C:\Users\John\Downloads\Still Image FHD Comparo.png Format : PNG Format/Info : Portable Network Graphic File size : 3.14 MiB Image Format : PNG Format/Info : Portable Network Graphic Compression : Deflate Width : 1 920 pixels Height : 1 080 pixels Color space : RGBA Bit depth : 8 bits Compression mode : Lossless Stream size : 3.14 MiB (100%)
Your problem as stated: "However, when it saves in a lower fullhd resolution in the ProRes 422 or HQ codec, these are large artifacts with compression."
No one on this planet can expect more detail than allowed by the pixel dimensions of the rendered output. I am finished with this thread.