musewhirl

As previously posted, this bug is can be closed since for follow PPP enabled, it returns the behavior prior to the changes, and hence passes the regression tests. And also as mentioned before, I don't generally disable follow PPP...except by accident, so rarely use the feature. But there are three scenarios worth reviewing. The first two are easy: I can see how a user could have a loop in the timeline while playing a composition and want to look at some other point out of view. Then they must disable...

All issues reported have indeed been fixed. This bug can be closed.

The bug has never surfaced again since reported. I think this can be closed.

Looks totally fixed now. The velocity default is now set to 100 for the segments I checked after the deprecation popup is closed. It also quietly fixes sessions affected by the zero default velocity condition, when they are saved. I did have one default velocity of 56, and since I never made (?) so it must have occurred as a side-effect of something else prior to this fix. This fix would not change it to 100, because it was not set to the unlikely value of zero. I could not duplicate the steps that...

The edited note now remains selected in the EventEditor after the editing popup closes, even if its location was changed.

Here are the screenshots using samples recorded at sample rate 44100kHz. I added a third screenshot 3-randomness-44100kHz.jpg to show that even those with no HRTimer can be on grid...sometimes. By eye though, they are far more likely to be off grid. I guess actual off-grid averages could be obtained via a statistical analysis comparing a sample with peaks exactly on grid with these...but it would have to be something like audacity comparing wave forms, and I'm not sure it even has those capabili...

It's important to bear in mind that it's not the zero per se which is the problem. The zero was always in the dropdown, but it was never the default. It becomes default when the OK is hit on that deprecated popup i.e. the one to correct the previous problem velocity issue. I can even see it happen now, but only with sessions after the change you made and removed from master. If any of those sessions are saved after the popup, then all the segments default velocities become zero. If the save is aborted,...

Ahhhh, but I didn't change the default. This problem is related to that change involving the "deprecated elements" popup mentioned in [#1774]. Prior to popup, the rg file <matrix> element has velocity=100. But after that popup instructs the user to save, the velocity in the rg file is changed to zero. The default velocity in the menu bar is correspondingly set to zero on opening the MatrixEditor on those elements leading to new notes being zero. Now that is going to cause considerable grief to anyone...