#Astrisks 'n stuff being added to new chord entries

1 messages · Page 1 of 1 (latest)

jade belfry
#

about 15% of the time, an astrisk is added to the chord when viewed in dot.io manager. sometimes it affects the chord output. I have a video here. you can see when I add the chord, as I am doing dup+i, it adds something in that you can see for a split second before the <impulse> word pop up. It shows what seems like a random character added to the chord I am adding at that time. Then it reflects on Chord manager. I have to change it in there, especially when the chord itself does not work the same as what I put in during impulse add.

#

alsoo, you can see library commit only goes to between 95% and 98% but it still holds the changes. Also again, When I click disconnect from dot.io it doesn't do anything, page needs to be refreshed to disc and then reconnect works fine again.

#

So yea, I pretty much just use dot.io to add chords now so I don't have to go back in and make the change. eliminates that extra step if I just input in the io in the first place.

#

I cannot say whether or not this happened in the beginning or not, when I first got it.

#

It isn't ideal to not be able to have impulse add work because adding dup into the input in io when creating a chord, doesn't work.

hollow talon
#

From the video, the asterisk is actually a Backspace, which requires multiple bytes to represent.

#

I saw you backspace an 'n' before 'one' and the BKSP gets recorded as part of the phrase

#

dot i/o currently does not render multi-byte action codes correctly.

#

My tool does show it, and you can even input it:

#

The only downside is that it stores chords as it's own format (JSON) when exporting, and I have yet to code the restore from file yet.

jade belfry
#

I see. Thats ok, if I can add there and then it can be exported for backups in csv from dot.io is the way I understand?

#

Chord entry works great. Love it. Nice work man, thanks for sharing that. I never noticed that part of the config site