I am new to the A4 but one thing that is really confusing me is the way simply selecting tracks when delay is being used causes an audible effect. If I just create a new pattern with the default sound and add delay to it why does selecting other tracks cause any audible result at all?
If this doesn’t make sense I can create a video to illustrate. I would love anyone with more experience to explain why this happens or how to stop it.
This is a bug introduced in the latest firmware, check the A4 forum, I posted about it there…there is actually a link to another post talking about the bug.
Just wanted to let you know that you aren’t going crazy, elektron is aware of the bug and I imagine it will be fixed (the previous firmware doesn’t do it).
you can wait… maybe for a long time
or you can load the previous OS which doesn’t have this issue… just sayin’ Same boat here…
I suppose the downside is that any tracks you make from now 'till the new OS may be altered by the new update… (see other thread)
who can say? it seems there is more than just 1 bug uncovered in the latest offering.
I’m sure it won’t be long before they fix it though, it’s kind of a REALLY BIG problem for their flagship synth right now.
wow…never noticed it…maybe because my clock is coming from my acme and is pretty solid…i ran a test , so with octatrack as masterclock there are in fact glitches…with my acme not
the fact that biologik mentioned the clock and you confirmed that causes it should be a step closer to fixing the bug…I don’t know how far elektron is on fixing it but that narrows down where to focus
Is it me or does it seem using OT as master clock seems to cause issues
the effect can actually be kind of cool but not in an uncontrollable state
for anyone that wants to hear what it sounds like
the bug is very pronounced on an output test I did to the zoom h5
the quasi-tape delay effect wasn’t meant…it sounded good though
hello, I do not think the problem is octatrak because i myself the same problem and it’s my Machinedrum is master, however I did the last update so I can confirm that the problem really comes from this update because before everything was working very well no problems.
no, thats not an octatrack issue…this was just a proof that this behavior is coming from a “wonky” midiclock, regardless if its coming from an octatrack, machinedrum, daw or anything else.
A4, had another issue with OT as master where trying to add/remove a trigger sometimes just wouldn’t work…you had to hit it multiple times to remove it…I think they fixed that in the last update right?