Index Error in Bin

Thank you Eriksimon, you gave me back 2 hours of work! I had already tried opening four of the back up copies and had the same problem. I went back further and was able to finally find one that did open.

As a follow up. I worked on the same file again the next day for a couple of hours, saved and closed the file. When I reopened it, I got the same "Index Error in Bin" dialog box again. The file opened with no regions in the Arrange window. I went to the Project File Backups, had to go back 5 versions before I could open the file correctly, albeit with a "Minor correction of project data has taken place" dialog box whenever I open the file. Apparently, the Minor correction does not actually include correcting the file however, as it appears every time the file is opened.

More good information. Thanks for the heads up!

I don't see any files in there now that are more than 31 characters. It looks like Logic does some truncation of names on import though, as I imported some sound effects files and see that the names have been changed to protect the innocent...or punish the ignorant, I'm not sure which.

Index Error in Bin is REALLY insidious. Based on the last 4 hours of my life, I would say that if you see this error, you may as well just trash your file and start all over. After getting this error, opening a file and having NOTHING in the arrange window. I was able to retreat to a backup that did not have the error and allowed me to work with the file. For a while. Eventually, I started getting "Minor correction of project data has taken place (1)" whenever I opened the file. Then when I made a change to the file and reopened it, I got the "Index Error in Bin!" message again. At least the regions in the Arrange window were there this time. BUT, when I made changes to the file, NOTHING was saved. It didn't matter if I added sound files, changed automation data, or added MIDI tracks. When I reopened the file all the changes were gone. I tried the Consolidate command, the Rename command, the Clean Up command, Save a Copy As, etc. No luck.

SO, I finally gave up on that tact, created a new, empty file, browsed to the prior file and imported all of the files and data into the new file. Thinking that should at least create a new index and fix the "Index error". At first things looked good, no errors. Then I tried to copy and paste the automation data which was NOT transferred in the rebuild process. Then the "Index Error" reared it's ugly head again. Now I have a file that can't be changed—since saving the file does not save the changes, I am basically screwed.

It looks like I'm going to have to go back to my Digital Performer version and use that...after I rerecord a bunch of tracks that I had added in Logic.

I'm kind of amazed that with an error like this, I appear to be the only one in the forum with this problem. But maybe that's because when I search for "Index Error in Bin" I can't even find my own trouble report. What gives with that? Maybe the big Spotlight has an opaque bat symbol covering it up.

In case anyone is following, here's how I "solved" my problem. I went back to a version of the file that I was still able to open (albeit with the "Index error in bin" problem). I couldn't change and save this file, but I was able to export all the tracks as audio files (I deactivated all of the plugins before exporting). I then imported these files into a new document and dragged them onto new tracks. This finally seems to have gotten past the "Index error" problem.

Now I just have to remix the whole project. Yeehaw.

Final note. The problem was reported to Apple and a solution was included in the latest update to Logic. The problem was actually caused by importing a Hyper Set from another file. Deleting the Hyper Set also cleared up the problem.