Transport Bug?

I've got the tryout version installed and I don't understand what's going on with the transport buttons?  There are two of these, both configurable.  Two of the configurations are 'Play from cursor to end of file' and Play from cursor to end of view'.  These work as expected, unless you have a highlighted section - at which time both options will only play that section.

This is not how it has always worked before.  Although they weren't configurable, the play button would just play the highlighted section and the other one (with circle around it) would play from the beginning of the highlight to the end of the file. My whole work model is based on this function working as it used to - any ideas?

Also, while I'm here, I set up a hotkey combination of Ctrl+Space to play preroll+postroll and skip selected area (nice feature, not before time).  This combination is usually the Record/stop toggle, so I deleted that reference.  Even so, when I tried it out, it recorded over my file!  I couldn't find any way around this and ended up having to assign another combination to the function I wanted.  I note, although the original hotkey has now been removed, the thing still drops into record if you press it - that can't be right?

Same thing here. You found a real bug!  Better send this one off to Adobe.

Same thing here. You found a real bug!  Better send this one off to Adobe.

No need - it was bugged right at the end of the development cycle, too late for a release date which couldn't be altered. This is the downside to this particular sorts of schedule - the SW has to go out, regardless.

Same thing here. You found a real bug!  Better send this one off to Adobe.

No need - it was bugged right at the end of the development cycle, too late for a release date which couldn't be altered. This is the downside to this particular sorts of schedule - the SW has to go out, regardless.

Ahhh, I see.  Does Adobe have a list of "known bugs" anywhere?  Might be a helpfull thing to have.

Same thing here. You found a real bug!  Better send this one off to Adobe.

No need - it was bugged right at the end of the development cycle, too late for a release date which couldn't be altered. This is the downside to this particular sorts of schedule - the SW has to go out, regardless.

Ahhh, I see.  Does Adobe have a list of "known bugs" anywhere?  Might be a helpfull thing to have.

Absolutely! What else is already "known" but not being talked about?

Chris

Absolutely!

I have to tread a little carefully here... and I'm afraid that the answer is absolutely not.

Ahhh, I see.  Does Adobe have a list of "known bugs" anywhere?  Might be a helpfull thing to have.

If there is such a list, it's a) not a public document, and b) it's quite difficult to define some of the things that reportedly happen with any software on different systems as absolute 'bugs' - because they simply don't affect some machines/users at all, anyway.

The general feeling is that Adobe are quite happy to register the bugs that users find. I certainly don't know what all of them are (does anybody? When has there ever been a perfect software release anyway?), but some I am aware of - and those I will indicate when you find them.

I nearly wrote a long spiel about why this is, but most of the reasons you could work out for yourself, if you approached this logically. But I can tell you that it has been agreed as a sensible policy not to reveal what's known about bugs, but to let users find them themselves. Report them on the forum, and if they are known about by anybody in the know, this will be indicated as such. If I know about them, Adobe certainly do - but the opposite is not neccessarily true at all. And that's really why a list won't be published - none of us could ever know that it was definitive. It's better to deal with things when they come up, and make a decision as to whether to pass them on based on current extant knowledge, rather than give a list that people might not bother to investigate much further. Yes it encourages you to investigate more - but Audition's recovery from errors is actually pretty good - serious damage is extremely unlikley, and I'm sure that the added input will be useful to Adobe developers.

Now, you might disagree with this completely - but that's what the present policy is, like it or not. What I can say though is that if there is a change in this, you will get to know about it.

Not sure what we are talking about here in relation to bugs, as Graeme mentioned two quite separate matters.

My understanding is that not playing beyond the boundaries of a selection under any circumstances is newly designed behaviour.  Whether this is to bring Audition into line with other programs I don't know, but there it is.  Tap the left arrow key to clear the selection and play from its start, or the right arrow key to play from its end.  Note also that the two play buttons default to the reverse of the behaviour in previous releases.  As in previous releases, right click on them to change their behaviour.

Transport Record/Stop toggle being hardwired to Ctrl/space seems to be a bug which I personally hadn't noticed before.

Not sure what we are talking about here in relation to bugs, as Graeme mentioned two quite separate matters.

I was referring to the ctrl+space "bug".  The behaviour of playback within/out selections has changed; not sure if I'd call it a bug.

When has there ever been a perfect software release anyway?

You're right, there never has and never will be a "perfect" release of any software.  I have seen many companies release or post bug/problem lists.  It's not a necessary thing, and probably 90% of the time I'd just skip over it.  There were a few times that I've run into problems with other software and I was able to see that the company was well aware of the issue.  So you carry on and work around it (or forfeit use of the application).

If it's Adobe's policy to keep it to themselves....then that is just what they'll do!  I was getting ready to search to see if such a list existed, but I thought I'd ask here first.

The behaviour of playback within/out selections has changed; not sure if I'd call it a bug.

It doesn't do what the menu says it should do - that's a 'bug' in my book.  Besides, why change something that worked?