Bluetooth foot pedal — How to avoid double page turns?

ShiroKuro I've had trouble with this as well. I've had my page turner for less than a year and I can't say I've mastered it. I've found that I need to keep my foot off the pedal when not turning the page, and then for turning the page it's a quick stab with my foot. It seems to work best if I'm wearing only a sock on my foot. With experience I've gotten better at it but I'm not good enough with it yet that I would feel comfortable using it in a performance.

My Airturn has an app. In the app you can set how the switches work - its been awhile since I did it, but I seem to remember you can set it to send a pulse on/off and no key repeats. Might be worth looking into if your pedal has an app. I also set the codes that mine sends so it always goes forward no matter which switch I press.

Sam

ShiroKuro interesting to read how different people use it. I keep my pedal slightly off to the side of the pedal lyre, so my foot is not hovering over the pedal, it’s resting on the floor. When I need to turn the page, I move my foot and tap the pedal. If anything, my problem is that the page sometimes doesn’t turn, not that I tier multiple page turns.

I used a PageFlip Firefly for 4 years, but I found I was getting more and more double page turns. I'm now using an AirTurn Duo, which for the moment is working better than the PageFlip: we'll see how it holds up after a few years.

I couldn't find a way with either of these pedals to prevent double page turns. I use ForScore as my music reading app. In "Performance" mode, if you turn pages by tapping on the screen, a double tap will be interpreted as a single one, which prevents unwanted double page turns when turning with your finger, but unfortunately this doesn't work with signals input through a Bluetooth pedal.

My preferred technique with a Bluetooth pedal is to put it next to the Una Corda pedal, rest my foot on it and do an up-down movement when I need to turn a page. When I need my left foot for the Una Corda or the Sostenuto pedal, I'll have to move my foot across and I may have to turn a page by hand.

If you use mobilesheets there's apparently a setting to avoid double page turns. It requires that you hold the pedal down for a short time before the page turn activates.

I don't have a pedal myself so I haven't looked at, looked into or tried it but it's apparently in there (somewhere).

ShiroKuro @rogerch does that mean you play from a paper score when performing?

Either paper score, memorized, or improvised. So far I've only been using the page turner (AirTurn Duo) for my sight-reading practice. When things go wrong the interruption is annoying but the stakes are lower than in a performance.

Sam My Airturn has an app. In the app you can set how the switches work - its been awhile since I did it, but I seem to remember you can set it to send a pulse on/off and no key repeats.

Thanks for the tip, Sam! I turned the repeat off on mine and that helps a lot!

It's so weird that the score viewer apps don't just have a simple threshold implemented. Me as a software developer, I would simply implement a setting of XXXX milliseconds that needs to pass by, before another "page-turn" click is accepted. And a long press would reset the score. Only one pedal-button is needed, then. Make hardware as cheap and simple as possible. And as a "page turn" I would not just go one page forward, it would be a programmable display section to satisfy the needs of repeats and codas. Something like display bottom 3 staffs of one page together with top 2 staffs of next page. This programmable concept would also allow to overlap always one staff, if needed.

But this is just my thought as a software developer, and I don't know the needs of a professional musician.

Btw: I found a good method to page turn printed music: Glue post-it stickers to the border of your sheet music. So you can't miss a page nor get accidentally two of them. Ring binding preferred.

WieWaldi It's so weird that the score viewer apps don't just have a simple threshold implemented.

Some years ago I wrote to the ForScore customer support asking them if there was a way to make the app ignore the second click of a double click on a Bluetooth pedal. Here's the reply I got:

Thanks for contacting us and I appreciate your feedback. Unfortunately we’re not able to offer a “debounce” feature for Bluetooth devices in the same way that we do for touch gestures on the screen due to technical limitations that make such a feature unreliable.

I'm no software developer, but I do wonder what those "technical limitations" could be.

MRC Those "technical limitations" is the unwillingness to do software changes. I would say, this is about one or two weeks in total, but distributed to different departments and therefore different people involved:

• Feature definition
• Human-machine interface (aka define menu layout)
• High level archtecture
• Low level archticture
• Detailed design
• Code implementation
• Unit test
• Code integration
• Component test
• Software test

You must know, software development has a lot of bureaucracy nowadays.

ShiroKuro I don't think so. If they implement a timeout that starts after a pageturn, let's say a 1000 ms timer that disables further page turns, it is safe to say it works on ANY device of ANY manufacturer.

Trust me, the company doesn't see the need to implement it. They think following:
Is it effort? yes (it cost money).
Is there risk of making bugs? yes (bugfixing costs money).
Do we earn more money? No, our customers buy the software as it is.

ShiroKuro I am very sure, this is hardware wear off. If something like the cushioning wears off, bounces become more likely. When I was a student in 1^st (or 2^nd) grade, I remember a physics lesson about a keyboard concept with an electro-magnetic induction switch (very expensive), that never does a double press nor omit a single, no matter how badly it is worn out. The physics professor told, this type of buttons are made for industrial usage, especially in difficult conditions with stuff like acid chemicals in the air. He told bouncing is an issue that happens on all normal mechanical buttons, and the only way is to detect a "drive through" movement, like this electro-magnetic induction, or a light barrier (like Novus NV5 key sensors, haha). But if the button is a conventional one, that triggers when two metal plates are touching and electric current starts to flow, you always get micro-bounces. And with wear and tear, the micro bounces become bounces beyond the sampling rate, and then you get double and triple presses. I remember we students started a discussion how software could solve this, and the professor agreed. After a few minutes he said, software isn't physics and he is here to teach us about physics concepts like the electro-magnetic induction.

tl;dr;
Wish you good luck on your concert!

WieWaldi Trust me, the company doesn't see the need to implement it. They think following:
Is it effort? yes (it cost money).
Is there risk of making bugs? yes (bugfixing costs money).
Do we earn more money? No, our customers buy the software as it is.

Thanks, WieWaldi, this was what I suspected.