-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time Settings #3683
Comments
XLights has always been known for the smartest users. This is how we keep the brain working…lol |
xLights also use "number of frames" in places which you have to multiple by the timing interval or inverse of FPS to get the length of time. Basic math knowledge is required. Maybe we should have a random math equation at startup to test users before use. |
The math to convert is simple, its just after many hours behind the keyboard the brain can start to get a little foggy and the time conversions harder to compute |
👍 |
Is your feature request related to a problem? Please describe.
Feature request is not related to a problem, just an enhancement to this already incredible software.
There are different time formats when in the sequencer tab -
In File/Sequence Settings, the "sequence duration" uses "seconds : thousandths of seconds (e.g. 300.200)
The timeline is set to display "minutes : seconds : hundredths of seconds (e.g. 5:00:20)
When right clicking on an effect and selecting "timing", it asks for milliseconds (e.g. 30020)
When using the Tools/Check Sequence feature, any effect problems are displayed as "minutes : seconds : thousandths of seconds (eg 5:00:200)
Describe the solution you'd like
A setting in "Preferences" that makes all time formats the same, versus having to convert time formats in your head. (Especially after a long night sequencing!)
Thank you, you guys rock!
The text was updated successfully, but these errors were encountered: