XAVCS 4k 10bit in V20 too slow to properly edit

Mindmatter wrote on 11/16/2022, 6:18 AM

Hi all
so with V20 being stable and good to me so far, I'm just rather frustrated about how it handles XAVCS 4k from my FX3.

Even at "draft / half or even auto" I'm sometimes down to 4 frames on transitions, normal cuts have such a delay that it's impossible to edit to music or a certain rhythm.

Of course i did all the usual tweaks we've been working with all these years already. An no, sorry, I don't like the idea to have to create proxies for hours after a shooting just to be able to work normally. Is there anything else I can do to at least have a fluent ( even if very ) low rez playback?
Thanks!

Back to post

Comments

Wolfgang S. wrote on 11/18/2022, 1:57 PM

@Mindmatter,

could you be so kind and offer a download for an origional XAVCS file that is decoded so slowly?

Maybe the development team can have a look to it.

Howard-Vigorita wrote on 11/18/2022, 3:37 PM

I tried Sony 4k 10-bit 422 xavc and that proved impossible to decode with hardware. Presumably because of the avc 10-bit 422. Proxy required to preview smoothly. I would expect their long gop hevc 420 to be tough also. I had better luck with 8-bit Canon xavc 422 mxf with an Arc board. Saw allot of extra 3d utilization. Canon and Zcam 10-bit 4k 420 hevc intra was still faster, however. With the fx3, I think the only intra option not 422 is 8-bit xavc.

RogerS wrote on 11/19/2022, 12:26 AM

While the AVC formats don't work with GPU decoders I found my Intel 13th gen processor in VP 20 can handle the A7sIII's formats at full speed (tested a few different ones). Same with HEVC but legacy decoder must be disabled as that format does use the iGPU in Vegas for 10 bit 4:2:2.

Yelandkeil wrote on 11/19/2022, 12:31 AM

I remembered once @alifftudm95 also met the problem: in XAVC there are 2 codecs, AVC or HEVC.
XAVC-S uses surely the Xtened AVC one and not HEVC.

So, the OP here is talking about XAVC-S.

Former user wrote on 11/19/2022, 1:04 AM

While the AVC formats don't work with GPU decoders I found my Intel 13th gen processor in VP 20 can handle the A7sIII's formats at full speed (tested a few different ones).

@RogerS Try this one, nothing special but I was testing it so can make a comparision

https://www.amazon.com/photos/shared/u75s4NixSLK2ZLDrjp29Mg.04o8T8Uc_s9_QEq7Uu7VkJ

Project at 4K 59.94fps, Conform file to 59.94fps, play on BEST/FULL, make 4 or 5 cuts, and fade them together with only a small overlap, the idea is to defeat the cache so we can see how Vegas works in an editing sense, not as a media player.

If you are not getting reliable smooth playback try reducing playback settings until hopefully it plays well

RogerS wrote on 11/19/2022, 4:00 AM

I downloaded it and put it on a 29.97 fps timeline as a nice smooth slow motion. It worked fine though the first few frames weren't at full framerate.

At 59.94 even starting it partway in where there are cuts, etc. causes big performance drops (5, 15 or 25 fps) until it catches up again. So not so good. Doing cuts to it on a 29.97fps timeline also causes big slowdown. Vegas is also using 17GB of ram which seems high for a single 160mb video (dynamic ram preview is only 3GB).

Reyfox wrote on 11/21/2022, 4:05 AM

Just dropping that clip on the timeline used up 11.6GB of RAM....