Difference between revisions of "MaxLooper"
(Created page with "MaxLooper is a plugin created to deal with inadequacies in Live's own Looper plugin, and integrate the parts of two other plugins that I've used on a regular basis for several ye...") |
|||
| Line 1: | Line 1: | ||
| − | MaxLooper is a plugin created to deal with inadequacies in Live's own Looper plugin, and integrate the parts of two other plugins that I've used on a regular basis for several years (SooperLooper and AugustusLoop). Its intention is to provide a wider range of feedback than Ableton's looper is capable of, and to make a looper that is capable of Tape-based | + | MaxLooper is a plugin created to deal with inadequacies in Live's own Looper plugin, and integrate the parts of two other plugins that I've used on a regular basis for several years (SooperLooper and AugustusLoop). Its intention is to provide a wider range of feedback than Ableton's looper is capable of, and to make a looper that is capable of Tape-based Looper style looping in a software looper. |
One of the main aims I've had for the patch is to have very precise timing that is accessible without a great deal of forethought. I was intrigued by the technique that Mosolume had of allowing the user to hit the "Loop" button ''after'' a passage had started and still have it lock to the correct quantization amount. That was the basis of my model, and has caused all sorts of problems. It seems like no one else uses this 'backwards quantization' method, and perhaps for good reasons. Anwyay, getting it worked out. | One of the main aims I've had for the patch is to have very precise timing that is accessible without a great deal of forethought. I was intrigued by the technique that Mosolume had of allowing the user to hit the "Loop" button ''after'' a passage had started and still have it lock to the correct quantization amount. That was the basis of my model, and has caused all sorts of problems. It seems like no one else uses this 'backwards quantization' method, and perhaps for good reasons. Anwyay, getting it worked out. | ||
If you're trying out the Looper, chances are you've noticed that it's not terribly intuitive. Granted. I've been using it for months though, and it works great. You can look forward to a new version of it soon, since I've figured out how to redesign it and make it do what I planned on it doing in the first place. | If you're trying out the Looper, chances are you've noticed that it's not terribly intuitive. Granted. I've been using it for months though, and it works great. You can look forward to a new version of it soon, since I've figured out how to redesign it and make it do what I planned on it doing in the first place. | ||
Revision as of 02:26, 1 January 2012
MaxLooper is a plugin created to deal with inadequacies in Live's own Looper plugin, and integrate the parts of two other plugins that I've used on a regular basis for several years (SooperLooper and AugustusLoop). Its intention is to provide a wider range of feedback than Ableton's looper is capable of, and to make a looper that is capable of Tape-based Looper style looping in a software looper.
One of the main aims I've had for the patch is to have very precise timing that is accessible without a great deal of forethought. I was intrigued by the technique that Mosolume had of allowing the user to hit the "Loop" button after a passage had started and still have it lock to the correct quantization amount. That was the basis of my model, and has caused all sorts of problems. It seems like no one else uses this 'backwards quantization' method, and perhaps for good reasons. Anwyay, getting it worked out.
If you're trying out the Looper, chances are you've noticed that it's not terribly intuitive. Granted. I've been using it for months though, and it works great. You can look forward to a new version of it soon, since I've figured out how to redesign it and make it do what I planned on it doing in the first place.
