Hi VSL Team,
I've been able to replicate several times now with both 32-bit and 64-bit VE-PRO servers when connected to Pro-Tools.
System:
Mac Pro - 2 x 3 GHz Quad-Core Intel Xeon
Memory: 16 GB 667 MHz DDR2 FB-DIMM
Mac OS X Version 10.6.4
Sound Interface: Apogee ensemble
MIDI Controller: M-AUDIO Keystation Pro-88
Pro Tools (LE) Version 8.0.4
VE-PRO - Build 6853
VI-PRO - Build 6853
ISSUE #1:
It doesn't matter if I have the servers connected or not. It also doesn't matter if the servers are even started in memory -- I saved the sequence in Pro Tools, rebooted the machine, reloaded Pro Tools and the sequence without starting the server. Tried to delete with the VE-PRO application not connected and the same issue is still present. There is no error message of any sort. It just blanks out. Pro Tools remains stable. Very repeatable.
NOTE: Also for the record, I did run the Disc Utility and repaired disk Permissions just to be sure.
I've literally have tried everything I can think of only left with creating a new sequence and starting over. This may be a Pro Tools issue considering that it happens when the server is not loaded into memory, but the VE-PRO application is still attached.
This does not happen with any other Virtual Instrument except VE-PRO.
Thought you might want to check on your end to see if you can replicate. Please let me know if you are seeing the same thing there. Ticket # 67988.
ISSUE #2:
I've been working with running both the 32-bit and 64-bit version of VE-PRO on a single machine. No problems except that when I save both instances metafile and try to load from the meta file, it only allows one or the other, not both. The only way I've been able to reload my setup is to load the 64-bit instance using the metafile approach and then load the 32-bit server, followed by loading the applicable vframe file or opening the metaframe file from within an empty 32-bit server menu. In the past, I was always able to just click on the applicable metafile. Actually, I was able to make an alias of each, save them to my desktop and click on both to bring up the two instances.
I should be able to load both by using the meta file approach shouldn't I? Please advise.... Ticket # 67988.
ISSUE #3:
This one is not repeatable but when I go to change channel colors in VE-PRO, the disc drive will cycle for about 3-4 seconds then VE-PRO quits. I've sent in an support ticket on this one many months ago but still no change. Usually, I will repair permission, then it will be ok for 10 or so color changes before it acts up again. The only thing I have running during that time is VE-PRO and Pro Tools. I've also had this happen using Logic and Cubase, so I don't think it is sequencer related...... I will again repair permission, followed by a reboot, and then I'm ok for a few color changes before it will again act up. Not sure if it is the permission repair or the reboot that resets things for awhile. Ticket # 67988.
ISSUE #4:
One other thing that I have noticed is when I load an instance of Miroslav Philharmonik AU in VE-PRO, the interface does not paint or should I say, fill out. It's mostly white. When I select a different channel and then go back to the channel with MP, the interface colors are then filled correctly. Ticket # 67988.
ISSUE #5:
When right-mouse clicking on the left column of VE-PRO in order to perform an insert, delete or duplicate a channel, the menu will blank from time to time. I found this happens when Pro Tools is performing it's auto-save function. Obviously, turning this off eliminates the issue, but personally, I would like to have it remain on. Not sure if there is someway that VE-PRO can maintain control until the menu function is completed. Ticket # 67988.
ISSUE #6:
When I go to load a channel preset in VE-PRO using VI-PRO and originally created using the latest release (Build 6853), VE-PRO crashes and the interface disappears from the screen. The application remains in memory but disconnects from the Pro Tools application. This has happened several times since receiving the latest update. A Crash Report has been included in the technical support request. Ticket # 68487.
Thanks.