What bugs you the most about 2.0 AS IT STANDS?

1.  Better ASIO implementation as discussed above.
2. True solo on the busses so I can listen to my effects returns easily.
3. Display issues as others have mentioned.  In my case I'm particulary bothered by the active track highlight.  I like to navigate through tracks with arrow keys and it can be tough to tell which track I'm on since the difference is a very slight shade of grey.  I's also like it if in the mixer view I could navigate between tracks with the left/right arrows rather than the up/down arrows.
JTC

I just found one - when I work on a track and set up real time effects that I want, sometimes I decide I need to double the track and pan it, but then I either have to repeat all the FX on the second track - or be sensible and set up a bus, but then I have to re set up all the FX

I would like to see drag and drop of effects between tracks or between tracks and buses - with click drag to move and shift-click to copy (with all parameters obviously)

1- Real-Time Effects on AA2.0 have a big load on CPU, a reverb on 2 tracks is  enough to give you Clicks to blow your mined off! In AA1.5 i used to have mutli effects on more then 50 tracks and play it real-time without a single click.

2- The undo/redo functions use to show the operation when you put the cursor on it, now that does not happen, and adding Redo to the MultiTrack would be handy.

3- Not having Mixdown and Mixdown Selected clips like AA1.5.

I'm surprised to see no mention of the problems with crossfades in this thread, as it seems to be acknowledged as a common problem. In my very short time using AA2.0, this is the thing I have had most trouble with. There seem to be several short-comings in the way cross-fades work:
1) Automatic cross-fades only work on clips, not on tracks, and only on volume, not on other parameters' slopes;
2) Automatic cross-fades only work on the start and end of clips, changing the volume level to or from minus-infinity dB. You cannot use them (reliably!) to control the slope of a change in the middle of a clip.
3) You need to use Logarithmic In for both the fade-in and fade-out to get a smooth-sounding cross-fade. Logarithmic Out does not appear to be much use.

I'd like an automatic way to select the type of slope of any change to an automation parameter (volume, pan, EQ, real-time effect, etc...). I'd like to highlight a region between a start time/value and end time/value and choose the curve or slope-type to apply to the transition. I'd also like to be able to set a default, so that all my transitions would be logarithmic (for example) unless I select something different.

To put these comments in context: I was trying to use Crossfade, Logarithmic In/Out to control a fade between two clips in MV, without cutting the clips into short pieces. I managed to make the incoming clip fade in with a logarithmic curve, by setting minus-infinity dB on the clip volume envelope at the in-point, 0db at the out-point, highlighting the area of the cross-fade, right-clicking the in-coming clip, selecting Crossfade and either Logarithmic In or Logarithmic Out. One gives a steep rise initially, tailing off gradually (what I wanted), the other rises gradually, steepening to the end of the fade (not sure what use this is...?). However, when I tried to make the out-going clip do the inverse, all that happened was that the volume at the in-point changed from 0db to minus-infinity dB, where it stayed!

In the process, I also discovered that edit points on a clip or track automation line can only be entered or changed by clicking or dragging with the mouse. I don't like using the mouse, at least for anything that requires some precision, nor do I like having to zoom in and out all the time. Instead, I'd like a menu option and/or keyboard shortcut to enter an edit point at the play-line's current position, to be able to enter the required value from the keyboard, and to be able to "nudge" an edit-point to exactly where I want it using the arrow keys. Maybe there should be an option to make edit points snap to the nearest cue-marker or similar "landmark"? I don't think is new functionality. Rather, it is filling gaps in an incomplete implementation of parameter automation.

Maybe I've missed something: Can you chose a logarithmic scale for the vertical axis for clip- and/or track-automation parameter-lines? If so, then simple linear slopes on the display, connecting the desired start and end values, would actually sound like smooth logarithmic fades. You'd need to be able to chose the axis-type by parameter, though: Great for volume changes but less useful for panning, for example.

You shouldn't have to have a control surface with powered faders to have full control over parameter automation.

Automation lanes are not saved properly if I change the sample rate of the session.
If you have a session recorded at 48000 sample rate and try to “save as” in a new folder downsampling to 44100 all automation is out of sync. If you set the time in samples you will see that all automation points stay at the samples and not in time.
There is some undo isues with automation too.

Lluís
(sorry, english is not good)

The worst thing for me, is that the Direct to Disc feature is faulty. 

I upgraded for the sole reason of using 2.0 for field recording with the Direct to Disc mode.
This mode failed to work at 2 out of 10 events, causing me to have to wait FOR SEVERAL
HOURS while the session files were saved!  It was lucky that I did not try to save in the
middle of the 2.5 hour event as I would have been unable to record the second half due
to the buffers saving.  It malfunctioned in this way with NO WARNING or indication that
it was NOT working in Direct-to-Disc mode (nor that anything was "different").  The very
next session, everything was OK until a few sessions later when it failed again!

Other folks have reported this same behavior, so it is not just some unique strangeness
of my system.  It is too bad that Adobe are not much interested in fixing AA bugs, but
instead in spending effort (that could have been directed towared repairing AA) in
creating and releasing another overlapping application (SoundBooth.., or is it SoundBarf?).

For this reason (and about a dozen other 2.0 problems), I am not using 2.0 at all anymore.
I still use 1.5 as my primary mix-down system and I am evaluating other DAWs for use
in field tracking (ones that will actually do reliable Direct-to-Disc recording).  Reaper may
be one such tool and there may be a couple more, but NOT Audition as it stands!!

It is too bad... because I have been an avid user of this product since it was CEP 1.0.

Interesting you should mention that apparently random problem.  I suspect that there's something about the way one uses the program that causes it, but I haven't worked out what and indeed that's one of the reasons I switched to another program for live recording.  What I do recall is that it seemed to have actually saved to disk when it gives that impression that it hasn't, and if you are really brave you can ignore the requests to save - and you should find that the recording is actually there.  But then who in their right mind wants to take that risk?!

Thanks Oz...

I will do a "brave test" of your suggestion to cancel the "wish to save" dialogs in
the relative safety of my studio with series of dummy tests, if I get the time.


Mod note: I have left ozpeter's reply because it contains information that might be pertinent to Adobe, but if you want more details about his alternative solution, send him a PM, and he'll oblige you with the details.

The conversion of the effects to VST has made some of the dialog interfaces quite small.  For example, the new Parametric EQ graph is so small on my monitor that I sometimes can't tell precisely what's what when creating a complex filter.  Not only is it smaller, but it's not resizable.  This is a relatively minor annoyance, but does make 2.0 less dependable for me when previous versions are adequate in this regard.  As monitor resolutions increase and pixels-per-inch also increase, smallish things like these get to looking even smaller!  Resizability, please!

This may be a case of being in a rush and not going back to read the manuals, but over the holiday break I got back to doing a multitrack mix in AA2.0 and tried using the automation lanes for the first time.  Unfortunately, as far as I can tell, there is no way of resizing the lanes independently of the track.  That is, the only way I could get more vertical room for fine adjustments was to make the whole track larger, but that meant that the track waveform view was also larger.  I wanted to only make a single automation lane larger, so that quite irritated me.

[Adobe]

I'm actually relieved to see so many of the same bugs as I have noticed myself posted here. And there are a lot I never ran into. I basically walked away from AA 2.0 after discovering that the program wouldn't xmit SMPTE while recording. (With no fix planned!!!) (The CPU overloads didn't help either...)

I got a new laptop at work (dual core - figured it might work) and went to install my 2.0 upgrade software (I started with CE2.0) and remembered that I had to have AA 1.5 on the machine before 2.0 would install. Then I remembered that I needed CE2.0 on the machine before AA 1.5 would install. I contacted Adobe - they said they'd turn that off for me if I called customer support. After being on hold for 45 minutes, I just started installing CE2.0...

What bugs me? Adobe.

Some of these have already been mentioned, but i'll post them again because they are MY gripes:

1) Choppy or sluggish metering and clock response using ASIO.

2) After all this time, I still can't get used to where things are placed in the menus in AA2.

3) Slow startup.  But, i've noticed this on every machine running AA2.

4) The hassle of reconfiguring the soundcard whenever I want to change the recording samiple rate, and it rejects my card's sample rate settings.  For example, if I confuigure the card to record at 88.2k, AA whines and tells me that it wants to record at 44.1k.  My card works at 88.2k.

5) This is a bit nit-picky, but I miss being able to customize the colors of the program as we could do in AA1.2 and older. 

I hadn't used AA2 for a while until yesterday, so I've been reminded of some more annoyances:

• I like iterating through the presets for the effects (particularly with some VST plugins) while previewing to try new ideas or find a good starting point for further tweaking.  AA2 makes this difficult by not remembering where you are in the preset list.  So, every time you try a new preset you have to use the preset drop-down and scroll.  This is particularly painful if the plugin has many presets.
• I think I've mentioned this before, but I want multiple clock panels.  Since all the panels are dockable, multiple panels in general would give more flexibility.  In particular, I often want to work in bars/beats but still have minutes / seconds / frames

That's all I can remember for now.  These aren't major, but such minor usability tweaks would make things more enjoyable.

Since Audition doesn't remember Waves' VST/DX plugin settings (among other plugins' settings) after saving a session... I find that to be a serious flaw that should be addressed.

Todays irritation is with the automation lanes.  There needs to be a way to move points in the automation lanes along with the clips in the track.  I can understand that not all uses of the automation lanes requires this, but it is necessary for work I am doing at the moment.

(Background info: I am working on a remix where I have been given a number of clips of a song, which I've cut up and rearranged.  Some of those clips have the wet/dry mix automated to fade in a reverb towards the end of each instance of the clip.  The problem is, I've now decided to add a couple more bars to the intro, so I've had to slide the rest of the track along, but the automation points stay where they were.  This meant I had to painstakingly move a bunch of automation points manually, which is actually very fiddly to get right.  I could see no way to select the points and slide them with the clips.)

It'd also be nice to be able to right click on the automation points to edit their values precisely, although now that I type this (away from my Audition installation) a vaguely recall double-clicking may do this.  I think a right-click option is more intuitive though.