@steliosfan VP16 loads some R5 clips that didn't load in VP18. Then the last vp18 builld improved things.

See my post, with updated info in the 2nd. post re: build 527 at the top of this forum. I found the decoding fix didn't work for Nvdec but did for Intel. Your probably out of luck with VP17, unless switching off decoding works.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-18-update-5-build-527--129048/

Before b527, switching off HW decoding in I\O fixed the issue for some clips.

The R5 and R6 clips I assume are similar .

Was the same problem (AMD Ryzen 3900x, Gtx 1060). The last update of Vegas 18 works OK with 10 bit hevc from Canon R6

General
Complete name               : C:\Users\Stelios\Desktop\9H7A9338.MP4
Format                      : MPEG-4
Format profile              : Base Media / Version 2
Codec ID                    : mp42 (mp42/hvc1/CAEP)
File size                   : 92.2 MiB
Duration                    : 17 s 880 ms
Overall bit rate            : 43.2 Mb/s
Encoded date                : UTC 2021-06-07 10:48:45
Tagged date                 : UTC 2021-06-07 10:48:45

Video
ID                          : 1
Format                      : HEVC
Format/Info                 : High Efficiency Video Coding
Format profile              : @L4.1@High
Codec ID                    : hvc1
Codec ID/Info               : High Efficiency Video Coding
Duration                    : 17 s 880 ms
Bit rate                    : 42.8 Mb/s
Width                       : 1 920 pixels
Height                      : 1 080 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 25.000 FPS
Color space                 : YUV
Chroma subsampling          : 4:2:2
Bit depth                   : 10 bits
Bits/(Pixel*Frame)          : 0.826
Stream size                 : 91.3 MiB (99%)
Language                    : English
Encoded date                : UTC 2021-06-07 10:48:45
Tagged date                 : UTC 2021-06-07 10:48:45
Color range                 : Full
Color primaries             : BT.709
Matrix coefficients         : BT.709

Audio
ID                          : 2
Format                      : AAC
Format/Info                 : Advanced Audio Codec
Format profile              : LC
Codec ID                    : mp4a-40-2
Duration                    : 17 s 877 ms
Bit rate mode               : Constant
Bit rate                    : 256 kb/s
Channel(s)                  : 2 channels
Channel positions           : Front: L R
Sampling rate               : 48.0 kHz
Frame rate                  : 46.875 FPS (1024 SPF)
Compression mode            : Lossy
Stream size                 : 553 KiB (1%)
Language                    : English
Encoded date                : UTC 2021-06-07 10:48:45
Tagged date                 : UTC 2021-06-07 10:48:45

Other
ID                          : 3
Type                        : Time code
Format                      : QuickTime TC
Duration                    : 17 s 880 ms
Time code of first frame    : 00:00:38:14
Time code, striped          : Yes
Language                    : English
Encoded date                : UTC 2021-06-07 10:48:45
Tagged date                 : UTC 2021-06-07 10:48:45
Bit rate mode               : CBR

In Vegas 17 even if I change to intel the same crash occurs. I bought this camera because of 10bit 1080 4:2:2 and dont want to use any other setting. During my years with Eos R was editing flawlessly but in 8bit.

My card is Radeon RX570.

So if i upgrade to Vegas 18 everything will be ok ?

So if i upgrade to Vegas 18 everything will be ok ?

Download the 30 day trial and you can find out for yourself on your system. There's always the problem that others with apparent similar systems may have a different experience to you.

Thank you.

Downloaded the trial, changed to 8bit video levels for performance, loaded the lut and it plays but the stuttering is awful.

I dont understand why the Canon EOS R 8bit Clog plays PERFECT in Vegas 17 on Best (Half) and Canon EOS R6 10bit Clog plays awfully even in Preview (Half)

@steliosfan Maybe because 10 bit and hevc are more difficult to decode. I assume the 8bit Canon R wasn't hevc?

The Intel Xe Gpu's are AFAIK the only ones that will give HW decoding of hevc 10 bit 422. That will then have to be fully supported in VP.

They are not yet available to purchase separately, only in prebuilds, laptops as IGpu's and desktops as IGpu's and also as discrete.

Answer is probably lack of hardware (GPU) decoding support. Check out performance monitor and watch your GPU closely.

Almost no GPUs decode 10-bit 4:2:2. Try 4:2:0 or transcode to something less compressed like ProRes, create proxies, etc. That's the price for being on the cutting edge!

understood. Thank you. Used proxies and its perfect. Do i loose color accuracy during editing with proxies?

I use VEGAS Pro 17 (b. 455) along with the Canon EOS R6, and also shoot in CLOG, though typically at 3840x2160 @ 29.970, so I can match my GoPros' or either the AX-33/AX-53 from Sony. Typically, here is the Bit Rates from these guys:

GoPro Hero 9 Black - 100 Mbps (HEVC)

GoPro Hero 7 Black - 60 Mbps (HEVC) / GoPro Hero 5 Black same BR though only AVC

GoPro Hero 6 Black - 68 Mbps

Sony AX-33/AX-53 - 100 Mbps (XAVC-S)

Canon EOS R6 - 170 Mbps (CLOG -HEVC - and it is IPB since they have not incorporated ALL-I)

What I do after ingesting footage from the R6, is open VP17, then use HOS Import Assist and Transcode out to the now ProRes that was implemented for VP17/VP18.

For the Hero 9 Black, I just preview the clips in MPC-HC (x64) (from the HOS Install), then figure out which ones I want to keep, and remove the rest. I typically, again using HOS, transcode those files to MagicYUV. Though now, starting to use ProRes more for them. Reasoning for this style, is that I shoot in the 5K mode with the GoPro Hero 9, and it looks great in 4K.

Why transcode? Well, both my comptuers are AMD ThreadRippers (2950X and 2920X) and both have AMD Radeon VII GPU's. Though all footage is on NVMe PCI-e SSD's. So, no Intel Hardware Assisted Encode/Decode for me. Plus, once I am done and ready to render, I can "kick it off" then go wash dishes, watch a movie, mow the lawn, etc. while leaving the machine alone to do its thing.

Using a 32 inch 4K monitor on each computer, and tried dong the "Proxy" flow, but my eyes are not that good. I also have a home-built server as a NAS, so once projects done, move all footage down to it for safe-keeping, so plenty of drive space. And those NVMe drives work fantastic with ProRes, Cineform, MagicYUV, UTVideo, etc. Heck, even doing screen recording in OBS, I have the file format for using the CPU in AVI with either MagicYUV or UTVIdeo, so no issues there, with the exception that these files are HUGE! That was using version 26.1 of OBS, and not sure if there is any file size difference with the newer Version 27 that was recently released. Test for another time.

Moral of the Story: Give Wayne a jingle on the Web, Tickle that cute little Otter with some monetary delight, and enjoy all that HOS has to offer. Oh, and if you prefer not to use ProRes in the transcoding, visit the MagicYUV site and purchase that Ultimate Edition, which when installed prior to HOS, will be incorporated into the available formats for use.

understood. Thank you. Used proxies and its perfect. Do i loose color accuracy during editing with proxies?

No. If you edit at best/full you'll be looking at the original file.

Change to preview/full when you want to see it in motion and you'll use the proxy file. When Vegas renders it will use the original file (not the proxy).

If you edit in 8-bit video mode and then switch to 32-bit video before rendering you can take full advantage of high-bit depths, which helps if you are shooting log. You just have to deal with video levels manually (just like in VP 17 and older.)