Txt File of Crash Report Attached

[VonJohin]

I open the program, add a track, it adds the track which starts to flash on and off on the screen while also making the record enable button flash with it. It starts the spinning beach ball of death and then has to be force quit to close. I am going to try remove preferences, etc. now, but something is very wrong here and I have not a clue what it is. It worked for one day, then it started doing this. I was pretty happy to have the Mac version mainly for Ninjam, and even paid for the license, but at this point, I'm not exactly getting my money's worth.

Maybe one of the folks who actually know about this stuff can look at this file and sort it out. Nasty little bug, this one.

P.S. - Please increase the text file upload size. It takes 440k, not exactly a lot in this day and age, to make a report, but your limit is an archaic 37k. The zip file just barely made it under that.

[VonJohin]

Brand new install of it, this time went to open the BradSucks demo and it did the same thing, and it only makes the first track's record button flash off and on but makes all of the tracks themselves flash, and then it gives the spinning beach ball of death. Something is broke somewhere.

I am going to give Reaper a benefit of the doubt now and try to reinstall the Pro Tools software/Core Audio drivers.

Also, I created a new user account to test, and installed reaper, and it launched OK, but that's not necessarily telling me why its doing this on the main user side. Any suggestions would be helpful, especially if you can tell me where to delete the previously scanned plugins file to let it try that again.

[VonJohin]

Still can't get it to run on the main user side and can't sort out what it is that must be corrupted for this to happen. Any suggestions? Anyone?

[VonJohin]

I trashed all the user library preferences, same issue.

Tried main preferences, same problem.

New drivers install for Pro Tools and all the idiot stuff like repairing permissions. Anyone?

It apparently has nothing to do with the 002 or Pro Tools drivers, because it does this even if they are not selected at all, either in the program or in Audio/MIDI setup.

[VonJohin]

Nobody got anything here?

[mrelwood]

It apparently has nothing to do with the 002 or Pro Tools drivers, because it does this even if they are not selected at all, either in the program or in Audio/MIDI setup.

Does it make a difference wether the 002 is connected or not?

[VonJohin]

Thanks. No, it doesn't seem to matter.

[VonJohin]

I fixed the problem. It appear that the control surface was causing Reaper to freak out if I added an audio track, MIDI track, etc. So I went in and deleted the control surface so it would stop looking for it, and now it works as it should (well, as good as a beta should).