|
theimage.com | how to facet |
| gemstone main | cabochon creation | |
| min data |
|
Animation of Gemstone Page 3
|
|||
| Helping compression with physical changes. Without getting into the precise way that compression works, there are a couple of things that can aid the file size if they are done even before the file is compressed
Compression codecs look at each sequential frame and determine what is being changed, large background areas (that are not changing from frame to frame) really compress well. If the object in motion is limited to a small area of the entire frame, then the remainder of the frame will compress to a higher degree. In this first example it was as simple as making the base (that the stone was setting on) non-reflective. The reflection in the original was changing from frame to frame with the moving stone. If there is no reflection then the area under the stone gets very little change. (See first image below - no reflection.) |
|||
| Original animation 16 fps
with reflection size: 2.1 MB New animation 16 fps without reflection size: 1.7 MB |
|||
| The next example shows the stone off center. If the stone moves more throughout the image, then it causes more overall change from frame to frame. This builds up over time and makes the file size somewhat larger. | |||
| Original animation 16 fps
with reflection size: 2.1 MB New animation 16 fps off center stone placement size: 2.28 MB |
|||
| So two things you can do to reduce size (or at-least avoid larger sized files) are center the motion as much as possible, and make the backgrounds solid and not reflective. | |||