There isn't a log file - I didn't want to introduce any unnecessary disk I/O which could impact the performance of the application. Perhaps at some point I'll add code for logging that is disabled by default but can be enabled in the settings, but that code then becomes code I have to maintain (i.e. any time I make changes, the logging code could be impacted), and it takes quite a bit of effort to add that code in the first place.
Without a way to reliably reproduce what you are seeing (and due to the fact that no other user is reporting this), my only recommendation at this point is for you to permanently embed your annotations in the PDFs. If you do this, then this problem can never occur again. You'll just need to load each score, enter the annotation editor, tap the three dots at the top right and then tap "Embed Annotations". You can still move or delete the embedded annotations if needed (you'll just have to enable the option to edit embedded PDF annotations), but if you aren't changing the annotations very much, then this will eliminate the problem altogether without causing any headaches. There is also now an option to automatically embed annotations that you could enable if you want to go down this path.
On a side note, the next update is going to replace the entire rendering framework in the Windows version to match what is used on Android. If this is purely a graphical issue of some kind (i.e. the annotations are showing up on the wrong scores, but those annotations don't actually exist in the score), then this change may fix this issue for you. The way to verify this is, when you see an annotation that doesn't belong, enter the annotation editor, bring up the layers window and see if that annotation actually shows up in the list of annotations. If so, then the annotation is being saved into the wrong song somehow. The only way I could imagine that happening is if there is some weird database issue where the wrong song IDs have been assigned to annotations, effectively assigning them to a different song. I would expect this to impact a large number of users if there was a bug like that though, so I doubt that is the case.
Mike
Without a way to reliably reproduce what you are seeing (and due to the fact that no other user is reporting this), my only recommendation at this point is for you to permanently embed your annotations in the PDFs. If you do this, then this problem can never occur again. You'll just need to load each score, enter the annotation editor, tap the three dots at the top right and then tap "Embed Annotations". You can still move or delete the embedded annotations if needed (you'll just have to enable the option to edit embedded PDF annotations), but if you aren't changing the annotations very much, then this will eliminate the problem altogether without causing any headaches. There is also now an option to automatically embed annotations that you could enable if you want to go down this path.
On a side note, the next update is going to replace the entire rendering framework in the Windows version to match what is used on Android. If this is purely a graphical issue of some kind (i.e. the annotations are showing up on the wrong scores, but those annotations don't actually exist in the score), then this change may fix this issue for you. The way to verify this is, when you see an annotation that doesn't belong, enter the annotation editor, bring up the layers window and see if that annotation actually shows up in the list of annotations. If so, then the annotation is being saved into the wrong song somehow. The only way I could imagine that happening is if there is some weird database issue where the wrong song IDs have been assigned to annotations, effectively assigning them to a different song. I would expect this to impact a large number of users if there was a bug like that though, so I doubt that is the case.
Mike