IR Block file scene assignment bug(s) in Cortex Control

Quad Cortex Bug Reports
1

CorOS Version: 2.3.1
Cortex Control Version: 1.0.1

Describe your issue:
The IR blocs are not able to use ‘Scenes’ on the IR File parameter.

Steps to reproduce your issue:

  1. Create a new preset, add an Dual IR block
  2. Select an IR file , then right-click on the file name and use the ‘Assign to scene’ command (the ABCD icon appears)
  3. Go to another scene, choose another IR File : The ‘ABCD’ icon disappears, and the newly selected IR File is the same on all scenes, erasing all the previously ‘scene-assigned’ values.

I expected this to happen:
When I do the exact same steps directly on the Quad Cortex, each selected IR File is stored in its scene. The ‘ABCD’ icon is kept and I can switch the IR File by switching to another scene.

I have tried the following things:

  • On the Quad Cortex , everything is functioning correctly, the issue only appears in Cortex Control.

NOTE: Another bug in Cortex Control concerning the IR blocks : the right-click that allows to do a ‘Scene Assignement’ if the IR File is not available on the ‘Single IR’ block, but only on the ‘Dual IR’ blocks (even if the latter doesn’t work as expected.)

NOTE 2: I reported this bug back in November 2023, in the ‘Beta’ period of Cortex Control, but since then I discovered the different behaviour between ‘Single IR’ and ‘Dual IR’ blocks, I created this new Bug Report…

2

Bug is still not corrected in Cortex Control 1.1 released July 31st !

Support team, can you confirm that my enquiry is acknowledged by the CC dev team ? Thanks.

3

Same here, can’t assign scenes for IR changes in CoCo. Works fine on the QC itself

1 Like
4

I can confirm the error and that the assignment on the Quad Cortex works.

1 Like
5

Strangely, I emailed support@neuraldsp.com 3 times since November 2023 asking if the Dev Team acknowledged this bug, but so far I had no response :man_shrugging:

I think I’ll have to send another mail :sweat_smile:

6

They lately seem to be somewhat picky about which mail gets answered and which does not: I sent an email two days ago and another one regarding another topic today. I got an answer for the one sent today, but not for the other one :sweat_smile:

7

Same here, i have to switch to the QC Unit to be able to assigne the IRs to scenes.

8

The bug is still present in Cortex Control 1.1.1 :tired_face:

This is insane, I reported this bug back in the Beta period of Cortex Control in November, reach support recently to confirm that the bug has been acknowledged by the dev team (apparently : yes …) and it is still not corrected !

For a bug that cause a loss of data in a preset, I would consider it as a serious one, but NDSP don’t seems to care …

1 Like
9

Follow up : I asked support team if my bug report had been taken into account, and they replied very quickly that this bug should be corrected in the next CC update (1.2.0) , as 1.1.1 was a ‘quick bugfixes’ to correct the most crucial bugs !

Thanks to the support team for taking time to keep me informed ! :+1:

1 Like
10

excellent, thanks for sharing that. I wish we had a better system for acknowledging bugs; I really think they care and are working constantly behind the scenes but just don’t always have time to communicate that.
Maybe I’ll fire that thread back up that is for listing ‘known’ issues they’re working on.

2 Likes