B
bdemenil
New member
For awhile I've been noticing problems with ntrack's processing of certain plugins - most notibly Waves C4, Timeworks reverbX, and cakewalk delay. Often, these plugins will run fine on their own, but problems occur when they are run in conjunction with other plugins. For instance, if I introduce a Waves C4 into a mix which is already running some Waves EQs and compressors, after a few seconds, the sound starts to degenerate, creating horrible static. I might expect something like this if my CPU was overloading, but it's staying below 60-70%. If I mixdown offline - there is no problem with the sound. I've had similar problems with some of the algorithms on reverbX. As for the cakewalk delay, i've been having trouble getting it to work at all with ntrack - keep getting a very delayed echo even at very small delay settings.
So, when ntrack V 3.1.9 was released claiming:
"Improved support for DirectX plug-ins that delay the processed signal "
I thought the problem had been addressed. So I installed 3.1.9, and tried loading up ReverbX with a 'Room' algorithm. Well, it didn't stutter and get staticy like before - instead it introduced a ~500ms delay. So I tried an offline mixdown, and found that while in previous ntrack versions the distortions in audio only manifested during real-time processing, the 'delay' I had noticed this time was also present in the mixdown.
Conclusion:
Ntrack still has a problem with 'DirectX plug-ins that delay the processed signal'. While previous versions seem capable of handling these plugins fine in offline mixdown, 3.1.9 doesn't work in real-time or offline mixing.
Notes: I use 96K 24bit audio. Sorry this report isn't very scientific; I haven't had time to do a proper study of the problem. Will do so soon - hopefully Flavio will correct this sooner.
So, when ntrack V 3.1.9 was released claiming:
"Improved support for DirectX plug-ins that delay the processed signal "
I thought the problem had been addressed. So I installed 3.1.9, and tried loading up ReverbX with a 'Room' algorithm. Well, it didn't stutter and get staticy like before - instead it introduced a ~500ms delay. So I tried an offline mixdown, and found that while in previous ntrack versions the distortions in audio only manifested during real-time processing, the 'delay' I had noticed this time was also present in the mixdown.
Conclusion:
Ntrack still has a problem with 'DirectX plug-ins that delay the processed signal'. While previous versions seem capable of handling these plugins fine in offline mixdown, 3.1.9 doesn't work in real-time or offline mixing.
Notes: I use 96K 24bit audio. Sorry this report isn't very scientific; I haven't had time to do a proper study of the problem. Will do so soon - hopefully Flavio will correct this sooner.
