What build of 22 are you using? There could be a memory leak or another issue with the media decoding.

When it freezes do you get an error reporter box? Sometimes that has a useful clue.

@Venator I would advise to try converting all your images to jpeg first, then you import as you like in Vegas.... I always make it a point of duty, that whenever i am working with images from any varied source, to batch convert them to jpeg format. That way, there will be no hiccups in Vegas.

Have you read this POST?

Yes, but unfortunately didn't find a solution to my problem.

What build of 22 are you using? There could be a memory leak or another issue with the media decoding.

When it freezes do you get an error reporter box? Sometimes that has a useful clue.

239. Also tried to install 243, but it didn't help, so I returned to 239. About an error box - mostly it pops up, but sometimes do not and I have to shut down Vegas with Task Manager.

@Venator I would advise to try converting all your images to jpeg first, then you import as you like in Vegas.... I always make it a point of duty, that whenever i am working with images from any varied source, to batch convert them to jpeg format. That way, there will be no hiccups in Vegas.

Yes, I think converting the images to jpeg can help, but then, as I understand, these images won't be 10-bit.

Thanks for sharing the problem report- no obvious clue here (sometimes the fault module is useful). I hope you submitted the errors.

What is your GPU?

I just checked and my Sony also shoots this format. I'll try a timelapse and see if I can generate a similar error. Roughly many images do you need to have before the problems show up with rendering? (thousands? 1 minute is 3600 frames at 60fps).

Also happy to try to render your folder of images if you can make them privately available.

 

1.    Enabling “allow legacy GPU rendering”

Surprised this is still in VEGAS. Instead of this try MagixAVC with Mainconcept (CPU only) vs NVENC, etc.

2.    Turning off “acceleration of video processing”

Good to know this didn't work.

3.    Turning off real-time antivrus scan

Wouldn't expect this to do anything.

4.    Enabling “legacy AVC decoding” and “experimental HEVC decoding”

I wonder if any of this has any effect on stills decoding; I would doubt it.

5.    Turning off video preview while rendering

That's not likely to do much these days; it's no longer using GPU resources from my understanding.

What is your GPU?

NVIDIA GeForce RTX 3070 Ti Laptop GPU

I just checked and my Sony also shoots this format. I'll try a timelapse and see if I can generate a similar error.

That would be great, thank you!

Roughly many images do you need to have before the problems show up with rendering? (thousands? 1 minute is 3600 frames at 60fps).

If I start rendering from the beginning, it always fails at around frame 2790 (each frame is a different image). Nothing of what I did had any effect - rendering fails strictly at that point, not earlier and not later.

Also happy to try to render your folder of images if you can make them privately available.

Yes, I can send you that folder. Would be very interesting to see if you can render it.

I'm not even able to import it as an image sequence - just got a memory error though as you can see I have plenty of VRAM and RAM available. (Using 22.243 here on my RTX 4060 laptop).

Will try again tomorrow.

@Venator said: "... it always fails at around frame 2790..."

Try this:

1. Use markers to divide your "3-minute video" into 30 second segments.
2. Select the video between each of the markers and render to Apple Pro Res 422, HQ or XQ (pick your poison) naming the files Segment 1 through Segment n.
3. Combine Segment 1 through Segment n in a new Vegas Pro project.
4. Render the new project to your desired output file type.
5. Report

I'm finding VEGAS (21, 22) can't read this media correctly and is getting the resolution wrong (is it only reading the thumbnail preview)?

MediaInfo says it is this but VEGAS says it's 320x180. Windows Photos also sees it as 320x180.

My recommendation until VEGAS support is fixed would be to convert them all to 16-bit TIFF or PSD which VEGAS can read without issue.

@Venator said: "... it always fails at around frame 2790..."

Try this:

1. Use markers to divide your "3-minute video" into 30 second segments.
2. Select the video between each of the markers and render to Apple Pro Res 422, HQ or XQ (pick your poison) naming the files Segment 1 through Segment n.
3. Combine Segment 1 through Segment n in a new Vegas Pro project.
4. Render the new project to your desired output file type.
5. Report

When I split my video into small fragments (about 30 seconds), I can successfully render each of these using my initial render settings (4K 60 FPS, MAGIX AVC/AAC MP4). Your render settings also work with no problems.

But when I try to render a whole video, without splitting, Vegas fails both with my and your render settings.