QC Firmware 3.0.1?

Quad Cortex
1

Having contacted support to let them know I was having issues where my QC would occasionally have no sound on startup, I told them I was using OS 3.0.0.

They queried this, which made me curious, so I was intrigued to see therefore that an appeared update overnight to 3.0.1.

No release notes for this that I can see, anyone know anything about it??

1 Like
2

i’m updating a this moment. Also Cortex control was updated to v1.1.1.

3

Cortex Control #### 1.1.1 (for CorOS 3.0.1) - Sep 11, 2024

##FIXED

  • An issue where Cortex Control would crash after booting on M1 Mac devices.
  • An issue where accepting an auditioned device with the Enter key did not work in certain scenarios in the Grid.
  • An issue where a crash would occur if the previously selected setlist in the Paste dialogue window was renamed and a slot from that setlist was selected as the save location in the Directory.
  • An issue where a crash would occur if a setlist was renamed on Quad Cortex while the Paste window was open, and a slot from that renamed setlist was selected in Cortex Control.

CorOS:

image
image1654Ă—1246 163 KB

image
image1654Ă—1246 189 KB

image
image1654Ă—1246 180 KB

image
image1654Ă—1246 170 KB

4 Likes
4

Wow!
Probably dsp1 and 2 are now returned in phase on parallel routing!

I’ll check

P.S.

Yep, now row1 and 3 if in parallel are back in phase BUT

sadly i have found another phase issue when i insert a split… :wink: already emailed the support

1 Like
5

Can you explain in more detail where/when the new phase issue happens?

6

Another example in video,
row 1 and 3, same cab but transparent blend is unusable :

If i sidechain the head, we have phase issue as we can see on this youtube grab

2024 09 12 17 15 14 (youtube.com)

7

Have you tried the Dynamic Latency Compensation that was added in 3.0.0? Didn’t work for me, but curious if it does in this case.

8

tryed … no result, out of phase, support engaged

9

Wow! Cortex Control seems usable again on a M1 Mac. Was very stable on v2 but the 3.0 update broke it. Looks like it’s back!

10

I meant the Phase issue you mentioned Here using a split. So there currently are at least two: Split and Transparent Blend?

11

From the last preset, i think that the issues are generated in several way from the transparent blend block algorithm

12

Did they fix the Lock Screen?

13

That’s a serious bug!

14

Hello, have you tried to pan both cabs to opposite sides and see what happens??

In my point of view, the “phase” you are saying and experiencing is just that both cabs are playing together, even though they are the same, when you do this you can have this type of issue. Just like I would mic up the same cab with two mics, if one of them is playing at the same time in the same position (regarding left and right) I can have cancellation of frequencies.
And by the way, volume check to the same volume as one cab only and see if you have the same problem

1 Like
15

Hi,
Try my example, or ear the video.
This Is phase not correlation without doubt

16

If i play the same cab in parallel, and centered , with the same settings, the only result that i must have Is a eventual volume rise up. But not a tonal change

1 Like
17

Hey Niksounds,
I see what you are saying. I was trying to bring something from the real world for here. But there will be any delay sending the info from one core to another (if you are aware that row 1 & 2 and 3 & 4 are processed by different cores). If you do the same stuff using only one of the cores it will work as a parallel path and you notice just a volume rise up.

18

Yep, but as tool would be fantastic use this block on all row, reserving one DSP for splitting on Effects and so on.
I see this tool in fact a little bit defective, (without accuse nobody)
Thank to clarification Felipe

1 Like
19

Today TRANSPARENT BLEND bring me on phase issues on ROW 1 and 2 using jp2c and se same cab using Transparent blend instead of splitter !!
But i’m a little bit tired to do a videos.

unusable block

…!