Hi, I have experienced similar issues with Nectar and the usual things like making the processing buffer larger have had positive effects in terms of reducing drop out but also introduce unsatisfactory latency. I feel this is a problem for Izotope to solve rather than it being a Cakewalk problem. My impression is that Nectar appears to be trying to do a lot of its processing in close to real time and when that imposes significant load on the processor drop outs appear. I'm not sure why Izotope chooses to do this as it would seem like an easy fix to process the waveforms over a longer period of time in close to real time when it is doing the analysis.
Hi, I have experienced similar issues with Nectar and the usual things like making the processing buffer larger have had positive effects in terms of reducing drop out but also introduce unsatisfactory latency. I feel this is a problem for Izotope to solve rather than it being a Cakewalk problem. My impression is that Nectar appears to be trying to do a lot of its processing in close to real time and when that imposes significant load on the processor drop outs appear. I'm not sure why Izotope chooses to do this as it would seem like an easy fix to process the waveforms over a longer period of time in close to real time when it is doing the analysis.