[ANSWERED] Refresh FPS and monitor / Stage Preview

[laurentR]

In Isadora 2 I was used to have multiple monitors ( or Stage Preview) in my control Panel, and to lower the refresh FPS rate to 5 in order to save some efforts for my computer. In Isadora 3, the option still exist for Monitor and Stage preview, but it does not affect the previews wich are still showing full frame rate. Am I missing something?

And what does it really change in terms of performance?

[Woland]

I think @mark might be the best person to answer this question

[laurentR]

@woland Thank you, I guess Mark might ;-)

I checked on 3 differents types and generations of Mac, running Sierra or High Sierra, and the problem is same. So I guess it is really a specificity ( bug? ) of 3.0.7

[DusX]

I agree that Mark will be the one that can tell you most accurately about any performance gains that limiting the FPS might offer in the current GPU based pipeline.

When it was CPU based, I know that limiting the FPS on these controls made for some substantial processing savings, but my experience with them since becoming GPU based is that its minimal.
I imagine its already in a GPU context, in the same way as the link rollover thumbnails are in the Scene Editor, and that whether or not they are shown in the output is of little importance processing wise. BUT I could be wrong.

In anycase I added this issue to our bug tracker as soon as you posted it.

[mark]

@laurentr said:

In Isadora 2 I was used to have multiple monitors ( or Stage Preview) in my control Panel, and to lower the refresh FPS rate to 5 in order to save some efforts for my computer. In Isadora 3, the option still exist for Monitor and Stage preview, but it does not affect the previews wich are still showing full frame rate. Am I missing something? And what does it really change in terms of performance?

Hi there, Mark here. Well, it for sure is a bug that the Stage Preview and Monitor controls do not respect the FPS setting. But it is not nearly as critical as the old monitor control which used CPU based bitmap images for rendering. Both the Stage Preview and Monitor controls were updated in Isadora 3 to use OpenGL textures when rendering their output. As long as your patch is using vid-gpu or vid-ci video streams, the performance hit rendering these images should be negligible. There will be a slightly higher performance hit if you're using vid-cpu video streams, because those CPU based bitmaps will need to be uploaded to the GPU (graphics card) for rendering.

Sorry we missed this during testing. But I don't think those settings are nearly as critical as in Isadora 2 and before. If you're having a different experience, then please elaborate.

Best Wishes,
Mark

[laurentR]

Thank you for all your answers. Since I am avoiding CPU stuff for long, I can't tell about performance issue in that case. But that's a very good news if we just don't have to worry about it ;-)

[Woland]

@mark said:

a bug that the Stage Preview and Monitor controls do not respect the FPS setting.

 I have logged this issue in our bug-tracker