Whenever I try to change the motion on the main track, Scaler locks up. I understand on a performance track you cannot change to a motion outside the existing motion group. But in this case I have no performance track, only a main track with an assigned motion. I’m not sure if changing to a new motion group is restricted on the main track, but in any case Scaler should not lock up when trying. Update On further testing I find that Scaler actually isn’t locking up but taking about 90 seconds to apply the change. You just as well say it is locking up because after 30 seconds of tapping around with no response I’m closing out the app anyway.
Do you have a third party plugin on that track? If so try removing it and try again please. Otherwise restart your iPad. There should be no ‘lock up’!
No plugins, just a sequence of chords on the main track. I did restart my iPad but that didn’t help. I think the issue is the length of the piece, which is 118 measures. I find that other operations, for example changing the motion resolution does the same thing. It seems that rebuilding the entire midi track on a long piece all at the same time appears to lock up Scaler, but it’s just taking a long time and there is no indication that anything is happening. It might be a good idea to pop up a message like Working… when an operation is going take more than a minute so the user doesn’t kill the app thinking it’s lock up. More important, and I’ve said this before, all the training videos and demonstrations that I’ve seen, both from Scaler and third-parties, involve compositions of only a few measures. But there are issues that come up on longer pieces that are not apparent with short compositions, so it probably would help if testing is done on, not only 4 measures, but on tracks with a 100+ measures.
Hey. What iPad are you using? I use Scaler 3 every day on entire tracks. Sure things can get slower but nothing like locking up. The recent update on Desktop is performing very well with 256 Bar tracks. There’s a new code merge in Beta for iOS due out next week. That also improves performance.
I’m using an iPad Pro 5th Generation with 256GB, iOS version 26.3.1(a).
I don’t want to over-exaggerate the amount of time it takes me to replace the motion on the main track on a 118 bar piece, so I timed it. On the iPad it took 58 seconds, WIth the same piece on a PC it took 4 min 11 seconds,
Is this what you are doing (changing global motion at the bottom)? If not can you give us some steps to follow so we can test please. As you can see attached its instant for me when I have 158 bars and multiple motions. iPad or desktop
Steps: On the Main Track I tap Select All from the 3-dot menu. Then on the Motion Selector above the keyboard I tap the name of the current motion which brings up the Motions window, In the Motions window I select a new motion by tapping the name. That is when Scaler freezes. Is there a way to send you the file for you to examine?
I started fresh with a new blank preset and built up a progression of 150 random chords and tried changing the motion on the main track. This time, like your sample, the motions changed in a second. So it seems that the file that is giving me problems may be corrupted. I can tell you that file has had many edits applied to it, adding and deleting performance tracks, changing motions, etc. Somewhere along the line one of those edits must have corrupted the file.
OK, sounds like something odd may have happened in one of your sessions. If it happens again please let us know here. S3 performance has improved greatly so we are always looking out for edge cases. Cheers.