https://1drv.ms/v/c/822e793e3877bece/IQB5rduGw3PbTrydiACJYIwmAWMduJ09jK-JlEPlsun19iQ?e=CIjPeo

I am on Vegas 22, I am starting to think that the GPU is not working. But I know Vegas sees it.

I just opened 22.250 with my laptop (RTX 4060). On an 8-bit preview at best-full I'm getting a solid 25fps. Overlap two clips and it plummets.

Is the GPU working? No because this footage doesn't work with any GPU decoding in VEGAS. See the MediaInfo below; 10-bit 422 AVC is the problem. 10-bit 422 HEVC would work with an Intel iGPU. 10-bit 420 AVC would work with an NVIDIA or other GPU.

General
Complete name                  : \DJI_20251005134106_0199_D.MP4
Format                         : MPEG-4
Format profile                 : Base Media
Codec ID                       : isom (isom/iso2/avc1/mp41)
File size                      : 5.76 GiB
Duration                       : 3 min 12 s
Overall bit rate mode          : Variable
Overall bit rate               : 257 Mb/s
Frame rate                     : 25.000 FPS
Encoded date                   : 2025-10-05 17:41:06 UTC
Tagged date                    : 2025-10-05 17:41:06 UTC
Writing application            : DJI Mavic4 Pro L3B
Cover                          : Yes
Cover type                     : Cover
snal                           : (Binary)
tnal                           : (Binary)

Video
ID                             : 1
Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High 4:2:2 Intra@L5.2
Format settings                : CABAC / 1 Ref Frames
Format settings, CABAC         : Yes
Format settings, Reference fra : 1 frame
Format settings, GOP           : N=1
Codec ID                       : avc1
Codec ID/Info                  : Advanced Video Coding
Duration                       : 3 min 12 s
Bit rate mode                  : Variable
Bit rate                       : 250 Mb/s
Width                          : 3 840 pixels
Height                         : 2 160 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
Scan type                      : Progressive
Bits/(Pixel*Frame)             : 1.208
Stream size                    : 5.61 GiB (97%)
Encoded date                   : 2025-10-05 17:41:06 UTC
Tagged date                    : 2025-10-05 17:41:06 UTC
Color range                    : Limited
Color primaries                : BT.709
Transfer characteristics       : BT.709
Matrix coefficients            : BT.709
Codec configuration box        : avcC

Other #1
ID                             : 2
Type                           : meta
Format                         : djmd
Codec ID                       : djmd
Duration                       : 3 min 12 s
Bit rate mode                  : Variable
Stream size                    : 1.57 MiB (0%)
Title                          : CAM meta
Default                        : No
Alternate group                : 5
Encoded date                   : 2025-10-05 17:41:06 UTC
Tagged date                    : 2025-10-05 17:41:06 UTC

Other #2
ID                             : 3
Type                           : meta
Format                         : dbgi
Codec ID                       : dbgi
Duration                       : 3 min 12 s
Bit rate mode                  : Variable
Stream size                    : 112 MiB (2%)
Title                          : CAM dbgi
Default                        : No
Alternate group                : 5
Encoded date                   : 2025-10-05 17:41:06 UTC
Tagged date                    : 2025-10-05 17:41:06 UTC

Image
Type                           : Cover
Format                         : JPEG
Muxing mode                    : moov-meta-covr
Width                          : 960 pixels
Height                         : 540 pixels
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Compression mode               : Lossy
Stream size                    : 247 KiB (0%)

Also, to see if your GPU is helping with media decoding, open Windows task manager, go to performance and look at the GPU tab. It has figures for 3D, decoding, etc.

Yes, I did go to performance and the GPU is essentially doing nothing. What are my options here? I know I could work with proxies, I'd like to see quality preview while editing. what would you do? Does Resolve have the same issue? Maybe I should try to learn and edit with Resolve?

The issue is that GPU makers stopped putting resources into decoding new variants of AVC. Resolve and Premiere have the same issue.

I'd check your drone for other recording settings.

For existing files you could batch transcode everything with ShutterEncoder to ProRes 422 or 10 bit 420 AVC or HEVC.

The issue is that GPU makers stopped putting resources into decoding new variants of AVC. Resolve and Premiere have the sane issue.

I'd check your drone for other recording settings.

For existing files you could batch transcode everything with ShutterEncoder to ProRes 422 or 10 bit 420 AVC or HEVC.

Is handbrake ok to use? I already have that.

That's crazy because this is the drones best recording format. This All-i codec was supposed to be a selling point for the drone. Now there's no GPU that can process it? Will there be information loss in the transcode?

Standard Recording vs. ALL-I:

Standard (H.264/H.265): More compressed, smaller files, easier on standard hardware, good for most users.

ALL-I: Uncompressed per-frame data, massive files, best for professional color grading and maximum post-production flexibility. 

In short, "ALL-I" is a professional-level feature on the Mavic 4 Pro designed for maximum creative control over your footage, available in the premium Creator Combo. 

Exclusive to Creator Combo:

Only the Mavic 4 Pro with the 512GB internal storage (Creator Combo) supports ALL-I recording

.

High Bitrate: Achieves a very high bitrate (1200 Mbps for H.264) for superior image quality.

Frame-by-Frame Encoding: Records each frame independently, preserving more detail than standard codecs.

Rich Color: Enables 10-bit 4:2:2 recording for significantly better color depth.

Demanding on Hardware: Requires powerful computers for smooth editing and playback due to large file size

It's interesting that VEGAS is struggling to decode an all I-frame format, though, as they do not use any temporal compression and they are easier on the CPU to decode as a result. ProRes is another all-I format. You could try the VEGAS 23 demo and see if it helps any, it does have some performance gains over VEGAS 22.

ProRes is "visually lossless", there is some compression, but for the most part, it is designed to be an intermediary format, so nothing your eye is going to notice. You'd have to do quality metrics tests to tell. If you really want to make sure you're getting every pixel and bit of detail from the original, you can always treat the prores files as proxies and use the "replace" function in the project media pool to swap the prores files for the originals before you render, but ProRes 422 4K should be more than enough to work with all the way through to the render and should play back smoothly. DO NOT use the extreme quality ProRes modes, they have such a ridiculously high bitrate that the SSD itself becomes the bottleneck trying to move all that data around.

Handbrake is fine, try the production standard preset and modify it from there. There shouldn't be any meaningful degradation with ProRes.

While All-I is easy on computers it's dumb that DJI chose 422 AVC as almost no GPUs can work with that. Is standard 8-bit or 10-bit? There's no 10-bit HEVC option?

I'd do a test of All-I vs standard and see if it actually makes a difference for what you do. If you're not doing log conversions I doubt you'll have any visual difference (with log the benefit of 10-bit and higher color depths is to avoid banding with the conversion. You'll have to be in 32-bit project mode in VEGAS at least for the render to take advantage of this precision.

Just a quick google search says this....

For 10-bit 4:2:2 AVC (H.264) hardware decoding, the best GPU options are modern NVIDIA cards, specifically the RTX 50-series (Blackwell) which offers specialized support for H.264 4:2:2, or Intel CPUs with Quick Sync (11th Gen+), which are highly efficient for this specific codec. While older cards struggle with 4:2:2, RTX 3060/4060 or higher provides solid performance. 

Best Performance (4:2:2 H.264/H.265): NVIDIA RTX 50-series (Blackwell) for superior 4:2:2 decoding and encoding.

Is this just old info?

This statement is correct. However, no Magix software currently fully supports the 50XX series.

This statement is correct. However, no Magix software currently fully supports the 50XX series.

Okay, i also read that the paid version of resolve would address this and work with H.264 4:2.2? Resolve hasn't achieved this?

Just a quick google search says this....

For 10-bit 4:2:2 AVC (H.264) hardware decoding, the best GPU options are modern NVIDIA cards, specifically the RTX 50-series (Blackwell) which offers specialized support for H.264 4:2:2, or Intel CPUs with Quick Sync (11th Gen+), which are highly efficient for this specific codec. While older cards struggle with 4:2:2, RTX 3060/4060 or higher provides solid performance. 

Best Performance (4:2:2 H.264/H.265): NVIDIA RTX 50-series (Blackwell) for superior 4:2:2 decoding and encoding.

 

Is this just old info?

I just download and run your sample footage on my over 10 yrs desktop system and it is playing back no problem. The system I was trying your footage on is a old AMD 16 Cores Threadripper with Radeon Vegas Frontier Edidion 16GB card. VP22& VP23 both ran your footage no problem, however VP 22 is much more butterly smooth. I did not try to test on my newest system. I can assured it will be much more better.

Yes, I did go to performance and the GPU is essentially doing nothing. What are my options here? I know I could work with proxies, I'd like to see quality preview while editing. what would you do? Does Resolve have the same issue? Maybe I should try to learn and edit with Resolve?

Davinci Resolve decimated Vegas Pro in Masking; Rendering, Playback TL. Vegas Pro is good. I still occasionally using it. But , there is no comparison when comes to performance; TL and Rendering. 4K 30P H264 10 bit GOP 422 source Rendering to 4k 10 bit 4.2.0 VP 22/23 I get about 90 frames. In Davinci Resolve I get 190-200 frames.

Just a quick google search says this....

For 10-bit 4:2:2 AVC (H.264) hardware decoding, the best GPU options are modern NVIDIA cards, specifically the RTX 50-series (Blackwell) which offers specialized support for H.264 4:2:2, or Intel CPUs with Quick Sync (11th Gen+), which are highly efficient for this specific codec. While older cards struggle with 4:2:2, RTX 3060/4060 or higher provides solid performance. 

Best Performance (4:2:2 H.264/H.265): NVIDIA RTX 50-series (Blackwell) for superior 4:2:2 decoding and encoding.

 

Is this just old info?

I just download and run your sample footage on my over 10 yrs desktop system and it is playing back no problem. The system I was trying your footage on is a old AMD 16 Cores Threadripper with Radeon Vegas Frontier Edidion 16GB card. VP22& VP23 both ran your footage no problem, however VP 22 is much more butterly smooth. I did not try to test on my newest system. I can assured it will be much more better.

It runs fine on my system as well, just playing the clips, and that's just the CPU doing the work. However when you try to transition two clips with a cross fade, it starts to stutter, don't know what else would happen if I tried to add CC. I'd like to be able to use my GPU for something lol.

I don't know what caused your issue. I have done many projects with h264 422, no problem with smooth Playback with color correction and Crossfade.