CoreOS 2.2.1 and Cortex Control beta 0.7.0.42 are now available

Quad Cortex
1

CorOS 2.2.1 and Cortex Control (beta) 0.7.0.42 are now available

We are pleased to announce that CorOS 2.2.1 and Cortex Control (beta) 0.7.0.42 are now available!

CorOS 2.2.1 is required to run the latest version of Cortex Control. Download it via Settings > Device Options > Device Updates on your Quad Cortex once connected to Wi-Fi. We recommend that you create a backup before updating your firmware.

Cortex Control can be downloaded from the Downloads page.

CorOS 2.2.1 Changelog

Fixed

A UI crash that occurred when tapping the Close button after tapping the Bypass parameter within the Assign Expression Pedal menu.

An issue where the Bypass parameter couldnā€™t be assigned to an expression pedal within the Assign Expression Pedal menu.

An issue where the EXP treadle position wasnā€™t accurately loaded when loading multiple Presets that feature Expression Pedal Bypass parameter assignments.

An issue where the animated progress indicator was not showing when uploading a backup in the Settings > Backups menu.

Cortex Control 0.7.0.42 Changelog

Fixed

An issue where clearing the Directory Edit Details text field and pressing Enter allowed for a Preset to be renamed with no characters.

An issue where clearing the Directory Edit Details text field and pressing Enter allowed for a Neural Capture to be renamed with no characters.

An issue where clearing the Directory Edit Details text field and pressing Enter allowed for a Impulse Response to be renamed with no characters.

An issue that caused Cortex Control to crash when loading Scenes while the Scene Mode Gig View was open.

A crash issue that occurred when Gig View was open in Stomp Mode and Presets were loaded rapidly on the Quad Cortex.

An issue where it was possible to create Presets with names containing fewer than four characters by pressing the Enter key on the keyboard during the saving process.

An issue where the Return and Send devices in the FX Loop category were missing their icons in Gig View while in Stomp Mode.

A crash that occurred when pressing the down arrow key after reopening and closing the contextual menu in the Directory.

An issue with the Dual IR Loader device where assigning parameters with the same name to an expression pedal caused problems with the expression pedal range sliders.

An issue where the Assign Expression Pedal menu option would be greyed out when right-clicking a device on The Grid that has its Parameter Editor open.

An issue where the option to rename a footswitch assigned to multiple devices was missing in Stomp Mode Gig View.

An issue where Ground Lift parameters were incorrectly displayed for OUT 3 and OUT 4 in the I/O Settings.

An issue where selecting bands in Parametric EQ devices was difficult when they were close together.

An issue where the Input Gate meter failed to accurately represent changes to the bypass state of the Input Gate when switching between different Scenes.

An issue where Cortex Control was failing to accurately load the default parameters of a Dual IR Loader device.

An issue that allowed Presets to share the same name within the same Setlist when a Preset was renamed via Edit Details in the Directory.

An issue where incorrect parameter values were sometimes loaded when previewing a device on The Grid.

An issue where selecting an Input or Output on The Grid while previewing a device would mistakenly commit the previewed device to the current slot.

An issue where the Live Tuner was not functioning correctly after closing and re-opening Cortex Control.

A crash that would occur if a user auditioned a Cab device and pressed Enter to accept the new device.

An issue where a non-functional contextual menu was displayed for Neural Captures in the Directory Search menu.

An issue where a non-functional contextual menu was displayed for Impulse Responses in the Directory Search menu.

A crash that would occur when attempting to rename an invalid local backup file in the Device Settings > Backups > Local Backups menu.

An issue where a ā€œCorOS update neededā€ error message was displayed for certain Presets after downloading a backup from previous Cortex Control builds.

An issue where any button or menu item could be triggered immediately after initiating the restore of a local Backup in the Device Settings > Backups menu.

An issue where the day, month, and year were incorrectly displayed for Impulse Responses added to the local Impulse Responses folder within the Directory.

A bug where the Cloud Presets and Cloud Captures folders would not display all Cloud items and would continuously show an animated spinner after uploading a Preset or Capture to the Cloud using Cortex Control.

An issue where the ā€œSend Reportā€ description text was partially cut off within the Device Settings > Contact and About Us menu.

An issue where the Directory folders failed to update properly after downloading a backup.

An issue where a ā€˜Bypassedā€™ device copied to the clipboard would be pasted as ā€˜Enabledā€™ when pasted into an empty slot on The Grid.

An issue on The Grid View where, if a device was copied and pasted on the Quad Cortex, the device would not display that it has Scenes assigned to its parameters.

Thank you for all of the feedback and bug reports you have provided so far.

4 Likes
2

Now my wahs are in the on state whenever I switch presets. Before if I had not used it and then switched they would be in the proper off state in the new patch. Now I have to rock to the pedal once to turn off the wah whenever I change patches. I even renove the pedal from the patch and recreated and still does it. Mission Engineering EP-2 using just the Out 1 to Exp 2, Bypass in the Heel position.

1 Like
3

I donā€™t see any mention of a fix for the absence of the Stomp Mode Bypass Assignment feature in Cortex Control Device Settings :neutral_face:

4

The Exp1 position on patch load is still incorrect in 2.2.1. For example, Configure Exp1 for Wah position and heel-toe inverted bypass, and save the patch with Exp1 toe-down at 100% with the Wah off. Load the patch and the Wah is incorrectly on, the patch shows edited, and Exp1 position is incorrectly read to be 90% (too low to effect bypass) while the Exp1 is toe down at 100%. I did recalibrate Exp1 and it goes from 0 to 100% correctly. QC is not reading the position of Exp1 correctly on patch load, the value is always too low.

1 Like
5

I have notified support directly but I would also recommend to email support@neuraldsp.com to log the issue.

6

I did. I tried saving the patch with Exp1 at various positions, and the patch always loads with a value that is lower. For example, save the patch with Exp at 63%, donā€™t touch the pedal, load the patch and the position is at 56%.

Same thing happens with Exp2.

7

Still shitty communication between the QC and my Mac Mini M2.
It starts ok, but then, when I go into scene mode on the QC and I switch scenes, Cortex Control get unresponsive.

8

Iā€™m using an M2 MacBook Pro and OWC Thunderbolt 3 hub with QC and the connection with Cortex Control is solid.

9

Then maybe it is the fact of going to the gig screen on the QC and switching from there using the footswitches?
Whenever I do this, CC stops mirroring what I do on the QC.

10

Yes it is worse, before if I didnā€™t touch the wah while in a preset and switch it remained off in the new preset, now it is on no matter what.

11

Cortex Control remains connected to QC and updating properly for me in Gig view.

12

Looks like I wonā€™t be updating :unamused:

2 Likes
13

To make sure: Are you using a direct cable connection without a hub or dongle? Since I moved to a single USB B to USB C cable the connection is rock solid on my MacBook Air M2.

14

Direct USB from the start, I never used a HUB

1 Like
15

Yeah, I tried again and this time it worked, looks like it is kind of random. Iā€™ll try to play a bit more with the CC to see if it happens again.

16

Well, I was playing around with it, and when I deleted a setlist in the directory, CC crashed on me and closed :smile:

Filling bug report right now.

I recorded my screen while doing it to add to the bug report. It happens every time. The setlist is deleted though, but CC crashes.

17

Thatā€™s a lot of fixes in a few weeks.

18

Hi, is there something i missed with importing new rigs ?

They appears in my download (in the QC) after selecting the Cortex Cloud but desappear when i click on the download logo (in the QC) and canā€™t where it goes :thinking:

Previously it was asking the location i wanted in my preset but now nothing.

19

I thought this issue was fixed with 2.2.1, but no: I have been tracking some songs for a couple of hours using the QC as the USB interface for mi Mac, and the sound still cuts out every more or less 2 minutes. Itā€™s a small cut, but well, it ruins a take when you are recording.
Seems to be related with USB communication. It did not happen before the CC release.
ā€”EDITā€”
The more you try, the more it happens: now it happens every 15 to 20 seconds. My QC is unusable to record my bandsā€™ songs :frowning:
ā€”2nd EDITā€”
After 1 hour it is totally unusable. Even playing back a 2 tracks audio using VLC (Reaper closed, just plain MacOS using thew QC as an audio interface) lags like hell.

I hope this gets fixed quickly, I really need to record my guitar parts for my band :stuck_out_tongue:

20

Okayyyyyā€¦I have done some testing. It seems that the problem is my 2nd monitor.
It is the only piece of equipment in my whole system that is actually grounded (and sometimes I see it flicker, meaning that something strange must be happening in the power supply of my houseā€¦also, I use PLC plugs for networking, so there is a lot happening in those wiresā€¦).
The problem happens agnostic of if this monitor is plugged in using USB-C (my normal setup) or HDMI, and it happens even though this is the only monitor plugged in.
So, my conclusion for now: either my Mac has a hard time with this particular monitor, or there is a bad grounding thing that enter the system from this monitor, and makes the sound from the QC cut out.

Either way, Iā€™m screwed as I canā€™t use this 2nd monitor to have my Reaper editor, or plugins view :frowning:

Strange thing is that it doesnā€™t seem to bother my Scarlett 2i2 that works perfectly with the 2 monitors plugged in.

1 Like