b3ta.com board

Home » Messageboard » Message 10657789 (Thread)

it's the fade

it causes virtually every single pixel in your image to change in every single frame

(

Griffin Saver Something, something, 2006, something., Thu 12 Jan 2012, 10:52, archived)

(

prodigy69 broke b3ta and made everyone leave, Thu 12 Jan 2012, 11:08, archived)

I would agree with this

if you didn't do the fade it would work out much smaller in file size.

(

maiden is filmed before a live studio audience, Thu 12 Jan 2012, 11:12, archived)

Thanks.

I just assumed that as I'd saved each layer as a 25k file, reassembling them would be about 350K.
Didn't realise GIFs end up much bigger!

(

da5id <YOUR SIG HERE>, Thu 12 Jan 2012, 11:23, archived)

It's not about each frame but the blending between frames the more pixels that constantly change

the heavier the filesize I can't remember the name of the b3tard but he does those silhouette animations which have a massive canvas size but are extremely small on filesize because the only moving parts are the silhouettes which are usually smaller on the canvas this is a prime example of gif optimisation.

(

maiden is filmed before a live studio audience, Thu 12 Jan 2012, 11:27, archived)

this started as a 20k file and ended up 344k with the snow effect

it's the amount of pixel movement, it ramps up the file size