One thing for sure you are feeding Vegas with a high overhead codec HEVC with a high data rate of 120MB/s, a high resolution, 4K at a high frame rate of 60 and a high colour depth of 10 bit. also your 32GB of ram is on the low side for 4K. Make sure your dynamic ram is set to default of 5% too. Would be nice to try your a bit of your media to see how it performs on other high spec systems but I think it will bring most systems down to poor preview performance. HEVC is supposed to be more efficient and not need massive data or frame rates to achieve high quality results, any reason you need such high values?

Similar GoPro footage plays back smoothly on my desktop (see signature) without a proxy.
Mark's hardware is similar though I don't see what the NVIDIA GPU is looking at the signature.

Video
ID                             : 1
Format                         : HEVC
Format/Info                    : High Efficiency Video Coding
Format profile                 : Main 10@L6@Main
Codec ID                       : hvc1
Codec ID/Info                  : High Efficiency Video Coding
Duration                       : 43 s 877 ms
Bit rate                       : 119 Mb/s
Width                          : 3 840 pixels
Height                         : 2 160 pixels
Display aspect ratio           : 16:9
Rotation                       : 180°
Frame rate mode                : Constant
Frame rate                     : 59.940 (60000/1001) FPS
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 10 bits
Bits/(Pixel*Frame)             : 0.240
Stream size                    : 624 MiB (100%)
Title                          : GoPro H.265
Language                       : English
Encoded date                   : 2023-07-07 21:48:41 UTC
Tagged date                    : 2023-07-07 21:48:41 UTC
Color range                    : Full
Color primaries                : BT.709
Transfer characteristics       : BT.709
Matrix coefficients            : BT.709
Codec configuration box        : hvcC

@mhammann57's Previous post is about GoPro & states -

Since my last post I have added an NVidia RTX 3060 graphics card

I wrote this about VP21 & which I still stand by for VP22.

@mhammann57 I use a GoPro11, Vegas Pro Edit 21 is a lot better than previous versions esp VP18, I've tried pretty much every GoPro format inc 5.3 & playback is pretty much flawless (No proxies). In previous versions I had stuttering, layback lag.. you name it, I can't remember exactly but performance was very poor. Like I say VP21 plays them as you would expect 👍 I'm still on Windows 10, I have an AMD CPU with no integrated graphics so as suggested test with the VP21 Trial first but you should see a big difference 👍

@mhammann57

Hi. Like @Gid, I too have one (two) all AMD systems (see signature), and use GoPro's from version 5 Black through 13 Black (except for the Hero 8 due to non-removable lens). When I had the Hero 3 Black Plus, the old GoPro Studio worked great to convert the footage to an .avi format for further editing, done in older versions of Sony Vegas Pro/Movie Studio, and now Magix VEGAS Pro/Movie Studio (R.I.P. Version 17 Platinum 💀). Once the GoPro establishment degraded the GoPro Studio App for the Social Media crowd, I used Handbrake for a time to convert to an easier .x264 format, but now use ShutterEncoder. I just convert all the footage to ProRes LT, at whatever resolution the camera was set at. All my drives are NVME, so speed not an issue, and my smallest drive amount for footage is 2TB (TeraBytes), with most at 4TB (cameras in signature). I always shoot at the High Bit Rate on the GoPro's, highest settings on my Canon's, and only shoot 4K30p (29.970) on my Sony AX-53. All footage is converted to ProRes LT, or for the Canon's at ProRes HQ.

There has been no problems with converted footage since VEGAS Pro got permission by Apple to use the ProRes codec officially, and prior to that with the old "Intermediate" VEGAS had, I would just put the footage on a VEGAS timeline, and then transcode to either the Intermediate format, or the Grass Valley HQX/MagicYUV .avi containers. I have not had an Intel based PC for quite a few years now, and even than, they would have been the HEDT desktop variants, meaning NO Integrated GPU (iGPU), so a CPU friendly editing codec was required.

One is not better than the other, just utilizing what is available and preferred workflow. Some on the forum have great success with the Intel platform, some with AMD. There are a lot combinations of computers in the world, including the software used, OS use and version/updates, which is why some on the planet like the Mac eco-system for its simplistic approach. Again, to each his own.

Hope this helps. Plenty of the forum members have used a variety of Handbrake, Shutter Encoder, Happy Otter Scripts, ffmpeg, etc. for their particular workflow, or lately the "Hardware Acceleration" abitlity for editing. All with great success, though which I am sure, involved a bit of patience and practice to achieve their results.

Good Luck and Happy Editing!

Do you know what your GPU model is? (if not find it in device manager/display adapters)

Can you share a screenshot of preferences/ file io in VEGAS?

GPU = MSI GeForce RTX3060
Screenshot of preferences/file IO:

One thing for sure you are feeding Vegas with a high overhead codec HEVC with a high data rate of 120MB/s, a high resolution, 4K at a high frame rate of 60 and a high colour depth of 10 bit. also your 32GB of ram is on the low side for 4K. Make sure your dynamic ram is set to default of 5% too. Would be nice to try your a bit of your media to see how it performs on other high spec systems but I think it will bring most systems down to poor preview performance. HEVC is supposed to be more efficient and not need massive data or frame rates to achieve high quality results, any reason you need such high values?

Thank you andyrpsmith! Yes, the GoPro 11 HEVC file is demanding and I also was considering upgrading to 64 GB of RAM. Dynamic RAM is at 5%. Do I need values this high? - Not really however, I just poured hundreds of dollars into a new GoPro, Vegas 22 software, and a desktop I thought could handle whatever it was capable of recording. Maybe I'm trying to avoid feeling like i should have stayed with my GoPro Hero 7. No problems with 2.7K using that. Funny thing, the 2.7K video from the GoPro 11 works well with V22 and it is HEVC @ 60FPS. (high bitrate). I too would like to try my media on a system w/similar specs. If you know how to share such large files, let me know. Thank you very much for helping! Mark

@mhammann57 Hi, I can't spk for everyone of course but generally GoPro HEVC files work ok in VP22, as I wrote there were a lot of posts about GoPro files in previous versions of VP but since VP21 (300) those posts have pretty much stopped. & I don't think Dynamic Ram Preview affects general playback,

This is a screenshot from this post

& a link supplied https://help.magix-hub.com/video/vegas/21/en/content/topics/5-preview/using_dynamic_ram_previews.htm?skinName=Dark

For me this pic is GoPro11 10bit HEVC files, 2 different AR's loop playing with my File IO settings just like yours, my RAM normally hovers around 15GB (I have Google/YT playing & some files open) so you can see that 17GB is not a huge rise, in fact just opening VP probably increased it to the 17GB.

I think you're looking in the wrong direction for the problem or ...... 🤷‍♂️

 If you know how to share such large files, let me know. Thank you very much for helping! Mark

@mhammann57 

1. Open Google, top right is a sq of dots - Open Google Drive.
2. Drag that video onto the Google Drive window, let it upload.
3. Right click on the file on screen - Share.
4. A window will pop up, General Access - choose anyone with the link - Copy link.
5. Then on here in a new comment at the top there's a chain button, paste the link on there
6. Click Comment

OK Gid! I'll give it a try. May take me a minute or two. Mark

https://drive.google.com/file/d/1qKkgjUKug1Sk1cRoHjw-QJyEw4VlLnem/view?usp=sharing

Link posted. It is namedGX010026 and is about 1.3GB. Thanks.

@mhammann57 Hi, that files plays like crap in VLC & MPC player & crashed my VP22,

I think that file is broken, I don't want to load it into VP again but it played like this in MPC Player until I clicked Stop in VP & got the white screen,

PS, Video Encode in Taskmanager is the screen capture, when not recording that box is empty

A few additional thoughts....
The video plays fine when using the GoPro 11 camera to view it.
I'm using a SanDisk Extreme V30 512GB microSD card
2.7K videos recorded on GoPro 11 previews just fine
The sample 4K project (city w/blue bldgs, traffic, & V16 features text) previews well except at "Best" settings.
Clips in dropbox (RogerS) inserted into timeline play smoothly.
V18, V21, and V22 are all installed on same Windows 11 PC. (Can they coexist???)
 

Chief24 - Thank you. I did try converting the video to ProRes LT using Shutter Encoder however, I still had the same stuttering/pixelation when playing the video. I am wondering why others with a similar Intel platform seem to be having more success with the GoPro 4K HEVC. Interesting thought about the non-iGPU chip. Your comments are greatly appreciated. Thank you!

@mhammann57 Yes they can coexist, I have VP18, 19, 20 21 & 22 installed. I'm on Windows 10 & have an AMD CPU so sorry someone with a similar PC to yours will have to try it.

@Gid Thanks Gid. Sorry for the crashing. I get the same results. Should I suspect the GoPro camera or SD card? I can try recording a video with a different SD card. Could this also be the reason VP crashes when trying to create a proxy? Thanks, Mark

@Gid  @andyrpsmith @RogerS @Chief24  THANK YOU! The problem is apparently related to the card reader I was using to transfer files from the microSD card to the computer. Must be defective or can't handle the files @4K. Transferring directly from the GoPro via USB produces usable files all the way to 5.3K 60FPS with 10 bit color and a high bitrate. Previews are much better. I am also able to create proxies without a crash. I feel like I owe an apology to all who helped me on this wild goose chase because I shouldn't have blamed Vegas 22 or my Intel desktop. Really appreciate the quick replies and thoughtful advice from all. I remain a Vegas fan! Mark