# 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:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![morisson](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/morisson/32/7021_2.png) [@morisson](https://unity.neuraldsp.com/u/morisson)\
**Post date:** [November 30, 2024, 4:12pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/1 "2024-11-30T16:12:09Z")

</div>

I’ve just noticed that the same presets I was using for recording (very simple compressor/amp/cab) which I was getting 80 samples (1.6ms) latency readings are now around 124 to 139 samples (2.5/2.9ms).  
Example: green 808 → EV101IIIS Red EL34 100W → 312 CA Stand OS S V30 90s (M) ) total 139 samples.

Anyone else seeing this ?

---

<div class="post-metadata">

**Author:** ![Niksounds](https://avatars.discourse-cdn.com/v4/letter/n/82dd89/32.png) [@Niksounds](https://unity.neuraldsp.com/u/Niksounds)\
**Post date:** [November 30, 2024, 9:04pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/2 "2024-11-30T21:04:49Z")

</div>

Can you share the preset?  
I’ll try it

---

<div class="post-metadata">

**Author:** ![morisson](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/morisson/32/7021_2.png) [@morisson](https://unity.neuraldsp.com/u/morisson)\
**Post date:** [November 30, 2024, 11:23pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/3 "2024-11-30T23:23:19Z")

</div>

Sure: [Neural DSP Technologies - Algorithmically Perfect](https://cloud.neuraldsp.com/cloud/discover/preset/view/8b242c46-e873-4f5d-9b85-11c92321dea3)

The same preset measuring input 5 → output 7 on CorOS 3.0.1 got me 80 samples. Now I get 139.

---

<div class="post-metadata">

**Author:** ![Blue](https://avatars.discourse-cdn.com/v4/letter/b/3bc359/32.png) [@Blue](https://unity.neuraldsp.com/u/Blue)\
**Post date:** [December 1, 2024, 2:38am UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/4 "2024-12-01T02:38:27Z")

</div>

I hope there’s not more latency. I’ve been fighting it since I got my QC and keeping my presets as simple as possible because I’m sensitive to it.

---

<div class="post-metadata">

**Author:** ![SimenRaaen](https://avatars.discourse-cdn.com/v4/letter/s/dbc845/32.png) [@SimenRaaen](https://unity.neuraldsp.com/u/SimenRaaen)\
**Post date:** [December 1, 2024, 2:47am UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/5 "2024-12-01T02:47:13Z")

</div>

Try using output 7&8 on QC

---

<div class="post-metadata">

**Author:** ![morisson](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/morisson/32/7021_2.png) [@morisson](https://unity.neuraldsp.com/u/morisson)\
**Post date:** [December 1, 2024, 10:57am UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/6 "2024-12-01T10:57:54Z")

</div>

I did. The output doesn’t seem to matter.

I’m just trying to understand if there’s something with my setup that is influencing this, but until friday I had 80 _stable_ samples of latency (CorOS 3.0.1), and after upgrading I’m having quite a lot more (and not very stable, it varies a bit). I didn’t change anything else ☹  
I’m pretty sure it is CorOS.

Example on how I’m testing this:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/2/248a19b5f31607656c2daf3809ccf1fbbdacd47a.png)

---

<div class="post-metadata">

**Author:** ![sleiweke](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/sleiweke/32/2166_2.png) [@sleiweke](https://unity.neuraldsp.com/u/sleiweke)\
**Post date:** [December 3, 2024, 3:04pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/7 "2024-12-03T15:04:02Z")

</div>

I will have to do some tests on this. I did a series of latency tests a couple months ago for my own purposes and I have all the results. I can run them again and compare.

---

<div class="post-metadata">

**Author:** ![morisson](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/morisson/32/7021_2.png) [@morisson](https://unity.neuraldsp.com/u/morisson)\
**Post date:** [December 3, 2024, 3:15pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/8 "2024-12-03T15:15:32Z")

</div>

That would be great. Looking forward to your results!

---

<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…

---

<div class="post-metadata">

**Author:** ![morisson](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/morisson/32/7021_2.png) [@morisson](https://unity.neuraldsp.com/u/morisson)\
**Post date:** [December 3, 2024, 11:01pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/10 "2024-12-03T23:01:36Z")

</div>

Ok thanks. Will try to see what’s happening on my setup. This is quite odd, but I guess I’m happy it’s not the QC 🙂

---

<div class="post-metadata">

**Author:** ![SimenRaaen](https://avatars.discourse-cdn.com/v4/letter/s/dbc845/32.png) [@SimenRaaen](https://unity.neuraldsp.com/u/SimenRaaen)\
**Post date:** [December 4, 2024, 3:44am UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/11 "2024-12-04T03:44:04Z")

</div>

Can you please explain how you measured it? thanks

---

<div class="post-metadata">

**Author:** ![derdoe](https://avatars.discourse-cdn.com/v4/letter/d/c57346/32.png) [@derdoe](https://unity.neuraldsp.com/u/derdoe)\
**Post date:** [December 4, 2024, 8:37pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/12 "2024-12-04T20:37:19Z")

</div>

Have you tried disabling row 4? I vaguely remember reading in another latency thread that the mere use of rows 3/4 also increased latency, even if there are no blocks involved.

---

<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 4, 2024, 9:02pm UTC](https://unity.neuraldsp.com/t/coros-3-1-0-worse-latency/16353/13 "2024-12-04T21:02:02Z")

</div>

With my soundcard and RTL utility.  
First i measured the soundcard latency (hardware+roundtrip) by putting a patch cable between output 3 and input 1.  
Then out3\>QC\>in1.  
The numers i get with the QC minus the one i got before gave me those results
