Skip to content

Saving a specific compound chord completely wrecks the chording library #196

@Mammal4963

Description

@Mammal4963

Setup: Save the below compound chord with the impulse menu.
shipment = s+p | m+n+t

Prerequisites:
s+p doesnt by itself have a chord.

m+n+t = [backspace] + ment
(I don't know if this matters).


After I save that compound chord on next reconnection I suddenly have over 6k chords in my library (when I only actually have less than 600 chords).

To fix the issue I have to remove all chords. Save it. Its happened twice now, and on the second time I needed to rollback to a previous version, factory reset, clear all chords, then there were a few chords remaining including s+p=[blank], that could not be deleted without a factory reset, then I could delete it. Something is clearly broken with that.

Once I deleted everything I could restore to a backup (which I luckily had taken the day before). Still lost a few chords, but wasn't too bad.

I think that the bug has something to do with the way compound chords are saved when the root chord doesn't have a chord output. I think it should use "no key pressed" as the output in this case instead of leaving it undefined.

But its just a theory because some other compound chords I made with no chord output for the root didn't make this issue happen.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions