Just grabbed the Split EQ and when I stick it on a track in Ableton, be it, hardware synth or a soft synth I get latency on the sound. any ideas?
PC: Windows 10, i7, 32GB of ram, RTX 3080 GPU so should handle it no problem.
Hello,
SplitEQ is designed for mixing applications and introduces about 70-80ms of latency due to the nature of the tonal/transient split.
You couldn’t mix with this, literally sounds out of time.
Hey moldiver, SplitEQ introduces latency, but your DAW (Ableton) should compensate for it. This is a standard feature of all modern DAWs.
In Live, you can confirm it is active under Options->Delay Compensation.
Delay compensation seems to have fixed it, forgot to check that as everything was running fine.
Cheers.
Glad to hear it!
Hello.
My case is a little different. After all, this plugin has a higher CPU cost than other mixing plugins. It takes up 10 percent of the CPU just to load it. I’m hesitant to load this plugin because I have more than 50 tracks in one project. Of course, the performance of the plug-in itself is amazing, but I hope it will be improved in the new version. If this is not possible, please add an optional switch to make it run lighter. Otherwise I will have to explain to my friends that this plugin is for mastering.
If I may add, I would like to be able to check the version I’m currently using.
Hi,
SplitEQ is certainly a CPU intensive plugin, due to the transient / tonal splitting algorithm. We have a ticket in our system to further investigate optimization of the split (as well as the whole plugin), but at a certain point further optimization would not be possible and you’d start trading CPU cycles for quality. FWIW, we’ve spent significant effort getting the plugin as zippy as we can, but there are likely some further optimizations we could explore.
Most modern DAWs run separate track processing across CPU cores, so you should find that even if the first instance takes 10%, subsequent instances of SplitEQ on other tracks will not keep adding 10% to the total usage. Additionally, SplitEQ shares some resources amongst multiple instances, so RAM shouldn’t skyrocket either.
You could try using larger buffer sizes to improve the CPU usage as well.
Currently you can see the version number of the plugin by hovering over the Eventide logo in the top right. We’ll also consider adding this to the “Info” dropdown menu.
Hope that helps,
Tom
Hi,
Tom
Thank you for your response.
Your detailed explanation helped me to make sense of it.
I just want to add that I love this wonderful plugin so much that I want to load it on all my tracks.
For the further prosperity of EvenTide.
With all due respect
Toco
SplitEQ is causing ~2 beat latency in MIDI editing in Logic (10.7.2), even with Plug-in Latency set to All, or ‘Audio and Software Instrument tracks’. Buffer is at max (1024). I reported an issue to Toontrack for Superior Drummer 3 about the lag in the Grid Editor (MIDI). After much troubleshooting, I identified that it was SplitEQ plug-ins causing the latency. Seemed to be a cumulative effect - the more SplitEQ plug-ins, the more the latency. Even bypassing the SplitEQ plug-ins didn’t work. They have to be removed altogether. Once gone, so does the MIDI lag. Sorry, Eventide. A great plug-in but unusable with this problem.
Hello,
Sorry for the issue you are having. I was not experiencing latency issues using a basic Drummer track in Logic, but we can try to reproduce this using Superior Drummer 3. Can you please send a screen recording of the issue to tskoglund(at)eventide.com so I can get a better idea of what is happening?
I also encountering massive latency with SplitEQ in Logic Pro and had to stop using the plugin. Love the idea and hope this can be remedied in future updates.
Hello,
Yes, SplitEQ introduces latency as many plug-ins do, this is necessary for for the transient/tonal split. However, many DAWs will easily correct this latency if your settings are configured correctly. In Logic, the delay compensation preferences can be found here: Logic Pro > Preferences > Audio > General
Indeed, plugins do introduce latency, but never have I seen this much. In Logic solo a track and turn SplitEQ on and off and on. The result is an unusable mush. No settings appear to compensate for this issue.
The latency compensation seems to be working correctly for me when I’m looping a drum loop that is playing in time with the projects metronome, when latency compensation is set to “all” and I add an instance of SplitEQ, the drum loop is still playing back in time.
Can you confirm that you have delay compensation set to “all” and you do not have “low latency” turned on?
Yes.
To see/hear the issue, please watch this screen capture video: https://www.dropbox.com/s/b1g37ygk3d0g7js/SplitEQ.mov?dl=0. You can see how enabling/disabling the plugin affects the sound.
Ok it looks like your settings are correct. Thanks for providing this example, but I’m sorry to say its difficult for me to tell what is going on in this video because there is no metronome and your drum track has a heavy swing. A simple way to test this would be to loop a single snare drum hit that plays in time with an audible metronome, so if there is an issue with latency it will be easy to see/hear it.
When I use Logic’s native bypass, there will be a small stutter because Logic is calculating the latency with the plug-in on/off, but this corrects itself very quickly. If you use SplitEQ’s built in bypass, you won’t experience this stutter because the latency isn’t changing. If you’re not experiencing latency issues when SplitEQ is active, then I would suggest using SplitEQ’s built in bypass.
I’m also having massive recording latency with SplitEQ on any track, not just the armed track. Which is a shame as I often add guitar parts to tracks later on. What’s also strange is that Live does not show this extra latency in the preferences. You can see the regular latency with no SplitEQ anywhere on the project (top pair) vs the extra latency caused by SplitEQ (bottom pair) below. The second (lower) track on each pair is the DI signal for reference. The regular latency is mostly fine, but the added latency makes tracking guitar impossible in any project that has SplitEQ.
I wonder if this also affects pre-recorded audio. As in, if I introduce the plugin after all the recording is done, will it still cause latency that is not corrected by Ableton Live?
I really hope this is fixed as it renders this otherwise great plugin very unattractive for me.
Hello,
Can you please let me know what buffer size you are using (it should be as low as possible to reduced latency while tracking without overloading your CPU). You should also have both “Delay Compensation” and “Reduced Latency When Monitoring” enabled in Live’s settings. I was able to reproduce your issue when “Reduced Latency When Monitoring” was disabled, but enabling this setting fixed this for me. Let me know if that helps.
Hi, thank you for the reply.
I recorded these at 128 buffer size which is what I usually use for tracking.
<p style=“text-align: center;”>As for the settings, I already tried enabling Reduced Latency When Monitoring which like you say should negate this issue but sadly it didn’t change anything. I haven’t played around with Delay Compensation though, I will give it a try. The strange thing is SplitEQ causing this latency even when off or on another track and Live does not report this added latency on the audio preferences tab. As long as SplitEQ is somewhere in the project, I get this added latency on the armed channel. I will check the Delay Compensation and get back to you. Thanks!</p>