So this is just with the library sync feature, correct? I imagine a library backup/restore wouldn't have this problem as it should just be using the same database. The code should be handling capo and setting it correctly, but I will run through some tests right now to see if I can reproduce what you are seeing. One more thing - the problem doesn't occur when updating an existing song, but only when a new song is generated during the sync, correct?
Thanks,
Mike
Thanks,
Mike