pm sent.

I am and have been running into the same problem. There is something strange going on. It hangs and have to do a complete reboot. A few of my songs originally opened, then I had a weird occurrence, it was like my audio engine slowed and got real garbled. I went back to X2 worked the file for a little resaved as another name opened in X3 and everything worked fine, on that particular song.
Since that time, none of the old files will work in X3a, B or C.
I have uninstalled X2 and that did nothing.
What I am finding is that when I try to open an X1 or X2 file in X3 it will hang, When I go to X2a and open it says that it can not find melodyne. The problem is V vocal is not working with the ARA integration of melodyne.????
if anyone hear of a solution, please advise 

By uninstalling X2 you've uninstalled VVocal.
X3 does not include VVocal as such but will use it if it is on the system. The same applies to R-Mix which is not included in X3 either.

Was this ever resolved?
 
I have a brand new hard disk drive, fresh install of X3 with all patches up to date. I am using in this instance X3 32bit. When I try to load any song that I used RXP on it will not show the file loaded or play. It will not let me add any of the provided rx2 loops. Nothing happens.
I created a new song and inserted RXP and the same thing. It will not load the loop. I can create a midi track and drag an RXP loop into it and it plays fine. RXP will not work in 64bit X3 either.
 
I also notice that any other rx2 files that I own from Loopmasters will not show up in the RXP dropdown. I know they are there because I can see them in the folder. I am running as ADMIN.
 
 
X3, Windows 7, i7 2600k 3.4GHz, 16GB RAM, 4TB HDDs, RME Babyface
 
 

I have a problem with X3 Producer not opening some 8.5.3 PE projects. Some run fine, others hang in "not responding" mode until I give up and close them with the task manager. I tried removing the unrecognized plugins and saving it, then opening the "cleansed" version but that didn't work.
 
I guess if nobody here has any ideas I'll call tech tomorrow, see if they have a clue.

Was the move from 32bit 8.5 to 64bit X3?

I was using 64 bit with 8.5.3 PE.
 

Did the projects use V-Vocal? If so, what version of SONAR was used to re-install V-Vocal?

I'm having the same problem. BUT, it's with new project files between 2 machines. If been using 2 machines for years, always working back and forth (on a monthly basis) for hundreds of project files and this started for me in November while using X3 (and now with Platinum). This mainly started when I upgraded machine #1 in November of 2014. The new machine is an i7 which originally had a fresh install of Windows 8.1. Machine #2 has been the constant and used to have Windows 7. I upgraded both machines to Windows 10 a few months ago (and to Sonar Platinum) hoping that would fix the problem, but it did not. Both machines have always been 64bit with similar setups. Sometimes I can open very basic projects on both machines as long as they only have a few tracks and plugins. Not sure if this helps, but figured I'd share it.

I have no idea if it applies or not - I had a 2nd computer that was a brand new build, with an AMD 8350 processor and 16 GB of memory, SSD primary drive, and a couple 2 TB drives, patch current in Windows, as well as all software.
 
And yet, on 1 single project, that had been created with X2a, and updated in X3e, it would almost every time hang Sonar, and additionally hang the computer most times, requiring a reboot.
 
I spent weeks looking at things, trying this and that, and literally only 2 days ago finally caved in and applied some BIOS updates, and from that point on, it has played back flawlessly.
 
I have ZERO idea as to why only this single project freaked out, but the BIOS updates DID make the issues go away.  I generally only update BIOS as a last resort, and over the past 20+ years have not had to do it more than a handful of times, but in this case it was like a miracle.  The documentation on the BIOS update simply indicated it addressed some system stability issues - which is what every BIOS update I can ever remembering seeing says (along with other things like CPU or memory compatibility updates).
 
Anyways - maybe there are these kind of underlying issues at work - worth taking a look at anyways.  And, Windows maintenance is up to date?
 
Apologies if there is nothing to the above - thought I would share it because I just did have a truly bizarre set of issues vanish after the BIOS updates.  
 
It would certainly seem like some sort of localized issue for what seems like a very very small number of folks, and it would likely be far more widely reported if it were a common Sonar defect.  Just saying it is worth digging more into your system and maintenance at some level for it.
 
Bob Bone