[droydmaester]

Thanks, Mike. With regards to #1–3, if I'm reading correctly, there should be a touch action to turn these on or off, but there is not currently in the Windows version because the touch action isn't included in the list of available options? Once this appears in the list, would it already be possible to add the turning on/off of face gestures via a smart button?

2. The status indicator would be helpful. Assuming that it might go in one of the two places mocked up (overlay or quick action box), then making it clickable as a toggle would be really great, and seems to me to be intuitive. To me, the quick action box seems the more logical place so that the indicator/setting would be visible quickly in performance mode without having to turn it off.


with indicator in either QA box or overlay; toggled off


with indicator in either QA box or overlay; toggled on. If setting to tie face gestures to performance mode were added, then toggling performance mode on would turn on face gestures as well.

As it currently stands, there are two major benefits I see to adding this functionality:
  - 1) battery saving by not using the camera in rehearsal mode (learning, marking up the piece, remaining on a particular page for a long period of time)
  - 2) stability. While markedly more stable than in my previous email to you, it still crashes somewhat frequently. I've noticed that if face gestures remain on for a while without detecting a page turn, they seem to stop watching for gestures at all (though the camera remains on as evidenced by a camera on LED on my device). Additionally, when face gestures are on, touching the screen (edges to turn pages or access features on the overlay) seems more likely to trigger whatever is causing the app to crash. (Not always, but it's much more likely to crash after touching the screen when face gestures are on.)


Perhaps long-pressing the indicator could take you to the face gesture settings page.

Regarding #4, there was something happening with a particular piece where I had a particular page turn mode set for that piece (i.e. 2 page turn) and it was preceded by an odd number of pages in the set list before it. Then, the first page would end up on the right side, and when turning two pages, then the next page would end up on the right (backwards reading order). I was able to figure out a work-around in the last few services I played.

I will experiment further and if this is still something I'd like to suggest, I'll start a new topic with some more detail and experience under my belt. Thanks again!

Thanks for sharing your experiences and feedback. Responses below:

1) Is this really necessary given that I already support a touch and pedal action to do this?

2) I'm okay with adding this, although, once again, I'm not sure it's necessary given that you can already assign a touch or pedal action to turn them on or off. What I'm missing at the moment is a status indicator so users know when it's active - adding that is on my list of things to do.

3) This is a bug - I didn't update the list of touch and pedal actions to match what is on Android/iOS. I'll get this fixed.

4) It sounds like the scenario you are unhappy with is if you put a blank page first, that blank page could end up on the right side, with the next page on the left side which you don't want. The only way to prevent this is the "separate songs in two page mode" setting. I don't want to have to add another "per-song" type setting to indicate whether it should be displayed separately from other songs, or force it's first page to be on the left, as that is just a can of worms with how the logic works given all the different page turn modes, display modes (including book mode), etc. I think the current setting to separate songs in two page mode completely covers this, and I'd like to hear more about why it is insufficient for what you are wanting.

Mike