08-21-2024, 10:30 AM
Why do you say the other bookmark doesn't belong to the MSP song file? It most certainly does. There is no other place to store it.
You still don't understand my analogy. User created bookmarks on Kindle aren't embedded in the pdf just as MSP bookmarks created by a user are not embedded in the pdf. Kindle stores user created things in a file for each book just as MSP stores them in a song file. My point is, many apps use the term "bookmark" for both user-defined and embedded pdf bookmarks.
When I create a bookmark in MSP, it does indeed point to an individual tune or specific page within that tune. Bookmarks (all types) work exactly as described. So I still don't understand your issue. If you think MSP is confusing, ForeScore is downright mystifying. So the grass isn't necessarily greener.
For my use, bookmarks are appropriate for ad-hoc marking of specific pages within a PDF from within MSP. Songs are appropriate for managing individual tunes within one large pdf or pdf files consisting of a single tune. Songs can be searched, filtered, grouped, put in set lists, hold annotations, store meta-data. They're the primary way to access and manage tunes. While MSP bookmarks can flag tunes within a large pdf, it's really the wrong tool for the job. Your bandmate needs to bite the bullet and make a song file for every tune. As you already know, it's quite easy to do using PDF bookmarks or, if you don't have PDF bookmarks, a CSV file. My MSP library has over 6000 tunes in a couple hundred PDFs, some of which have PDF bookmarks, some of which don't. For the ones that don't, I made songs using CSV files, something anybody who has excel, google sheets or even notepad can easily do.
In any case, I'm just another user like you. I don't represent Mike's views at all, only my own. When I see a suggestion for a change I'm likely to find even more confusing, I speak up since Mike will immediately jump on every suggestion and make a change.
You still don't understand my analogy. User created bookmarks on Kindle aren't embedded in the pdf just as MSP bookmarks created by a user are not embedded in the pdf. Kindle stores user created things in a file for each book just as MSP stores them in a song file. My point is, many apps use the term "bookmark" for both user-defined and embedded pdf bookmarks.
When I create a bookmark in MSP, it does indeed point to an individual tune or specific page within that tune. Bookmarks (all types) work exactly as described. So I still don't understand your issue. If you think MSP is confusing, ForeScore is downright mystifying. So the grass isn't necessarily greener.
For my use, bookmarks are appropriate for ad-hoc marking of specific pages within a PDF from within MSP. Songs are appropriate for managing individual tunes within one large pdf or pdf files consisting of a single tune. Songs can be searched, filtered, grouped, put in set lists, hold annotations, store meta-data. They're the primary way to access and manage tunes. While MSP bookmarks can flag tunes within a large pdf, it's really the wrong tool for the job. Your bandmate needs to bite the bullet and make a song file for every tune. As you already know, it's quite easy to do using PDF bookmarks or, if you don't have PDF bookmarks, a CSV file. My MSP library has over 6000 tunes in a couple hundred PDFs, some of which have PDF bookmarks, some of which don't. For the ones that don't, I made songs using CSV files, something anybody who has excel, google sheets or even notepad can easily do.
In any case, I'm just another user like you. I don't represent Mike's views at all, only my own. When I see a suggestion for a change I'm likely to find even more confusing, I speak up since Mike will immediately jump on every suggestion and make a change.