Latency error in EQ+

[_leras]

I have sent them a suggestion on this to enable to PDC after the next press of play. They maybe wanted to avoid clicks on adding EQ+.

They should really fix it though.

[flechtwerk]

Sorry for bumping this, and sorry for a small rant, but I just can't believe this is not being fixed. A DAW like Bitwig is made for FX chains running stuff in parallel, and EQ+ is unusable for that if you want to avoid the unwanted side effects. It could just be a hidden setting in the Inspector Panel, "Compensate latency" or something like that. But having a stock EQ with uncompensated latency (and not really warning about it!) is just unprofessional.

In every Bitwig version change, I hope to find something about this problem in the changelog, but it seems to be not happening :/

[billcarroll]

I've stopped using EQ+ and now just use Pro-Q 3.

EQ is the most important plugin in any DAW, and I have to agree EQ+ needs to be fixed.

[flechtwerk]

I use EQ-5 for smaller duties and Equilibrium for bigger ones. But EQ being such an important tool, it's a much faster workflow when you can immediatly see (and correct it) in the device panel... So a good stock EQ is important imho.

[valankar]

Here is the response I got from support in July 2021:

EQ+ introduces around 4 samples latency which intentionally do not get compensated for to enable click-free operation when loading or deleting it while playing.

And my response:

Would you please consider changing this? To me, there should be a big warning about any effect not compensating latency. It leads to many people trying to use it in parallel configurations and ending up with big surprises. By default it should compensate, and if for some reason a user does not want this there could be an option to not compensate.

Another option mentioned in the thread is to just have it detect if project is playing or not, and if playing don't compensate latency until stopped.

I also notice EQ-2 and EQ-5 don't have clicks when enabling/disabling filters, and it seems right to do similar for EQ+.

Older thread is here:

viewtopic.php?t=566555

[PhilipVasta]

I feel like there must be something fundamental about the design of EQ+ that prevents latency compensation from being viable. That it avoids clicks when loading or deleting may be true, but to my mind it seems little more than a nicety; it seems more like a side effect than a deliberate design choice. Uncompensated latency, especially in an environment like Bitwig where users are likely to run things in parallel, is so fraught with potential problems that I can’t imagine the Bitwig developers would intentionally leave it that way unless they absolutely had to without completely rewriting the device. I think the avoidance of clicks is probably convenient explanation but not the real one.

[Dionysos]

Is it actually a constant latency across the frequency spectrum, or actually a phase shift caused by oversampling?

[billcarroll]

Is it actually a constant latency across the frequency spectrum, or actually a phase shift caused by oversampling?

"EQ+ introduces around 4 samples latency which intentionally do not get compensated for to enable click-free operation when loading or deleting it while playing." - Bitwig Support

I recommend everyone who is not happy with EQ+ (I include myself in this) send an email to support@bitwig.com to let them know what you think and would like to see for EQ+.

[liquidsound]

This is why it's called EQ+ (+4 samples latency)

[swindus]

This is why it's called EQ+ (+4 samples latency)

[Lutein79]

In latest Beta Bitwig was added latency to the EQ+

[Chameleonman]

In latest Beta Bitwig was added latency to the EQ+

Send a bug report. The latency was a feature.

[questionaire]

In latest Beta Bitwig was added latency to the EQ+

Does your comment mean that the latency everybody is talking about seems to adressed by Bitwig and that it is solved? I never paid attention to the latency myself
I can see some latency being compensated 0.4 msec in the mixer

[questionaire]

In latest Beta Bitwig was added latency to the EQ+

Does your comment mean that the latency everybody is talking about seems to adressed by Bitwig and that it is solved? I never paid attention to the latency myself of EQ+
I can see some latency being compensated 0.4 msec in the mixer so issue solved right?

Soory double post

[pdxindy]

In latest Beta Bitwig was added latency to the EQ+

Does your comment mean that the latency everybody is talking about seems to adressed by Bitwig and that it is solved? I never paid attention to the latency myself
I can see some latency being compensated 0.4 msec in the mixer

Yes, the latency of EQ+ is now compensated.