Basically, I'm running MuLab UL 5.3.25 on a Windows 7 Pro 64 bit system and have various VST programs installed..both 64 bit and 32 bit versions..the latter bridged using JBridge and there has been no issues with this setup to date.
So I found it a little strange and a bit worrying when, towards the end of last week, vsts started to "die" for no reason..they just go silent and will not make a sound. For example: Let's say I open a project I'm working on, that already has a number of tracks recorded and I want to start work on a new element of the mix recording a new track. So I load, say, the Alchemy VST..which I have also never had an issue with, but after a 20 minutes or so of using it, it just goes silent and even if I were to hit record, nothing is recorded, as there is no sound.
The other tracks already recorded play away just fine..even those that were recorded using Alchemy..it just seems to be the current instance of Alchemy that is the problem. Now that's all well and good..if it were just Alchemy it is happening with..but it's not. It happens with any plugin I am using and the only way I can get things to work is to close every thing down and reboot my system..and open up MuLab and start all over again..until it happens again.
To be honest, it's getting to be very annoying and I wish I new what's causing this. I've scanned my system for malware and viruses and it comes up clean. I'm gone through each item that shows in the Device Manger..including the hidden ones and checked and updated all their drivers..all to no avail.
For the record, this issue has only started since I upgraded to the latest version of MuLab..in fact, that's the only change I've made to my system of late..so I'm wondering is it something to do with the upgrade? The funny thing is why does it seem to just happen after a while of working..and not when I first load a VST?
Any help or advice you guys can offer would be very much appreciated.
Thanks in advance.
![Smile :)](./images/smilies/icon_smile.gif)
Dan (Solaris65)