Wow Carl,

I'm glad to read you think you may have an idea what's going on. I've noticed on my machine, which is admittantly older than many, the amount of time needed to save a BiaB file can vary.

BiaB seems to do a lot of background tasks during the save function. For instance if you're saving a SGU file that will be used as part of a UserTracks, BiaB may create a "memo.txt" or "options.txt" file during the save process. Then there are other tasks like updating the screen or message log. While some tasks happen with every save, others don't so it's easy for me to understand why the time needed to save changes.

I don't use BiaB for live gigs but many forum members do. A few have mentioned in other postings they prefer to use BiaB live, versus using prepared tracks, for greater variety or to accommodate musicians that ask to set-in. Obviously there are limitations and advantages to both methods. Luckily, both methods work.

Jim Fogle - 2025 BiaB (Build 1128) RB (Build 5) - Ultra+ PAK
DAWs: Cakewalk by BandLab (CbB) - Standalone: Zoom MRS-8
Laptop: i3 Win 10, 8GB ram 500GB HDD
Desktop: i7 Win 11, 12GB ram 256GB SSD, 4 TB HDD
Music at: https://fogle622.wix.com/fogle622-audio-home