MacEachaidh wrote: And unless I'm wrong, AA has never been part of any Creative Suite so far anyway. Hasn't that been Soundbooth's role, and Audition was left as a specialist pro-level app? I'm afraid that history didn't work quite like that, but for your edification (and the fact that from your last post you seem to have an eminently sensible approach to upgrades), I'll relate the later chronology for you: Audition was put into CS development after 1.5. And this resulted in what could only be regarded as some sort of late beta that got accidentally released - AKA Audition 2. What happened was that corporate planning and code development didn't coincide at all, and as a release it was rushed out with unseemly haste to meet the corporate deadline. All the other progs in the suite only needed a bit of tweaking to meet that particular release date, but Audition was getting a complete rewrite, so this really wasn't fair on the developers at all. End result - Audition got out of the CS cycle, and Audition 3 was created and released as a separate entity again - but only when it was ready. Being in CS in itself doesn't matter - but being in the corporate release date structure certainly does. Anyway as a sort of compromise, when Audition got out, the developers agreed to create a cross-platform app that would be in the suite permanently - and that's how Soundbooth came to be. End result is that one development team has to develop both products, so major releases of either inevitably take longer to achieve. This does make commercial sense, because the apps are different in their stated intentions and to an extent, their operational approach, but being developed by one team each product 'informs' the other to a degree. And from a corporate POV, I suppose that managent is happy, because they get extra leverage from the team. But as far as releases in general are concerned, Audition 3 works fine. Audition 1.5 works fine, and for some applications has advantages. You can use the software, and it doesn't need constant updates to keep it working without regular disasters. There's a comment on AudioMasters that attempts (in a tongue-in-cheek way) to suggest that software development should all be done the Microsoft way, where they have to keep releasing bugfixes for their bugfixes, and Adobe have sensibly not gone down that route at all. They get it pretty much right at the initial release, and don't issue any service packs until either there is a pressing need for a particular fix (rare) or a cumulative pile that can be done in one hit (also rare, but has happened with 3.0.1). If you are using this software as any sort of a revenue generator, and have clients around, then the last thing you want is software that you have to keep updating, and you aren't really sure of the status of. And that's why the Audition release model is the way it is - and long may it continue like that.
... View more