You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has happened to me several times now. During a long session, at some point "sort by Key" stopped working correctly.
Steps: sort by BPM (click in column header), select some row, sort by Key (click in column header).
The sorting itself worked correctly, except for the selected row, which would not be in the part of the table with the same Key.
E.g. I would select a row with key Fm, and after sorting the rows above and below the selected row would be with key A, and subsequently sorted as expected. But the selected row was not in the right position.
In addition to that, normally the rows are ordered by tempo as the secondary sort key (as in all tracks with the same key are grouped, and order by tempo). When this situation occurs the tracks with the same key are ordered seemingly random (or probably by some key, but not tempo).
This behaviour continued but occasionally the sorting would work correctly. After restarting the app the problem disappeared.
I am not sure if this happens at random, or if it is some specific action or circumstance that triggers this (I am even wondering if it is by design and I haven't figured out the rationale). I haven't seen this in the past though.
Version
2.5
OS
macOS
The text was updated successfully, but these errors were encountered:
Bug Description
This has happened to me several times now. During a long session, at some point "sort by Key" stopped working correctly.
Steps: sort by BPM (click in column header), select some row, sort by Key (click in column header).
The sorting itself worked correctly, except for the selected row, which would not be in the part of the table with the same Key.
E.g. I would select a row with key Fm, and after sorting the rows above and below the selected row would be with key A, and subsequently sorted as expected. But the selected row was not in the right position.
In addition to that, normally the rows are ordered by tempo as the secondary sort key (as in all tracks with the same key are grouped, and order by tempo). When this situation occurs the tracks with the same key are ordered seemingly random (or probably by some key, but not tempo).
This behaviour continued but occasionally the sorting would work correctly. After restarting the app the problem disappeared.
I am not sure if this happens at random, or if it is some specific action or circumstance that triggers this (I am even wondering if it is by design and I haven't figured out the rationale). I haven't seen this in the past though.
Version
2.5
OS
macOS
The text was updated successfully, but these errors were encountered: