| 2013-07-10 15:01:12 |
Colin Ian King |
bug |
|
|
added bug |
| 2013-07-10 15:01:12 |
Colin Ian King |
attachment added |
|
video of stopwatch https://bugs.launchpad.net/bugs/1199838/+attachment/3732215/+files/DSCF3397.AVI |
|
| 2013-07-10 15:04:28 |
Colin Ian King |
description |
Today's image on a Samsung Galaxy Nexus (which isn't the most snappiest fast device).
I started the stop watch and it is really painful to watch the 1/10ths of a second erratically count in steps that show that we have some non-realtime counting occurring. I took a 30 frames per second video (see attached) and broke it into individual frames using:
ffmpeg -i DSCF3397.AVI -f image2 image-%3d.jpeg
and observed the following stop watch time and number of frames each time was displayed:
Time Frames
0.26.1 4
0.26.3 3
0.26.4 5
0.26.6 7
0.26.8 4
0.26.9 2
0.27.0 5
0.27.1 5
0.27.3 3
0.27.4 1
0.27.5 2
0.27.6 3
0.27.7 5
0.27.8 6
0.28.0 5
0.28.2 5
0.28.4 5
0.28.6 2
0.28.7 3
0.28.8 3
0.28.9 3
etc..
At 30 frames per second we should see each 1/10th of a second change every 3 frames or so. Note that some times (0.26.6) are rendered for 7 frames (~0.233 seconds) and some timings (0.26.2, 0.26.5, 0.26.7) are not being rendered at all. The accuracy of the stopwatch is only about to ~0.25 seconds which is a bit poor.
Also, I find it visually disturbing that I don't see the 1/10th of a second count steadily, especially jarring when one sees a value on screen for ~0.233 seconds. That's easily jarring on the eye. |
Tested on today's image on a Samsung Galaxy Nexus (which isn't the most snappiest fast device).
I started the stop watch and it is really painful to watch the 1/10ths of a second erratically count in steps that show that we have some non-realtime counting occurring. I took a 30 frames per second video (see attached) and broke it into individual frames using:
ffmpeg -i DSCF3397.AVI -f image2 image-%3d.jpeg
and observed the following stop watch time and number of frames each time was displayed:
Time Frames
0.26.1 4
0.26.3 3
0.26.4 5
0.26.6 7
0.26.8 4
0.26.9 2
0.27.0 5
0.27.1 5
0.27.3 3
0.27.4 1
0.27.5 2
0.27.6 3
0.27.7 5
0.27.8 6
0.28.0 5
0.28.2 5
0.28.4 5
0.28.6 2
0.28.7 3
0.28.8 3
0.28.9 3
etc..
At 30 frames per second we should see each 1/10th of a second change every 3 frames or so. Note that some times (0.26.6) are rendered for 7 frames (~0.233 seconds) and some timings (0.26.2, 0.26.5, 0.26.7) are not being rendered at all. The accuracy of the stopwatch is only about to ~0.25 seconds which is a bit poor.
Also, I find it visually disturbing that I don't see the 1/10th of a second count steadily, especially jarring when one sees a value on screen for ~0.233 seconds. That's easily jarring on the eye. |
|
| 2013-07-10 15:06:36 |
Colin Ian King |
summary |
clock app: stopwatch tens of a second are not at regular intervals |
clock app: stopwatch tenths of a second are not at regular intervals |
|
| 2013-07-10 16:08:32 |
Colin Ian King |
bug task added |
|
ubuntu-power-consumption |
|
| 2013-07-10 16:08:44 |
Colin Ian King |
bug task deleted |
ubuntu-power-consumption |
|
|
| 2013-07-10 18:39:24 |
Nekhelesh Ramananthan |
ubuntu-clock-app: status |
New |
Confirmed |
|
| 2013-07-10 18:39:27 |
Nekhelesh Ramananthan |
ubuntu-clock-app: importance |
Undecided |
Medium |
|
| 2013-07-10 18:39:29 |
Nekhelesh Ramananthan |
ubuntu-clock-app: milestone |
|
coreapps-13.10-month-3 |
|
| 2013-07-16 19:03:02 |
Nekhelesh Ramananthan |
ubuntu-clock-app: milestone |
coreapps-13.10-month-3 |
usable-state |
|
| 2013-08-08 14:12:24 |
Colin Ian King |
tags |
|
rls-s-incoming |
|
| 2013-09-05 19:03:14 |
Nekhelesh Ramananthan |
ubuntu-clock-app: milestone |
usable-state |
coreapps-13.10-month-4 |
|
| 2013-10-19 16:12:48 |
Nekhelesh Ramananthan |
ubuntu-clock-app: milestone |
backlog |
1.4 |
|
| 2014-01-13 12:20:46 |
Nekhelesh Ramananthan |
ubuntu-clock-app: milestone |
1.4 |
backlog |
|
| 2014-06-04 14:44:32 |
Marc Deslauriers |
bug |
|
|
added subscriber Marc Deslauriers |
| 2014-08-27 11:27:55 |
Nekhelesh Ramananthan |
ubuntu-clock-app: status |
Confirmed |
Invalid |
|
