phillipm@ohio.edu

I'm currently very disappointed in the quality of audio processing using a custom Max For Live patch within Ableton Live. Though I am a novice Live user, I am a long-time Max user and know what I should be hearing. Using my (very simple) patch as a standalone Max patch, the resulting processing of incoming audio is as clean and clear as it needs to be. Using the same patch as a Max for Live device yields audio with lots of ugly glitches.

I'm wondering if there is a compatibility issue at the heart of the problem ... or if it is simply that Ableton has put some sort of throttle on Max processing in order to avoid any possibility of an major overload crisis. What compatibility issue am I worried about? Read on.

I originally made the patch in Max 6, but I currently have Max 7.0.6 installed and both versions yield clean audio output. When I am running Ableton, Max For Live launches my copy of Max 6. with a banner announcing that Max 7.0.6. is available. So I click on the link and go to my Ableton home page and click on the link for downloading version 7 of Max for Live and it redirects me to the Cycling 74 site for downloading Max 7.0.6, whereupon I get the message that the file already exists ... which is true... because it's the version of Max I have installed. Huh?

I'm currently very disappointed in the quality of audio processing using a custom Max For Live patch within Ableton Live. Though I am a novice Live user, I am a long-time Max user and know what I should be hearing. Using my (very simple) patch as a standalone Max patch, the resulting processing of incoming audio is as clean and clear as it needs to be. Using the same patch as a Max for Live device yields audio with lots of ugly glitches.  

I'm wondering if there is a compatibility issue at the heart of the problem ... or if it is simply that Ableton has put some sort of throttle on Max processing in order to avoid any possibility of an major overload crisis. What compatibility issue am I worried about? Read on. 

I originally made the patch in Max 6, but I currently have Max 7.0.6 installed and both versions yield clean audio output. When I am running Ableton, Max For Live launches my copy of Max 6. with a banner announcing that Max 7.0.6. is available. So I click on the link and go to my Ableton home page and click on the link for downloading version 7 of Max for Live and it redirects me to the Cycling 74 site for downloading Max 7.0.6, whereupon I get the message that the file already exists ... which is true... because it's the version of Max I have installed. Huh?


is-this-a-live-problem-or-a-max4live-problem

My first thought would be to ask you whether or not you've turned the "warp" feature off on the audio clips you've loaded. It seems as though that's the most common thing that Max users who have little experience with Live do that causes them grief....

(I guess my next question is why is "warp" a default?)

Followed by ... how do I get Live/Max for Live to launch version Max 7.0.6 instead of Max 6?

Bingo....THANKS!!!
(I guess my next question is why is "warp" a default?)

Followed by ... how do I get Live/Max for Live to launch version Max 7.0.6 instead of Max 6?


Warp is enabled by default because 99.99% of Ableton's customers want the loop munging by tempo that the function provides. They don't mind that it sounds like ass, apparently, as long as it stammers to the beat. :-)

Is this a Live problem or a Max4Live problem?