Had a look at a Nikon sample. doesn't play smoothly for me on VP21b315, plays smoothly on VP22b93. I only have the 1 sample but simulate multiple clips by cutting and removing slices. I have poorer playback in general than you, but don't get the frozen clip thing. Probably depends on hardware.

VP21b315 playback

If you don't have a nikon, well that's why you should have offered that info in the first post🐙

One is likely being cached in VRAM before playback but the other not? Really for 8K HEVC I'd make proxy files.

Your source is too heavy for most computer systems, the details of which you have not provided.

Render proxy files, as has already been suggested.

For further assistance, start by posting the full details outlined here:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

"Your source is too heavy for most computer systems,"

Then why:

"first plays fine as shown second stutters. If I save and load it back up and click on the second file on the timeline *IT* runs fine"

Maybe one use nvdec, while other not? Upgrade to V22.
Or share the two files, so we can check on our system.

Hey folks,

Thanks for replying.

Here are the files if you want to try them ...

https://drive.google.com/file/d/1JCkfQsxJqC7KRSUF_ufz2LjSGTOLDTE0/view?usp=sharing

and

https://drive.google.com/file/d/1CZD1HRCMrXHB_gL8z2fEyr9fAN15TYtR/view?usp=sharing

PS: Its MOV files from the Nikon Z9 at 8K H265 10bit

@UltraVista ...

Here's the PC spec, hardware, OS and file info ...

OS Name    Microsoft Windows 10 Home
Version    10.0.19045 Build 19045
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    RYZEN
System Manufacturer    Micro-Star International Co., Ltd.
System Model    MS-7C37
System Type    x64-based PC
System SKU    To be filled by O.E.M.
Processor    AMD Ryzen 9 3950X 16-Core Processor, 3500 Mhz, 16 Core(s), 32 Logical Processor(s)
BIOS Version/Date    American Megatrends Inc. 1.40, 10/09/2019
SMBIOS Version    2.8
Embedded Controller Version    255.255
BIOS Mode    UEFI
BaseBoard Manufacturer    Micro-Star International Co., Ltd.
BaseBoard Product    MPG X570 GAMING EDGE WIFI (MS-7C37)
BaseBoard Version    1.0
Platform Role    Desktop
Secure Boot State    Off
PCR7 Configuration    Binding Not Possible
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume2
Locale    United Kingdom
Hardware Abstraction Layer    Version = "10.0.19041.3636"
Username    RYZEN\Rikki
Time Zone    GMT Summer Time
Installed Physical Memory (RAM)    32.0 GB
Total Physical Memory    31.9 GB
Available Physical Memory    23.1 GB
Total Virtual Memory    36.7 GB
Available Virtual Memory    25.3 GB
Page File Space    4.75 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualisation-based security    Not enabled
Device Encryption Support    Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualisation Enabled in Firmware    No
Hyper-V - Data Execution Protection    Yes

Name    NVIDIA GeForce RTX 2070 SUPER
PNP Device ID    PCI\VEN_10DE&DEV_1E84&SUBSYS_870A1043&REV_A1\4&2283F625&0&0019
Adapter Type    NVIDIA GeForce RTX 2070 SUPER, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 2070 SUPER
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_defcd1ccab02e3ec\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_defcd1ccab02e3ec\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_defcd1ccab02e3ec\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_defcd1ccab02e3ec\nvldumdx.dll
Driver Version    31.0.15.5222
INF File    oem80.inf (Section001 section)
Colour Planes    Not Available
Colour Table Entries    4294967296
Resolution    3840 x 2160 x 143 hertz
Bits/Pixel    32
Memory Address    0xF6000000-0xF6FFFFFF
Memory Address    0xE0000000-0xEFFFFFFF
Memory Address    0xF0000000-0xF1FFFFFF
I/O Port    0x0000F000-0x0000F07F
IRQ Channel    IRQ 54
I/O Port    0x000003B0-0x000003BB
I/O Port    0x000003C0-0x000003DF
Memory Address    0xA0000-0xBFFFF
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPSI.INF_AMD64_DEFCD1CCAB02E3EC\NVLDDMKM.SYS (31.0.15.5222, 57.30 MB (60,078,616 bytes), 01/05/2024 19:35)
 

File 1:

General
Complete name                            : F:\New Age Fitness\2024-07-08 - NAF - Wishaw - IG Videos\Use these too\2\DSC_1516.MOV
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   2016.09 (qt  /niko)
File size                                : 2.15 GiB
Duration                                 : 46 s 560 ms
Overall bit rate                         : 397 Mb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-07-08 14:43:36 UTC
Tagged date                              : 2024-07-08 14:43:36 UTC

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L6.1@High
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 46 s 560 ms
Bit rate                                 : 394 Mb/s
Width                                    : 7 680 pixels
Height                                   : 4 320 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                                : 10 bits
Bits/(Pixel*Frame)                       : 0.475
Stream size                              : 2.14 GiB (99%)
Language                                 : English
Encoded date                             : 2024-07-08 14:43:36 UTC
Tagged date                              : 2024-07-08 14:43:36 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : lpcm
Duration                                 : 46 s 560 ms
Bit rate mode                            : Constant
Bit rate                                 : 2 304 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Bit depth                                : 24 bits
Stream size                              : 12.8 MiB (0%)
Language                                 : English
Encoded date                             : 2024-07-08 14:43:36 UTC
Tagged date                              : 2024-07-08 14:43:36 UTC

File 2:

General
Complete name                            : F:\New Age Fitness\2024-07-08 - NAF - Wishaw - IG Videos\Use these too\2\DSC_1518.MOV
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   2016.09 (qt  /niko)
File size                                : 2.54 GiB
Duration                                 : 54 s 840 ms
Overall bit rate                         : 398 Mb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-07-08 15:02:38 UTC
Tagged date                              : 2024-07-08 15:02:38 UTC

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L6.1@High
Codec ID                                 : hvc1
Codec ID/Info                            : High Efficiency Video Coding
Duration                                 : 54 s 840 ms
Bit rate                                 : 395 Mb/s
Width                                    : 7 680 pixels
Height                                   : 4 320 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                                : 10 bits
Bits/(Pixel*Frame)                       : 0.477
Stream size                              : 2.52 GiB (99%)
Language                                 : English
Encoded date                             : 2024-07-08 15:02:38 UTC
Tagged date                              : 2024-07-08 15:02:38 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : hvcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : lpcm
Duration                                 : 54 s 840 ms
Bit rate mode                            : Constant
Bit rate                                 : 2 304 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Bit depth                                : 24 bits
Stream size                              : 15.1 MiB (0%)
Language                                 : English
Encoded date                             : 2024-07-08 15:02:38 UTC
Tagged date                              : 2024-07-08 15:02:38 UTC



@RogerS : Id agree normally but since it plays one of the files perfectly I dont see the point of transcoding. If it loads one then another should work fine. And they both do, depending which one I click on first after loading Vegas the first will work fine and the next one will be terrible.

@mark-y : As noted above, if it runs one smoothly then why go to the transcoding trouble?

@relaxvideo : Exactly my thoughts and I havent upgraded to V22 as Ive only started feeling safe using V21 without it blowing up all the time. its as if the makers beta test the current version until its good after a year then launch the next one where we become the free beta testers for another year ... while paying hundreds in upgrade fees.



 

Thanks for the files.

Sadly, i'm not the right person to test it, because both video plays at 0.1 fps by me :)

My beloved mediaplayer MPC-HC does play these fine with nvdec (1660 Ti), no problem.

But in latest Vegas 22 nvdec is not used. Don't know the reason.

Check your nvdec usage while playing. (with afterburner or gpu-z)

And don't know if only cpu decoding is used, why it's only 20%??

Id agree normally but since it plays one of the files perfectly I dont see the point of transcoding. If it loads one then another should work fine. And they both do, depending which one I click on first after loading Vegas the first will work fine and the next one will be terrible.

To create a proxy file, right-click in project media and create one. It does create a temporary XDCAM file for smooth preview and then swaps in the original upon render.

The point is to have good preview performance which you don't have as you came here to complain about it.

As to why I can guess that there is some kind of a VRAM loading issue with the new decoder. Personally I stayed with VP 21.208 as the final and most stable release of that branch of VEGAS. 21.300 was the start of a new higher-performance branch that I found too many issues with to work with in 21 and while 22.93 is a big step forward with squashing bugs will likely stay with 21.208 for another patch or two to 22.

The advantage of the subscription is as VEGAS is in active development. It's all rolling and the annual upgrade marketing cycles have little to do with the development cycle.

@djrikki2, no idea unless you provide details of your HW.

On my machine both clips run smoothly at any point with any Interrupt, in V21 and V22.
->My Signature

... while paying hundreds in upgrade fees.
 

Invest million banknotes for your fitness, and cherish hundreds bucks for an upgrade?

The HW listed above?

If the upgrades worked that would be great.

Installed V22 latest from the site...

Same thing happens :S

AMD Ryzen 9 3950X 16-Core Processor, 3500 Mhz, 16 Core(s), 32 Logical Processor(s)

RTX 2070 SUPER

RAM 32.0 GB

Windows 10 Home

This is your PC, can you click your icon at the top of this page - My Profile & fill in your Signature with the full name of your CPU, GPU & amount of RAM, also inc the Vegas version, this will then show at the bottom of your comments,

@djrikki2 Hi, I have a not too dissimilar PC to yours, an AMD CPU with no integrated graphics + an RTX GPU albeit mine is a bit more powerful so I can only show how it goes for me,

Geforce screen capture adds a bit of pressure on the GPU but playback in VP21 (315) is very good (better without Geforce screen capture)

Without Geforce capture

This is with Geforce screen capture but like I say play is still good, no proxies built.

Same goes for VP22, playback is good in both without Geforce screen capture so it's hard to tell if one is better than the other.

Installed V22 latest from the site...

 

Same thing happens :S

 

If you're primary interested in the 9:16 version for social media, don't swap around the resolutions, use 2430 X 4320 see if that plays better. It plays fine for me, as @Yelandkeil asked what is your hardware, are they playing from an SSD?

The edit points don't look smooth, but I think it's Vsync in viewer, the actual encode looks fine. I also found another problem, Vegas can't encode 4320x7680 natively but can via voukoder encoder plugin.

playback VP21b315

Pop two files onto Vegas 21 / 315 - both 8K HEVC files, on to the timeline - first plays fine as shown second stutters.

If I save and load it back up and click on the second file on the timeline *IT* runs fine but the *OTHER* file stutters.

My untested guess is that the first file you add uses mostly RAM space, and when you load the second, it spills over to your scratch drive, a name for Virtual Memory.

my two cents: it's clear that fine details do not always benefit from how many pixels a picture is taken, when I see these underexposed recordings.

I also agree with @mark-y findings. (edit: which he just deleted)...

I wouldn't obsess over the observation that one file plays back relatively smoothly and another stutters. I suspect that is an anecdotal, rather than a significant observation. Getting any smooth timeline playback with such megalithic source is what we call a miracle in my little corner of the universe.

• HEVC is harder to decode than walking on a bed of nails. Zen won't help much here.
• Expecting smooth realtime decoding of 400Mbps video, even on the fastest of this generation of GPUs and system environments rides at the peak of optimism.

I see your practical options at this time to be fairly limited:

• Try a different editing software.
• Re-encode your files to larger but faster AVC CBR in Shutter Encoder. This is my preferred first option.
• Use a lightweight proxy during editing and live with the lower preview resolution, in deference to preview performance.
• Lower your expectations of preview performance in Vegas.
• Wait for the next generation of iGPUs, which will be heavily optimized for hardware-accelerated video performance and AI processing.
• Change your shooting format to something that is closer to deliverable on mass media.
• Most home computers and streaming connections won't do much better than 4K 8 bit, so the overkill ratio of your acquisition format vs. practical deliverability is somewhere in the neighborhood of 512:1. All wasted resources that you probably wouldn't notice unless your video is to be displayed on a modest football stadium screen.

Main takeaway: It's still just teevee.

my two cents: it's clear that fine details do not always benefit from how many pixels a picture is taken, when I see these underexposed recordings.

I also agree with @mark-y findings.

Point well taken. Thank you, @3POINT

I was rearranging the order of my posts, which were only lightly edited.

In the real world of commercial video delivery for home consumption, shooting 100Mbs AVC CBR would seem to provide more than enough quality headroom, aka vanity space, for delivery. I can get through that well enough in Vegas, even on my modest i5 / Intel graphics system.

@djrikki2

I usually refrain from offering advice to videographers, since I retired about the time HDR came out, but I'll share a couple of thoughts:

• Invest in lighting, rather than more camera equipment.
• Shoot XAVC-S format for editability and deliverability without having the need for intervention by separate intermediate or proxy transcoding.

There, I've stepped outside my comfort zone with advice, so I'll leave my piece of the discussion there.

@djrikki2

Sorry to jump back in; you appear to be using Nvidia Game Ready Drivers 31.0.15.5222, rather than the Nvidia Studio Drivers strongly recommended for video editing.

In Vegas, right click on the help menu, and let Vegas help you find the correct Nvidia Studio Driver  version for your RTX 2070 Graphics system.

Welcome to the discussions, and Best of Luck!

Here are the files if you want to try them ...

https://drive.google.com/file/d/1JCkfQsxJqC7KRSUF_ufz2LjSGTOLDTE0/view?usp=sharing

and

https://drive.google.com/file/d/1CZD1HRCMrXHB_gL8z2fEyr9fAN15TYtR/view?usp=sharing

PS: Its MOV files from the Nikon Z9 at 8K H265 10bit

I only tried the 2nd one but no problem playing it on my laptop with vp22 without a proxy. Even though laptop has a 4k monitor which might slow it down a little compared to hd. The frame rate was slightly less than 25p while screen capturing with OBS which scaled 4k to hd while recording:

Used default i/o settings for vp22 with video and i/o prefs both using its 3060. Got better performance on the same machine with vp21 build 208 with it's default setting of i/o using the Iris/Xe for decoding. Frame rate got to 25p after a few moments:

I missed your hardware specs before due to it being in that sprawl of text, its

2070 super(215w), 3950x 16core cpu, 32GB ram

I think that should play it smoothly in VP21 and VP22,

As a comparison in Best/FULL I get 23% peak CPU use, 17% average, your CPU is faster, GPU use is 115w peak, 70w average. playback with display set to preview/auto, peak GPU use does not much lower, 107w.

To help diagnose if your system can't really play this file , and the cache is just giving you the illusion it can play it, change your display setting from preview/auto to BEST/FULL. with your 8GB of Vram the maximum it could possibly cache is 1 second. so playback would be expected to die much faster

@Howard-Vigorita did a test with his 3060 GPU, it's slower than your 2080super and has less VRAM, so it shouldn't be a GPU problem but his CPU is faster @Gid 's cpu would be slower than your 3950X for general processing (not cpu rendering) so your CPU shouldn't be the problem either

One idea I've thought up to determine if it's your system is capable. download the free Capcut, start it, but before you load your files, click the options cog go to settings/performance and turn off automatically build proxies, then start a new project and load and edit your files. In right hand top corner of preview window is a burger menu , click select preview, change it to prioritize quality. Capcut does 8K projects since last update.

If you can edit with Capcut that would point to some problem with Vegas on your system, either your system not in full health but Capcut better optimized or system is fine but some problem with your Vegas install or incompatibility.

OR, as suggested just use proxies with Vegas for 8K.

Howard:

"only tried the 2nd one but no problem"

But why? If the whole topic is about problem with the 2nd clip??
One plays fine also by op..

mark-y:

"playback with such megalithic source is what we call a miracle "

I don't call this a miracle, if my ancient i7-2600 cpu and ancient 1660Ti gpu can playback without any problem in a mediaplayer:

My cpu release date is: 2011! Now it's 2024. Miracle would be if a nowaday system cannot handle this format.

"expecting smooth realtime decoding of 400Mbps video, even on the fastest of this generation of GPUs and system environments rides at the peak of optimism."

See my ancient system above and how easily can it decode in realtime.