Possibly specific to the A1, If you'd be willing to share some of those files via google drive/dropbox, I'd like to take a crack at it, and pass them along to the team to see if we can reproduce the issues.

As far as the "VEGAS is diverting resources away from performance and stability to add new features"... there's an announcement coming regarding that which will make many users here very happy... and not just the "we're putting more attention on that and less on new features" that they already announced previously. I'm not at liberty to tell you now myself, unfortunately... but I have convinced those in charge of such things that sharing the news is going to be very beneficial for them, and they've indicated a willingness to do so.

Sure, will drop some files soon.

I really hope these time it's true. If it will actually happen, and Vegas will work at least better with those files, I'll buy VP21 License with no questions. I will support them financially, with great pleasure, if those troubles will be fixed after such a long time.

Possibly specific to the A1, If you'd be willing to share some of those files via google drive/dropbox, I'd like to take a crack at it, and pass them along to the team to see if we can reproduce the issues.

As far as the "VEGAS is diverting resources away from performance and stability to add new features"... there's an announcement coming regarding that which will make many users here very happy... and not just the "we're putting more attention on that and less on new features" that they already announced previously. I'm not at liberty to tell you now myself, unfortunately... but I have convinced those in charge of such things that sharing the news is going to be very beneficial for them, and they've indicated a willingness to do so.

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

@Kloverton I don't have GPU decode of 422 color, but it's still a test of the render engines even if I would not edit without a proxy. I have found using scene detect to analyze 1 minute of video is a good benchmark. If the processing takes less than 1 minute playback should be fine.

Capcut and Resolve take around 1:25 to process the 1minute clip, so I know I will have dropped frames

(2x playback)

This is playback in Resolve, everything is slow and laggy, but if I had the 16 core or a newer generation CPU maybe it wouldn't be even without GPU decode. We can see if Vegas performance will increase, it looks like it would have taken around 13minutes to complete the scene detect on the 1minute clip and thus it's not playable

Do you have an A1 file you can share that is less than 15GB? That's really more than is needed to just do a test of the media.

Haven't tested 8K in a while but last time I used it VEGAS automatically created a proxy file and it worked fine. It was possible to render out in 8K. For 4K120 that's for slow motion so should play back reasonably well on a 24, 30 or 60fps timeline when "added at project framerate."

Update: finally got it to download (3 min file = 15GB. Yikes.)

8K HEVC 10-bit 4:2:2. Not a dream editing format!

General
Complete name                  : C2374.MP4
Format                         : XAVC
Codec ID                       : XAVC (XAVC/mp42/iso2/nras)
File size                      : 13.7 GiB
Duration                       : 3 min 44 s
Overall bit rate               : 524 Mb/s
Frame rate                     : 29.970 FPS
Encoded date                   : 2023-07-27 17:37:08 UTC
Tagged date                    : 2023-07-27 17:37:08 UTC

Video
ID                             : 1
Format                         : HEVC
Format/Info                    : High Efficiency Video Coding
Format profile                 : Format Range@L6.1@High
Codec ID                       : hvc1
Codec ID/Info                  : High Efficiency Video Coding
Duration                       : 3 min 44 s
Bit rate                       : 520 Mb/s
Width                          : 7 680 pixels
Height                         : 4 320 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
Bit depth                      : 10 bits
Bits/(Pixel*Frame)             : 0.523
Stream size                    : 13.6 GiB (99%)
Encoded date                   : 2023-07-27 17:37:08 UTC
Tagged date                    : 2023-07-27 17:37:08 UTC
Color range                    : Limited
Color primaries                : BT.709
Transfer characteristics       : BT.709
Matrix coefficients            : BT.709
Metas                          : 3
Codec configuration box        : hvcC

Audio
ID                             : 2
Format                         : PCM
Format settings                : Big / Signed
Codec ID                       : twos
Duration                       : 3 min 44 s
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                    : 41.1 MiB (0%)
Encoded date                   : 2023-07-27 17:37:08 UTC
Tagged date                    : 2023-07-27 17:37:08 UTC

Other
ID                             : 3
Type                           : meta
Format                         : rtmd
Codec ID                       : rtmd
Duration                       : 3 min 44 s
Bit rate mode                  : Constant
Encoded date                   : 2023-07-27 17:37:08 UTC
Tagged date                    : 2023-07-27 17:37:08 UTC

@Kloverton I was able to render it OK on the desktop in my sig.

I didn't wait the full hour it would have taken to render the complete file... are you not able to render it AT ALL, or does the render crash later on into the render? If it does, I'll run another test later where I try to render the complete file.

I'm using the same GPU as you, RTX 3090.

For what it's worth I did a test with this file and my laptop from 2017 which has a 4GB GTX 1050 GPU. It took about an hour to create the proxy file, at which point playback was fine though undoing after making cuts took longer than usual.

I then just did a render. I learned MagixAVC doesn't go up to 8K, at least with NVENC, but MagixHEVC does, even on a 10XX series GPU. I rendered out the 8K file and it averaged about 1fps and finished in 1 hour 41 minutes. That was to an 8-bit 4:2:0 final render and I did it in 8-bit full mode. This computer is clearly not ideal for such media, but it worked.

Also I'd run the range hood when the gas is on.

For what it's worth I did a test with this file and my laptop from 2017 which has a 4GB GTX 1050 GPU. It took about an hour to create the proxy file, at which point playback was fine though undoing after making cuts took longer than usual.

So it's clear using proxies for this camera format in Vegas is not achievable in a standardized workflow, both in proxy creation and render. Just the act of creating proxies is taking 20minutes per 1 minute of footage. Has to be transcoded before use, and at 8K with an editable codec they will be huge files, but at least it should be possible to use in a reasonable manner... maybe anyway

I then just did a render. I learned MagixAVC doesn't go up to 8K, at least with NVENC, but MagixHEVC does, even on a 10XX series GPU.

That's a legal format thing, 4096x4096 is the maximum resolution for hardware decoding or encoding in AVC on any consumer GPU

I rendered out the 8K file and it averaged about 1fps and finished in 1 hour 41 minutes. That was to an 8-bit 4:2:0 final render and I did it in 8-bit full mode.

We can imagine he's editing projects, not transcoding and because of all the lag I saw on the timeline It's possible there's a higher than usual chance Vegas is going to crash at an edit/fx point during rendering. Although Vegas should be using a lot of resources it isn't, so should not be stressing his computer resulting in hardware failure.

I tested with 1 minute of footage encoding to 8K HEVC 420 8bit via voukoder NVENC

Vegas 2.36fps

Resolve 23-24fps

@RogerS are you able to test again with your 13600K CPU with GPU decode?

Before I came to VEGAS I was using Final Cut Pro which wanted to create optimized media for everything- even HD AVC. I had to wait hours just to import media from the day's shooting and start editing. So this isn't so far off from that experience. Though I wouldn't be shooting or delivering 8K for documentary work where there's a lot of footage.

With my desktop HEVC decoding works and it created a proxy file for the 3:30 min. long media in about 8 minutes; the proxy file is about 800mb.

I was able to cut and manipulate the media on my laptop once the proxy was created. Not a great experience given the hardware I have and I wasn't sure what I was trying to replicate, so just undid that and rendered without error.

On my desktop it plays back horrendously at best/full (1-2fps). Decoding is working but it's nowhere near enough. Using the proxy file (preview/auto) you get full framerate and it's easy to cut, rearrange and fade clips, etc.

A transcode 8K HEVC render took 20 minutes. No errors.

If think Kloverton doesnt like proxy creating/editing (just like me :) )

"sticking 8K logos on their website, which it cant even handle, loading 1 frame in preview for 8 seconds on 18 Core processor and RTX 4090."

He don't talk about proxy files editing. Sure, with proxies we can edit everything which can be converted.

My two cents

"Resolve 23-24fps" isn't exactly what I'd call a smooth editing experience for 30fps media either, especially with no effects or grading applied. I would want to use proxies in that case as well. There's a reason resolve just implemented a proxy system recently. Even it can't do everything.

@fr0sty My point was an efficiency of render engine test, not that using 8K HEVC without a GPU decoder being usable, with Resolve having 10x the efficacy of the Vegas render engine with that particular 10bit HEVC file. It's not a real comparison though, because Vegas is only using 1 or 2 cores to decode, ideally it would use all it's CPU cores to decode and then a better comparison can be made. Fact is though currently for @Kloverton and his A1 using 10bit HEVC 422 Vegas won't multicore CPU decode.

Also with the Resolve example using proxies is perfectly achievable but for me and kloverton this isn't a real alternative with Vegas given how long it takes to create the proxies and encode the original file. For RogerS and people with 422 GPU decode proxies are an alternative in Vegas, but even so 20minutes to transcode 3m30 file 8k HEVC NVENC is not ideal

@fr0sty My point was an efficiency of render engine test, not that using 8K HEVC without a GPU decoder being usable, with Resolve having 10x the efficacy of the Vegas render engine with that particular 10bit HEVC file. It's not a real comparison though, because Vegas is only using 1 or 2 cores to decode, ideally it would use all it's CPU cores to decode and then a better comparison can be made. Fact is though currently for @Kloverton and his A1 using 10bit HEVC 422 Vegas won't multicore CPU decode.

Also with the Resolve example using proxies is perfectly achievable but for me and kloverton this isn't a real alternative with Vegas given how long it takes to create the proxies and encode the original file. For RogerS and people with 422 GPU decode proxies are an alternative in Vegas, but even so 20minutes to transcode 3m30 file 8k HEVC NVENC is not ideal

@fr0sty My point was an efficiency of render engine test, not that using 8K HEVC without a GPU decoder being usable, with Resolve having 10x the efficacy of the Vegas render engine with that particular 10bit HEVC file. It's not a real comparison though, because Vegas is only using 1 or 2 cores to decode, ideally it would use all it's CPU cores to decode and then a better comparison can be made. Fact is though currently for @Kloverton and his A1 using 10bit HEVC 422 Vegas won't multicore CPU decode.

Also with the Resolve example using proxies is perfectly achievable but for me and kloverton this isn't a real alternative with Vegas given how long it takes to create the proxies and encode the original file. For RogerS and people with 422 GPU decode proxies are an alternative in Vegas, but even so 20minutes to transcode 3m30 file 8k HEVC NVENC is not ideal

That's only assuming that you create said proxies using Vegas's internal proxy creation tool, Vegas has multiple ways to create proxies. You can do so with happy otter scripts, you can encode the proxies using an external app like shutter encoder, and then swap out the media with the proxy files, swapping them back before render, there's multiple ways to go about it.

I'm definitely not trying to say it's ideal, but for people to say that it is unusable is a stretch.

That's only assuming that you create said proxies using Vegas's internal proxy creation tool, Vegas has multiple ways to create proxies

@fr0sty But the proxy problem comes with 2 parts, the creation and the encode of the original file. It is true even without a GPU decoder I can transcode 1minute of this A1 8K footage in not much more than a minute to a 1080P proxy, but the Vegas render still has to deal with the orignal file, for me it takes 13minutes per each minute of footage to encode, no fx, no color grading, for others it's more like 20 minutes her 1 minute of footage.

The alternative would be entreating giant prores422 files, it's something like 24GB per minute. at 8K this also doesn't play without dropped frames for me, but it is editable, and the encode time will be much more reasonable, . Not a perfect work around due to the 8K resolution/dropped frames, but I'd most likely prefer it to a 10 minute encode taking at absolute minimum130minutes

I changed a video setting in vegas pro 20 to hdr and then changed it back to what it was and now all video looks like I have to color grade as it is all washed out. Any ideas how to fix it so video looks normal

seems like i figured out how to reset vegas pro to default setting and that worked

Vegas 20 build 411. Windows 10, 32GB Ram, GeForce RTX2060 (But I also have a Windows 11 machine with 3070Ti with same issue): EXPLORER WINDOW issue: slow to display contents of folder. If I open up an explorer window in Vegas which has more than just a few folders and files (try it with 100, then try it with 1000 files), it takes up to a full minute for Vegas to come back from freezing. I presume it's reading the contents of this folder. Is it cataloging or something? Doesn't seem like it b/c if I click on the same folder a little bit later, it still takes a long time to display the contents of the folder. Once in a folder, try clicking "Last Modified" to sort the files by date, and it again takes a long time to do it, locking you out of doing anything else until it's finished. I keep SFX in a series of folders for handy use, and prior to Vegas 20 (19, 17, 11) it showed the contents almost immediately. Curious if there's a setting or if I should change the way my files are cataloged?

Using Project bins wouldn't work for me since I have a lot of SFX and don't always need access to them.

Thx

jmm in STL.

I have problems with the latest version V20. Everytime when I use the voice-recorder the program shuts down. I tried 5x but always the same problem.

Did you already tried one of the other Audio devices?

Is it safe to assume that Vegas 20 (build 411) means Update 3 is already applied?

Build 411 is the current build of VEGAS Pro 20.

I'm curios why 8-10-12 bit HEVC decoding is supported from GTX1630 (!) but only in 4:2:0 and 4:4:4 format.

Why 4:2:2 is so special for nvidia? https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new