some v1.00 r3922 bugs

• Jan 19, 2011 - 15:00

I am working with the latest nightly build in the hopes of helping debug it. Amazing program!

1. Open up demo Bach-bc2.mscz, which has parts. Select tab for another part like Trumpet. Now close the score. the trumpet part will end up still visible, as though it is now the wallpaper. Clicking around on the wallpaper will crash the program. This behavior seems consistent on scores with parts.

2. Selecting note entry, eighth notes and just randomly typing note letters (a-g) into the score will eventually crash the program.

3. The playback tempo on a new score, even when 100 BPM is selected, is shown as 120 BPM but 1079574528% under Play Panel. Needless to say music plays back so fast you can't hear it.

4. The moving blue bar when playing music leaves small artifacts behind in the staff. The staff thickness and color change slightly, but get restored properly when you stop playback.

5. When you scroll around to look as the score, you can go way above or below (or sideways to) the score. Why have such a large work area when it is mostly empty? it makes it easy to get lost as the blue outline bar also disappears.

6. How come you can't delete a line break element from its right-click menu?

7. Dragging the last two glissando elements leaves black pixels over the staff. Let go of the mouse button and the artifacts disappear.

Comments

• Jan 19, 2011 - 17:32

Do you know for sure the build you are looking at is meant to be for 1.0? I made that mistake when they first announced that 1.0 was coming, but it turns out the latest builds are *not* 1.0. They represent the work that is going into the *next* major release after 1.0. And indeed, it's plenty unstable, as would be expected of a program still under very active development. the 1.0 development is going on in a separate branch and isn't being posted nightly as far as I know. My understanding is that we are supposed to wait until an actual pre-release or beta build is announced.

Reply

• Jan 19, 2011 - 18:03

You're right, Marc. I was trying the nightly build R3922 thinking it was the latest v1.0 pre-release. What a major difference between the two! I like the enhanced interface in the nightly.

I went back to pre1 and checked most of my findings. Except for two things (#5 and #7) the rest appear to be new features, and they are nice but unstable. Is someone interested in my findings on the nightly builds? I don't mind playing with it, just to find the bugs.

So, I submit the following two questions or comments...

1. When you scroll around to look as the score, you can go way above or below (or sideways to) the score. Why have such a large work area when it is mostly empty? It makes it easy to get lost as the blue outline bar in the window below also disappears. You can't drag the blue box beyond its borders so I don't think the scroll in the score window needs to be big either.

2. The last two glissando elements "gliss" leave black pixels over the staff as you drag them into place. Let go of the mouse button and the artifacts disappear.

Reply

• Jan 20, 2011 - 12:42

Regarding #1 - If you're on a computer keyboard with the Home/End/Page Up/Page Down keys, you can always press the Home key if you get lost, and you will be taken to the first page of the score. Page Down takes you to the next page of the score, Page Up takes you to the previous page, and End takes you to the last page.

Reply

• Jan 20, 2011 - 13:10

It's not a matter of getting lost, its that someone can so easily. You can only drag the blue box around so far in the bottom window (score thumbnails) so why the ability to scroll around in what seems to be an infinitely large area in the main score window? Whats the point to all the unused real estate?

Reply

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