What bugs you the most about 2.0 AS IT STANDS?

[Please read and understand all of this post carefully before posting your own contributions.]

Please read and understand all of this post carefully before posting your own contributions.


Okay, I want you to think very carefully before answering this question - what I'm really looking for here is quite short lists from people - four or five items maximum, please. This is not an attempt to open a flood gate. Take your time - there's no mad rush for the answers.

Considering the Audition 2.0 feature set as it stands, what is it that you'd like Adobe to attend to improving or fixing the most? This isn't about what you'd like to see added - you can put those items in this forum separately anyway. It's about the perceived order of importance of things that currently bug you about the program as it is currently released.

Incidentally, Adobe didn't ask me to do this, and may choose to ignore it - although hopefully they won't. I just think that prioritising the things that annoy end users the most, and attempting to improve those, would be a good thing to try to persuade them to attend to, if you see what I mean. And some hard evidence might well help...


Please Note:

I will remove, as I have already once, all messages, or parts of them, that don't qualify in this thread. They will rather defeat the point of it. I may also edit for clarity.

Why? Because there's no way that Adobe will add features in a dot release, and initially I would like what's present now to work properly, or at least better. And I'd like a nice, clear list! I realise that there are one or two grey areas in this, and I'm happy for those to stand, I think, because they relate either to previous functionality now missing, or are considered to be an important missing part of a function that's already implemented.

For me, what seems to be the resource-hunger of the app - slow startup, fewer tracks supported than the opposition if the effects load is high, metering sluggish,asio oddities, and a general feeling that form has been given priority over the function.

I use AA mostly for editing, rather than recording and so haven't encountered the ASIO and other performance issues as much as others here.  So my main gripe would be the still-finicky VST plug-in support.  I understand perfectly well the AA is not a MIDI sequencer (and I don't want it to become one), and so pure VST instrument plugins don't need to be supported.  However, things are always so clear-cut in the world of VST plug-ins and there are several hybrid plugins available which aren't so readily classified as a "pure" effect or a "pure" instrument.  AA appears to reject these as VST plug-ins, even though they can be used to process audio.  Any MIDI capabilities that such plug-ins provide could be ignored by AA.  So, I would like AA to be less restrictive about which VST plug-ins can be used with it.

Toolbars - lack of color on buttons.

Poor toolbar customizability. I want to see only these buttons (not group of buttons) which I need. MS Office has had this for ages.

Slow start.

Sometimes crashes with "pure virtual function call" message. I experienced it while using lasso tool.

Crazy track placing when adding tracks in MV.

I'll echo Peter and Paweł for my list.
1) Performance.  As an example ... with 1.5 I have my desktop set for a large Freq and Phase analysis windows on my secondary monitor.  With 2.0 I have to shrink those windows WAY down to get clean playback.  Graphics overhead on 2.0 seems substantially greater than with 1.5, and I am not interested in trading performance for looks.

In some ways, 2.0 performance in great, but in other areas it's very poor.  Keep the good, fix the bad.

2) Placement of tracks in MV

3) Put color back in the toolbar.  It's too important for finding the right button BEFORE your mouse gets there.

4) Slow startup.

I would echo the plea for better performance. The whole idea behind ASIO was that it was a simpler and more efficient driver model. Adobe seem to have lost the plot here it seems. If the old version can do 16 tracks on a PII 233 with the less efficient MME drivers then any new version should be able to improve on this.

Following on from the performance issue, if Audition can't keep up then I want it to tell me - not to sneakily carry on recording with glitches in the resulting files.

I would also like to see all the external sync issues sorted out. As an extra I would also like to be able to sync to ASIO positions but just making MTC work properly would be a good start.

The play button behaviour also needs to be sorted out - it should work as it used to.

Effects automation for DirectX effects would be helpful.

The ability to cut and paste sections of automation data would be good.

That's all I can think of for now.

Cheers

James.

The play button behaviour also needs to be sorted out - it should work as it used to.

Right click on the tranport buttons to reset them to the old defaults (if I'm understanding the problem correctly).

The play button behaviour also needs to be sorted out - it should work as it used to.

Right click on the tranport buttons to reset them to the old defaults (if I'm understanding the problem correctly).

In edit view, when you select a portion of audio you can only play that portion, no matter what you select when you right click on the button. I seem to remember that SteveG acknowledged that this was a bug a while ago. I don't know if it happens to everyone but it has certainly happened to Steve and myself.

Cheers

James.

OK

1) Sort out the stupid way AA imports audio tracks and gives them silly numbering!

2) When you zoom in on a set of tracks keep those tracks on screen!

3) Make it possible to switch between effects rack and the mixer by clicking on the tabs instead of having to close the effects rack every time!

4) Simplify the Bus functions - now you have to select the bus, deselect the Master, increase the send level and adjust the pan for every single track, why not default to select bus, deselct Master, set send to 0 and pan as for the track?

1) The ASIO implementation should run much more efficient then it currently does.  It is sluggish, cannot handle effect loads that other programs can easily handle, and has sync problems when recording at higher buffer rates. This issue is my main annoyance, and hopefully, it will get fixed in the next release.

2) Choppy framerate on the meters.  Although i've read people here claiming that it is a video card issue, I doubt it, and rather think that this problem is actually tied into the 1st issue, the ASIO implementation.  

3) Fix the programming errors that result in occasional "Pure Virtual Function Call" crashes.

4) Reset the track numbering system to 0 when a session is set to defaut with no recorded audio, it seems like that would be common sense.  Or, alternatively, allow a "save session as template" that would do this.

5) Very slow startup time.

[live]

1) With AA1.5 I was able to apply Full Reverb to a bus, route several tracks to it and playback live. Now I can't, Full Reverb is obviously more of a resource hog (32 bit impulses probably) and is now unusable as far as I'm concerned.

2) A serious omission is a reasonable way to control presets. Whether migrating from an older version or migrating between machines, there needs to be a simple way of doing this.

3) Under External Controllers>Configure I see the option to remap my control surface switches to different Audition commands, but this doesn't work at all. This is not a new bug - it didn't work in 1.5 either.

4) Erratic meter behaviour in MT on playback - if a signal drops suddenly to zero, the meters keep "bouncing" for a second or so afterwards. This can be fixed with asio4all, but shouldn't need to be. Which brings me to:

5) ASIO implementation. I don't know whether Audition is really the problem here. Since asio4all fixes many of the problems, maybe the typical ASIO driver contributes to the problem. Still, don't some programs provide a choice of ASIO or WDM??

Yes, most of the above, but especially......

1. The external controllers end of things needs sorting out urgently. The combination of AA2.0 and the Tascam FW-1884 would be a killer if it all meshed together properly. The same goes, presumably, for other controllers.

2. Reducing the load on the PC, adding a WDM option (but maybe the onset of Microsoft Vista and whatever that does about audio will relate to this) and improving the look of the program would help a lot.

Would love to see the return of the option to mixdown to a temporary file in EV, rather than bouncing to file and re-opening or bouncing to track.  I don't see this as a bug, so much as an oversight that should have been in 2.0, as an added mixdown option.


Emmett

The color choice is limited to light or dark. I'd like to see the return of custom color selection.

1) To further the ASIO discussion, please consider the plight of those using hardware with no native ASIO support.  In my case, using ASIO4ALL provides slightly better performance.  Still, it appears that forcing any WDM involvement creates sync issues -- such that I don't trust AA2.0 for editing sound for video.  With an ASIO card this would be a non-issue.  Of course, sound/picture/meter performance in 1.5 is stellar.  Feast or famine.

2) Compatibility with existing presets.  Even if you could import pre-2.0 presets, we've seen that many of them no longer would produce the same result due to re-written effects modules.  For certain kinds of pinpoint cleanup and editing, I can't stop using 1.5 because of all the presets and techniques that I can't transfer to 2.0.  Of course, the latter has the lasso tool!  So I wish this could be addressed on both levels: making import possible and making them compatible.

3) Compatibility with existing sessions.  Because of the changes in effects, the changes in the panning law, new bus routings, and the 3dB change in master output calibration, an existing pre-2.0 session mix can sound quite different (i.e., wrong) when played back in 2.0.  This is not a problem if you're building from the ground up.  Quite often, I'm not.

4) XML stability.  We've all seen the occasional posts where presets disappear altogether because something hiccupped in the XML files.

Thanks for giving us this opportunity, Steve.