I’ve been trying to recreate exact steps to see if there’s something else repeatable (pun) tied to the issue, but this will also occasionally result in the retrigger to be stuck “On” when you are just single trigging using the track button. The only way to get it to stop is to switch to M2-4. Unfortunately, the bug seems to be as random as the stuck step sequencer I mentioned above (which I can only recreate by leaving the box turned on for a few hours)
That’s been reported already pre release, hopefully it’ll be tidied in an upcoming release
1 Like
"Thanks for the report!
This is a known bug and it has been fixed for the next OS.
Best Regards,
Patrik - Elektron"
2 Likes
I’m all for ultra clarity too in these moments
There is another clue which is easy to overlook and may or may not be documented, I had a look but couldn’t find a mention or relevant hit for ‘inverted’
But if you struggle to see a viable SoundPool sound from another, note that when scrolling through those sounds, only the valid ones are inverted (i.e. black text on white rectangle) whereas the ones with an exclamation marker are highlighted by a white frame around the existing white text on black
I understand this was an area subject to review, so it may still change and may find its way (if not already there) into one of @eangman’s peerless documents
For my preferences, it would be so much better if the ineligible sounds were just filtered out or incredibly easy to see as no use here (without even knowing what’s in the manual)
The inverted clue is useful, but it’s so easy to just focus on the text and overlook the ‘highlight’
I agree that ! alone is not a reliable ‘tell’
1 Like
Good catch! I honestly missed that it was designed like that. I have adjusted it now and it will be in the next version of the manual.
4 Likes
Noticing a bunch of MIDI issues around wrong CC parameters, some of them shared, some incorrect , changing pattern doesn’t work and so on, and I see bunch of reports in this thread already. Have you folks reported them to Elektron already? Then I won’t add another email to their queue 
1 Like
Yes this issue is reported and it is being investigated/worked on
4 Likes
For syntakt overbridge plugin, I am not getting any modulation illustrations. For example, if I am using the LFO to modulate the Tune of a track, the Tune knob does not illustrate that its being modulated. Also, the LFO does not illustrate its movement in the LFO panel of the plugin.
On my analog heat, all modulation is illustrated. The LFO cycle shows its movement, and the knobs being modulated show that they are being modulated with the little shader around the knob.
Am I missing something? Is this feature not yet implemented for Syntakt, or is my Overbridge not working. I checked in both the standalone app and in my Daw.
When using the key combination [NO] + [TRIG] key during LIVE RECORDING to clear the trigs from a sequencer track, it erases the preexisting trigs, but adds a single new one for the start of the erasure. You can’t effectively erase all trigs of the live recording. The act of erasing adds a single trig, and if you repeat the key combination to erase the first one, another trig will be added. Holding the key combination throughout a few repeats of the track/pattern will not erase the single added trigger either. The only way to erase it is to press the key combination again, which then repeats the problem.
Is this expected? I would think that pressing the key combination would not add a trigger (assuming you are holding No prior to pressing the trig), and that if it did, holding the key combination would erase the added trigger on the next cycle, resulting in the desired no trigs.
3 Likes
My +drive seems to be empty. If I do func+level/data then the screen says “+drive has no sounds”. Same thing if I do func+sound then choose sound browser.
Is this a bug or am I missing something obvious?
me neither
When powering down and the power switch is off the display remains enlightened for a few seconds.
very zen 
FWIW Fine here, so you may want to qualify how you are connected up, does it do this when it’s standalone using its own psu ?
Bug ? : CP Vintage decay only affecting noise spectrum
There’s two components to the clap which can be balanced
Bal 0 = Noise > Bal 127 = pitched ‘tone’
SYN/DECAY only affects the Noise part
This may be a conscious choice; just a pity that it affects the sound design possibilities if you have the noise off
EDIT Please Note : The Body Env does do this, so maybe the idea was always to have two envs
So I’ll leave this up, but I don’t believe it is a bug, just flagging to be sure that the Decay isn’t for the voice as a whole
Otherwise it may be handy to put Noise Decay in the banner rather than just Decayto reinforce the distinction
Zen not on purpose as i am not nativ speaking, but makes think…. nice side effect.
Yes, on its own psu and it was running for quite a while
I am not bothered about it, just wanted to mention
1 Like
I’m not sure if they’re bugs or not, but has anyone had the following happen?
-
the M1 retrig button locks on (button 13). I’ve had this happen a few times. Maybe it’s a feature?
-
the Step Rec mode not moving forward a step after choosing a note
Cheers
Alex
Yeah I was finding the second thing the other day
1 Like