If you put a Trigless Lock Just before (space permitting) that is TRUE every three, then put a Not Previous on the main target then it will play as you desire I think
.
PS
Re nomenclature
I read A:B as every B, but with an offset of A when started (offset from 1, where 1 is 1st pass)
2 Likes
^ it’s such a simple concept, but surprisingly difficult to express in a simple sentence 
I read A:B as every B passes ; whilst A denotes the initial pass count
.
it is tricky, indeed, must resist offset and phase in the description - I think Simon explained it well, he seemed to be the champion, his explanation stuck with me
.
Perhaps A is the solitary first case pass count, thereafter every B
I read A:B as every B passes ; whilst A denotes the initial pass count
.
it is tricky, indeed, must resist offset and phase in the description - I think Simon explained it well, he seemed to be the champion, his explanation stuck with me
.
Perhaps A is the solitary first case pass count, thereafter every B[/quote]
On A every B?
I think the explanation in the release notes is really good:
“A:B will be true on the A’th pattern iteration, then true again after B iterations, repeating indefinitely. You can use this setting to program periodically recurring notes, where the period can be longer than the actual patten. If you for instance set it to N:4, the note will be triggered every fourth loop of the pattern.”
Maybe not so good for beginners (for lack of better word), though. Obviously written with a bit of an engineering mindset. 
Hmm…
What A:B does is that it will count your pattern as several cycles depending on what value you select for B.
If you set B to 2, it will regard your pattern as “finished” when it has looped twice. That gives you a choice of two cycles where you can choose if the trig is going to be active or not.
So if you set B to 8, and A to 3, the trig will be active on the third cycle of the pattern, out of eight total. This is regardless of Pattern length.
It’s basically a counter function. It will count your pattern as many times as determined by the B value, and then you select which cycle of the pattern your trig will be active.
After the B value of counts, it will start counting from 1 again. Where it counts a Pattern as a cycle is determined by the Pattern total or maximum length
EDIT: Oops, swapped A & B, fixed.
2 Likes
It would be nice to be able to play one note or another conditionally
I think you inverted the A and B there. Should be A/3:B/8 , yes?
well…at least i hope they do make some music themselves though 
indeed - TRCs that only enable/disable parameter lock activation on a trig, not the trig itself 
This conditional trig stuff is starting to get me itching for an Analog series instrument, for the first time.
indeed - TRCs that only enable/disable parameter lock activation on a trig, not the trig itself [/quote]
Can’t you do it by locking note parameter change then?
BTW I hate this forum platform, buggy as hell on iOS and pretty terrible user experience on windows too, Elektron please sort it out FFS, without doubt hands down the worst forum platform I have ever used.
Oh yeah, this update has been totally worth the wait.
Best.Update.Ever! Messed around all night with the various settings and let them play out and record into Live. Came up with some super cool variations and modular-esque sounds. Thanks so much Elektron team
indeed - TRCs that only enable/disable parameter lock activation on a trig, not the trig itself [/quote]
Can’t you do it by locking note parameter change then?[/quote]
I’m wondering if we are all on the same page - I read the request as being a wish to change Trig on > off to Trig pitch1 > pitch2 as the conditional event
.
I believe it may be sorta possible on choked track pairs if you layer two sounds (otherwise identical except pitch) then if one is on False condition the hidden track will play (and will hide normally when the TRC is true on the higher numbered track)
.
it’s possible to lock changes on subsequent trigless locks, but that will give a different effect
ive really revisited my songs with this update, i love it!
is it possible to lock the fill? it would be cool if you could double tap the page button to make the fill active without having to hold the button. maybe theres a way i dont know about?
If you want the fill to stay - what’s the downside of just using a different pattern altogether? This is clearly designed to be a temp variation.
^ If fill is your main use of TRCs - then someone else illustrated a logical advantageous use of PREV condition
.
If you have one FILL TRC near the start of your pattern, then follow it with PREV conditions where you want fill - then it will work as normal (ie Page down) (except it will only initiate after the first one near the start is passed)
.
So, if you want to ‘lock’ that fill on, just nudge that initial TRC from FILL to Not(FILL)
.
a bit clunky perhaps, but I wouldn’t hold my breath waiting for a sticky fill - although the logical way to implement it may be to press(hold) Page ‘then’ tap YES !
true, i suppose i could make a duplicate but modified kit but i dont want to jump between kits that may have different track mute/scene’s enabled. plus having basically a totally new pattern for the kit at the push of a button is amazing.