I have a few songs where sometimes I play faster or slower depending on my mood or crowd feel. Or sometimes my tempo just sucks, lol......however sometimes when i try to back an auto-scroll up a bit cause i'm going slower than the scroll rate.....it will adjust to where I stop adjusting, but then resume scrolling at an insane speed.
Is this related to a setting? I feel like (from memory) its not on every song, but last night for sure it happened and I just could not fix it. Once it starts scrolling super fast, its a train running away.
Please turn off Settings > General Settings > Auto-Scroll > Recalculate Speed If Overridden if it's on, and submit a help ticket if that doesn't fix it.
I will try that and report back.
Appreciate your help, though I rarely need it here, your response time and willingness to help/support is amazing.
Hi Arlo,
I hope you're doing well.
I've noticed some unexpected behavior with the "Recalculate Speed if Overridden" function in the app, and I'm wondering if it has changed or if its functionality has somehow reversed recently.
In many of my songs (I have hundreds), the pre-existing scrolling settings no longer seem to produce the same results, even though they've worked flawlessly for years.
Here's my use case:
I perform long medleys—sometimes 8–10 minutes—containing a lot of text, chords, and notes. To keep everything in sync and visible on-screen, I've been using a combination of "scroll to page" and auto-scroll. My automation typically follows this logic:
Scroll to a specific page.
Start auto-scroll at a designated time.
Stop auto-scroll at a specific time.
Scroll to another page.
This setup has always been reliable, producing predictable results. However, since one of the recent updates to the iOS app, I've noticed a change in behavior. It seems that the recalculation now factors in time or text position differently than before.
For songs that previously worked well, this change causes the scrolling speed to decrease progressively as the medley goes on. This results in the automation tracks producing incorrect outcomes.
I hope my explanation makes sense! Could this be an issue with my installation, or has something changed in the app?
Looking forward to your insights.
Best regards,
Arie
PS: I just found that switching the Recalculation to OFF, seems to eleveate the issue. May be the default settings did change causing the issue to appear in one of the last updates?
Please try this again in the new version 2024-11-22 coming out tomorrow, and if that doesn't fix it, submit a help ticket:
https://helpdesk.arlomedia.com/arlomedia