Notes dropped in old bitwig when going faster

[baconpaul]

@sense and I had a long chat on slack this morning about bitwig 1.3 with head of surge. He notes that as notes go faster - not super fast but faster - they sometimes drop. We diagnosed a couple of things because I thought the problem may be that he is running into line 228 returning without having processed all events. See the discussion on slack #general Jan 19 around 7am for more on why I think that.

This issue lets us track it. Immediately I'm going to send him a branch for debugging.

[itsmedavep]

This tool may help with diagnosing what is happening with the MIDI.

http://www.midiox.com/

[baconpaul]

Well we confirmed it wasn't what I thought it was. So now we don't know what it is.

[itsmedavep]

Another tool suggestion to figure out the MIDI. This one is far more up to date than MIDI OX

http://www.tobias-erichsen.de/software/loopmidi.html

[sense-amr]

i can definitely attest to this happening :) ... and i have no idea why ! .. tried Baconpauls special branch and it didnt result in highlting the issue so it must be something else.. but it still happens.. and there are some other odd anomolies .. such as losing each second row on the octave of notes.. lets see if i can demonstrate with a video here..
weirdbitwigSurgePoly.zip
bearing in mind this IS a test with the special Baconpaul build..
i can do a normal build version test too ..

[sense-amr]

here is normal build ..
weirdbitwigSurgePoly_NormalBuild.zip

[baconpaul]

My special build has only debugging information so is same as master when you tested it.

[sense-amr]

yes then this is an ongoing issue through out all the builds of surge i guess.. like i said i have noticed it happening before but kinda found ways to work around it being a problem in the music and sound i was making.. but it really is still there.. and its weird cos its not consistent .. and pretty hard to reproduce exactly the same result each time..

[sense-amr]

i mean lets be honest a synth that still plays multiple notes AFTER switching it to "MONO" mode .. isn't really working properly ?

[mkruselj]

Closing due to multiple reasons: BWS 1.3 not being relevant anymore really, lack of feedback on the issue if it was maybe fixed in newer versions of BWS and/or Surge. Issue probably doesn't happen anymore. If it does, we will reopen it. If it doesn't, may it rest in peace.