Ok I checked every setting inside out, and I would conclude: No, LP3 doesn’t follow tempo changes. However even if you drastically change the tempo and then put it back to the old tempo, loops will slowly drift back into sync, which is really impressive.
I have another question however, hence the double post:
I wanna stack 3 Lp3. I would like to have the status of all 3 units displayed on my mod dwarf at the same time. Is there any possibily to do this?
There are only two buttons w LED unfortunately. But I wonder if the status of a loop could also be display on the display, by mapping it to a knob?
I don’t currently have the loop status displayed on a knob. If you have a computer connected via USB or bluetooth to the Dwarf, there is a Java-based application for the LP1 that displays the status of all the loops. While it doesn’t control the LP3 plugin, it will display the status.
This is what I have been trying to do on my dwarf, however the knob wouldnt display loop status. Can you share in detail how this woild work? And is this confirmed to work on dwarf?
thx for the tip, but I wanna go computerless
Ok this is what I thought. Is this the same on your hardware units?
Hey, I’m playing more with this and experiencing odd behaviour:
I mapped the Loop function to a FS on my dwarf. The Display shows play when overdubbing and vice versa. So it is displaying the exact oposite state. Or is this meant to show what happens when you press the button? Feels very confusing to me.
Even when overdub is off, the feedback parameter is active. Is this intended? Coming from other loopers i expect this to only do something with overdub engaged.
I love to keep layering/replacing with feedback between 0 and 0.5 and then switch to play once I wanna freeze a loop. I can’t really use this technique in the current state.
The display shows what the button will do and not the current status.
Feedback is feedback. Overdub is overdub. Each does its job independently of the other. What you want is controlled ducking. Interesting concept but it is different than the feedback control.
Ok I get the Idea, still confusing, cause in this case I’d rather want the display to show me the current state.
The Ableton looper and some other loopers operate like I described it: The Feedback is only working when overdub is engaged.
I guess when you see a looper as a digital delay line, then it makes sense to have the feedback always working.
For me this boils down to: If I could somehow get the individual loop states as midi information, I could just patch my own workaround.
Would it be possible to get the loop states somehow from the control chain output?
I’ve always seen that as the function of the replace feature in my loopers although I’ve never allowed the partial decrease of the previous loop, it is something that could be considered.
It allows for quite practical use cases, the one that I described.
Also the TC Helicon loopers in their voice boxes operate that way. They have the Feedback set to 98% in the default setting. That way with each overdub the older layers gets turned down just a little bit, preventing the layered loop from clipping / becoming too loud. This wouldnt work if the Feedback was working all the time.
It would be very useful If there was the option to get midi start / stop messages out of lp3.
I like to use the first loop to create a master tempo. If you wanna sync up drum machines and sequences and such with the first loop, you would wanna have a midi start message, after the loop goes from rec to play state.
I usually work in a BPM range from 80-150bpm. Sometimes when creating longer first loops I end up with very slow tempos, such as 60bpm. It would be great to have the option to half/double the created tempo. Also setting a BPM range would be a great feature.
This week, as I started to play more - I am bumping into the same issue at least every day.
LP3 stops suddenly stops responding to controls, at least “LOOP” button.
It is assigned to midi CC signal, and I see button presses in WebUI when I send the CC signal, but LP3 does not start record, basically does nothing. Clicking in WebUI by mouse does the same (nothing).
I’ve tried:
Erasing
Switching between host sync and self sync
Turning plugin on and off
Clicking other controls of LP3 at random.
Only thing that really helps is reopening pedalboard or removing LP3 and adding it back.
I’ve had this happen a couple times. I always chalk it up to beta plugin interaction or something, have to unplug and plug the unit back in. One of the quirks…
I’m not seeing this lock up myself and use the Dwarf most every day. So, perhaps you can tell me how you use it and if there is any specific press or sequence that always leads to a lock up.
@ignis32@oeSmash The problem you are having is that the plugin is crashing. I finally got it to crash here and seems to be related to reverse. I’m making a change that fixes the problem that I encountered and also does some additional sanity checking in the code to avoid doing bad things if there is another bug somewhere. I’m hoping this will fix your issue.
Good to know there are improvements.
I’ve been focused lately more on filling my giant gaps on music theory, rather than looping. But that’s a reason to return to use looping once again, would report if get reproduced again after the update.
I need also to notice that I do not even have reverse assigned.
My midi assigned controls which I use are:
LOOP, TRIGGER, UNDO, ERASE,
Hw assigned controls:
REC/DUB, RECORD MODE
Btw my looping pedalboard is rather heavy after adding some neural network stuff, and in retrospective I wonder if LP3 crash probability correlates with CPU usage intensity. ( which sits somewhere within 60-80 percent)
P.S.
127 for press, 0 for release. Anyway, when I get the issue reproduced, LP3 does no react to WebUI clicks as well.
Ok, it is still possible that the changes that I made will fix things. There were certain oddities around bounds checking on the loop that have been fixed.
I’ve noticed a bug while using LP3 Basic - it does not record exactly as much as was recorded, it adds about 2 seconds of silence to the recorded loop. I thought the issue is because of MOD footswitch but I’ve tried it on DuoX buttons and the result is this same.
It reffers to DUox - I have not noticed it while using Dwarf.
I bught also Looperlative (the big one) but have not tested it yet.
Hi @Lukasz,
I don’t know if it’s related but I had a similar experience whit the LP3 when I didn’t know the ending tap had to happen before the end of the bar. If it’s a tiny bit too late, you can have a whole blank measure added to your recording. I’m not sure it’s still the case but you can read a few posts from this one :
LP3 Basic is the big one. The little one is called LP3 One.