Casper Jeukendrup

See also what I said last month on Slack: > Since 4.4 is out, we’ve had a suspicious amount of reports of MIDI loops, seemingly all from Linux users; I...

@krasko78 Sorry, another rebase is needed... I've reviewed this, and have no objections, but I'm not confident enough to approve it, also considering the consequences for new unknown dock widgets,...

Currently, MIDI output is enabled if and only if a SoundFont is selected. Ideally, we should be able to select for each instrument individually to which MIDI device it should...

Personally I consider MIDI output as basically "not implemented". It was implemented in a rush, in an attempt to match MS3 in the most minimal way possible, but even that...

According to the history listed here, it was closed because it was fixed in https://github.com/musescore/MuseScore/pull/24944. This fix has probably been included in the 4.5 update, released last Friday. If anything...

We're certainly planning to address https://github.com/musescore/MuseScore/issues/19262, but I can't say yet when. Outputting time code too might deserve a separate feature request. FWIW, there are also ongoing efforts to support...

The JACK work is already in progress anyway, so no feature request needed for that; but for MIDI time code output, you could create a request, if that still matters...

When something doesn't pass the XML schema validation, I don't think we can expect MuseScore to read that correctly. And the schema check basically can't be wrong. But the bad...

Closing as not actionable

This remark may be superfluous, but watch out that the implementation takes into account that the last selected element may be deleted without touching the score view, so this shouldn't...