Support
Looper's Delight
|
Support |
|
|
Holding [LOOP START] is interesting, but I need the option of having AUTO STACK as the default. The idea of holding [LOOP END] is also interesting and I picture that as AUTO STACK with STACK set to MOMENTARY. Minimum requirements for AUTO STACK to be useful to me — foot location doesn’t need to move (excludes Method #4) — Bro-sync slaves can [AUTO STACK] by default I have 2 Rangs bro-synced, each with a SideCar. I would like the option of the SLAVE entering [AUTO STACK], which requires it either being default-able or a message being broadcasted over bro-sync. I believe we can please everyone, but it would cost 2 toggle spots. There are 4 different combinations which can be accomplished with 2 toggles: 1) Default [LOOP END] behavior ([LOOP START] tap) -Normal or -Auto-stack — if MOMENTARY STACK is on, this will stack while [LOOP END] is held down 2) Alternate [LOOP END] behavior ([LOOP START] hold) -Enabled or -Disabled Holding [LOOP START] will engage the opposite behavior of 1 Toggle #1 seems absolutely necessary to me, and I’d have it always on Auto-stack, of course. I’d prefer toggle #2 Disabled, but I could probably live with it being fixed at either value. Thanks, -Jason On May 21, 2014, at 1:53, Mark Hamburg <mark@grubmah.com> wrote: > On May 20, 2014, at 2:58 PM, Jason Fistner <jfis.lists@gmail.com> wrote: > >> I’m so excited that Mike et al. are finally considering this!!!! >> >> In sum: >> Method #3 >> >> More detailed: >> Let’s first look at some reasons for wanting to enter [STACK/ OVERDUB >> MODE] mode immediately at [LOOP END]: >> a) Flow >> - as us loopers know, it’s crucial to keep things moving and changing— >> especially at the beginning! most people do not have our tolerance for >> repetition. >> b) Signal Smoothness >> - hard cuts on delay and reverb trails reveal the seams and can take a >> listener out of it >> c) Volume/ dynamics smoothness >> - sometimes by the end of the loop, especially in long loops, the >> volume of what is being played at the end doesn’t match what it was at >> the start (inadvertently, by some psychological magic :D ). going right >> into [STACK] mode can smooth this out. > > I think these correspond to my two categories with (a) being the first — > I just want to start evolving the loop immediately — and (b) and (c) > being the need to get some overlap at the end to smooth out the > transition or deal with delay and reverb trails. I argue that in the > latter case, it’s actually inconvenient to need to tap a switch again > when done — though not nearly as inconvenient as the tap dance the > Boomerang III currently requires to go straight into STACK. I would also > argue that in the first case, you know that’s what you will be doing. > That’s why I liked the idea of being able to use a hold at the beginning > of the loop to indicate a desire to go into stack when done recording — > i.e., Press (Start Recording) - Hold - Release - Press (Start Stacking) > — and a hold at the end of the loop to generate an overlap without > remaining in stack — i.e., Press (Start Recording ) - Release - Press > (End Recording, Start Stacking w/o Decay) - Release (End Stacking, Start > Playing). If you hold at both ends of the loop, there just need to be a > decision as to whether the “go into stack” behavior holds or whether the > “momentary stack” behavior holds. > > Mark >