MarkGuitar I had considered that exact question as part of my decision to move from using .WAV to .MP3 files. It goes without saying that there should be an additional overhead to playing MP3 vs WAV due to, in theory, the decompressing on the fly that has to occur for MP3 playback.
The big questions then become:
- Is it a theoretical performance impact or a practical (i.e. real world) performance impact?
- If there is a performance impact, how much?
I just did a very unscientific test using ST4 Build 1897.
I played a multitack song with 2 x stereo WAV files and another with 2 x stereo MP3 files and watched the CPU meter at the top of the screen.
There was no perceivable difference in CPU impact.
In my case (iPad 9th Gen with iOS 26.0.1, ST4 playlist open, timestamped lyric sheet with highlighting open, audio regions defined and Top Panel Display = Audio Regions control [i.e. buttons]) both songs ranged from 20-30% CPU.
Just out of curiosity, I then tested another song also using MP3 files but no Audio Regions - big difference on CPU. It was usually below 20% with the odd spike into low-20s.
So on my device with my config, Audio Regions are a bigger performance impact adding approx. 5-10% CPU overhead.
Very unscientific, but makes me comfortable that I'm not risking increasing load on my iPad by moving from WAV to MP3.