Hello, thank you very much for the quick response. Here are the required data:

Format                                   : XAVC

Format: XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
File size                                : 544 MiB
Duration                                 : 15 s 360 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 297 Mb/s
Frame rate                               : 100.000 FPS
Encoded date                             : 2023-11-05 01:26:02 UTC
Tagged date                              : 2023-11-05 01:26:02 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High 4:2:2@L6
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 15 s 360 ms
Bit rate mode                            : Variable
Bit rate                                 : 290 Mb/s
Maximum bit rate                         : 280 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Rotation                                 : 270°
Frame rate mode                          : Constant
Frame rate                               : 100.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.349
Stream size                              : 531 MiB (98%)
Encoded date                             : 2023-11-05 01:26:02 UTC
Tagged date                              : 2023-11-05 01:26:02 UTC
Color range                              : Full
Metas                                    : 3
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 15 s 360 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 2.81 MiB (0%)
Encoded date                             : 2023-11-05 01:26:02 UTC
Tagged date                              : 2023-11-05 01:26:02 UTC

Other
ID                                       : 3
Type                                     : meta
Format                                   : rtmd
Codec ID                                 : rtmd
Duration                                 : 15 s 360 ms
Bit rate mode                            : Constant

@Mobby It's a codec problem in the sense that gpus do not support decoding avc 4:2:2... only way to get a gpu to decode it is to transcode it to 4:2:0. I just tried playing a sample of that format and Vegas does generate a bit of gpu copy utilization... I assume for caching.

@Mobby Thanks n sorry had to go out @Howard-Vigorita I just created an XAVC 422 AVC & had no prob with it, I've not a lot of experience with these so if it's not the right type of file can you share one or tell me how to create one?

290 Mbps 100fps 10 bit 4:2:2 will likely never preview smoothly [edit /] in Vegas [/] on any terrestrial system.

I wonder if you could get by with less extreme shooting settings.

What will it be used for?

Build a Proxy file using the posts on this forum as your guide. Search.

The OP file seems to be a mp4 file.

Rewrapping to an mxf one may help with preview speed because Vegas will use another dll to read it.

Right click on the file, "create video proxy" from the right click menu, wait for the proxy to finish, set preview quality to preview, and it will play back smoothly.

290 Mbps 100fps 10 bit 4:2:2 will likely never preview smoothly on any terrestrial system.

@mark-y 120fps version plays back ok on Resolve. Vegas's render engine is inefficient, but it still doesn't mean it can't be played back on Vegas, @Former user with his threadripper most likely could play it fine, but not for most people.

@Former user I missed out the 100fps bit, I couldn't work out how to create that,the best i could do was XAVC 422 AVC 59.94.

Hello, first of all, thank you very much for the numerous responses.

@fr0sty

I want to begin by mentioning that I'm familiar with creating proxy files and do use them. However, this doesn't solve the issue of having to wait for everything to update before I can begin working. What's also bothersome is that the creation of proxy files doesn't seem to affect the trimmer since it likely still accesses the original file. It only becomes a problem during editing when a larger composition is involved with multiple files added. My primary concern here is the overall performance of the program with such files, and I believe there are underlying issues that go beyond proxy creation.

@mark-y

As @Todd-A0 has already pointed out, Resolve allows for processing files without the need for proxy creation or extensive setup. I don't like making comparisons, and I do want to continue working with Vegas, but it's becoming increasingly frustrating when I feel like I have to go through countless settings before I can work on my footage. This shouldn't be the case.

That's why I had to mention this problem, and from what I've read here, the suggestions seem to revolve around either altering the actual file or Vegas lacking certain attributes to properly handle such files. If I missed something or if the automatic translator has presented statements differently, I apologize. I would appreciate it if someone could perhaps summarize the whole issue once more.

@Mobby Here's my attempt to summarize.

10-bit 4:2:2 files don't work with GPU decoding with any GPU or editing software and this is the main tool VEGAS has to improve playback performance. Other editors can use different GPU resources to achieve smooth playback. We've learned that a new video engine for VEGAS is in the works, but until it exists that doesn't help us.

For now you can test the formats your camera is capable of shooting and find ones that work well in VEGAS and give you the quality and file size you are looking for. 10-bit 4:2:0 AVC should work fine and 10-bit 4:2:0 HEVC may be fine as well. (There is also an update coming shortly for VP 21 which may help with HEVC).

Otherwise you can convert them to a file type VEGAS works well with, or create a proxy file to speed playback. It isn't a settings issue.

@Mobby I am sorry, my response to you was not generalized to accommodate other nonlinear editors, including the one you and another contributor mentioned by name. I did not mention that my advice was specifc to Vegas, with which I am most familiar.

Best of the Holiday Season!

As an fyi, the clip in this format I tested on my laptop was over an hour long. It edited and played OK... see laptop specs in my signature. Just tried it with the new vp21 release as well as vp20 and no difference I can detect.

Considering only the low gpu utilization mentioned at first, Vegas proxies won't change that since they use xdcam-mp4 format which only cpu-decodes. Though there could be an impact due to increased decoding speed feeding gpu-accelerated fx more quickly. Only a transcode to a format gpus can decode will otherwise increase gpu utilization. If you want to preserve the 422 color, hevc is the only gpu format option available. But it only decodes with recent-model Intel gpus. Not with Nvidia & Amd. Next best choice is 420 avc which all 3 gpu makers can decode. It probably also needs to be cut back to 8-bit. Another way to go, somewhat like xdcam low-compression, is ProRes. That will preserve 422 and 10-bit but make even larger files and likely increase cpu utilization.

If it's acceptable and allowed, I would like to provide the clip for you to test and see how it performs on your end. I don't have significant issues with playing back a clip myself, but perhaps it may help others in testing some aspects.

https://we.tl/t-CHZG40wFrh

I hope the next update will address this issue and enable the processing of such recordings. Even though I occasionally use other programs for specific tasks, I'm a dedicated Vegas user and would like to continue using it.

I would try to set the project properties to 25 fps, and preview it with the preview quality preview/half. Then you should be able to edit it in Vegas at least (depending on what you wish to do).

That clip is 100 fps. But otherwise the same avc 422 format as the 50 fps clip I already have from another recent thread. After I exploded it into an hour+ loop with a video concatenation script I usually use to join camera clips. Seem to be getting allot of complaints about that format lately... which should also go to the camera makers as well as the gpu makers. Though I doubt it'll get much traction from the gpu makers since the rest of the world is moving away from avc.

I agree with @Wolfgang S. on reducing the project rate. When doing slomo edits, even a lower rate works well... Vegas has presets for both 1/2 ntsc as well as 1/2 pal.

Sure the clip is 100 fps. But with the suggested settings, I achieve both a smooth playback and see no continuing playback after stoping the playback. Tested on my laptop.

Maybe that helps to edit the footage within Vegas Pro 21 b187, even if it is not a perfect solution but more a workaround.

Hi, just for the record, I get similar playback to you @Mobby but changing the project to 25fps as suggested it plays ok.