I have a high spec PC (see below left) but I have to switch my ASIO samples to at last 2056 (usually kept at 256) to get Melodyne stable as a plugin to Sonar X1. Otherwise it lets me work for a few minutes then it seems to have trouble drawing its own screen content, and then it (and Sonar X1) lock up and I can't terminate either by the Task Manager - I have to turn off the PC!!!
Using such a ludicrously high level of samples causes small but noticeable sync problems between MIDI and audio tracks, so it's not tenable to keep working around things that way.
Surely with my PC I shouldn't have to raise the samples to any more than normal, and certainly not to 2056?

Edit:
When things freeze Task Manager shows:
(i) 3GB of my memory is in use, i.e. half. (When I load Sonar empty it takes up 1.4GB, and with my project it's 2.8, with ME inserted 2.9GB)
(ii) Processes say that Melodyne is 'Running' but Sonar is 'Not Responding'.

My project is in 48Khz. Is Melodyne uncomfortble unless it's 44.1Khz?

John

Hello John,

the recommended buffer size is 1024 samples from our side. Have you tried that? We know it is a high value but it is the price you pay for being able to use DNA.

Hi Ulf

Yes, I tried that first but had to keep raising the samples. Under 2056 I get the exact same effect after about five minutes or so of working, ME becomes unable to draw blobs, then a few seconds later doesn't respond at all and stops, at the same time causing Sonar X1 to freeze solid, with a complete restart or the PC being necessary.

John

Hello John,

are there any other plug-ins involved? It is not a general problem. You do use the 64 bit version of Sonar X1 as well as the 64 bit version of Melodyne editor, don't you?

Hi Ulf

Yes, there are other Sonar plugins on other tracks, e.g. EQ and Reverb, but surely I shouldn't have to go to every track and turn all those off whilst I use ME?

Yes, I'm using Sonar 64 bit and 'Help' in ME says it's the 64 bit version.

John

Hello John,

no, these plug-ins shouldn't cause any problems. Have you tried a fresh 44.1 and/or 48 kHz project to see if the same error occurs?

Yes, I get the same problem.
I've run some other 'elimination' tests and now found that the crash is time-based. In other words, nomatter what other things are running, or what the sample rate is set at, I get the freeze-up after about five minutes working. The Performance monitor in Sonar X1 shows nothing is straining memory or disk transfer-wise. I can work around things, therefore, by only working on a short clip at a time and hurrying up before my time is up!
This is obviously crazy with a 'power' setup like mine.

Does this 'time limit' symptom suggest anything? Something must be building up or looping and then causing the stall. I'm not au fait with programming etc, but is this indicative of a memory leak or something similar that progressively builds until freezing the host is the only option?

PS: Sonar X1 has had a problem with Intel's AVX protocols (no, I don't know what they do either, but apparently Sonar's code has to thoroughly take them into account to enjoy certain performance advantages) and I was in direct email contact with Cakewalk's CTO last month over two specific glitches in Sonar which they ultimately tracked to errors with their AVX programming in Sonar X1's 64bit version running under Windows 7 and with Windows 7 Service Pack 1 installed. I understand AVX issues will be fixed in Sonar X1's patch X1c due next month. If you cannot throw any further light on this problem then I must pin my hopes on this Sonar patch.

Hello Skyline,

let's close this issue here and continue here:
viewtopic.php?p=26366#p26366

Best, Ulf