F5F Stay Refreshed Software General Software Is there a method to control video timing in 100ths of a second rather than frames per second?

Is there a method to control video timing in 100ths of a second rather than frames per second?

Is there a method to control video timing in 100ths of a second rather than frames per second?

R
Roccoboy8
Member
Find
162
11-10-2023, 08:01 AM
#1
I frequently log my bowling practice, but it's challenging to rely on the timing devices at various lanes. Some are inaccurate or positioned differently based on the center alignment. Others are located at the end, middle, and even some other spots. My goal is to calculate my average speed. This is straightforward—I can pause in Filmora at the release point and stop at the impact point to capture the time. The issue with Filmora is that it measures time based on frames per second, not actual seconds. For example: each second is represented by 30 frames instead of a precise second.

I understand the math is simple—take 70 frames and multiply by 0.033 for 30fps to determine my duration (about 2.31 seconds, or 31/100 of a second), then divide the lane length (60ft) by that duration to get my speed in feet per second, and finally multiply by 0.682 to arrive at my MPH.

However, using an online calculator has helped me find ball speed when I have the time in seconds measured in hundredths of a second. The challenge remains with Filmora: it doesn’t show time in hundredths of a second, only frames. This forces me to pause the video at the release point and manually count 70 frames or similar to reach the headpin, which can take hours for a single session.

I’ve checked if there’s an option in Filmora to adjust this setting during editing. I also tried measuring time at both the release and contact points, knowing each second is roughly 30 frames, but the results still don’t align perfectly. With all online tools and Filmora, it seems there are three different ways to measure a second—making it difficult without spending excessive time.
Reply
Reply
R
Roccoboy8
11-10-2023, 08:01 AM #1

I frequently log my bowling practice, but it's challenging to rely on the timing devices at various lanes. Some are inaccurate or positioned differently based on the center alignment. Others are located at the end, middle, and even some other spots. My goal is to calculate my average speed. This is straightforward—I can pause in Filmora at the release point and stop at the impact point to capture the time. The issue with Filmora is that it measures time based on frames per second, not actual seconds. For example: each second is represented by 30 frames instead of a precise second.

I understand the math is simple—take 70 frames and multiply by 0.033 for 30fps to determine my duration (about 2.31 seconds, or 31/100 of a second), then divide the lane length (60ft) by that duration to get my speed in feet per second, and finally multiply by 0.682 to arrive at my MPH.

However, using an online calculator has helped me find ball speed when I have the time in seconds measured in hundredths of a second. The challenge remains with Filmora: it doesn’t show time in hundredths of a second, only frames. This forces me to pause the video at the release point and manually count 70 frames or similar to reach the headpin, which can take hours for a single session.

I’ve checked if there’s an option in Filmora to adjust this setting during editing. I also tried measuring time at both the release and contact points, knowing each second is roughly 30 frames, but the results still don’t align perfectly. With all online tools and Filmora, it seems there are three different ways to measure a second—making it difficult without spending excessive time.

Reply
Reply
S
ShaneTV
Member
Find
162
11-10-2023, 08:49 AM
#2
I think it would be wise to reach out to Filmora Support.
https://filmora.wondershare.net/support.html
It seems unlikely that such requests haven't come up before, and they might have ideas for a practical fix.
Reply
Reply
S
ShaneTV
11-10-2023, 08:49 AM #2

I think it would be wise to reach out to Filmora Support.
https://filmora.wondershare.net/support.html
It seems unlikely that such requests haven't come up before, and they might have ideas for a practical fix.

Reply
Reply