As I understand, LFOs set to trig (TRG) mode should activate only when and if a trig is played that has LFO.T on the trig page) switched ON (assuming this is switched off for the track in general).
So in other words, on a track with LFO.T switched OFF, and no trigs plocked to set it ON, the LFO should never take effect.
I am clearly wrong with this because, with the above setup and a simple LFO modulating sample tune, I hear it take effect.
What am I missing here?
Thank you in advance.
The Trig options are for resetting the LFO phase and fade in/out timings. Locking LFO Depth to 0 is the best way to stop its effects on a track.
Yes this. Why?
The way, I understand it is that instead of the LFO being free running, trig mode makes it start at the beginning of the LFO phase Every time you press a key or trig.
Just for clarity the OP is asking about the LFO.T on the Trig Parameter page
As opposed to the trig mode on the LFO page which can can be selected as a MODE.
I have had the same case. LFO.T turned off and still hear LFO effects.
Have you got latest fw update? I can’t recall having the issue in a while…although I have mostly stopped used LFO for fades so much because of this issue.
The LFO is always running if not set to “one shot” or “half shot”. The LFO.T parameter sends a trig to the LFO. And depending on the LFO mode will either reset from start or sample and hold if it is in that mode.
It does not do anything with the “output” of the LFO.
Exactly.
It’s not an on/off switch for LFO.
It’s some legacy parameter from when the LFO settings could not be plocked.
If you want to cancel the effect of an LFO for a trig, locking depth to 0 should be ok in most cases.
What is the exact use case you’re trying to achieve?
Thanks, guys. OK I understand now that the LFO is always running (unless it’s on one/half-shot). To clarify, I’m refering to the LFO page > mode = “TRIG”. I had mistakenly thought that meant the LFO would not activate until and unless a step with LFO.T set to ON was triggered.
@eangman maybe the LFO.T parameter from the TRIG page and its interaction with the parameters from the LFO page could need some attention. 
@mitya33 is there something in particular you were trying to achieve that you don’t?
No, the LFOs have always been lockable. It servers a purpose in that you can choose to not trigger the LFO even when not placing a trigless lock and vice versa.
LFO.T is - should the LFO trigger here?
LFO mode is - what happens when the LFO is triggered?
Confusing? Yeah 
I meant that on the early trinity you couldn’t plock LFO triggering parameters.
But you could more or less do so on the Monomachine with the trig lane. I thought LFO.T parameter was somehow a reminder from such past.
Anyway, thank you for clarifying ^^
AGHHHHHHHHHHHHHHHHHHHH why are fades on Elektron so complicated???
(Sorry, I just had to get that out of me.)
The keen-eyed among you will discern from the above that I’m still struggling.
I’ve read various threads on this, and the helpful replies in this thread.
All I want to do is gradually turn down my filter frequency from its current value down to 0, once, over the duration of a pattern.
I have a 4-page pattern that plays twice. LFO.T is off for the pattern. My LFO1 is set to destination = filter freq., wave = ramp, depth = 0; mode = one (I want the frequency to be turned down, and stay turned down).
I then have a trigless trig on the first step of the first page, which is conditionalised to the second playthrough (2:2). This has LFO1 depth = -50 plocked to it.
My thinking is, the LFO is always running, but has no depth, so does nothing audible. Then this plock happens, and suddenly it has a depth of -50, so should kick in.
This is emphatically not what happens.
Is this rocket science, or just me?
It sounds like the LFO.T should be on, if I’m understanding correctly. LFO.T means the LFO is triggered (by a trig).
The Digitakt doesn’t have trigless trigs, like the OT. It has lock trigs. Lock trigs do not trigger the LFO if you have LFO.T off.
I would turn on LFO.T and p-lock a trigger, not a lock trig. If you don’t want that lock to make a sound, then p-lock its volume to zero or something.
No.
I recommend creating a test project. In that project use something very obvious, like an LFO to the pitch of a sound, and then test. Create patterns, mess around with LFO.T and p-locks… You’ll figure it out
Good advice. Modulate pitch to start with as it’s so easy to hear. Then when you have the modulation you want, switch to the right destination, and adjust depth.
Yes it’s a pain.
I think you need to lock LFO.T back on again where you want it to trigger.
And maybe ramp set to half or maybe exp set to half.
My logic being you want to come from 50 to 0 not from 50 to -50 or to jump back up at the end of the cycle. I’m sure you are doing it anyway but use the graphic on screen to make sure the ramp goes in the right direction. You can make speed and depth go negative!
And remember that this table is in note length so 1 equals 16 steps. The fact we need a table and it doesn’t just show the length on screen drives me crazy.
Thanks for this (and other replies, everyone). I think this is the essence of what I was missing.
Are you saying that if I have LFO.T tuned off for the track, then place a yellow lock trig with LFO.T p.locked on it won’t trigger the LFO?
Instead I need to use a note trig and turn the volume down to zero?
What’s the point of being able to p.lock LFO.T on a yellow lock trig then?
