As the title suggest, below is the EoF error that I'm getting:

http://i.imgur.com/lxhE75c.jpg


In case it's tough to see, it seeks to the arpeggio chord all the way to the left of the pic. It does actually save the arrangement .xml, but I get the following error in the Toolkit when trying to add it:

http://i.imgur.com/XRC5iIJ.jpg

I am in fact using the latest version of EoF (1432). Here's the arrangement's .xml: https://www.dropbox.com/s/arrwi04wmwtsndx/PART%20REAL_GUITAR_22_RS2.xml?dl=0

Deleting the entire arpeggio and re-charting it did not work. Some backround:

This project is nearly a year old, and used to work perfectly until I decided to swap in a new .ogg, which somehow led to a shifting of the entire beatmap - requiring EVERYTHING to be synced all over again. I received this error when trying to save it after the re-sync.

And help/advice would be much appreciated! Thanks in advance...

I'd need the EOF project to do any troubleshooting.

Ah, didn't realize you'd need that too. Here it is: https://www.dropbox.com/s/5da57l7ny1pgqih/notes.previous_save.previous_save.previous_save.previous_save.previous_save.previous_save.previous_save.eof?dl=0

I'm not sure why it adds another "previous_save" to the file name each time the project is saved. It doesn't happen with the vast majority of my other projects. But I suppose this might be besides the point :D

Thanks, I've fixed this. It looks like it would only happen if the base chord in an arpeggio/handshape had more than one non ghosted gem. As far as "previous_save" being appended during each save, this would probably only happen if you are opening the previous_save backup each time you load your project (meaning you are editing an old version of the project). The next hotfix changes the file extension of project backup saves, so it will be hard for people to do this on accident.

Awesome. Thanks as always for the help.

Will you be releasing the next hotfix soon?

Up now.