Hi Aleja78,

Thank you for the thorough detail and explanation of your issue. I've been away for a couple weeks, but will address this now. Your songs should work as structured, and we'll work to fix this.

1. Has support for older BB2Go songs with *_render.m4a files changed in the newer iOS app versions? - This sounds like a bug, and *_render.m4a file compatibility shouldn't have changed in the last update.

2. Is there a way to convert or migrate these older songs so the existing rendered M4A audio is preserved and used by the iOS app? - Opening one of these songs in the app, then saving again should move the .m4a content (if present) into the song file.

3. Is there a utility in BIAB 2024 Windows (or another method) to embed or link an existing *_render.m4a into the SGU file without rendering the song again? - The 'bundling' feature where .m4a and notation / RealCharts content is saved into the song file is exclusive to the mobile apps at this time.

4. Is “M4A+ Ready” related to this older ZIP import format, and is there a way to recover or convert these songs? - "M4A Ready" indicates .m4a audio content in the same directory as the song. "M4A+ Ready" corresponds to a song file with the .m4a audio bundled in the same file.

The "your_old_biab_songs.zip" file should only be visible in the Export view, so it sounds like another bug. The archive is created to collect (for backup, or re-import) all old files from the old version of iOS Band-in-a-Box, prior to the 2.0.0 update. It can sometimes be empty, and the "Open" function in the app isn't calibrated to handle it, either way.

- Tim