File size optimisations, Animate, OAM, Muse

hi,

 

i'm hoping might have suggestions file size optimisation in above workflow. comparing output animate cc 2017 html 5 same as3. animated header responsive site ios game, flash not option (good name movie???)

 

the issue i'm having (summary: oam file big) seems relate animate / muse doing pretty dreadful job of packing assets export. i'm assuming limitation either of oam or html 5, either way seems increasing overall file size of output, not reducing it. symptoms duplicate data, poorly packed sprite sheets , others.

 

if has optimisation method above workflow appreciated. otherwise i'm going quills, magic markers , carrier pigeons.

i guess i've answered own question; of solution may sophomoric i'll mention here in case else finds useful. underlying problems i) in coming @ flash background ii) publish dialogue being bit on clunky side iii) not being able find documentation on specific issue.

 

so, animation 7.8mb 1.6mb, bear in mind html 5 not appear able use nice flash tricks such having jpeg masks alpha channels. seems therefore idea sort background elements can flattened jpeg images , accept transparent pngs going pretty full-fat in final output.

 

all of usual image-specific optimisations still seem apply, right-clicking in library , deciding images can highly compressed using photo jpeg still valid. however, separating jpeg content transparent pngs , treating them separately seems helpful too.

 

the kicker though, , i'm guessing bunch of people have been looking @ previous post, knowing already, , figuring out polite way tell me, need select 'both' when exporting sprite sheets. hindsight pretty dam' obvious, hindsight everything. can afford crunch jpegs quite considerably, of course pngs alpha you're stuck if animating transparent elements, best optimisation available seems to contain these components within single sprite sheet (if possible).

 

with respect clunkiness of publish interface, issue me within target folder overwrite files not delete unused content. turned out useful in so-called optimisations caused html folder examining jump in file size couple of megs, making cause obvious.

 

so seems work; html 5 isn't quite bad thought was, , apologise nice people @ adobe questioning parentage

More discussions in Adobe Animate CC - General

adobe