Why the developers are wrong...

Hi

first post, so lets make it an interesting one.

I've read about Muscore, and had good reason to give it a try, you'll see why later. I also note that the developers say that Muscore is more about the engraving rather than the playback.

This is where the developers are wrong, yet simultaneously right, and the explanation of that dichotomy follows...

With Finale, and Sibelius, and Notation, and lastly Muscore 1.3/2.0. I created a simple score, you can too if you want to reproduce the results.

The score was this, 4/4 time, key of C, Tempo =90, 1 measure, with four quarter notes, F,A,B,D. With NO markup anywhere.

Exported this to midi, the results, were varied, they included, notes (within the same app export midi) had different note velocities, as well as differing note lengths.

After completing these tests, then contemplating of the horrors of exporting a much lager score, I decided to give Muscore a try. Same test...

Muscore on this test was the -ONLY- app to actually generate the notes with BOTH

a) equal length
b) equal velocities.

Let me say that again, Muscore was the only app to export the midi with consistent velocities and lengths.

So developers while you are quite right in wanting the engraving to be right, you now know too that Muscore is the ONLY app that actually generates the midi correctly.

Given that, you might want to seriously rethink your position on the importance of export/playback, because nothing else out there works...correctly - but Muscore.

All the best

PS you might say this is a minor test, but if these other apps can't get this right, you can pretty much be assured that and further complex test's will not improve whats clearly a bad situation.