That was a neat trick. Turns out that swfmill is producing flash files with only one frame in them, despite the fact that I specify multiple frames using the tags and the fact that the data for multiple frames is being packed into the files. It's also producing compressed files, which could be contributing. But aside from those two things and the objectid numbers the files are mostly the same.
However, when I changed my movie tag to <movie frames="32"> it worked just fine. ^-^ It really should be noted somewhere that if the number of frames isn't specified it'll crash MX or do Really Strange Things. Maybe when running swfmill simple, some sort of warning or error could be generated? Thanks again so much for your help. If the XML files from my two moves would be of any help to the developers, let me know. - Charles On Jan 15, 2006, at 5:52 PM, Mark Winterhalder wrote: > hi Charles, > > this looks perfectly good to me. the only thing i noticed, looking at > your script, is that you increment the depth for each image. i > wouldn't do that, since it results on the images being placed on top > of each other, i.e. in frame ten, there will be a stack of ten images > but only the latest is visible since it covers the rest. this would > have interesting effects if you worked with transparency, but probably > isn't what you're after. just leave the depth at 1, subsequent > images/clips will replace previous ones. > > anyway, that most likely isn't what's causing your problem. > what you could do, if you feel a little adventurous, is to generate a > simple sequence of, say, two or three images as you'd like them to > appear in flash mx, and then have a look at it's swfml-l output. > swfml-l is the lowlevel variant of the swfmill markup, very close to > the actual SWF format. you can get it like this: > > swfmill swf2xml input.swf output.xml > > then do the same with an example of the swfmill generated SWF that > won't load and try if you see where the difference is -- maybe you > notice something between the base64 encoded image data. > > mark > > > On 1/15/06, Charles Wardlaw <[EMAIL PROTECTED]> wrote: >> Hey, thanks for the reply. Yes, that's exactly what I'm after. >> >> I did a quick mod as you suggested, and this time I got a different >> result: The SWF *was* importable as an asset into the library of >> another project and it came up as a Graphic object and a bitmap, and >> not as an animated movie clip. But this is a step closer than >> before. I know all images are inside the SWF because a) it's 1.3 meg >> in size, and b) it plays fine in SAFlashplayer and in Firefox >> (although those two were true before I removed the library tags). >> >> Does the following look okay to you? This is the output of my script >> on a single image: >> >> <?xml version="1.0" encoding="iso-8859-1" ?> >> >> <movie version="6" width="720" height="480" framerate="24"> >> <background color="#ffffff" /> >> >> <frame> >> <clip id="kulippu0" import="0000.jpg" /> >> <place id="kulippu0" name="myKulippu0" x="0" y="0" >> depth="1" /> >> </frame> >> >> </movie> >> >> For a lark I tried removing the <background> tag to no effect. Also, >> if you don't place clips on stage the file is effectively empty >> according to Flash MX. In case you're curious, the python script I >> wrote is at http://ministryofdoom.org/cloud/foxfire/scripts/ >> img2swf.py. >> >> Anything else you think I should try? >> Thanks again, >> - Charles >> >> On Jan 15, 2006, at 4:20 PM, Mark Winterhalder wrote: >> >>> hi Charles, >>> >>> so, if i understand you correctly, you have a series of images and >>> turn them into a single SWF, one per frame? >>> >>> you don't actually need the library tag if you don't want to pace >>> the >>> images on stage with actionscript later on. just remove it from >>> around >>> the clip-import tags. i don't know why flash crashes, but that >>> should >>> eliminate one potential cause. setting the version to 6 shouldn't do >>> any harm, either, but isn't well tested -- just try it. >>> >>> hth, >>> mark >> >> >> _______________________________________________ >> swfmill mailing list >> swfmill@osflash.org >> http://osflash.org/mailman/listinfo/swfmill_osflash.org >> > > > -- > http://snafoo.org/ > jabber: [EMAIL PROTECTED] > > _______________________________________________ > swfmill mailing list > swfmill@osflash.org > http://osflash.org/mailman/listinfo/swfmill_osflash.org _______________________________________________ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
