Note Release - randomly gets stuck

[Adam_G]

@d-healey yes it does that. youll hear it a couple more times intermittently. but do you now here notes dropping randomly?

[d.healey]

@Adam_G I haven't heard any notes drop

[Adam_G]

@d-healey youre right its easy for me to say, been a lifetime fl user

[d.healey]

@Adam_G I used it about 20 years ago when it was called Fruity Loops :)

[Adam_G]

@d-healey i used it back then too :anxious_face_with_sweat:

[d.healey]

It's been going 10 minutes now and I can't take any more of the beeping :) I haven't had any drop outs and the hanging notes haven't reoccurred. Without a reliable way to reproduce the issue it will be difficult to fix unless it's obvious in the code.

[Adam_G]

@d-healey it does happen at the same time stamp everytime though

[Adam_G]

@d-healey thank you for testing it

[d.healey]

@Adam_G

it does happen at the same time stamp everytime though

Tell me more, I was just playing it in a 1 bar loop.

[Christoph Hart]

I‘m pretty sure that the reason is the handling of left over samples from the last audio buffer which causes some midi notes to be dropped because the timestamp falls outside of the range but I‘m not in my studio where I have access to FL Studio so it has to wait until I can properly debug this.

[Christoph Hart]

But just to be sure: aligning the tick lengths doesn‘t help here?

[Adam_G]

@Christoph-Hart thank you for looking into it. no unfortunately having that option ticked makes no difference for me. ill await your findings

[Christoph Hart]

Alright, I've found and fixed the issue (on the timestretch branch), so please check if it still produces stuck notes. Your MIDI file plays back correctly now, but there might be other edge cases that I haven't covered yet.

[Adam_G]

@Christoph-Hart you sir are the greatest of all time

[BWSounds]

@Adam_G
how did you build it? it keeps failing for me

[Sawer]

@Adam_G Agree! Works on my end also here!

[rzrsharpeprod]

@Adam_G One of my testers is having this issue as well and it's frustrating to not be able to pinpoint the issue and be able to solve it

Edit - I should have read the entire thread before replying to a post midway through.
It seems that it may be fixed in the latest build - I shall build and test later