Build 1848 crashes /slow to respond

DickyDutch

Have sent you my crash report via email. Latest build is slow to respond eg can take up to 5 secs to go from from playlist to song list. Other button presses also slow to response. App also freezes. Testing on iPad.

peter

DickyDutch Thanks, I received the crash log. At the moment I can only tell that it is not a crash but the app was terminated by iOS because it was using too much CPU. I don't know why at the moment but I hope analysing the log will give some hints.

AnthonyB

Not seeing any UI lag/performance issue here with 1848 (iPad 9th Gen, iOS 26.0.1)

Dare I ask - have you tried rebooting your iPad?

Could you provide some more info e.g. iPad model? iOS version? anything else.

I imagine if it were an general Build 1848 bug the thread would be lighting up with others reporting same so, at face value, it feels like some local to your environment or config.

DickyDutch

AnthonyB will try rebooting iPad as you suggest

Sharonzaz

AnthonyB Not seeing any UI lag/performance issue here with 1848 (iPad 9th Gen, iOS 26.0.1)

Dare I ask - have you tried rebooting your iPad?

wow, how did I not think about this???
I shut down my ipad after every gig and since I downloaded the beta it has been on, app quite laggy
and slow to respond, reading I had an oh wow moment, rebooted and the app is now snappy.
thx 🙂

AnthonyB

Oh that's interesting!

Assuming multitrack audio - how many tracks? audio files format?
Other audio plugins in use in the mixer?
What does the CPU meter above song title say?

DickyDutch

Rebooted iPad and re opened ST4. Operation still very very slow and froze completely at one point with the CPU meter at 80%!. I don’t appear to have the same problem on my iPhone 16 but I only have less that 20 songs loaded on that whereas on my iPad I have my full ST3 backup loaded approx 10gbs

peter

DickyDutch I have analysed the file. The high load is caused by the song list rendering. How many songs do you have in the song list?

peter

I have found a potential cpu performance issue in the song list that will eat up more and more cpu cycles just for rendering the list. It should be noticeable with maybe 500 songs and more. So if you have more than 500 songs, please check if the cpu load is lower when showing the song list after the next update.

DickyDutch

I currently have 1019 songs!

peter

The fix should have a very noticeable effect on that number of songs. Please give me feedback after the next update.

peter

Build 1865 released, please test if this resolves the load issue

DickyDutch

Have updated my IPAD to Build 1865 and so far haven't had a crash. However I can report that when I change views from Songlist to Playlist (and/or vice verse) by tapping the buttons at top left of screen it can take up to 4 secs for the relevant list to appear which seems painfully slow and something I'm not used to with ST3! The CPU is typically showing between 30 to 40% during the wait. In fact i don't think I could use ST4 on my IPAD as it is - the whole thing seems to me to be sluggish compared with ST3. Perhaps I need a new IPAD - I’m currently running iOS 17.7.10

peter

Can you please send me a database only backup? I would like to see if I can reproduce the issues with such a large song database. Please email it to support@stagetraxx.com.

peter

Disregard my last post. I have generated enough songs to experience laggy lists myself. For me it starts to feel laggy at 1500 song with an old iPad Air 3 but running iOS26 which has reportedly better list view performance than older iOS versions.

peter

iOS26 is a bit faster displaying large lists than iOS18 on basically the same cpu (iPad Air 3 vs iPad Mini 5). Both devices can handle 1000 songs fine. 3500 songs is where switching between song list and playlist view then needs about 2 seconds on both devices. CPU spikes to 50% when switching between views. Opening mixer has a 1 second lag.

When the song list is hidden, all lags or gone and the app feels snappy. So it is definitely caused by the song list.

An iPad Pro 1 with iOS16 is basically unusable with 3500 songs.

DickyDutch

peter Thank you Peter for your explanation - but can anything be done to cure the problem do you think?

A possibility of course is to provide users a way of migrating specific songs from ST3 to ST4 so that the ST4 song list could be minimised/cleaned up. I know I’ve got songs in ST3 that I probably won’t ever play again but reluctant to delete them!

peter

I think I will be able to speed it up so that working with 1000 songs on old devices will be fine. But 3000 songs on some of the oldest spec iPads capable of running iOS16 will not work satisfactorily.

For old devices, I might add an option to get rid of the alphabet sections. This is one thing that eats up especially much cpu. Try to switch the sort order to for example play "Play Count". That is an instant very big performance boost on my devices just by reducing the number of sections.

The next update will have some more optimisations.

DickyDutch

peter Thank you Peter I look forward to to the next update