Delay + Track Selection causing artifacts

S_R · 2014-08-18T00:00:00.000Z

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.

Many thanks!

biologik · 2014-08-18T00:36:59.000Z

not sure what you mean. if you hit a different track #, you get some sort of change in the delay effect from a different channel?

S_R · 2014-08-18T00:53:07.000Z

It’s sounds like more of a pitch change. I just created a blank project to test it.

Put a single trig on track1 trig 1 and start playback
Turn up delay on track 1
Press the track 1 button or any of the other track select buttons repeatedly during playback and notice the effect

When I do this I hear changes in the pitch of the note being played back…

I’ll try and make a quick video…

S_R · 2014-08-18T01:03:01.000Z

Here is a quick video that shows what I am talking about:

It gets more obvious when there is more going on in the track but you can clearly hear the change when moving through the tracks in this video.

poonti · 2014-08-18T02:35:24.000Z

If I’m hearing this right, it’s all the delayed notes that are affected but not the trig itself. Hmmm, wonder what’s going on!!?

biologik · 2014-08-18T02:56:12.000Z

turn off the external sync for bpm and only use transport send… i bet that’ll fix it.

I find that when I use ableton to slave my A4’s bpm i get the same drift because it’s trying to adjust.

S_R · 2014-08-18T04:10:21.000Z

Interesting, that does indeed make the problem go away…does that mean there is no way to use tempo sync? It is currently sync’d to the Octatrack.

Thanks for the tip this was driving me crazy!

subq · 2014-08-18T05:44:23.000Z

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).

S_R · 2014-08-18T12:34:08.000Z

Thanks for the help and sanity check guys, look forward to an update fixing this then!

analogback · 2014-08-18T13:01:30.000Z

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.

switchbox · 2014-08-18T13:55:08.000Z

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

subq · 2014-08-18T16:00:14.000Z

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

tsv · 2014-08-18T17:12:44.000Z

I noticed this with the AK slaved to the RYTM as well. I hope it gets sorted soon. I’ll test when synced to logic and pro tools also.

It does make a cool pitched tape sound but you don’t always want that as subq said.

analog_therapy · 2014-08-19T11:49:04.000Z

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.

switchbox · 2014-08-19T15:05:20.000Z

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.

nirun · 2014-08-19T15:32:46.000Z

revert to 1.1D and you should be all good, i had the same problem with the newest OS as subq already mentioned.

subq · 2014-08-19T20:43:48.000Z

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?