Sunday, June 18, 2017

MobileSheets on Windows 10: growing pains

I've been relying on MobileSheets on various devices for several years now, first on Android and more recently on Windows 10. The Android version was mature and stable when the developer (all by himself, it's a one man show) undertook the huge task of porting the app to Windows. I had tried it under emulation with the DuOS Android system, but never really used it that way much as I had an Android tablet that I really liked.

The native Windows release combined with Microsoft's Surface Book starting to turn up used on craigslist for increasingly temping prices was enough to push me over the edge. For most of this past year, an entry level Surface Book has been both my primary computer and my primary music reader. For various reasons, I've just moved to a significantly upgraded Surface Pro 4. One of those reasons was my increasing frustration with the music reading experience.

Some of this is inherent to the design of the Surface Book - mostly battery life in the clipboard and pen performance, and also because I had an entry level model, the limited storage in the clipboard and the fact that the microSD card lives in the base, so I would lose access to it whenever I wanted to work with just the clipboard. Ultimately, pen performance was the number one factor that tipped me back over to the Android version on a Samsung Chromebook Plus as my primary music reader.

One of the main areas the performance of the Windows app is not on par with the Android app is accuracy in annotation. The pen lags in a way that makes small figures difficult to draw accurately and quickly, which is basically what string players need in rehearsal. Now, I'm not sure how much of it is the pen technology itself (Microsoft Pen Protocol vs Wacom EMR in the Chromebook) and how much is MobileSheets inking engine, but the end result was that rehearsals with the Surface Book were frustrating in a way that working with the Chromebook is not.

Inking is significantly smoother using Xodo (a PDF reader, without specific music tools) on Windows, so I'm going to go ahead and blame the software. Using Xodo in rehearsal was perfectly acceptable, but without setlist tools and half page turns, it's not nearly as nice to use in performance. I do wish I had access to one of the new Samsung Galaxy Books to see if the Wacom EMR based spen technology is enough to make the Windows version of MobileSheets as easy to use as it is on the Chromebook.

The Windows version has seen some more significant bugs along the way as well. Two of which bit me in performance. Now, I have to give major credit to the developer, since he's working alone and fixed these bugs very quickly, but they hit me at just the wrong time to cause some major annoyance in performance.

The first bug involved annotations not acting properly over half page turns, causing the bottom half to display annotations for the next page once the top half was turned. This was only a problem for a few days, but those few days happened to hit right over a Pops concert, so I played that concert without half page turns.

The second, more significant bug, involved the complete loss of annotations between an Android backup and a Windows restore. While this is a rather specific scenario that not many people are going to have a problem with, it bit me right as I was headed into the studio to record for Resonance. I had been using the Chromebook in rehearsal as we were making lots of changes and I wrote a ton on the music.

But, I love the giant screen of the Surface Book so much, I thought I'd use that for the actual studio days. I didn't think there'd be anymore writing, just playing. I did a backup from the Chromebook the night before and restored it to the Surface Book the next morning. Of course, I didn't thoroughly check the restore before leaving for the studio. When I showed up and opened the parts, I had zero annotations. Remember that part where we had been making lots of changes and writing a lot in the parts? Yeah, it was all gone. Well, not gone, just not on the Surface Book. It was all safely in the music on the Chromebook still, thankfully. Which is a large part of why the Chromebook came with me on the second day.

That bug was fixed the next day.

It also took several attempts to restore the backup on the smaller Surface 3 to be able to use it as an auxiliary display for background parts. It kept failing (probably due to the bug with the way annotations are stored) taking over 2 hours of fiddling in between things to finally get it loaded properly.

So, of course, this brings me to my real problem, which is my inability to leave well enough alone. This all started because I was tired of dealing with the quirks of the Qualcomm pen on the HP Pro Slate 12; mainly that I had to hit the button on the pen to wake it up then wave it over the screen to make sure it had synced with all the mics before writing to avoid huge jumps in the cursor position.

I'm sure at some point, I'll get tired of the (relatively) smaller screen of the Chromebook, or of the fact that I have to flip it around leaving the keyboard face down on the stand, and I'll pine for a larger screened slate again.

So what's the point of all this rambling? For the time being, if you want to use not an iPad for sheet music, your best bet is a large Android tablet, which means your options are very limited right now. There are tons of 12" Windows slates on the market, if you're adventurous enough to put up with MobileSheet's occasional growing pains, but the last few have been significant enough and the timing unfortunate enough for me to step away from the Windows platform as a performance reader for a while longer.

No comments:

Post a Comment