This looks like a strat vs sg debate to me - it's what we call horses for courses over here. Choose your weapon gentlemen and PLAY! HNY Gareth From: mark@grubmah.com Subject: Re: The EDP and the Looperlative and me Date: Fri, 31 Dec 2010 09:59:56 -0800 To: Loopers-Delight@loopers-delight.com On Dec 31, 2010, at 9:08 AM, William Walker wrote:
I'm not sure why it's so important to you and Rick that I come to love the LP-1. I appreciate it and I appreciate the offers of help, but it's rather odd how saying that one is more comfortable with the EDP elicits some of the reactions that it does. My initial post on this thread was sparked by a question from someone else a few weeks back on why one might prefer the EDP and I tried to sort through what it is that I find appealing about the EDP.
One thing I'll note on learning curves is that almost all of the Looperlative discussions start with: "It's really easy to program a MIDI controller for it." It's worth noting that that's a much bigger initial learning curve than exhibited by the EDP for which you can get a custom footswitch for which the software has already been optimized. The EDP programming depth is about customization, but on arrival it's set up and ready to go whereas the Looperlative is relatively lost without a MIDI controller or at least some programming of the user buttons. Now, I'm certainly capable of doing that programming, but now I need to step back and start thinking about designing a looper control set that's right for me.
So, I start down that path and I ask what, for example, would I like to do? Hmm. I've had times where I have my feedback set to 0% and basically just work with a long synchronized delay, but I'd like to be able to transition to feedback = 100% to build a seamless loop. I can program a button to go to feedback = 100%, but I can't program a button to go to feedback = 0%. I could use a continuous pedal to control this with a suitable MIDI controller, but that has it's own set of complexities with respect to when the controller signal gets sent. Given a sufficiently powerful MIDI controller, I could program buttons to send those control values but now we're out of the "the Looperlative is trivial to get working with a MIDI controller" realm. My first thought had been to use Replace+ mode, but it's interaction with Rec/Dub proved to be "interesting".
Now, that said, this is difficult to make work with the stock EDP as well given that substitute is a sustained function (cool for quantized replace, not a good answer for a generic take the feedback to 0% option) and various interface modes aren't friendly to stereo EDP use. But my point is that the EDP basically comes optimized for a particular way of working whereas the Looperlative comes expecting the user to program it to fit their working style only to then present various at times unexpected bumps in the road. Maybe this is also why I generally prefer Apple equipment. It has all sorts of limitations, but it has also been subjected to a lot of focus on making it good at working in a particular way.
But really with the Looperlative, it comes down to saying: Here's what I want to do. Then figure out what the Looperlative would need to do to best approximate that. Then figure out how sophisticated a MIDI controller I need to get. Then get it programmed. Maybe at the end of the day that all works out well, but it also feels a lot like what I spend my time at work worrying about doing.
Mark
|