MIDI Input Latency in Note input mode

• Feb 24, 2017 - 18:54

Hi, I'm trying MuseScore 2.0.3 and I think it would be perfect for my needs, but there's that latency issue in Note input mode that seems to have no solution. I'm on Windows 7 x64, I have a good PC (8-core, 16gb ram, etc.) and a Yamaha mixer with its low latency ASIO drivers. When I play the MIDI controller (Nektar LX49) I have no latency until I press the N key (Note input mode).
I tested all possible I/O combination (ASIO4All, MME, Direct Sound), but things are even worse...
I don't want to enter notes one at a time with the PC keyboard, I want to use the MIDI keyboard.
It's simple. :)


Comments

What latency issue do you mean? The sound might happen a few milliseconds after you press the key, but I'm not sure how that would prevent you using a MIDI keyboard to enter notes. You are aware, though, that note entry is still one at a time when using MuseScore just as it is when using the computer keyboard? So it's not actually any faster.

In reply to by Marc Sabatella

Ok. I don't know if you're one of the coder but now I'll explain what you or they should do.
I actually don't even need Musescore; many DAWs have the musical notation function integrated, but I would like to write drums tabs.
Musescore seemed perfect and it is (nice gui, easy to use, no latency when you play) until you enter the Input mode and it has to track what you play (here you have latency, notes going out of the bar).
Now, if I can not use the MIDI controller to enter more than one note at a time, tell me what is this program for?
I take less time to handwrite.
So make it works at least with ASIO4All drivers... I don't mind if it can not render notes on the score in real-time, I don't want latency when I hit the keys!

In reply to by mark7ones

Yes, I am one of the (many) developers. But I'm still not sure what you mean. Have you read the Handbook on note input? It describes how to enter notes into MuseScore using MIDI. Yes, it is one note - or at least, pone chord - at a time. The purpose of MuseScore is to produce beautifully engraved printed scores. Yes, you can write scores by hand, but they won't look nearly as nice. Also, it might be fast to write by hand for simple things, but it won't be nearly as fast for more more complex music - can your hand do copy and paste? automatic transposition? can your computer playback what you write by hand? Some DAW programs might have notation built in, but generally they don't specialize in it, so they won't do as good a job of it as MuseScore - just as MuseScore doesn't do as good a job of handling real-time MIDI as DAW software.

Basically, think of MuseScore as a word processor for music. There are some things that make sense to write out by hand, others that make more sense to use software to produce.

In reply to by Marc Sabatella

I think the answer is in the last couple of sentence in the OP:

"I don't want to enter notes one at a time with the PC keyboard, I want to use the MIDI keyboard.
It's simple. :)"

It seems obvious that there is a lack of understanding just how complex all the related issues are.

In reply to by xavierjazz

Ok, sorry. Clearly I have no idea of the issues or how complex it is.
I saw MIDI input (ok).
Choose you ASIO drivers (ok).
So I thought... now I play my controller in real time and I have my score. :)
As I said I can do it in the DAW, but I don't have drums tablatures as in Musescore.
It would be nice if it was possible... I would buy this program immediately.

In reply to by mark7ones

You can record a standard MIDI file using whatever software you like, then import into MuseScore. But again, the only reason to do this would be to get beautifully printed scores. if your goal is just to get a recording, there is no reason to use MuseScore at all.

But FWIW, MuseScore is free - there is nothing to buy :-)

I have this very issue. In my case, latency is so high that it interferes even with step entry mode. Most notably this happens when I am putting in a run of 16th notes. Often I will finish playing the run on the midi controller, and for several seconds after the software is still notating the notes. I will change the rhythmic value to continue on notating, and that will register and the software will finish notating the incomplete run with the incorrect rhythmic duration. Sometimes the lag is so high that the software may even stop responding. Since this issue has begun, MuseScore's utility for step entry is severely damaged. I am finding that inputting into an .ly file is now faster than step entry in MuseScore (in the past, the opposite has been true for me).

In reply to by nikrepka

Hmm, can you describe your setup in more detail? Maybe attach a score and precise steps to reproduce the problem? Unless some other process is hogging the CPU or other system resources, you shouldn't be seeing a latency of more than a very small fraction of a second; note input should be virtually instantaneous upon release of a key. Note, though, that it is *release* of a key, not the pressing, that triggers entry, in order to facilitate entry of chords.

Also, even if MIDI latency is an issue, no reason to resort to typing up .ly files - just use the computer keyboard entry in MuseScore, or the piano keyboard window.

In reply to by Marc Sabatella

Okay. Consider the excerpt entitled "test.mscz" attached. What will happen is that I will select 3 using numpad to set it on 16ths. Then I will begin playing the run on the midi input device. I will reach the final note and select 5 to change to quarter note. Meanwhile the software is several seconds behind, still notating the 16ths. But what happens is that I will select the 5 and MuseScore will finish off the unfinished 16ths using quarters instead, resulting in something like the second attachment (bad.mscz).

As someone who transcribes a lot of music, this kind of issue is extremely costly, as it requires extensive correction after entering notes. (I usually have my eyes on the sheet music I'm transcribing and don't catch the rhythmic issue until several bars in.)

FWIW, I found this issue goes away when closing inspector. It seems inspector creates some serious lag in input mode.

Attachment Size
bad.mscz 4.7 KB
test.mscz 4.3 KB

Do you still have an unanswered question? Please log in first to post your question.