When both FILL and a second trig condition (eg 2:6) are activated on a step,
FILL behavior is not consistent. Not all FILL trigs play when the page button is pressed down.
If you have both a trig condition e.g. 2:6 and FILL, it should play every 6 steps starting from the second pass if you hold FILL while you expect it to play. I would advise to test this with lower values though ^^
It should play when PROB && COND && FILL are true (“&&” being the Boolean operator AND)
Now that they’re going to be in there with pattern logic, they might as well fix the pattern change bug with varying scale speeds that’s been a thing at least since the A4 launch
(edit: that would be December 2012, my kids are half the age of the pattern bug)
I’m sending program changes from an Octatrack to the Analog Four.
When I set the A4 in the advanced pattern mode, the A4 starts changing patterns late. Changing the pattern change value in the A4’s scale settings just changes how late it is, not fixing the problem.
(I’m being a bit salty and unfair about it, because I know that Elektron Support knows about the bug, I last emailed them 2 years ago about this one. But hey, at least before being salty on the forum, I waited for some 12 years!)
If you press func+page, set to per track with func+yes, and then start messing with sequencer speeds, the pattern change and reset values don’t work as intended. Typically, upon receiving a program change, the machine in question (here, the DTII) changes patterns 16 steps late.
Oh. I have to test this with another device, but yes it’s annoying.
I remember having seen this surfacing, but I don’t use Program Changes so much myself.
Reporting here so people are aware:
Page looping resets the track playback. (Looping page 5-8 will play 1-4 in the background instead of 1-8 in the background which was intended.)
I started mine first time: its loading the big fat demo project, it takes quite a while.
While the loading process, I went to the project menu, and tried to init a new empty project, and load it, to skip the demoprojects. I guess it does not want to be touched while loading.
Then I turned the unit off.
After a restart I waited till the demo loading finished, and after that process I init an empty project. looking good so far.
comb filter is nice. has formant quality and is quite thick!
my inputs don’t noise. fine, lets hope for the best.
Destinations are never restored properly after a temporary save / reload, loading a project or rebooting the unit.
They can even be set to invalid destinations (like LFO 1 depth modulated by LFO 1) depending on the value during the save.
I can reproduce it on OS 1.01 straight after an empty reset, by simply creating a midi track, setting a destination and saving / reloading to temporary.
