[Zubersoft]

While it's possible that could end up helping, things always get more complicated the more people that are involved, and if there is a distribution of responsibilities, I wouldn't feel comfortable dictating a schedule to people who are volunteering their time. I really appreciate anyone who would be willing to help in that way though. Perhaps if I open source some of the code at some point (perhaps create some modules that are open source but keep some of the code proprietary), that could open up possibilities. 

Mike

[Richard Berg]

Very understandable.  I know how it feels to spend your time managing developers when you'd rather just be coding.

The only way it would work is to farm out bugfixes / feature requests that are low priority for the product as a whole, yet the outside dev feels strongly about.  They also have to be fairly self-contained (in the sense of code modularity).  It would not work for major surgery that's on the critical path for release planning, like the Direct2D rewrite discussed here.

[Margaret.Maestro]

I totally agree with a better use of Stamps as to put in fingerings, bowings, breathes and all other more ''classical'' oriented marks, and that the question is about time: the ability to choose and nudge a selected symbol from a pop-up menu is a thing, but being able to choose a reduced set of marks to place in one shot would be better by far (releasing over the music places and saves it?).
Anyways, those I deal with hand writing for now, but I wish to use more of the Stamp tool when this technique is developped in the program...

Let's all hope we get more and more users (upcoming Apple collegues?), in order to guide Mike in his development strategy.

Dominic

I totally agree with this! I'm using msp on android and am absolutely loving it! My one bugbear however is adding stamps and annotating quickly, especially in choir rehearsals.

It would be great if I could create a subset of quick access stamps that are relevant to the rehearsal I'm going into. For example, the main stamps I'm going to use for choir are flats/sharp/naturals/rests and breath marks (using the bow mark for this at the moment, but if you add a tick or something similar that would be awesome!). At the moment I have to scroll through to find it, add it and nudge it into place, which is much slower than my pencil and paper wielding counterparts.  If those subsets were then able to be saved under a label (so I could have one for choir, another for when I'm marking in fingering for the piano) that would be even more awesome.

Another thing that would be useful would be an option to have a coloured frame around stamps or making the colour of stamps selectable so that it's obvious that it's a stamp rather than part of the original music. I had a situation where the conductor wanted to shorten a semibreve by 1 beat, so I added a crotchet rest using the stamp, but, when we came back to that section later in the rehearsal, at first glance it looked like there were 5 beats in the bar. I ended up adding a coloured square around the annotation but doing this then adds time to the process of adding it.

I appreciate you're really busy Mike, but thought I'd add my tuppence since you were already discussing annotations!

[Petra-Kathi]

Hi Mike,

..., and even if I did hire someone, it would create significant complications as then I would have to be a registered LLC with multiple employees instead of a sole proprietor. 

W/r/to the employees' management chores, there may be a "workaround". At least there is one over here in Germany: The so called "Werkvertrag" (treaty to deliver a certain functionality for a pre-defined amount of money) and the "Dienstleistungsvertrag" (treaty to deliver a certain amount of working time for a pre-defined amount of money). Both imply that the cooperation partner remains an entity of its own, so no employment is created. It is rather a business deal between independent partners. Both require the definition of a clearly defined goal (some 2 pages perhaps), but this is nothing compared to the work chores implied by officially hiring employees.

Cheers,
Petra

[Richard Berg]

@Margaret have you considered drawing those by hand?  Faster (no need to select a specific tool), less precise (you probably won't mistake it for an engraving issue), and color coded.

[Margaret.Maestro]

@Margaret have you considered drawing those by hand?  Faster (no need to select a specific tool), less precise (you probably won't mistake it for an engraving issue), and color coded.

Unfortunately it's not very accurate, a crotchet rest isnt really recognisable because my tablet doesn't have stylus tech built in. To get a crotchet rest recognisable I'd have to zoom in and draw it quite big, which is extra time.

[Geoff Bacon]

I tend to use text rather than free hand drawing (I find it easier and neater)
Perhaps you could devise some shorthand that indicates a crotchet then tidy it up when you get home ? (I use a Redo setlist to remember songs I need to re-edit).
I realise that this is not what you want but possibly a workaround until this updated feature gets released

Cheers
Geoff

[Cancoillotte]

What I would like to see to ease notation, on the top main menu of the annotation window:
* direct access to a few pre-selected stamps, or the 5 to 10 last used or both. For example, I need only a few of them every time (b, #, natural, mf, f, p...)
* direct access to a few pre-selected color. I  only need red, black maybe sometime blue. I don't need to choose the complete gradient of a given color. I'm a musician, not a painter ;-)
Thanks

[Eddfiddler]

Is there any prospect of a persistent stamp mode in the near future? I know we'd discussed this at one point, and I'd hoped it would be made an option (maybe via options menu) for staying in stamp mode rather than having to hit stamp for each insertion. As mentioned it would save me tons of time every time I undertake a new piece of music putting in violin fingerings.

[Zubersoft]

My plan was just to wait until the annotations rework so that I'm not spending effort changing existing functionality that is just going to be replaced. I was hoping to have the annotations rework finshed by now, but due to frequent feature requests, support requests and bug reports, I haven't had time to dedicate to the rework, so I'm way behind on it. I'm going fulltime on MobileSheets starting January 1st, so that should finally give me the time needed to develop the new functionality. 

Mike

[anvers]

 Save confirmation procedure between page turns in annotation mode...

Hi
I am using mobilesheets for big scores (both in terms of number of instruments/pages and number of pages..) in classical music.
I need to annotate and turn the pages very quickly.
The problem I encounter is that there is a lag in annotation mode as the app needs to save at every page turn. This makes the use to slow, as I have to move very fast in the score. 
When annotation mode is not enabled everything works fine and it is really great
Is there a way to disable   the save procedure for every page turn ? And have a sort of autosave at selectable time ?
Thanks a lot !

[Zubersoft]

Unfortunately, no, because the changes aren't cached in such a way that you could go through every page, and save all the changes to every page at the end. With the upcoming redesign, there is no longer a separate editor screen and my plan is to only save when exiting the annotation editing mode or at regular intervals (which will be configurable in the annotation settings). The reason to save at regular intervals is if you never leave the annotation editing mode but you had done a significant amount of annotating and then the tablet ran out of power or the app was shutdown, you wouldn't want to lose all those changes. So I was thinking about choosing a default of saving every 60 seconds or something like that, which the user can then change if they want (or disable it if they don't care about the risk).

Having said all that, saving the changes is normally very fast as it's just updating a few tables in the database. What kind of device are you using? It sounds to me like there is an issue with the write speeds in the storage. 

Mike

[anvers]

Unfortunately, no, because the changes aren't cached in such a way that you could go through every page, and save all the changes to every page at the end. With the upcoming redesign, there is no longer a separate editor screen and my plan is to only save when exiting the annotation editing mode or at regular intervals (which will be configurable in the annotation settings). The reason to save at regular intervals is if you never leave the annotation editing mode but you had done a significant amount of annotating and then the tablet ran out of power or the app was shutdown, you wouldn't want to lose all those changes. So I was thinking about choosing a default of saving every 60 seconds or something like that, which the user can then change if they want (or disable it if they don't care about the risk).

Having said all that, saving the changes is normally very fast as it's just updating a few tables in the database. What kind of device are you using? It sounds to me like there is an issue with the write speeds in the storage. 

Mike

Thanks for your quick reply !I am using:
Galaxybook 12, W10, i5, 8Go, 250 Go
The only thing I could try is to check if there is a difference if the score is on the main ssd or the added storage. 
To be completly clear, is there a difference for you in the speed by page turning in stylus mode and in the read mode ?

[Zubersoft]

If you are using the Windows 10 version, then what I said shouldn't really apply. If you have an SSD, the write speeds should be just fine, as that is where the database would be stored (regardless of the storage location selected in the settings). There is going to be a difference in the speed of the page turns though as the pages aren't cached in the current annotations editor, so it has to load each page individually. The new design utilizes the cached pages, so there will be no such delay.

I think it would be best to have you try this out with the new annotations design to see if it's still a problem, as a significant number of changes will be coming. The Android code is nearing completion, so I'll be opening that up for beta testing while I finish up the equivalent changes for the Windows 10 version.

Thanks,
Mike

[anvers]

Very good news then I will wait for the new design.
This is exactly as you wrote. From the moment I use the annotation editor while I at the same time  need to turn the pages, it is laging at every page turn. For my use, it is not quick enough as I would need almost the same speed as in the read mode.
Thanks !