Flame 2025 Rocky Delay / hanging when selecting clips

Flame Flame Questions
, ,
1

Hi everyone,
I’m having issues with a long delay when selecting clips. Working along fine, then I click on a clip on the desktop, in batch, where ever, and there is a long delay, 15, 20 seconds, before the clip is selected. This happens throughout the day. Support checked the Resource Manager to see if GPU was full, but this happens whether it is full or not. Also happens with clips cached to local nvme storage. This is intermittent though. GPU is RTX A6000, machine is a Lenovo P620, Threadripper, 256GB Ram. Just updated to Rocky and 2025. This was not happening on Centos 7 2023.
Is anyone else experiencing this?

Thanks,
Andrew

2

Hey @andrew_heropost
I have a similar rig, 2025.2.2 running on P620, A6000, Threadripper, 256GB, Rocky 8.7 and no problems.
Is it one specific project/user?
Do you have other systems connecting to your framestore?
IP conflict?

I’m sorry, I don’t have enough experience to comment on OS configuration issues.

3

Out of curiosity, what types (wrapper, codecs) of media do you have in the project? I know you said it happens even when cached, but I assume the media was originally brought in linked?

I have similar issues at random but have never completely narrowed down the cause but have my theories.

4

My frame store is set to ProRes4444. I’m assuming everything is being converted to that when cached.

5

I do have an NFS connection to a mac and also to a Windows server.

6

I mean what are the original file types of the source material?

7

Files types vary, but usually ProRes 4444 from a color correct session. But also, Red files, Alexa files, MXF. It doesn’t seem like a file type issue.

8

Long shot. Do you have any color management changes in the Flame Setup app?

image
image1918×1316 148 KB

9

It looks just like your image. What should it look like?

10

Long shot, are these clips from an external archive?

We experienced this when moving to 2025 on jobs where the project was started offsite and moved onsite via cached archive. It was looking for the wiretap gateway of the original machine, rather than the current machine. Changing restore option to Convert to Local Path seemed to fix in some, not all, instances

11

This project was not an archive restore from another machine, but I have run into this, and will look into the Convert to Local Path feature. That is good to know. Thanks!

12

I believe this is related to an NFS share with my server.