|
I have to agree to an extent on this one. I do my DJ mixes in Ableton and I have noticed this as well. From my experiences, it boils down to two things:
1. Time stretching. If I stretch a track or sample more than +/- 5 BPM, I will start to notice this effect. This is especially true when the algorithm is set to Beats. As you correctly point out, Repitch is basically useless.
2. Transient Setting. I have noticed that if I change the Transients setting from the default 1/16 to 1/8, I can alleviate this problem to a great extent, but it depends on how much the BPM is altered from the original. The farther I get from the original, the worse it gets and the less this trick works.
I don't know exactly why this is, but I have my theories. I think its all related to the beatmapping functions. I remember when I used to do my mixes in Acid Pro 2.0, I got a much warmer sound. When I tried to use Acid Pro 3.0, where they introduced the beatmapping feature, it exhibited the same behavior, which lead me back to using 2.0. Eventually I started using Ableton for mixed CD's, because it's beatmapping and transposition features were superior.
SO, from your standpoint, I think what is probably happening is that inexperienced producers are not paying attention to these tiny details, and after working in Ableton for a while, they probably just get "used" to this sound. I think that if most of them were to start working in another DAW such as Logic or Cubase, they would notice that the effect is no longer present.
I have always thought that the time stretching in Logic and Cubase were superior to Ableton. However, that makes sense if you think about it. Both Logic and Cubase have been around longer, and have had more time to work on their time stretching algorithms. In addition, both of these packages do not rely on the "beatmapping" feature to do timestretching (although it is an option).
Because Ableton was designed with a different purpose in mind, their approach to time stretching is different that these other DAW packages. This is most likely the primary reason why a lot of tracks done in Ableton sound this way, and probably a primary source of the argument that Ableton's summing is somehow "inferior". I don't think that is actually true, but I do think that the problem with Abletons time stretching algorithms contributes to this argument.
|