Any chance that the replace function would be quantized to the loop length? Having that option like on the LP1 and LP2 would be very powerful!
EDIT: Also in the documentation says the following:
"The previously described buttons can be assigned to physical buttons as is standard for MOD Devices. When assigned to physical buttons, the Loop, Track/Part, and Rec/Dub buttons also display current track status through the LED above the button. For Loop and Rec/Dub the LED indicates state as follows: ā¢ Solid White indicates empty track. ā¢ Blinking Red indicates recording. ā¢ Blinking Green indicates overdubbing. ā¢ Solid Green indicates playing The label on the button is also changed to show the next state after a single tap of the button for the Loop button."
But on my Mod Duo X, the led colour of the physical button doesnt change colour, neither the label on the button changes to show the state.
Which makes the navigation on the looper, without the computer, very blindā¦
Just checking-- is the LP3 still available? With a freshly updated firmware, It doesnāt show up in the Mod Duo plugin store (not for me anyway) and https://www.looperlative.com/plugins/lp3-mod-basic is a dead link.
LP3 is still on the store yes.
It is available for the Dwarf since 1.11, and Duo X since 1.12 (currently in release testing phase).
It is not available for the Duo.
I have a MOD Duo X and the āSee Documentationā link points to
modduox.local/effect/file/documentation?uri=http%3A//looperlative.com/plugins/lp3-mod-basic&v=1_0_1_9
in my case.
I hope this info and picture helps to find it on your device, too.
Is there any chance to implement that double-tap on simplified LOOP trigger (when Recording) without releasing second tap for some time will do Erase?
Currently, flow is the following - tap to Record, double-tap to Stop, long press to Erase from stopped state. However, before long press is registered, there is a short period of time when loop starts playing triggered by initial press of the long press.
I understand why starts playing -, this allows precise timing to launch the loop, but as it is you cannot do erase without a second of undesired noise.
Doing double tap without releasing the second tap to Erase (like doubletap and longpress combined) is how I remember BOSS RC-300 works, and that seems much less confusing and will allow erasing without unwanted partial play of the loop.
In this case, unlikely. I mean - desired behavior heavily relies on the state of the looper, that is known only to the looper itself. I hardly can imagine how ādouble tap with long release of the second tap only when looper is in recording stateā can be expressed in CV modules.
Iām not sure if I got it.
The Multi Button to CV used on the Looperlative will have the Looperlative reflecting the state of the Multi Button to CV. The double tap on that is a normal (fast) double tap.
Just upgraded my MDX to 1.12, just to get that nice feature for visual feedback of the looper.
Found out that it does not work on my setup.
Currently I use m-wave chocolate midi foot pedal, via midi bluetooth dongle.
As far as I understand, HMI kicks in only when physical buttons are assigned to the looper controls. But it is, at least, unlikely that I will do foot taps on the MDX buttons. They are not footswitches. Also looks like MIDI cannot be assigned in parallel with physical buttons.
Therefore, seems to me that midi controls and led feedback are mutually exclusive. Which, in case of lack of footswitches on MDX means that I can only use looper blindly.
Do I miss some workaround, or Iāve lost this battle?
For loop status (record, play, stop, ā¦), you can assign the āEXTRA STATUS LEDā to a function that is tied to an MDX button. So, you will need to have at least one function on an MDX button.
If you assign the TRACK selector to an endless knob, you can read your current selected track from that.
BTW, Iām currently the MDX in combination with a MIDI controller for foot switches.
Thank you, that was very useful. This option is hard to notice for me. Maybe it is flu and temperature that Iāve got, but I could not find it for about half an hour even knowing that is should be there Anyway, seems like it solved my problem.
Here is my attempt to set Looperlative using two footswitches of my m-wave chocolate 4 footswitch controller.
(I use two footswitches on chocolate dedicated for delay and overdrive control, leaving me with only two footswitches for looping, and therefore āminimizedā controls.)
One (left in my case) MDX screen is enough for required assigments, using only half of an assignments page.
assign: Button 1 - Erase function.
Works as a panic button. As I still have some issues with stopping and erasing everything, even while it is much easier now when I at least understand what state looper is in now, still good to have panic button, even if I have to push it by hand.
lp3 setting: Extra led status : Erase.
First button with Erase function starts showing green,red,white indication of
playing/overdubbing, recording, empty state respectively
assign: Button 2 - Part
I am not going to actually touch it, but it provides color indication for the current track and part with four colors, and button text label provides some additional info to read as well.
assign: Endless knob 1: Track
Not going to do something with this knob actually But it provides on-screen text label that shows current Track and part status with text label.
Harder to see than color indication from Button 2, however handy when you still doubt what these colors mean.
Midi bindings (minimized controls):
For both midi bindings, midi pedal is configured to send 127cc value when footswitch is pressed, and 0cc value when released.
a) Track/Part switch
b) Loop switch
notice:
Contrary to how I understood documentation, quote āFrom stopped, a single press starts the track playing. A long press erases all tracks.ā
seems like it does not erase all tracks, but instead erases only current track and part.
Yet another reason to have that dedicated erase/panic button.
lp3 setting Recording mode : Self-sync.
Makes sure that recorded parts and tracks will be in sync with each other, probably it is something that one needs by default for basic stuff, if not - you already know better what you need here.
With this controls configuration, I have access to recording, overdubbing, tracks, parts, and have two color-coded HMI indicators.
Four pots on the screen are free, and can be set, to, for example, volume pots or feedback, or whatever. Probably it could be a starting point for other people who are just starting their attempts to make use of LP3.
Pretty much more than I had yesterday, I would say.
The LP3 plugin doesnāt actually have any knowledge of what is a MIDI button and what is an MDX button. The long press does work on the MDX buttons. If it doesnāt work on the MIDI buttons, then weāve found another failing in the MOD base software.
That said, I personally never liked the horrendously overloaded multi-button. I think it is an abomination and only put it in at the request of MOD. I think it is much better to have erase, undo and redo on separate buttons. In fact, this is my configuration:
Endless knobs: Track and Trigger Function
Knobs: Volumes and Feedbacks
Buttons: Play/Stop (Extra status LED assigned to this), Erase and Loop Multi (for the track color indication)
My MC6 MIDI controller has Rec/Dub, Trigger, Undo and Redo.
After a couple of days of looping attempts, Iāve found it almost impossible to make use of āpartsā with minimized controls multibuttons. Formally they are still accessible, but in practice I could not make use them for something meaningful, it is just too complicated tap dancing. From that perspective I should agree.
However, otherwise from that - it seems to be very helpful in my case, when there are only two footswitches to spare for looping. Maybe I will get Softstep one day, or will finalize my own diy controller, and it will open the road to more convenient controls but before that - this abomination is my way to go, so I hope you are not going to deprecate it
At least I am really able to record/overdub/stop (per single track) and use both tracks, and thatās usable enough. Quite good for the two button controls.
The LP3 plugin doesnāt actually have any knowledge of what is a MIDI button and what is an MDX button. The long press does work on the MDX buttons. If it doesnāt work on the MIDI buttons, then weāve found another failing in the MOD base software.
Interesting part is that MDX physical button (in momentary_on mode) behaves the same way, Iāve tested today.
Documentation says for LOOP switchbutton: From stopped, a single press starts the track playing. A long press erases all tracks.
Actual behavior I see is: From stopped, a single press starts the track playing. A long press erases current track
(or maybe current part of current track, but as I said I could not make much of the parts mechanics anyway, so Iāve skipped testing parts thing)
Real behavior makes sense to me, I even am not sure what is better - documented or actual behavior, as for me - I am fine as it is. But reality does not match written documentation.
P.S. / Something like feature request below:
The only actual thing that I consider requiring fixing at the moment is that I can clean track via LOOP multibutton only from the stopped state, and before couple of seconds will pass that are required for LP3 to detect that it was actually long tap, it is temporary considered as a short tap, that triggers āplayā action and track plays unwanted head of the previously stopped track. (I was mentioning it somewhere above in this thread, I believe that feasible fix for this problem is that double tap during playback should clear the track, in case if the second tap of the double tap sequence is long.
Iāve seen behavior like that on at least one of my loopers - jamman solo. I do not access to these looper anymore due to war and other stuff, but here is a quote from Jamman Solo manual:
Basically, as you can see it is the same behavior as LP3:minimized_controls when erasing from the stopped state, but erasing from playback or recording is missing in LP3, and it would be great to get it, I am bumping into this all the time, intuitively trying to do this doubletap+hold move by muscle memory.
I guess there is no much sense in asking for changes when even mod cloud is dead, but if MOD reboot is going to be successful and LP3 development will continue, please consider this particular thing as a feature request.
Just checked. The code erases the current part of the current track. So, now the question is fix the code or fix the documentation. The question is which is the more useful behavior.
Anyway, seems like it solved my problem.
