• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Clarification on Snippets and Annotations
#1
Hello,
I'm trying to understand how snippets work in MobileSheets. From what I gather, snippets do not actually duplicate a portion of a score, but rather create a reference to a section of the original file.
However, I've noticed that when I add an annotation to a snippet, that annotation does not appear in the original file. I was expecting the annotation to be visible in both, since the snippet is not a true copy but rather a reference.
Could someone clarify how this works? Are annotations in snippets independent from the original file, or is there a way to ensure they appear in both?
Apologies if this topic has already been discussed elsewhere—I tried searching but couldn’t find a clear answer.
Thanks in advance for your help!
Reply
#2
A snippet is a new song that references the same file as the original but with a different page order. Annotations are not stored in the PDF - they are stored in the MobileSheets database and are separate for each song. However, if you do want them to be embedded in the PDF, you can use the "Embed Annotations" option in the annotations editor to make that happen. Then the annotations would show up in every song that uses the same file.

Mike
Reply
#3
Thanks, Mike! I appreciate the explanation.
I tried the "Embed Annotations" option, and it does work, but I noticed two drawbacks that limit the advantages of using snippets (considering that my workflow mainly consists of applying fingering to organ music scores):
  1. The editability of annotations—especially deletion—seems to be only partial. Deleting annotations appears to happen in "blocks" rather than allowing precise removal.
  2. Since the PDF seems to be rewritten each time the annotation editor is closed, this process can take a long time for large files. In my case, a ~100MB file takes 40 seconds to process on an Windows 11 PC (i7-4770/32GB/3.40GHz)).
Granted, in my case, an alternative could be to embed the annotations only once they are finalized.
I assume this behavior is due to the inherent limitations of embedding annotations directly into the PDF. Are there any alternative solutions in development or under consideration, similar to how ForScore handles this without the same performance issues?
Thanks again for your help!
Reply
#4
I'm really not sure why you are seeing those performance issues. How many pages is that 100 MB PDF? The PDF library should only be embedding and modifying pages that were actually changed, not all of the pages. I might need to have you export your song to .msf (right-click the song, click Share->Export as .msf and share the .msf with mike@zubersoft.com) so I can see if I can reproduce the issue you are describing to see if there is a potential solution. 

As far as the deletion issue, select the annotations individually (either with the selection tool or the layers window) and then you can delete them directly without using the eraser tool.

Mike
Reply




Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2025 MyBB Group.