I’m optimizing a project and there are two behaviors in TD that I don’t understand.
The first is that it seems to be adjusting its performance to the project’s FPS, which causes it to drop some frames when there’s a processing spike. That is, if I set it to 50, sometimes it drops to 49 or 48; however, I can set it to 60 and the percentage of dropped frames is the same.
The second is that there doesn’t seem to be a direct relationship between the number of active base comps and the project’s performance. At a certain point, when I have many base comps activated, there is a drop in performance, but up to that point, I can increase the computational demand without a progressive decline in performance.
To clarify this second point, I’m sharing a screenshot of the project, where you can see the different base comps that I activate from top to bottom. Each of them has an output to Spout.
from just this description it’s hard to pinpoint something with certainty but a good test is checking with the Performance Monitor when Framedrops occur (you can use the Frame Trigger Option to only give you a cook chain Performance Monitor Dialog - Derivative)
Another point would be that framedrops can happen when running in the editing network while when outputting content in Perform Mode, those might disappear (Perform Mode - Derivative)
Further have a look at the article on optimization and see if you can pinpoint the source for the higher frame times.
Thank you for the tips. I´ve already use the performance monitor and the probe tool. But what I can´t really understand is the why the overall perfomance is being afected for the FPS of the project. That is, that the porcentage of dropped frames is the same with the project at 50 or 60 FPS…
