-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bug: Framerate of videorecoding is not intuitive #303
Labels
bug
codeReadyForRecheck
The issue is fixed/implemented AND merged into development, but needs to be rechecked there
Milestone
Comments
wurzelkuchen
added
bug
docsNeeded
The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
codeImplementationNeeded
This issue requires a change in the code of Neodymium
labels
Nov 7, 2024
4 tasks
oomelianchuk
added a commit
that referenced
this issue
Nov 13, 2024
oomelianchuk
added a commit
that referenced
this issue
Nov 13, 2024
oomelianchuk
added
codeReadyForMerge
The issue was implemented and the branch is ready to be reviewed and merged into develop
and removed
codeImplementationNeeded
This issue requires a change in the code of Neodymium
labels
Nov 19, 2024
oomelianchuk
added a commit
that referenced
this issue
Nov 26, 2024
oomelianchuk
added a commit
that referenced
this issue
Nov 27, 2024
oomelianchuk
added a commit
that referenced
this issue
Nov 28, 2024
into #303-framerate-of-video-recoring-is-not-intuitive
wurzelkuchen
added a commit
that referenced
this issue
Nov 28, 2024
…ng-is-not-intuitive Bug: Framerate of videorecoding is not intuitive #303
wurzelkuchen
added
codeReadyForRecheck
The issue is fixed/implemented AND merged into development, but needs to be rechecked there
and removed
docsNeeded
The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
codeReadyForMerge
The issue was implemented and the branch is ready to be reviewed and merged into develop
labels
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
codeReadyForRecheck
The issue is fixed/implemented AND merged into development, but needs to be rechecked there
Quick Description
When we capture a video or gif, the playtime of the recording does not match the real time.
We currently only have
video/gif.oneImagePerMilliseconds
as a property to configure the delay between to images. This property changes the duration of the video, which should not be the case. It should only affect the framerate.Actual Behaviour
If i record a video of a test with a runtime of X seconds the screen recording is much faster than X seconds and highly depends on the
oneImagePerMilliseconds
property.Expected Behaviour
If i record a video of a test with a runtime of X seconds the screen recording should have a duration of X seconds. Changes in the
oneImagePerMilliseconds
property should not change the playback duration.The text was updated successfully, but these errors were encountered: