Error: Twitter did not respond. Please wait a few minutes and refresh this page.
Tagsaccessibility Adobe AIR Alchemy Apollo AS3 ASR ASV blogging captionate chromatic dead decompile developer encrypt flash Flash Builder Flash Killer Flash Paper Flash Platform flash specs Flex Flex Builder FLV FLV specs free guitar tuner JSFL Manitu Group multi-core obfuscate online open flash open SWF Player poster premium features silverlight SWF SWF 9 SWF specs tuner UAE vista XAMDF
Tag Archives: ASV
Today, we released the 12th anniversary edition of ASV¹ (ASV 2012/05) and also SWF Revealer 2.08 update.
Thank you all!
Update (2012/05/17): To add some value to this dull post:
In the first days, people sent us their own SWFs to get back the decompiled AS, in order to believe that ASV really worked as advertised. We required people include their name in the SWF so that we know it’s their own work…
Here are the samples we had on our site:
ASV 1.0 with SWF v4
movie2.swf (~6k), by Scott Romack, submitted on May 30, 2000.
movie2.txt (~2k) ASV 1.0 text output.Notable notes: This was the first ever sample we had. “Note the line Duplicate Movie Clip (“motion”, “motion” & x, x + 16384) The value added in Duplicate Movie Clip action is actually in the SWF and ASV 1.0 showed this. Later versions of ASV hides this value in order to make its output more compatible with Flash.“
ASV 2.0 with SWF v4
curvers9-1.txt (~8k) ASV 2.0 text output to Flash 4 syntax
curves9-2.txt (~7k) ASV 2.0 text output to Flash 5 syntaxNotable notes: Also demonstrated ASV 2.0′s ability to convert v4 AS syntax to v5 AS syntax.
ASV 2.0 with SWF v5
analog_clock.swf (~10k), by Marcos Pinto.
aclock.txt (~2k) ASV 2.0 text output.Notable notes: Demonstrated decompilation of the (then new) onClipEvent.
¹Action Script Viewer – the first SWF/Flash decompiler released on May 16, 2000.
So I haven’t been posting lately.
I was obviously busy, but main reason was (as I have written before) I didn’t want to sound like trying to sell more copies of ASV using my blog, and I didn’t want to post off-topic, but any on topic useful bits of info I could share was un-shareable. What was left was Adobe press release like news, like the recent Flash CS4 10.0.0.2 update, but I decided I didn’t want that long ago.
Of course, I can always post about hot topics of the day, like recent Flex Builder name change to Flash Builder. Well, I hate it and I think it’s wrong. Adobe is exploiting the ‘Flash’ name and I think it will not help the ‘Flash’ brand or the platform. A totally, absolutely wrong move – will cause lots of confusion in the long run* (so I totally disagree with KP on this one). OK I said it, it won’t change anything (other than maybe some people with strong feelings about this will start not having good thoughts about me).
A few months ago I even did an off-topic test blog to see if I can really post at least daily. I saw that I could.
Today is ASV’s 9th anniversary. I had to post, because I realized if I didn’t, some people might get wrong ideas about us, ASV, ASV’s future etc. We are on pre-release for quite some time now, for various reasons, but we are working and alive just as we always have been (We released last pre-release ASV just 16 days ago with improved SWF 10 and AS3 support). Second of all, I call myself ‘ASV Guy’, so this makes this post appropriate. And 9 years is quite a long time for any product.
I don’t know how often I will post here, hopefully my next post will not be exactly this day next year…
* Unless Adobe is getting ready to ‘phase out’ Flash IDE, the authoring tool, which would be a worse (or probably the worst) move and Lee Brimelow says this is not the case.
We will be changing version numbering of our products. Admitted, if we didn’t feel we have to do this, most probably we wouldn’t have cared at all.
For ASV, we started with version 1.0, in 2000. And major versions went like 2, 3, 4… We reserved .5 minor update for a somewhat very significant update and normally minor updates went like .01, .02, .03… Internal releases made us skip minor version numbers released and sometimes we increased the minor version to avoid confusion (People do confuse 5.1 and 5.01).
We synchronized ASV major versions with major Flash versions. ASV 1 supported Flash 4, ASV 2 supported Flash 5, ASV 3 supported Flash 6 (MX)… I personally liked this because it was straight forward and it made things simple. But this was mostly because Flash major versions were synchronized with major Flash player versions (and so SWF versions). After all, you created Flash (SWF files) with Flash (the authoring tool). Why should there be a major player release if there’s no tool to support the new features? Then there was Flex… (Flash was not the only authoring tool that can support a new player anymore).
Frankly, I think we still would be reluctant to change the versioning, if ASV didn’t lag behind. We currently have ASV 6 ‘pre-release’ version. Again, the most important reason it’s called a pre-release is probably because we don’t have the documentation/help yet. Otherwise any release version is also bound to have bugs/issues or some missing features. Current ASV pre-release can even open SWF 10 content (found on the web), displays a warning about the version because it’s not supposed to support SWF version 10. And of course new Flash release is near and skipping version 6 of ASV, because it’s released as pre-release versions, doesn’t sound good.
I never liked other naming/versioning schemes… Windows 95, Office 98, MX, CS3, Flash MX 2004 (version 7 which was released in 2003 BTW)…
One thing was sure, we would never use arbitrary letters or acronyms as the major version designator. Using year or date was surely better and then the date actually meant something. If the software is clearly dated, you don’t need any other version numbers. The developer assigns the numbers anyway and there’s no standard (We did skip ASR versions 3 and 4 to align it with ASV version. Some developers use odd/even minor version numbers for unstable/stable builds, we never did that because we never have unstable builds. Some skip versions 4 and 13 because of superstitious reasons. There’s no standard really).
So, it’s ASV 2008… We ourselves hated the way it sounded first. But make no mistake, it won’t be deceptive like dates on magazines. I never got used to reading a mag dated into the future… So, let months be another number of the version, and the day another. If you have ASV 2008/10 that will mean it’s released in October 2008. In the about box, you will see a verbose version string like 2008/10.14, where 14 will mean the date of release.
We are losing the arbitrary version numbers, version number will be the time stamp. That’s our solution and we believe it’s superior to arbitrary numbering, cuts the confusion and has many other advantages to both the developer and the users.
We always made updates free, and charged for some upgrades. Since our version numbers depended on new release of Flash (and then we needed some time for supporting the new Flash), you never new exactly when there will be a new major version. And because it was not feasible for us to work on many versions, usually what happened was that we stopped working on a previous version and started working on the new version. Bug fixes and improvements even for earlier versions of SWF went into the new version, old version just stayed as it is… We did have a grace period but someone who purchased ASV when a new version released did get longer free upgrades than someone purchased just before the grace period (and received the next version as per our ‘next version upgrade free’ policy). In short, using dates lets us offer things like: ASV with 1 year of free updates, or ASV with 2 years of free updates. There will be no ‘upgrade’ in the normal sense, major version number will change from 2008 to 2009, when 2009 comes…
Is this new? Not really. And most software do need major version numbers to indicate milestone releases. Ours didn’t, we have realized. Our version number (which will be the date) will mean that the software is what we had at that date, nothing more, nothing less.
Do you want to purchase a copy of ASV and see this in action? You’ll have to wait till mid-October…
All the above is quite condensed, I can write a small chapter about this change. Let me finish by saying that we will never inconvenience our current customers, they will get what we have promised at the time of their purchase and maybe some more because we would be cautious (rather than err) about this.
I moderate all comments. That surely stops any spam reaching ‘published’ state and to you, but I have to deal with them all. Most spam and inappropriate comments are not interesting at all. Here are two comments I received for my last post in succession:
Always enjoy reading this blog. Please keep up the good work.
Commenter name: jamie
Commenter email: firstname.lastname@example.org
IP address: xx.xxx.xxx.xxx
IP address shows this one’s from Florida. There’s no email, no pharmacy URL etc., nothing that would raise the red flag, but it doesn’t have any real content either. I guess this one might be from a spammer checking out if he can post a comment. I can even amuse myself thinking it’s from someone real who enjoys reading my blog…
The next one is a bit nasty:
Im sorry to hear that your quitting smoking Burak , if theyres anyone
who deserves lung cancer its you .
My new years resolution is to releace and promote as much copys of ASV
as i can . Poetic justice as far as im concerned now you know what it
feals like to have your work stolen
Commenter name: Raymond
Commenter email: email@example.com
IP address: xx.xxx.xxx.xxx
Raymond is from Texas, as it seems by looking at his IP. Obviously he doesn’t know how to spell and he uses a QWERTY keyboard. I’d guess he’s rather young. He ends kindly with his ‘regards’. His email address really isn’t random. You can guess the QWERTY layout even when someone is just pressing random keys wildly to make up a fake address, his address is not random in that sense, he probably keyed the address in neatly one key at a time… He uses a capital for my name and for sentence starts, which I find quite rare for this kind of a comment. Is he really angry or is he working for a cigarette company, I cannot decide. He’s after ‘poetic justice’, hmm, I don’t hear that phrase frequently, maybe he’s a bit older than I first thought… What do you think?
Raymond, I’m sorry if someone stole your work, but your comment is very rude. (And I had my work stolen, cracked, key generator-ed, translated to obscure languages, many times. I assure you I know how it feels).
We have just made ASV 6 Alpha1 available to all licensed ASV 5 users. It’s really an alpha release, very incomplete.
Still, we think it will not be totally useless. And with the future alpha and beta versions, we hope our users will help us finding issues (With this alpha1 release, there are so many known issues, we are not really looking for reports from our users).
For example, the AS3 decompile engine integration to ASV is not complete at all (and neither the decompile engine), so you’ll see timeline scripts as classes, where each frame script is a method. Most probably you won’t be able to see those classes in later builds and each frame script will show on its own frame…
These updates mainly enhance the decompile engine and fix some bugs. (No CS3/AS3 support yet, it will come with 6th versions and ASV 6 is expected to be available by July 16th, 2007).
I will keep this post short. ASV license owners: if you are also using SWF Encrypt 4, please test your protected SWFs with the updated version (and let us know if you find a bug). Thanks.
(We think most probably these will be last 5.x updates for ASV, UAE and ASR. Not that we won’t release updates if a serious bug is found. May 16th is ASV’s 7th anniversary, and I tend to think it would be a nice coincidence to have the final 5.x version released on that day…).
… If you have a Flash obfuscator, it’s easy to obfuscate SWF files in SWC files using your current obfuscator. You don’t really need to purchase a separate SWC obfuscator. And if you have a SWC obfuscator…
Another day, another update… How embarrassing! Nevertheless, this has happened before and we had to do what we had to do. We released updates, within 24 hours of the 5.20 updates, which fixes a single bug. Current versions of ASV, UAE and ASR are now 5.21…
This made me think why we don’t release updates more frequently… Obviously the reason is testing and quality assurance. This one bug was about having a one-too-many semicolon somewhere as a string constant – so it was an easy fix and required not much testing…
Speaking of updates, Ted Patrick’s post on Adobe Flex 2.01 update was quite enthusiastic…