Midi In has changed (0.9.6 regression)

• Jan 22, 2010 - 00:46
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

First reported on the forum
In 0.9.5, Midi In worked as follow:

  • Select a duration
  • Press the key on the MIDI keyboard
  • Note appears on the score

From r2451 (and maybe before)

  • Press the key on the MIDI keyboard X times
  • Click on a duration toolbar
  • X notes appears on the score

I'm not sure it's on purpose but it's less convenient for note entry because there is no immediate feedback.

Comments

• Feb 23, 2010 - 09:37

You might test with VMPK (Virtual midi piano keyboard).
And a Virtual MIDI Driver. I use LoopBe1 but there are others (Midi Yoke, Maple, etc...). I didn't find one open source though.

Reply

• Feb 25, 2010 - 23:27

Has there been any resolution to this? MIDI note input is distinctly less efficient than it was in 0.9.5 especially when using a computer piano keyboard MIDI controller emulation like Sweet Little Piano. In 0.9.5 I can select the duration, activate SLP and play away and notes are added with every piano key press. In 0.9.6, I have to press a piano key then click on the duration in MuseScore then go back to SLP hit a key, and back to MS and hit a duration, etc.

It is slightly easier with an external MIDI device. I can hit a note on its keyboard with my left hand and then click on the duration for it to appear in MuseScore. But this is still a lot less efficient than selecting the duration then playing successive notes on the keyboard.

I'm using MuseScore in a college class of 30 students. We wouldn't be able to use 0.9.6 as is for their entering notes via MIDI because I can't have them buying external MIDI controllers.

Why was this procedure changed from 0.9.5?

Reply

• Feb 26, 2010 - 05:10

Norman Lowrey,

"Has there been any resolution to this?"
Please read the comments above. Are you using a nightly build that is newer than 21.feb? Please include the revision number of the testing build that you are using. For details see [[nodetitle:How to report bug or ask for support]] .

"Why was this procedure changed from 0.9.5?"
Things can break. This is the nature of code development and the purpose of nightly builds, prereleases, and testing.

Reply

• Feb 26, 2010 - 16:13

David,

---"Has there been any resolution to this?"
"Please read the comments above. Are you using a nightly build that is newer than 21.feb? Please include the revision number of the testing build that you are using. For details see How to report bug or ask for support."

Thanks for reply. I did read those comments, which is why I asked if there had been any resolution to the reported problem. I see you commented "Reported as fixed in ChangeLog (21.feb). I don't have a MIDI keyboard to test with though." I gather this refers to a more recent nightly build than the official 0.9.6 beta release on Feb. 2, which is what I've been using to test out things to see what changes have been made from 0.9.5 which I'm having a class of 30 students use for their theory/composition assignments. I frankly haven't had the time to test nightly builds but will try to get to this as soon as possible.

Sorry if I didn't follow proper procedures here. I had also glanced over that page of How to report bug or ask for support but was submitting this in a rare spare moment (because of having a snow day at our university, of all things) so forgot about the details.

Anyway, I know a tremendous amount of work is going into developing MuseScore. I'm greatly appreciative. Thanks!

Reply