Serious Absynth rendering problem in Mackie Tracktion 2

I've been trying to render a track in Mackie Tracktion 2 I made using absynth 3.02 but no matter what I do it keeps having silent gaps in the rendered audio. This happens if I render to track, render to a seperate file or even when I use 1:1 speed. And I've tried upping my ASIO latency to max as well but makes no difference. Even a freeze had the same gaps. The really annoying thing is it's not even a CPU heavy track - it's only one track!! - the problem seems to be in the areas where automation is heaviest so it may be connected with that.

My PC is pretty high spec so this shouldn't be happening - P4 3.6, 2GIG DDR2 RAM, Creamware Scope soundcard (2 of them), 3 SATA 200 HD's, fast graphics card. Well optimised for audio (the usual reduced set of services etc) - no other tasks running needless to say.

In the end I had to render using the workaround of recording directly into Scope's own recording utility - VDAT.

I've brought this up on the Tracktion forum too but I have a feeling it may be at least partly Absynth's problem as I have had similar problems with Reaktor in the past (though they were eventually fixed - by NI and Mackie) and I know others who have reported similar incompatabilities between Tracktion and NI products.

 

Oh and to add insult to injury I can't seem to get the DXI to load either - so I can't use my alternate host (Project 5 V2) either.

 

the skipping and hanging of notes is a known problem but NI just doesn't do anything about it.

 

ok that sounded a bit harsh. they tryed fixing it with the 3.02 update and the problem was fixed with a couple of people but there are still allot of people (including me) that still have the problem, even with the update installed.

 

Yes, it also happens with Kontakt (GPO and EWQLSO).

I found that it was possible to replicate the problem in realtime by maxing out the CPU.

It's almost as if Kontakt (and Absynth) is having a "CPU Panic" at rendering time, which I find just baffling.

Currently using TapeIt2, but this is an annoying problem and it does seem that NI are a bit quiet about it.

Dunno what more we can do to bug-test it for them. I'd be happy to try out a number of solutions for them in order to nail this problem.

 

That also sounds very much like the problem Reaktor 4 used to have with Tracktion - it also used to go crazy when rendering/freezing and overload the CPU. That was fixed but maybe it wasn't just Reaktor that had the problem (maybe some shared code/methods between these apps?)