You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great plugin btw!!! Until now, I used the Octolapse plugin only for adjusting my camera settings and not for timelapses :-)
My suggestion:
Let us modify Camera settings "on the fly": Let the settings window appear when a button on the main screen is pressed and/or better: let it run in a tab on the right side of the window.
It is a bit fiddly to go into the settings menu, choose your plugin and then adjust the settings...
Keep up your good work!
Best regards,
Peuqui
The text was updated successfully, but these errors were encountered:
It's location in the settings is deliberate. The expectation is that most users will access the camera settings fairly infrequently after getting the camera setup and that it really doesn't warrant the space on the 'main' screen that could be used for things that a user would interact with more frequently.
Hi and thanks for your fast reply!
Sure, for most users, the position in the settings may be suitable.
Unfortunately, I need to reconfigure my camera settings fairly often to reflect the situation of lighting. E.g. lighting changes in regard of the size and color of the 3D print and the ambient light brightness.
Suggestion:
You can add a button in the settings window, where everybody can choose, if one wants to add this really nice feature to a tab or not.
Great plugin btw!!! Until now, I used the Octolapse plugin only for adjusting my camera settings and not for timelapses :-)
My suggestion:
Let us modify Camera settings "on the fly": Let the settings window appear when a button on the main screen is pressed and/or better: let it run in a tab on the right side of the window.
It is a bit fiddly to go into the settings menu, choose your plugin and then adjust the settings...
Keep up your good work!
Best regards,
Peuqui
The text was updated successfully, but these errors were encountered: