The strangest prank SONAR has ever played on me
I was listening to an old song the other day and decided that it could benefit from the addition of some percussion, so I pulled up the project, added a half-dozen hits and then saved and exported it. Nothing else was modified, just the addition of a few percussion hits.
So I was surprised when I later played back the file and halfway through the song everything suddenly went to sh*t. Some clips were no longer starting playback at the correct time. Thinking I'd accidentally nudged a clip, I went in to find which track was wacky, but the problem was in half of the 55 tracks. At about the halfway mark, some tracks just went wildly out of sync with the rest of the project.
Then I examined the tempo map. This is a dynamic orchestral piece, so there are several tempo changes. The original tempo map looked like this:
But in the corrupt project, the tempo map looked like this:
Here's what I believe happened. The percussion library I'd added was a home-made Kontakt library, to which I decided to add three new samples while the project was open. When I dragged the samples into Kontakt's mapping editor, the Kontakt UI went all goofy and left a large gray blank spot in the middle of the mapping editor. I closed and re-opened the Kontakt UI and all was well again, so I gave it no more thought.
That's when I saved the project and when it (silently) became corrupted. Fortunately, I had a backup so I renamed the corrupt project, restored the backup and was able to compare the two. I believe the problem occurred because I had exhausted memory while editing the Kontakt library, which somehow corrupted the in-memory image of the tempo map.
Three conclusions:
1. SONAR doesn't handle low-level error conditions gracefully (no news there)
2. Don't edit Kontakt libraries within a SONAR project
3. Freddie's been right all along: 64-bit does matter!