Hi Andrew, I installed the latest git version of MusE and played all songs which I completed so far since last summer. They play without any error until the end.
Regards, Jens Am Montag, 21. Dezember 2015 schrieb Andrew Deryabin: > Hi Jens, > > Mainly this fix is for already recorded staff, midi keyboards send > this message just right. > So you can, of course, test it. > > I think the test is passed if all your songs are playing right after > recent updates :) > > Regards, > Andrew > > 21.12.2015 12:41, Jens Radloff пишет: > > Hi Andrew, > > > >> There is a message ME_NOTEOFF which is a standard midi note off > >> message width code 0x80. It's sent only when playing with midi > >> keyboard as part of jack/alsa midi events. > > > > I do not have an external midi keyboard, so I could not test your > > fix, right? > > > > Regards, > > > > Jens > > > > Am Montag, 21. Dezember 2015 schrieb Andrew Deryabin: > >> Hi guys, > >> > >> While rewriting midi support code for lv2 I found some interesting > >> moment: > >> > >> There is a message ME_NOTEOFF which is a standard midi note off > >> message width code 0x80. It's sent only when playing with midi > >> keyboard as part of jack/alsa midi events. > >> But when playing midi parts this message is not sent at all, even > >> when transport is stopped. > >> While digging I found _stuckNotes array which is used for sending > >> note offs automatically (fix me). But due to small bug in code for > >> adding stuck events to this array, instead of adding ME_NOTEOFF, > >> ME_NOTEON was added. Some instruments handled this without any > >> problem, but others (like Calf monosynth) continued to play last > >> note after transport was stopped. > >> > >> Hope the fix ( bd84479) will work (like in my case). > >> Please check - if it works for you too? ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
