MIDI input latency over 300ms.
Reported version
3.0
Type
Performance
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
I just upgraded to 3.0, and MIDI input is now painfully slow. When I press a key on the keyboard, there's a delay of almost a second before I hear the note sound. Then I release the key, and there's a similar delay before it stops playing. Worse, there's a separate delay for every note: if I play a chord, they don't all sound together. They get played arpeggiated, with a significant delay between notes.
This is in version 3.0.0.20137 running on macOS 10.13.4, using CoreMIDI for MIDI input.
Comments
How big of a score are you working on? If it only happens on a big score but not on a small score, it could be due to #280952: Score Editing Slow
Does it happen on a fresh blank score?
That might be the case. It's 60 measures of full orchestral score, so not huge, but not tiny either. I tried an empty score with only one instrument, and there was no perceptible delay. Note, though, that it happens even when I'm not in note entry mode, so all it's doing is playing sound, not actually editing anything.
Ok. Sounds almost certainly to be a result of #280952: Score Editing Slow, rather than an issue with slow midi input. Making as duplicate.
I don't think it's actually the editing that's slow. It happens even when I'm not in note input mode, and using the mouse to make changes to the score is still fast. But it does seem to be the same issue that's being discussed in https://musescore.org/en/node/280890.
> "using the mouse to make changes to the score is still fast"
Just to be clear, what type of changes are you making with your mouse that are fast?
In reply to > "using the mouse to make… by ericfontainejazz
Moving notes around or inserting new notes.
In reply to Moving notes around or… by peastman
With 60 measures in a score with >50 instruments, using the mouse and qwerty keyboard is fast, though it is very slightly slower than on the same score with 20 measures. I don't have a real noticeable slowdown until i get somewhere over 100 measures, and have a several year old computer with not much memory. It sounds like you have a midi issue. What's strange is that you're the only person I've see talking about midi being slower.
I have compared midi input into an empty document. Musescore 3 shows a bigger delay than Finale Notepad 2012, chord shows a slight arpeggio. My system: Musescore 3.4.2.9788 Intel Core i7-7500U, 16 GB RAM, Win x64 10.0.18363.720, USB-Midi-Keyboard Akai LPK25.
Version 3.6.2 stable.
MIDI Input with both a USB MIDI Controller, and a USB MIDI Synthesizer both have incredible latency.
Compared with different APIs: ASIO vs best latency from WASAPI,MME,DirectSound, etc
MuseScore 3.6.2: 177ms w static, 352ms
Finale Notepad 2012: 24ms, 87ms
Ableton Live: 12ms, 97ms
FL Studio: 14ms, 97ms
The issue may actually be caused by the issue tracked below.
https://musescore.org/en/node/322301
The Input latency has been an issue since 2016 from the forums.
The latency here makes it impossible to use midi input for anything faster than 100 bpm, as we can put in 3 notes a second before musescore fills out all the rests with notes, merges notes together as chords, etc.
Tested with five different MIDI controller keyboards, all have extreme latency ~ 300ms. Happens with any midi input at all. This basically prevents an entire feature from working.
Still no more than 5 reports, still not crashes of corruptions
and first report against 3.0
Still not sure whether it really isn't a duplicate of #280952: Score Editing Slow