Latency in SD 1.5 and Logic 5.0

The Spektral Delay 1.5 update works fine for me in Logic 5.0 (PC) with one exception: a large latency on Audio Instruments.

Does anyone else have this problem? Is it a known bug?

Basically, SD is unusable on Audio Instruments in Logic 5.0 without moving the tracks around to compensate for the delay. And of course, the latency is far too large to be usable when playing Audio Instruments live

Scott

 

Exactly the same problem here, although I'm on a Mac. See the other thread re: Spektral Update 1.5 and Logic 5.0.


Andy

 

I asked our Spektral Delay developers because of this problem. I hope it will bring some light into the behaviour of Spektral Delay under Logic. Reading this should make undestandable a) that SD is female b)that Logic is male, c) that there is no chance for her to avoid the big latency in Logic. So for Live performances I suggest using the standalone program or using it as send effect. If you want to add the effect to an audio instrument channel, rather do it in a second take after recording MIDI. Here are now the comments from the developers:

Spektral delay is an FFT plugin. (this we all know). what one must keep in mind when working with FFT's in realtime is the following: the higher the analysis level (eg how many frequency bands you are analyzing) the higher the latency. the formula used for computing the throughput latency can be found on page 74 of the manual.

SPEKTRAL DELAY will automatically delay the 'dry' signal of 'dry/wet'
mix in order to maintain the phase relationship of the incoming signal to the processed signal, and to enable host programs which support latency compensation to operate correctly.

ok, now on to logic audio... Spektral Delay 1.0 did not function properly on audio instrument tracks in logic audio--> why? because logic audio is telling spektral delay that he will be operating at a framesize of 1024 samples, however in fact logic is splitting this 1024 sample buffer into many smaller buffers without informing the spektral delay about this. it is a question of efficiency versus latency on behalf of emagic. the problem is that spektral delay needs to be able to know how many samples she will get so that she can determine which analysis/resynthesis algorithm she should use. the problem is further compounded by the fact that the subdivision of
the buffers by logic is neither consistent nor predictable. the fact of the matter, is that unlike a synthesizer or a time-domain effect processor, the spektral delay needs a certain number of samples before she can do her job, and she cannot change which algorithm she is using for each incoming buffer (every 3 milliseconds) because it simply is not possible. therefore, when spektral detects that a host program is registering itself with a particular buffer frame-size and then consequently changes that buffer-frame size without notifying spektral, she will go into a double latency mode and re-buffer her inputs. yes, this is a shame in the case of an insert vst effect on an instrument track in logic audio. but then why not use spektral
as a send effect? if you are working with a send effect then you should be able to monitor your dry signal with the original latency and monitor the delay effect seperately ( "delay" and "latency" are interchangable words, no?).

Best regards
Marius Wilhelmi (NI)

 

Marius,

I must congratulate you (and your developer) on your thorough and complete reply. This is exactly the kind of response I was looking for. Thanks!

(I must mention that this is the same HIGH level of support service that you provided when I had a question about FM7's FX panning. I really appreciate it. You have a NI customer for life.)

I forgot to even try using it as a send on live Audio Instruments! Great tip!

I wish that emagic would offer a configuration switch that would make Audio instruments work in a true 'Cubase-compatible' mode. This would sure eliminate a lot of really wierd 'male/female' plug-in problems

Scott

 

Native Instruments and Logic

I thank you for the reply, but I have to say that I'm about done with both of these companies. If I add up all the time I've waited for Emagic and NI to deliver on features that were in products that they had already released and that I had already paid for I can't tell you how many months that would be.

I would be better equipped to handle this news if I had been warned... NI, you left me out to dry for 6+ months with no updates or explanations on SD, a completely nonfunctional application (I have a MOTU 828 and a Mac) and now this. Well, to be fair this sounds like something that you can't do anything about but I think you;'ll understand how irritated this gets me after the long wait.