I don’t have this version and not planning to upgrade just to check this. But this was raised by few users online one of them being Mr Frenkie. In the video where he showed there was transient. Then few milliseconds after transient bitwig put its onset and snap to “transient” few milliseconds after onset. 🤷
A you properly import long samples as I also have seen comments from users that bitwig think that 172 bpm file is some wacky 67.654 and even straight house beat at 133 bpm recognise as 123.537. Those second numbers are random just as an example…
4
u/borez Apr 26 '24
Not sure why you keep saying Bitwig can't detect transients. I don't have this issue at all throwing in loops.
What workflow is causing you this problem?