Баги программы (Bugs of the program)

• Mar 7, 2018 - 19:29

The following is a post from the Russian forum as translated by Google. The original is located at https://musescore.org/ru/node/270108. I told Iota that I would post replies for him in Russian, but others are welcome to reply directly to this post.

If you do not have to write about the bugs of this music editor, then correct me.
I do not know whether the developers will be able to read these messages about the bugs found in the program in Russian, but because of the lack of knowledge of English, one has to write in Russian.

The more I study this editor, the more creeps disappointment. The reason for this - a large number of bugs.
Testing conducted on versions 2.1; 2.2; 3.0; and found bugs were present in all these versions.

1) The View menu has enabled all available windows. After the restart, half of them are no longer displayed. It is necessary constantly, after each restart of the program to include them.
Strangenesses are also observed in the View menu for problem windows. For the missing window, the menu view is active, or vice versa.

2) In the program settings, I disabled the input via the midi keyboard, but after restarting, the midi keyboard icon is still active. Those. the setup option does not work. I think there are plenty of such non-working options, if you specifically look.

3) When you try to open the notes of version 1.2 in the program 3.0, the editor crashes with an error. After restarting the program can not start because of a repeated error.

4) I do not know how anyone, but I do not get the normer to scroll through the settings of the synthesizer and mixer. You twist the slider one way, and it turns in the opposite direction or behaves unpredictably.


Comments

If it helps in the dialog:

1) This is not a bug, it is normal that optional windows reset to default status on program restart. In Edit / Preferences you can specify certain windows you want open by default. This could conceivably be extended to include other windows if there was a consensus this was valuable enough to justify the added complexity in the UI.

2) Not sure which "program setting" was used to disable MIDI, but in general, MuseScore needs to be able to look at the status of the system on startup to decide what devices to use, otherwise it wouldn't be able to automatically recognize new devices. So I'm sure that's a bug either. A clearer step by step description might help.

3) There is no 3.0 - only highly experimental nightly builds of something that may eventually become 3.0. Indeed, it is well-documented that this is nowhere near usable and may crash or otherwise do bad things.

4) The knobs in the Mixer work in a way that will feel natural to users accustomed to similar controls but can indeed feel unnatural otherwise. Think of them as sliders that just happen to display in a circular fashion. So slider up makes numbers bigger - moving the dialog clockwise.

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