Audition 3.0.1 bugfix patch

After - well, quite a long gestation period, Adobe are very pleased to announce the release of a patch for Audition 3.0., and you can download it here.

I have to say that this should fix quite a number of issues with a lot of different installations. Personally, I haven't managed to get the patched version to crash at all - and I have been trying for some time!

But apart from any other considerations, this is certainly an act of good faith from Adobe - despite what many have suggested, they have listened to the problems that people have been having, and have acted on them. Nobody is trying to suggest that this is the be-all and end-all of patches, or that it fixes absolutely everything, but I happen to know that the list of what's been attended to is pretty long (it's on the web page if you scroll down) - which is why it's taken quite a time to test and release. Most of these things aren't huge - mostly more like 'annoyance' size, but hey, I think it's worth it.

Thanks for the link, Steve.

RMS statistics still not fixed?

RMS statistics still not fixed?

Well, it's not in Adobe's list, but it's been mentioned before in one of my intermediate ones - so we'll have to try it and see...

Well, it's not in Adobe's list, but it's been mentioned before in one of my intermediate ones - so we'll have to try it and see...

So it's likely it's been fixed.

Do you know how to reliably replicate the bug? When I encountered it, I was unable to find out how to produce it consistently, I suspect that it might even depend on the contents of memory around the area occupied by the audio data. Which means that even if I can see the error with a file on a non-updated copy of AA, getting no error on the same file on an updated copy does not prove that it has been fixed.

So it's likely it's been fixed.

Well, enquiries have been made - let's put it like that!

Do you know how to reliably replicate the bug? When I encountered it, I was unable to find out how to produce it consistently, I suspect that it might even depend on the contents of memory around the area occupied by the audio data. Which means that even if I can see the error with a file on a non-updated copy of AA, getting no error on the same file on an updated copy does not prove that it has been fixed.

Somewhere I do have replication steps, yes - but it will have to wait until tomorrow. The good way to do this wasn't mine incidentally - but I think I have a note of it, anyway.

Well, enquiries have been made - let's put it like that!

And indeed, I got an answer. It was fixed, and then for a series of complicated reasons (possibly unrelated), it got 'un'fixed again. I have been assured that this situation is known about, and in the fullness of time it will be repaired. So, for the moment, you can't trust the RMS values in the stats at all, I'm afraid.

And indeed, I got an answer. It was fixed, and then for a series of complicated reasons (possibly unrelated), it got 'un'fixed again. I have been assured that this situation is known about, and in the fullness of time it will be repaired. So, for the moment, you can't trust the RMS values in the stats at all, I'm afraid.

Thanks for explaining! Un-fixing something already fixed seems a bit weird. Anyway, I have already written an equivalent procedure in matlab which is even more suitable for batch processing, and can be more easily included in more complex procedures.

damn!  I'm fairly speechless . . . not my typical experience with Adobe to even acknowledge that their software could possible present anomalies that needed to be addressed

no matter the issues the patch addresses I'm happy that Audition folk got Adobe to release anything at all

(& I spend so little time on Adobe web sites it's unlikely I'd discover it anywhere but here so thkx t' forum yet again)

Un-fixing something already fixed seems a bit weird.

There were good reasons for this, I believe.

Un-fixing something already fixed seems a bit weird.

There were good reasons for this, I believe.

Pity you signed that NDA!