Advancing to next song in setlist using bluetooth pedal

[David & Kristin]

Hey there, sorry to pile on with another question right after my first one was sorted out. I'm actually not sure if this particular behaviour is expected or not, so it may not even be a bug.

I use an Airturn BT-200 2 button pedal connected through bluetooth to change through songs added to a setlist.

I don't have any fuctions assigned as "long press/hold" actions, and have the "AirTurn mode" turned off. I have the AirTurn buttons set to send Page Up and Page Down commands, and those register correctly when I use the "Test connected pedal" function in the app. I have the "short press/click action" in the app assigned to "previous" and "next" for the two buttons on the pedal. I have the "show warning before moving to the next song" option turned off. I do have the the "try to scroll before changing songs" option turned on, and it generally seems to work as expected.

The one place where things seem to behave a bit funny is when using autoscroll. When autoscroll scrolls a song to the end, it ends up taking two presses of the pedal button to move to the next song.

(Though I know nothing about coding, and have no way of confirming this thought, but it seems as though the app isn't recognising that the song is fully scrolled to the bottom when the scrolling is being done by the autoscroll function, and so maybe the first pedal click is somehow taken by the app as a scroll command, even though the song is already at the end, and doesn't actually show any more scroll movement with that first click.)

If the "try to scroll before changing songs" option is turned off, only one click is needed to move to the next song, regardless of autoscroll function. This is as I'd expect.

When not using autoscroll, it also works as expected. Pedal presses manually scroll the song, and once the song has been scrolled to the bottom, the next single click moves to the next song.

Even when using autoscroll, if I use a pedal button to manually scroll to the end, overriding the timer, the next single click moves to the next song.

To be clear, this was happening before the most recent update to the autoscroll timing, so it doesn't seem to have been brought about by that fix. Though I can't remember exactly, a few years ago I didn't seem to have this issue. I've had the same pedal and device throughout. I didn't use the app much for a year or two, and after updating and starting to use it again in the past few months, I noticed the need for two clicks.

Overall, it's not a huge problem, as an extra button press isn't too tough of a workaround. I just though I'd let you know, but please don't take this as a complaint. Let me know if there's any other info I can provide which would be helpful.

Thanks again for all the time you've put into this app.

David

[Gareth Evans]

Thanks for the detail in your bug report!

You were spot on with your theory about the app didn't recognise that the window was fully scrolled to the bottom as this check wasn't being called at the end of the autoscroll, only when manually scrolling, so the app was first trying to scroll before moving to the next song.  I suspect this bug has been there since the beginning of v6.

Fix in place for v6.3.0

Best wishes,

Gareth

[David & Kristin]

Thanks for your reply. I've just updated to v6.3.0 and still have to use two clicks to move to the next song in the set. Whatever change was made doesn't seem to have solved the issue as I'm experiencing it. If there's any other info I could provide, I'm happy to help.

Also, on a separate note, after this recent update the autoscroll timer is now autohiding regardless of what setting I've selected in the menu. I usually leave the timer display permanently on (deselecting the "Autohide autoscroll" option), yet now the timer hides after 30 seconds whether this setting is turned on or off.

Thanks for your help

David

[Gareth Evans]

Hi David,

Whilst tweaking the autoscroll code, I forgot to run the check for the user preference before hiding!  I've fixed that now.

I'm a bit stumped on the two clicks issue - I did see the same issue as you before when you previously raised it, but the last change I made has fixed that on my devices.  I'll keep checking to see if there is anything else I can see.  Can I check that you are using Performance mode?

Gareth

[David & Kristin]

Yeah, just double checked and it is set to Performance mode.

I fiddled with a few things to see if I could discover anything else, but it's still acting the same as it was previously.

Let me know if there's anything else I can do to be helpful.

All the best

David

[Dean Brenneman]

David, have you updated the app, since Gareth made the fix?  And have you tried logging out of the OnSong App and then logging back in?  That particular trick helped me recently when I had updated the app but it was still behaving like it had not been updated! Good Luck

Dean

[David & Kristin]

Hey there, I just wanted to follow up and check in about this. I have made sure the app is updated, and have restarted the phone and app and such.

Just the other day, I tested this again with a different phone, which is a different brand with a different version of android, and I'm getting the same behaviour on both. Not sure it would matter, but one phone is a Google Pixel 4a with Android 13, and the other is a Sony Xperia Z5 with Android 7.

(As a follow up on the side issue of the autoscroll timer hiding, that's working as it should, and is staying on throughout the scrolling in line with the selected setting.)

Is there any reason the fix you made to have the app check that the window was fully scrolled at the end of autoscroll wouldn't work with certain settings or versions of android? I've tried adjusting a bunch of display and footswitch options, but can't seem to find anything that helps the problem.

Thanks again

David

[Gareth Evans]

Hi David,

I'm not seeing that on my test devices, however,  I can't test all devices and don't doubt that it might be happening for you (I certainly don't have either of your devices).  I've put in an additional bit of code to force the app to treat the end of normal autoscrolling as a the page having been scrolled to the end (rather than trying to check this by calculation).  Hopefully this will help.  Expect this in v6.3.3.  Can you let me know if this fixes it.

[David & Kristin]

I've just had a chance to do some testing with new version (actually 6.3.4 now).

Good news, the two clicks issue seems to have been resolved. When autoscroll takes a song to the end, a single click advances to the next song in the setlist. Thanks for your persistence in solving this.

Not sure if it's related, but unfortunately another small quirk seems to have popped up. When autoscroll has taken a song partway through, clicking the "previous" button on the pedal immediately brings up the previous song in the setlist, rather than trying to scroll up first.

In the same situation (autoscroll having taken a song partway through), clicking the "next" button on the pedal scrolls down (as expected).

What I've also noticed, is that in the same senario (autoscroll partway through a song), if the "next" button is clicked first (scrolling the song down a bit), and then the "previous" button is clicked, it funtions as expected (scrolling the song up a bit).

In either of the last two cases, with the button clicks successfully scrolling the song first, when the top or bottom of the song is reached the next click in the same direction brings up the previous or next song in the setlist (as would be expected).

Sorry to bring up bad news mixed in with the good! Thanks again for all you do with this app!

David

[David & Kristin]

Hey Gareth, I just wanted to check in briefly about the latest scroll thing.

Have you had a chance to test the behaviour I described, where sometimes the previous button (with try to scroll before changing songs turned on) scrolls up as expected, and sometimes it jumps to the previous song? I'm just curious if the problem is limited to my device, or is affecting others as well, and if you have any thoughts about a solution?

Thanks again for all your help, and sorry this has been so complicated.

Merry Christmas

David

[Gareth Evans]

Hi David,

So sorry for the delay - I've been snowed under at work recently (day job), so the app (fun evening job) has had to take a bit of a back seat!  I'm planning on spending some time on it today to see if I can see what is happening.  I suspect you aren't the only user seeing this.  I've stopped using my page turner just down to space on the floor (typical guitar player who loves getting new pedals), so because it hasn't affected me, I am often unaware of issues.  I suspect some of these bugs were introduced when I tried to apply the last fix for you.

I'll let you know how I get on, hopefully with a fix in time for a Christmas present for you!

Gareth

[Gareth Evans]

And that was a quick fix!  Sorry again for the delay, but expect this in the next release this week.

[David & Kristin]

Gareth

Glad it was a quick fix, your support is awesome. And no apology is needed for any delay; it's a free app after all, so any help at all is already a bonus!

Hope the load from you day job slows down soon, and you get to enjoy a restful and worshipful Christmas.

David