4.1.1.23071203 has the same broken basic functionality as the earlier version.
Recording, say, quarter notes from a midi device, the 'cursor' moves forward, highlighting where the next note should be inserted. But subsequent notes are all entered into the same place.
So if you start on the first quarter note of a measure, nothing you do will enter notes on the second, third, and fourth notes.
Instead of advancing with each note entry, all the notes are added to the first beat of the measure.
I would attach a video file, but that functionality is broken.
(Show us how little you care.)
Comments
This is an old bug that also happens with MU3. I'm still wondering what triggers this behavior.
Works for me, though I had to update my keyboard driver.
In reply to Works for me, though I had… by bobjp
I'm on Mac OS X and so no keyboard drivers are necessary for any of my Arturia keyboads, all of which have the same problem.
In reply to I'm on Mac OS X and so no… by edwardoneill
Interesting. I see Mac drivers for my Yamaha, as well as Arturia keyboards. Plus firmware updates, which contain drivers.
In reply to Works for me, though I had… by bobjp
Maybe if I uninstall Muse3....
Did you open a GitHub issue reporting this with steps to reproduce the problem? If so, please post the link to that issue so we can check on its status,
If not, first step is for your to provide more details here so someone can try to confirm the problem. MIDI input works fine in general, so either something is unusual about your system or about your process. Please provide precise steps to reproduce the problem you are seeing. If you'd also like to do a video - those are occasionally helpful, but not normally as much as precise steps we can read and follow - just upload to YouTube or the link and include a link here.
In reply to Did yuou open a GitHub issue… by Marc Sabatella
I did not report on Github because I reported here.
The problem is commonly reported.
MIDI input does NOT work fine in general, or I and others would not be having this problem.
The "precise steps" are the same note entry.
I will add a video shortly.
In reply to I did not report on Github… by edwardoneill
https://vimeo.com/manage/videos/850691643
Here's the behavior.
In reply to https://vimeo.com/manage… by edwardoneill
Based on the video, it appears your keyboard is failing to send note off messages. See if that can be configured in its settings.
In reply to Based on the video, it… by Marc Sabatella
This happens with three different Arturia keyboards.
Are you telling me 0% of Arturia keyboards send note off messages?
Then the keyboard should play never-ending notes when sent to any midi device--which is not the case....
In reply to This happens with three… by edwardoneill
I'm saying that based on the video as the only evidence we have, it seems that this particular keyboard is not sending the proper messages. If you see similar with other keyboards, then the same may be true of them. But, itt could also be that your OS and or its built in MIDI driver or some other utility running on your system is filtering these messages out and not allowing them to be passed to MuseScore properly. Really hard to know for sure without diagnostic tools running on your system.
But to be clear: lack of note off messages - whether due to an issue with the keyboard itself or some system software - is really the only thing that would explain what you show here. MuseScore processes new notes only when note off messages are seen - that is to allow chords to be played even though technically the notes come in sequentially no matter how simultaneously you play the notes. So when there is no note off, MuseScore tries to attach the new note to the current note to build a chord, and when there is no current note, nothing happens until the note off is received.
In reply to I did not report on Github… by edwardoneill
Did any fellow user confirm the issue here when you reported it? If so, they should have then directed you to open an issue on GitHub. But I don't see any previous report of this from you here. Perhaps you forget to hit Save when you wrote up your post?
Anyhow, I have no problems whatsoever with MIDI input; works perfectly as expected. So again, if some unique attribute of your system or the precise steps you follow is causing a problem, we need those details Please tell us the details of your OS, your MIDi device, and give precise step by step instructions we can read and follow (videos are not so helpful).
Once a fellow user here on the forums confirms they can reproduce the problem given the steps you provide, then you can report the issue on GitHub. And then the developers can begin investigating.