I'd rather not re-corrupt my database, and backups aren't working (I'd love it if they did so I could start testing this better). Reason I went radio silent for a while is because I had a horrible corruption (from a clean, new ST.DB) after micromanaging my songs a bit. I don't EXACTLY know what causes it, but it's as if the information gets offset from the track data increasingly so (where track names for each track get pushed further and further backwards, this has the humorous effect of making tracks first have no title, until they start having garbage titles from reading portions of the ST.DB that aren't supposed to be read as text). Curiously, you can only see the corruption on the Xbox and not in the software in my experience.
I used 1.3 alpha back then. Same version today for the first time in a year and had a corruption happen, thankfully early on.
After this, I babied it:
- I added music one soundtrack at a time and FTP'd after each
- I did not delete tracks
- I did everything in linear order
Everything turned out fine this time. I think it's related to deleting tracks on an already existing soundtrack (then adding new tracks to the same soundtrack), and/or moving on to a new soundtrack after doing it.
I'll send off an affected ST.DB file if I make this happen again (unintentionally) or intentionally (after a backup).
I'd rather not re-corrupt my database, and backups aren't working (I'd love it if they did so I could start testing this better). Reason I went radio silent for a while is because I had a horrible corruption (from a clean, new ST.DB) after micromanaging my songs a bit. I don't EXACTLY know what causes it, but it's as if the information gets offset from the track data increasingly so (where track names for each track get pushed further and further backwards, this has the humorous effect of making tracks first have no title, until they start having garbage titles from reading portions of the ST.DB that aren't supposed to be read as text). Curiously, you can only see the corruption on the Xbox and not in the software in my experience.
I used 1.3 alpha back then. Same version today for the first time in a year and had a corruption happen, thankfully early on.
After this, I babied it:
Everything turned out fine this time. I think it's related to deleting tracks on an already existing soundtrack (then adding new tracks to the same soundtrack), and/or moving on to a new soundtrack after doing it.
I'll send off an affected ST.DB file if I make this happen again (unintentionally) or intentionally (after a backup).