Melodyne and Other VST Issues

I have been using Sonar X1 since it was released and have had a number of intermittent and unusual problems.  Current issues:
 

• Melodyne works fine in some projects (even many instances).  In one project, while I was editing in Melodyne, I lost all the audio from most--but not all-tracks.  For example, I could open RealGuitar and clicked on the strings and hear the sound, but the RealGuitar tracks would not plays.  Same issue for Ivory and SI-Bass.  There are many. many hours of work and performances in this project and this is a major problem.
• In another project with very few tracks, editing in Melodyne locks up Sonar and I have to reboot the PC.  Only three VIs and two vocal tracks with Melodyne.  That project is lost unless I can copy all the tracks to a new project and hope for the best.
• In many projects, there seems to be a limit on the number of VI (soft synths) I can use.  6 will be fine, but when I add a 7th, I lose all the soft synth audio.  On other projects, I may be OK until I get to 9 VIs.  In some projects, all the soft synths work.

This all seems to be related to on-going issues with Sonar and VSTs.  Any ideas at all?  This is killing me.
 
Thanks.

Hi.  Tech who supports me advised me to hold off on X2 a bit.

I am firmly convinced that there has been something set up wrong from the first.  I am almost at the point of buying a new PC or MAC, and reinstalling everything--which means a lot of huge sample libraries.

Here is the catch 22: I can't stop to do that or I will never finish a critical project; however, I am constantly stalled on my project by these issues.

konradh


Hi.  Tech who supports me advised me to hold off on X2 a bit.

I am firmly convinced that there has been something set up wrong from the first.  I am almost at the point of buying a new PC or MAC, and reinstalling everything--which means a lot of huge sample libraries.

Here is the catch 22: I can't stop to do that or I will never finish a critical project; however, I am constantly stalled on my project by these issues.

Why were you told to hold off on X2?  They said to go back to X1?  Just curious.
I personally own both and still use X1 cause it's quicker to do what I want it to do.  Editing especially.

I would not get too exited. There is no mention the tech works for Cakewalk.

Sorry for any confusion. The technician is with Sweetwater and today he suggested trying a trial version of X2. I think he hesitated at first because like many people, he is leery of going to new versions when they are first out.

A few observations from my studio:

The operating system is windows... not always a rock solid OS. Things do go wrong from time to time .... just because. 

I don't generally "run out" and buy the latest upgrades and don't always load the updates as they come out. 

My current DAW is running XP pro/32 and X1 essentials (no updates) and is not internet connected. It runs pretty much like the day I first turned it on after I built it myself. 

If I load X1, and while working in my project, I notice that the generally smooth operation of X! starts to become erratic in any way..... audio glitches or a cursor that starts to get a bit "jumpy"... I will click on SAVE and then close the system completely down, including the interface and start again from a complete power off condition.

I have melodyne editor (ME) and it is probably, without a doubt the most CPU hungry plug in the stable. 

As a result, I use some precautions when I work with it. I don't very often run multiple instances of it, as having it in two or more tracks at any given time. One track at a time.  The second thing I have learned about ME.... it will crash and glitch the DAW from time to time when things don't flow correctly inside the box, and that will often result in a crash and subsequent loss of work. So I tend to work in manual correction mode, and I work on one line of the song at a time. I click SAVE when I finish that line, before moving to the next. 

Most of the time, my system is rock solid and ME runs perfectly fine and smooth and causes no problems. However, when I do see that the system is not running like a top, whatever the reason, I'm always willing to click SAVE and reboot to a fresh start.   

Clicking on the SAVE should be a habit anyway if you do not have the autosave feature turned on, which I do not. 

If you want a save icon, Duckbar has one.

Maybe, however since the whiteouts are occurring now without Duckbar, it would indicate the problem probably lies elsewhere. Who knows, it might fix the problem. Although, I have installed Duckbar on my machine, I do not use it. Installing Duckbar makes no changes to SONAR. Running Duckbar will launch SONAR unchanged with the Duckbar toolbar on top of SONAR. The program also has a backup facility to make it easy to get back to the original SONAR install should you elect to use the Duckbar modification tools.