While working on a project, I wanted to go back to V-Vocal and tweak the lead vocal track. For the first time X2 froze up and I had to get out of the program After rebooting and getting back into X2, when I tried to load v-vocal all I get is a white screen. I closed that project and loaded another I had used v-vocal on and tried to edit a vocal track with V-vocal and got nothing but a white screen. I did not lose anything, but v-vocal will not load, only a white screen. Any ideas?
Thanks and Merry Christmas
Marty

Problem solved. I reloaded disk one of x2 and v-vocal is working again. I do not know what caused this problem but it is now resolved.
Merry Christmas
Marty

mgwitt - I'm having this same issue, but I guess more severe. I'm getting an actual X2a crash when I load V-Vocal. What do you mean by reloading Disk 1 of X2? It's been a while since I installed X2, but doesn't it just install start to finish when you click the install? How did you do a Disk 1 only?

The custom install option allows you to select which parts to install. You can install V-Vocal only if you wish.

lawajava,
Sorry to hear you are too having a problem. When I ordered X2, I ordered the disk. It came with 4 disk. I inserted the disk labeled 1 and installed everything on the disk until it asked me to install Rapture 1.2.2. I then canceled the install, rebooted the computer and I had v-vocal working again. This all began happening after the X2a install. Also, I had to remove v-vocal off the track I had done before the crash and redo the v=vocal part because I could not hear the vocal track. However the track was ok after removing v-vocal. So far no more crashes. For v-vocal it was the "white screen of death"!

This was a surprise to me because X2 had worked great until tonight. I hope thr gurus get this fixed soon. 
Good luck,
Marty

Scott and Mart thanks. I spoke on the phone with a fellow friend from the forum here and he also has X2A Producer installed. On my request he fired up V-Vocal and although he said it acted quirky on launch it did successfully act as normal. So I see it as an issue that may be local to my install and may not necessarily be an issue for others. I'll try the reinstall method Scott has outlined and comment again after I've retested it.