Quote from
RichardF on 3. June 2021, 16:31
The problem for that is that the frameranges of shots are saved in a configfile and configfiles are getting cached in memory in Prism to improve the performance. When one user updates a config, other users, which have Prism already open won't see the updated information unless they clear their configcache.
The easiest way to clear the config cache is to rightclick on the refresh button in the Project Browser.
If that is still a problem I could add the option to disable the caching completely. Depending how you share files with your team that might have a big performance impact or no noticable impact at all.
The problem for that is that the frameranges of shots are saved in a configfile and configfiles are getting cached in memory in Prism to improve the performance. When one user updates a config, other users, which have Prism already open won't see the updated information unless they clear their configcache.
The easiest way to clear the config cache is to rightclick on the refresh button in the Project Browser.
If that is still a problem I could add the option to disable the caching completely. Depending how you share files with your team that might have a big performance impact or no noticable impact at all.