Have the UHD770 GPU handle decoding (preferences/ file io). You can try legacy vs the newer decoder- for me it really depends on the footage which works more smoothly.

It's 10-bit 4:2:2 which GPUs other than Intel can't decode and even Intel in VEGAS doesn't work so well in my testing. There's no in-camera HEVC 10-bit 4:2:0 setting is there? I find that's pretty good with the Intel iGPU.

No there isn't unfortunately, only 4:2:2. And the performance is fine, I do proxies for everything. Just a full on crash 1-3 times per day. These are the settings I've been using.

The only thing I THOUGHT stopped the crashing was turning off GPU acceleration but haven't tested that long enough to know for certain.

During rendering it's not using the proxies so it's having an issue with the source media. Try unchecking legacy HEVC?

Otherwise instead of taking time to create proxies just transcode to say ProRes 422 instead and skip HEVC entirely?

FWIW HEVC is under development in 21 and hopefully going to significantly improve.

During rendering it's not using the proxies so it's having an issue with the source media. Try unchecking legacy HEVC?

Otherwise instead of taking time to create proxies just transcode to say ProRes 422 instead and skip HEVC entirely?

FWIW HEVC is under development in 21 and hopefully going to significantly improve.

Sweet jeebus that would be nice. I suppose I could try to figure out a nice handbrake workflow although that will get VERY time and space consuming when I have 2TB worth of wedding footage to transcode. In the meantime I'll try unchecking that and see if it stabilizes at all

It may not be slower than the slow VEGAS proxy system : )

I assume you need to preserve the 422 data so a transcode to AVC 10-bit 420 isn't an option? That works great in VEGAS. I use ShutterEncoder for such batch re-encodes and it's faster than what VEGAS is capable of.

I'll keep testing HEVC 422 as it's a format I'd eventually like to use (well I'd like to use cameras that have that as an option for log footage.)

I'll try shutter. And IDEALLY I'd like to preserve it but I also don't do much grading as of now. Eventually maybe Resolve, but that doesn't even need transcoding, it's like butter. I'm open minded to AVC 10-bit 420 to see if my end work suffers. Does shutter have any presets that you'd recommend I try? I hope it doesn't double my storage needs lol

Hi Mark, one faster test idea would be to change hardware decoder to off before rendering and see if the crashes go away. That would work with the existing proxy workflow.

To test ShutterEncoder, choose function and then editing codec Apple ProRes or output codec h264. For ProRes there arent many settings to change.

For h264, change bitrate adjustment to CQ and set a quality of your choosing (19?).

You can right-click on the file in the upper left to see file information (MediaInfo) and use that to keep settings similar to the original (for audio say PCM 16-bit 48khz audio and put it in a mov container or convert to AAC and keep in mp4).

Colorspace try Rec 709 10 bits, advanced features set GOP= your framerate (24, 50, etc.)

Try one and compare it against the original to see if the quality works for what you are doing. You can then batch convert.

Hi Mark, one faster test idea would be to change hardware decoder to off before rendering and see if the crashes go away. That would work with the existing proxy workflow.

To test ShutterEncoder, choose function and then editing codec Apple ProRes or output codec h264. For ProRes there arent many settings to change.

For h264, change bitrate adjustment to CQ and set a quality of your choosing (19?).

You can right-click on the file in the upper left to see file information (MediaInfo) and use that to keep settings similar to the original (for audio say PCM 16-bit 48khz audio and put it in a mov container or convert to AAC and keep in mp4).

Colorspace try Rec 709 10 bits, advanced features set GOP= your framerate (24, 50, etc.)

Try one and compare it against the original to see if the quality works for what you are doing. You can then batch convert.

I'll probably deal with the crashes either until Vegas fixes it (I have no hope) or I move to resolve. Unfortunately transcoding to 420 h264 just looks awful after I render through Vegas. More artifacts, banding, etc. But transcoding to prores creates files double the size of the original, which won't work wither. Transcoding through Vegas seems the most convenient and maybe I'll put up with the issues for now.

Transcoding to 10-bit 420 and then rendering from VEGAS in 32-bit mode looks awful?

Transcoding to 10-bit 420 and then rendering from VEGAS in 32-bit mode looks awful?

I don't render in 32 bit mode. Otherwise it would take me two weeks to render one wedding lol. And yes the h264 option under output codecs at a 150mbps bitrate rendered my usual way had awful banding.