Step 13 at 120bpm gets retriggered(max velocity?)
There seems to be a possible bug for me in the step sequencer since the last update. If I put a note on the step 13 and the project is at 120 bpm the step seems to retrigger the step if fleksi sampler is used or if I use a synth it seems to get triggered harder(maximum velocity?). This only happens in the first cycle after pressing play after that the next cycles the step gets triggered without problems. And if I change the bpm to any other than 120 the step also behaves normal. I’ve also restarted the iPad without luck.
iPad 8 iPadOS 18.1. On my iPhone 13 Pro ios 18.1 the sequencer behaves without problems.
Comments
I can't replicate this on iPad 9th gen iOS 17.7.1.
@Sigi If you can reproduce this reliably, please consider sending your project to info@...
Thank you!
Yea on my iPad 8 I created several projects at 120 bpm and it happens consistent. Shared the project to my iPhone 13 Pro and it works without problems.
Do you mean info@ beepstreet . Com?
@Sigi Yes, exactly 😊
This is probably unrelated and most likely user error, but I noticed just adding a number (any number ) triggers a burst every bar or something? iPhone 14 ios 17.5.1
Transport isn’t even running
why?
😮
Weird.
I can't reproduce this on:
iPad running iOS 17.7.1
iPhone XR running iOS 13.6.1
iPhone 8 Plus running iOS 16.7.7
but it happens on an iPhone 12 running iOS 16.7.
Because the number changes the bias of the output signal...
...modulate the number at high speeds and you've just created an oscillator :)
@samu except that the number generator sends a DC value which is only supposed to click once 😉
That was my expectation… once!
Could different sample rates have anything to do here?
Played with that and different buffer sizes, no change here.
Ah good then I got the right one :)
I’ve noticed also that it only happens in standalone.
So strange. I can't reproduce it on my devices with iOS 18.1 either. I'll try to find an old device I have and report back.
It seems that setting the buffer size from 512 to 256 and back fixed the retrigger behavior. :)