After adding the foundry camera solver there has been an immediate issue brought up whenever hitfilm autosaves or I manually save. As hitfilm's save function requires that all processes other than the render engine to stop, data from the camera solver need to be saved as well. This can be ALOT of data and the time to save is directly reflective off it. A single-camera solve can cause save times upwards of 15 seconds. Which is a nuisance if you plan on having an autosave interval of 1-5 minutes. It only gets worse from there. It frustrates me especially when I am sharing my progress with a friend and "ITS AUTOSAVE TIME!!!" followed by an awkward pause as we listen to an audio stream with a frozen screen. Therefore I propose that the save function be paralleled so that there is no impact on editing at all while it happens. I dont know how difficult this is to implement or if its even possible. But I would like some optimization to the save system.
Testing was done on system with specs: CPU: R9 3900x, GTX1070, (editing drive - ADATA500gb NVME), 32GB RAM, Windows 10.
Tracking settings: # of features: 150, total tracking frames: 1119, Clip format: 4k 60fps.
Total project file size: 53.3MB
Save time: 8.5 seconds