Canon CLog 3 shows as blank on timeline and freezes VP 23

william-g wrote on 2/28/2026, 1:26 AM

Hi, VP 23, build 356. Canon CLog 3 footage from my Canon R6 mk II shows up as a blank video track on the time line. The audio track plays as normal Non CLog footage show perfectly fine.

The Clog footage can be played in various media players without issue.

The video track shows as 3840 x 2160 and as HVEC. A 12 second clip took over 5 minutes to create a proxy file - and the proxy file video track was also blank (sound played normally) .

in Project Media - if you had another file from another camera (e.g. Osmo Pocket 3) that clip too will show as blank, although if you do manage to drag it to the timeline it will show as normal eventually. VP23 is very sluggish with these CLog 3 files on the timeline - clearly doesn't like them.

The computer is quite fast - Ryzen 9 5900XT with 64gb RAM and an Nvidia RTX 5060 ti and has never had an issue rendering or creating proxy files before from any camera.

Not sure if it is a Vegas setting thing as other seem to be able to edit Clog 3. Maybe a codec?

Any tips or hints gratefully received.

Thanks

Comments

3POINT wrote on 2/28/2026, 1:39 AM

My Osmo-pocket 3 HEVC files can be used without any issues in VP23.302.

You're using VP23.356, a build that was withdrawn just 3 days after it's release due to severe bugs. I'm not sure if your issue could be solved be reinstalling build 302, but I would give it a try. I myself reinstalled build 302.

RogerS wrote on 2/28/2026, 1:46 AM

It's a codec issue. The RTX 50 series supports 10-bit 422 decoding but VEGAS hasn't enabled it. In practice that means that such footage shows up at blank in VP 23 unless you turn off hardware decoding in options/preferences/ file io.

william-g wrote on 2/28/2026, 2:41 AM

It's a codec issue. The RTX 50 series supports 10-bit 422 decoding but VEGAS hasn't enabled it. In practice that means that such footage shows up at blank in VP 23 unless you turn off hardware decoding in options/preferences/ file io.

that worked brilliantly, thanks very much

RogerS wrote on 2/28/2026, 2:48 AM

My pleasure. Hopefully this will be addressed before long as not having GPU decoding on hurts performance for supported codecs.