So, I updated my OT to the new operating system. I was messing around with some samples one on a flex track and one on a static track both of which have neighboring tracks. I noticed that the delay was stopping after I pressed stop once. Previous to the update everything was working fine. I have tried all permutations of delay settings, even the freeze delay. They all stop with one second of pressing the stop bottom. Now one interesting observation, the master track delay works as expected. I did a system reset and remounted my set. Problem persists.
1 Like
Did some more tinkering. Typically I when I place a delay on a track it is the sample track as opposed to the neighbor track. I usually put a reverb on the neighbor track. I do this to get the a reverb on the delay taps. At any rate, I went a head and placed the delay on the neighbor track and it works normally. i.e when the sequencer is playing I hear delay and when I press stop the delay keeps playing. Also, in my normal config (with the delay placed on the sample track and the reverb on the neighbor track) if the sequencer is stopped and I trigger a sample normally I get the delay sounding like I should. If I press stop once the delay goes away.
If I have a sample on a track that is not followed by a neighbor track, it behaves normally. The delay taps continue on and on after stop has been pressed only once. So it seems to be something is messed up in the sample track > neighbor track pathway.
1 Like
i noticed that neighbour tracks are cutting off audio from thru tracks shortly after stopping. this seems to be a bug in the new OS…
1 Like
Confirmed. I get the same scenario. The tail cuts out sharply after 3/4 of a second or so.
Created a ticket.
1 Like
…maybe they took a shortcut when getting rid of that annoying constant weeping tone bug when coming from a through track to chain up with a silent start…oops…
nice one. i mailed the beta bug mailbox too
1 Like
damn.
Haven’t even updated my OS and last night I couldn’t get the echo freeze delay effect to work on a new project I started. Delay effect would just disappear after about a second.
As anybody that submitted the problem heard anything back about this?
i got an acknowledgement which suggested that it would get investigated/squashed
1 Like
I heard back from HQ as well with a confirmation. They filled in that the cut seems to happen with any effect in slot 2 with a tail. It’s forwarded to the devs. Hopefully a swift squash.
There’s another quirk with the delay since 1.25C:
The delay buffer does not seem to clear when the sequencer stops. Not even when double-tapping to silence it - i.e., the next time you hit play, you get the delay tail layered under your track sound. Seems like you need to dial down the feedback, or select another track and trig it, to silence the delay buffer.
Anybody else able to confirm this?
I haven’t experimented with different use cases.
Was this there in pre-1.25C?
1 Like
I vaguely recall this may have been so, but I know the glitch from other gear/plugins. Very unfortunate, the other (non OT) annoying one is stretching a delay to reveal the ‘earlier in the day’ buffer contents. Not near OT to test but hope this gets attention too, good spot(s)
1 Like
It’s painfully blatant when working with SYNC off and longer delay times. Very annoying for dröne and tëxture type work. If I can get a confirmation or two my unit is not bananas, I’ll toss it over to HQ and add to the bug list.
1 Like
I found that the buffer will erase if it is allowed to pass once (equal to delay time) after a dbl-stop, if you start again early it plays what’s left of the buffer, if you let the same time as the delay length to elapse it will wipe it, that’s with me testing on full send and full feedback and sync off.
1 Like
Well done for spotting/reporting guys. Problem fixed in 1.25D 
Not sure about buffer erase, my hunch is that this is just how it is, but I can’t say if it was different previously
glad this got fixed so quickly. all is well in the world once more 