I’m facing the following issue: I have some animations of white lines in PNG format at 12 frames per second (fps). The problem occurs when I change the color of the lines using the color themes; it significantly slows down the animation. What would be the solution to this?
It seems that the frame rate (fps) is not the root cause of the issue. I tried creating the animations with a lower frame rate of 2 fps, and they still experienced the same slowdown when the color theme was changed.
1 Like
Is it just the animation that slows down or the overall performance of the watch?
If you switch back to the standard color, will the watch work normally again?
What smartwatch you use?
1 Like
I use the Galaxy Watch 4, although I don’t think the problem is the model, when it is retuned to white it doesn’t present problems, it must be the commands I use for the animation, example:
([SEC_MSEC]>(0.1+(5*(floor([SEC]/5)))))([SEC_MSEC]<=(0.175+(5(floor([SEC]/5)))))?100:0
([SEC_MSEC]>(0.175+(5*(floor([SEC]/5)))))([SEC_MSEC]<=(0.25+(5(floor([SEC]/5)))))?100:0
([SEC_MSEC]>(0.25+(5*(floor([SEC]/5)))))([SEC_MSEC]<=(0.325+(5(floor([SEC]/5)))))?100:0
It is part of the commands in the opacity box for an animation that lasts 5 sec to then rotate to complete the 60 sec of the min.
The solution that I see for the moment is to make the animation for the 60 sec, even if it means the increase of memory. Or maybe consider not making color changes in the face watch.
1 Like
For starters I can not get your formulas to work in a test .
You have to highlight them and then hit </> in the message formatting . That protects them form being corrupted in the transfer to here . I am one of those that can only help if I can test . Make sure the Pixel count of your images is not too high .
.
([SEC_MSEC]>(0.25+(5*(floor([SEC]/5)))))*([SEC_MSEC]<=(0.325+(5* (floor([SEC]/5)))))?100:0
.
This works . So I am getting a 75ms flash in 5 seconds . on one test image .