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
What was the reasoning behind why motion was downsampled to 20 fps? Is it because of compute constraints or you found 20 fps was optimal and enough to see complex ranges of motions?
The text was updated successfully, but these errors were encountered:
Hi,
Actually there is no specifical result for this. Primarily because all
motion databases (40fps, 80 fps) can be downsampled to 20 fps. And usually,
it's enough for visual effect.
On Sun, 10 Sept 2023 at 22:11, smandava98 ***@***.***> wrote:
Hi. Great work! I just had one simple question:
What was the reasoning behind why motion was downsampled to 20 fps? Is it
because of compute constraints or you found 20 fps was optimal and enough
to see complex ranges of motions?
—
Reply to this email directly, view it on GitHub
<#88>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKRYNBZOHH3GU6AIJW3UNKDXZ2FO3ANCNFSM6AAAAAA4SV6PXU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Hi. Great work! I just had one simple question:
What was the reasoning behind why motion was downsampled to 20 fps? Is it because of compute constraints or you found 20 fps was optimal and enough to see complex ranges of motions?
The text was updated successfully, but these errors were encountered: