# CorOS 3.1.0 - worse latency?

**URL:** <https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353>\
**Category:** Quad Cortex\
**Created:** [November 30, 2024, 4:12pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353 "2024-11-30T16:12:08Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![blablabloblu](https://avatars.discourse-cdn.com/v4/letter/b/d78d45/32.png) [@blablabloblu](https://unity.neuraldsp.com/u/blablabloblu)\
**Post date:** [December 3, 2024, 10:39pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/9 "2024-12-03T22:39:06Z")

</div>

I measured it and noticed the same latency as before:

1.8ms Base latency (no blocks)  
3.2ms Most-used preset  
4.4ms Preset with FX loop  
4.2ms One of my most hardware-intensive presets (using only rows 1/2)

Here other users have also made measurements that align with mine.

> [@QC numbers report (latency, send levels, etc.)](https://unity.neuraldsp.com/t/qc-numbers-report-latency-send-levels-etc/10291):
>
> Since none of these numbers are mentioned in the documentation, I thought we should have a report post concerning latency, levels and maybe more. So far I discovered that : Using Rows 3 & 4 adds 2.5ms to the latency was true with CorOs 1.4 Using the Send/Returns adds 2.5ms to every conversion (Digital to Analog and Analog to Digital) was true with CorOs 1.4 The Send Output is 4.5db louder than unity gain when using a TS cable. [Still true and tested here for CorOS 2.0.0](https://unity.neuraldsp.com/t/qc-numbers-report-latency-send-levels-etc/10291/15) This post is not in…

---

_[View the full topic](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353)._