VP Various Recent Builds & NVIDIA RTX 3050 Ti Cards

ALO wrote on 3/17/2025, 9:09 PM

Is anyone have success editing 10-bit HEVC with NVIDIA notebook cards?

The last couple builds/versions of Vegas have just been terrible for me. Things have progressed from manageable-but-frequent app crashes to total OS crashes that require a hard reset. I've given up on 32-bit mode entirely; this is happening in legacy 8-bit mode. I work primarily with GoPro 5k at 150 Mbps. Suspect some kind of memory leak, because it seems to happen after a set period of time of editing (using proxies!).

I do use the legacy fx chain instead of the color grading panel & I know at least some of those fx (like color curves) are broken in 32-bit mode.

If anyone is having no issues with a current Dell XPS notebook and this kind of intake media, please let me know

Comments

ALO wrote on 3/19/2025, 6:35 PM

Okay let me try again: is anyone successfully working with 20-30 GoPro 5K/10-bit HEVC clips on a 4K Vegas timeline, using Vegas-created (automatic) proxies, doing basic editing/grading using Preview Quality = Preview (Full) using NVIDIA graphics cards (either desktop or laptop)?

Ie, program is stable enough to edit without regular catastrophic crashes, and will successfully render out 10-20 minute projects directly from the HEVC source?

Otherwise I'm going to assume this is just not a stable Vegas workflow and a transcode (maybe to ProRes) is necessary for both editing and rendering?

ALO wrote on 3/24/2025, 6:22 PM

okay I've been replacing everything with Apple ProRes 422.

Still got my system freeze after 10-15 mins, but then realized I had an HEVC clip (my splash screen). Replaced that. Still system freeze. Realized I have a Vegas Tiles & Text media on my timeline; replacing that with ProRes next. Freeze occurs both with my pro sound card and onboard sound card.

Other than the crash/freeze which forces me to hard-reset windows, Vegas is a lot more responsive editing ProRes so I can see why so many transcode to it

RogerS wrote on 3/24/2025, 6:30 PM

Does system freeze mean VEGAS freeze? If Windows freezes up I think you have bigger issues than just VEGAS and would troubleshoot broadly with stress tests, 3dMark, etc. VEGAS can't generally cause blue screens or take down Windows itself.

ALO wrote on 3/25/2025, 11:32 AM

yes Vegas freezing everything inc windows. I may try a new system to rule out hardware/config issues

Chief24 wrote on 3/25/2025, 12:28 PM

@ALO

I too also use GoPro's. I have a 5 Black, 6 Black, 7 Black (2 actually), 9 Black, 10 Black, 11 Black, 12 Black, and 13 Black. Now, I don't shoot small length clips, as I use these for my daily walks of around 3.1 Miles/80-90 minutes, and I use the highest resolution and Bit Rate possible. So:

All filmed at Native White Balance, Color Flat (note below), ISO 100-1600 (except 5 only 400 ISO)

5 Black - 4K30p (29.970) bit rate is around 60 Mbps

6 Black - 4K30p bit rate around 66 Mbps

7 Black - 4K30p bit rate around 60 Mbps

9 Black - 5K30p bit rate around 100 Mbps

10 Black - 5.3K30p bit rate around 100 Mbps

11, 12, 13 Black - 5.3K30p bit rate around 120 Mbps (12 & 13 in GoPro Log)

I then use Shutter Encoder to Transcode the .mp4 (AVC or HEVC) container file to ProRes 422 LT, as that has a small enough file size to not be unruly, but with the 11, 12, & 13 Black, also maintains the 10-Bit color.

My signature has both computer specifications, and that ProRes 422 LT .mov container file works wonderful, and has for quite some time with Vegas Pro. I have used those files with VP 17 and up, though currently I am only really using VP 21 (315) & 22 (239) on both computers.

I also have a Canon R6, R6 Mk II, and R7, of which I only shoot C-LOG 3, usually 4K30p (29.970), so the files are HEVC 4:2:2 10-Bit .mp4 files IPB compression, and I transcode them to ProRes 422 .mov, and they work fine also.

So if you notice my computers, they are AMD Threadripper HEDT, meaning no Integrated graphics (iGPU) like the Intel processors that have the 4:2:2 10-Bit hardware decoding (I think 10th Gen on), and my AMD GPU's do not have the hardware decoding/encoding for that either. And no, even if I could find an Nvidia 5000 series card available and not at the extremely disgusting price, I would not change.

 

Self Build: #1 MSI TRX40 Pro Wi-Fi w/3960X (be Quiet! Dark Rock Pro TR4) @ stock; 128GB Team Group 3200 MHz; OS/Apps - WDSN850X PCI-e 4.0x4 4TB, Documents/Extras - WDSN850X PCI-e 4.0x4 4TB; XFX AMD Radeon 7900XTX (24.12.1); Samsung 32 Inch UHD 3840x2160; Windows 11 Pro 64-Bit (24H2 26100.2894); (2) Inland Performance 2TB/(2) PNY 3040 4TB PCI-e on Asus Quad M.2x16; (2) WD RED 4TB; ProGrade USB CFExpress/SD card Reader; LG 16X Blu-Ray Burner; 32 inch Samsung UHD 3840x2160.

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS (Happy Otter Scripts); DVD Architect 7.0 (100);

Sound Forge Audio Studio 15; ACID Music Studio 11; SonicFire Pro 6.6.9 (with Vegas Pro/Movie Studio Plug-in); DaVinci Resolve (Free) 19.1.3

#2: Gigabyte TRX50 Aero D w/7960x (Noctua NH-U14S TR5-SP6) @ stock; 128GB Kingston Fury Beast RDIMM @4800 MHz; OS/Apps - Seagate Firecuda 540 2TB PCI-e 5.0x4; Documents/Extras/Source/Transcodes - 4TB WDSN850X PCI-e 4.0x4; 4TB Inland Performance PCI-e 3.0x4; 2TB Inland Performance PCI-e 4.0x4; BlackMagic PCI-e Decklink 4K Mini-Recorder; ProGrade USB SD & Micro SD card readers; LG 32 Inch UHD 3840.x2160: PowerColor Hellhound RX Radeon 7900XT (24.12.1); Windows 11 Pro 64-Bit (24H2 26100.2894)

VEGAS Pro 20 Edit (411); VEGAS Pro 21 Suite (315); VEGAS Pro 22 Suite (239) & HOS; DVD Architect 7.0 (100); Sound Forge Audo Studio 15; Acid Music Studio 11

Canon EOS R6 MkII, Canon EOS R6, Canon EOS R7 (All three set for 4K 24/30/60 Cinema Gamut/CLog3); GoPro Hero 5+ & 6 Black & (2) 7 Black & 9 Black & 10 Black & 11 Black & 12 Black (All set at highest settings - 4K, 5K, & 5.3K mostly at 29.970); Sony FDR AX-53 HandyCam (4K 100Mbps XAVC-S 23.976/29.970)

RogerS wrote on 3/25/2025, 7:39 PM

yes Vegas freezing everything inc windows. I may try a new system to rule out hardware/config issues

Can you see what Windows Reliability History shows for these critical events?

ALO wrote on 3/25/2025, 8:34 PM

fr0sty wrote on 3/25/2025, 8:38 PM

I see Windows reports 2 hardware errors right before that VEGAS crash... maybe a source to investigate. Have you tried driver updates?

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

RogerS wrote on 3/25/2025, 8:44 PM

Please share screenshots of the Windows errors and Windows was not properly shut down. When you click it should give more detail as to what happened, and if lucky may give a driver name, etc. that's the cause. I used similar data with NVIDIA support to determine that the generic studio driver was causing problems with my laptop as it shipped with a custom driver and that was crashing Windows.

ALO wrote on 3/26/2025, 1:34 PM

I believe "not properly" was me holding power button to force shutdown of frozen/nonresponsive system

RogerS wrote on 3/26/2025, 11:18 PM

None of these are telling me much of anything. A recent hang here at least points to a file I can then search for and learn is an Intel graphics driver:

ALO wrote on 3/27/2025, 4:14 PM

I found some drivers/bios stuff that windows update had failed to update to latest. I'll update those and see if issue persists...