Here it is:

Medianfo for output files:
General
Complete name                            : G:\Render\Coppelia2021_2pm\Copellia2021Sat2pmDraft2.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 2.74 GiB
Duration                                 : 1 h 31 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 4 301 kb/s
Writing application                      : Voukoder (VEGAS)

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 1 h 31 min
Bit rate                                 : 4 165 kb/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.067
Stream size                              : 2.66 GiB (97%)
Writing library                          : x264 core 157 r2981 b5bc5d6
Encoding settings                        : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=34 / lookahead_threads=5 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 1 h 31 min
Duration_LastFrame                       : -20 ms
Bit rate mode                            : Variable
Bit rate                                 : 128 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 83.1 MiB (3%)
Default                                  : Yes
Alternate group                          : 1

M

In the Voukoder x264 Video Options, try crf=20 instead of 23. This will cause a bigger file.

If that doesn't clear it up completely, set vbv-maxrate and vbv-bufsize as shown. This will raise your effective minimum bitrate without hurting peak motion.

Aha! I will give it a try. Thank you.

@dxdy I've experienced that exact issue with mxf footage from my xf305 with Magix render templates. I don't think it's a Voukoder issue. In my case it only occurred on the camera clip splits on the timeline and only in a random manner more than a half hour into continuous shoots with splits every 5 minutes. My theory is that it's a Vegas buffer management issue. In any event, my cure has been to glue all the camera splits into one long clip using the ffmpeg concat filter. I think HOS has a similar facility which you might prefer if you don't have ffmpeg installed somewhere on your search path.

I thought I posted the ffmpeg solution once before but apparently not. It's a 2-step process. First I drop a copy of this windows batch file I call "mfx_list.cmd" into the folder holding the MFX camera clips to join together and double-click on it to run it:

(for %%i in (*.mxf) do @echo file '%%i') | sort > mxf_list.txt

It creates a file named "my_list.txt" that you can edit with notepad in case there are clips in the folder you don't want glued into the output file.

Then I drop a copy of this windows batch file into the same folder and run it. I call it "mxf_cat.cmd":

ffmpeg -f concat -i mxf_list.txt -c:v copy -c:a copy -map 0:v:0 -map 0:a:0 -map 0:a:1 mxf_cat.mxf

It reads the text-file list and emits a glued clip named "mxf_cat.mxf". Note that this script is specific to my xf305's mxf format that contains 2 mono audio streams for L and R. I see from your mediainfo yours is the same.

Howard-Vigorita: Thank you. You have described my conditions exactly. To support your thoughts about a Vegas buffer, if I go to the camera clip split that gave me a problem, set a region around it of several minutes, render it with same settings, the problem does not occur. This pixelation is a recent development. I have been using the XF300 for years, merely copying the MXF files off the card and onto an internal SSD, and then dragging them into Vegas. I have enough fussy users that they would have complained loudly and not a single one has.

Fwiw, I first started seeing the problem in VP17, but only for continuous shoots over around a half hour. Got into the practice for a while of playing through the boundaries where clips abut and dropping markers where they show pixelation... which actually seem to be pixels from a partial frame elsewhere in the project which is why I think it's a buffer thing. Playing through the markers before doing a render makes it go away. Joining the clips has worked better for me with the added benefit that Vegas behaves better in multicam edit without clip splits. So does the v18 grading panel which is clip-oriented.

Btw, I just studied your mediainfo more closely and notice that your Voukoder render converts to 420 color... makes a smaller file but throws away the actual color depth captured by your camera. It's triple ccd sensor array which captures full rgb, albeit down-converting it to 422, is what makes that camera so special. Cameras these days tend to only have a single 420 sensor and get phony-422 by up-converting.

Howard-Vigorita, thank you again. Do you know if there is a way to keep it from downgrading from 422 to 420? The tiny files are great for drafts, but for the final I would like the best I can get.

If it's the final render I think 420 is the most appropriate for delivery. If you want a pristine master, render to ProRes, too.

@dxdy To keep your 422 in the render with AVC using Voukoder you need to choose the x264 (ffmpeg lib) encoder. It's in the Pixel Format drop-down at the top. The x265 lib also has it. As mentioned above, all the ProRes formats are 422 too. If you go through all the pain of editing 422 (it's bigger, can't be decoded in hardware, and its slower to render, even to 420 in hardware)... you might as well deliver the fruits of your labor.