2009/8/18 Nick Sabalausky <bus_mailingli...@semitwist.com>:
>> That's the one I've been using for about the last couple weeks. My usage
>> of it probably isn't a particularly taxing usecase (I'm just using it to
>> import some images and place them into flash 7 movieclips), but it seems to
>> be working fine for me (aside from the morph/multiple frames issue, of
>> course) on WinXP, 32-bit.
>
> Some additional information about my experiences with that build of swfmill
> (and comparisions with 0.2.12.4):
>
> - My project uses both png and svg images (the svg ones were created in
> inkskape), and they all work fine (jpg works for me fine too). I am getting
> a few "some svg features aren't supported before swf version 8" warnings,
> but it hasn't actually been a problem (and I'm using flash 7 anyway, plus
> I'm saving using inkscape's "Inkscape SVG" rather than "Plain SVG"). On
> 0.2.12.4 I get a few other swfmill warnings ("WARNING: shape not closed;
> closing (...some coords here...)" and "DEBUG: accumulated rounding error
> (...some coords here...)") that your build doesn't give me. I assume that's
> an improvement. :)Yes, it's quite valid not to close paths in SVG (there's an implicit line back to the initial co-ordinates). I believe this was one of Ralf's fixes. > - I just tried changing a couple of my mp3's from externally-loaded to > built-in via swfmill. They are 128kbps, stereo, 44khz and just under a > second in length. On your build they work perfectly fine. On the old > 0.2.12.4, they play all garbled. The build I've uploaded in the last few hours should also support 22kHz and 11kHz MP3s, and any bitrate supported by MP3 for those sample rates (thanks Robin!) > - I used Audacity to convert those mp3's to wavs (16-bit, stereo, 44khz, > pcm), but on both your build and 0.2.12.4 I get "WARNING: Cannot import > assets/switch_on.wav (unknown extension), skipping" and (predictibly) they > end up being silent. This should work on the very latest build but to tell the truth I haven't actually tried it yet! (Thanks again to Robin). > If there's anything else that would be helpful to you for me to try, I'd be > glad to give it a shot and report my results. I've found it fairly easy to introduce catastrophic breakage with apparently innocent changes to the build scripts. For example, swfmill simple was completely broken in trunk for quite a few weeks, and I was happily using broken builds without noticing. Therefore, at this stage it would be reassuring just to know I haven't somehow broken your usual workflow :). Cheers, Dan. _______________________________________________ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
