Neural DSP - Cortex Control beta, CorOS 2.2 released

[Whizzinby]

Wait, this means that (as of some time yesterday)… you still own a QC?? I assumed the FM3 had sent it packing. Here’s to small victories! :)

Yeah I think I’m going to keep it. I don’t need the bread for anything else catching my attention, and it’s fun to have a couple devices to play around with. I think I’m going to keep the FM3 as a daily driver and for recording, and use the QC to integrate with other gear (IRX, pedals etc.) since it’s so easy to configure more complex signal paths (and midi) on the fly with it, on device.

Plus I won’t have to declare a side on the battle line.

 

[mbenigni]

Yeah I think I’m going to keep it. I don’t need the bread for anything else catching my attention, and it’s fun to have a couple devices to play around with. I think I’m going to keep the FM3 as a daily driver and for recording, and use the QC to integrate with other gear (IRX, pedals etc.) since it’s so easy to configure more complex signal paths (and midi) on the fly with, on device.

Plus I won’t have to declare a side on the battle line.

Funny, I was thinking along very similar lines just yesterday: that it might be nice to have an FM3 on/under my desk - where FAS Edit is a must anyway - and use my QC for more portable applications e.g. moving between rooms, guitar cabs, pedal boards, etc. The on-unit editing and cloud integration make QC ideal for this sort of thing, since you don’t wind up dragging a laptop around behind it.

 

[fretworn]

 

[Whizzinby]

Funny, I was thinking along very similar lines just yesterday: that it might be nice to have an FM3 on/under my desk - where FAS Edit is a must anyway - and use my QC for more portable applications e.g. moving between rooms, guitar cabs, pedal boards, etc. The on-unit editing and cloud integration make QC ideal for this sort of thing, since you don’t wind up dragging a laptop around behind it.

Best of both worlds! Winning combo.

 

[DrewJD82]

I’ve got no gripes with them doing a public beta, this is probably the only way they could get themselves out from under their own thumb for a bit, by giving the customers what they’ve been asking for while developing it. My only negative outlook towards all that was showing it at NAMM nearly a year ago and think it would have been better to just release it instead of the usual NDSP media parade, but like I said, the progress is more important than the griping.

Naysayer is gonna naaaaaaay-

Amending this as I wasn’t aware how they rolled out that last update, which was a FW update AND the beta for CoCo. These guys need to allow for users to roll back FW if they aren’t going to do public betas. I’m guessing neither @Whizzinby or @mbenigni is using expression pedals? I guess the FW messed with the expression pedal blocks so no matter what they were set to, when you engage a preset using an effect with the expression pedal, the effect is automatically on when you engage the preset.

With no way to roll back FW, everyone is stuck with it until they release a hotfix or go through and re-save each preset/scene with the issue.

 

[Whizzinby]

Naysayer is gonna naaaaaaay-

Amending this as I wasn’t aware how they rolled out that last update, which was a FW update AND the beta for CoCo. These guys need to allow for users to roll back FW if they aren’t going to do public betas. I’m guessing neither @Whizzinby or @mbenigni is using expression pedals? I guess the FW messed with the expression pedal blocks so no matter what they were set to, when you engage a preset using an effect with the expression pedal, the effect is automatically on when you engage the preset.

With no way to roll back FW, everyone is stuck with it until they release a hotfix or go through and re-save each preset/scene with the issue.

This is why you buy an FM3 as part of your QC starter pack. Then you can keep rocking during any FW shenanigans.

 

[Mongillo19]

Naysayer is gonna naaaaaaay-

Amending this as I wasn’t aware how they rolled out that last update, which was a FW update AND the beta for CoCo. These guys need to allow for users to roll back FW if they aren’t going to do public betas. I’m guessing neither @Whizzinby or @mbenigni is using expression pedals? I guess the FW messed with the expression pedal blocks so no matter what they were set to, when you engage a preset using an effect with the expression pedal, the effect is automatically on when you engage the preset.

With no way to roll back FW, everyone is stuck with it until they release a hotfix or go through and re-save each preset/scene with the issue.

That's what I don't get when people complain about fractal updates "breaking" presets. The only time that usually happens is for major firmware updates.

Neural breaks your entire device with updates it seems anymore whether it be wifi, standby mode, and now expression blocks?

I didn't even see @SeeD post lol just curious how a gripe of the Axe Fx was breaking presets on updates when the QC seems to do the same if not worse

 

[DrewJD82]

That's what I don't get when people complain about fractal updates "breaking" presets. The only time that usually happens is for major firmware updates.

Neural breaks your entire device with updates it seems anymore whether it be wifi, standby mode, and now expression blocks?

“Don’t install updates on the first date, that’s a you problem, not a NDSP problem”

”But the update had the bug fixes that actually let me use the QC normally”

“Don’t worry, it’ll be fixed in a hotfix…..“

 

[Whizzinby]

That's what I don't get when people complain about fractal updates "breaking" presets. The only time that usually happens is for major firmware updates.

Neural breaks your entire device with updates it seems anymore whether it be wifi, standby mode, and now expression blocks?

Dude. When I went to do the 2.2 update so I could play around with Control…

• Boot
• Had to log into my account (it never auto logs in)
• Couldn’t log in, “no internet connection”
• Go to wifi settings, “forget” my wifi network (I could run a lunar launch with the amount of connected devices with zero connection issues in the same room)
• Reconnect to my wifi
• Log into account
• Hit update
• Loses internet connection at 30% download (says “weak” connection)
• Forget wifi again
• Log back into wifi
• Download resumes

There are some serious bugs with wifi connectivity and the inability to auto login in to your cloud account. Luckily it’s not a frequent occurrence to need that connectivity, but every single time you want it, you can bet you will have to either re-login to your cloud account and/or reconnect to your wifi.

 

[SeeD]

That's what I don't get when people complain about fractal updates "breaking" presets. The only time that usually happens is for major firmware updates.

Neural breaks your entire device with updates it seems anymore whether it be wifi, standby mode, and now expression blocks?

I didn't even see @SeeD post lol just curious how a gripe of the Axe Fx was breaking presets on updates when the QC seems to do the same if not worse

Yeah with the QC, we need to be a bit careful with FW updates, it should be an option to rollback.

But by breaking presets and going foreward, that used to be a problem with Fractal Audio, as if you want the new stuff in the future, I needed to tweak my presets in the past, reset amp block ( a lot of times) and just think about all the parameters that would then be defaulted ??

 

[Mongillo19]

Yeah with the QC, we need to be a bit careful with FW updates, it should be an option to rollback.

But by breaking presets and going foreward, that used to be a problem with Fractal Audio, as if you want the new stuff in the future, I needed to tweak my presets in the past, reset amp block ( a lot of times) and just think about all the parameters that would then be defaulted ??

Sure but they usually don't change the time that much unless it's a bigger firmware update (which isn't all too frequent).

I guess I'd rather edit my amp tone slightly than deal with a malfunctioning unit? I guess it doesn't seem any different between QC and Fractal with QC being arguably worse is my point.

 

[Mongillo19]

Dude. When I went to do the 2.2 update so I could play around with Control…

• Boot
• Had to log into my account (it never auto logs in)
• Couldn’t log in, “no internet connection”
• Go to wifi settings, “forget” my wifi network (I could run a lunar launch with the amount of connected devices with zero connection issues in the same room)
• Reconnect to my wifi
• Log into account
• Hit update
• Loses internet connection at 30% download (says “weak” connection)
• Forget wifi again
• Log back into wifi
• Download resumes

There are some serious bugs with wifi connectivity and the inability to auto login in to your cloud account. Luckily it’s not a frequent occurrence to need that connectivity, but every single time you want it, you can bet you will have to either re-login to your cloud account and/or reconnect to your wifi.

Mine has been sitting in its box for awhile now

 

[SeeD]

Sure but they usually don't change the time that much unless it's a bigger firmware update (which isn't all too frequent).

I guess I'd rather edit my amp tone slightly than deal with a malfunctioning unit? I guess it doesn't seem any different between QC and Fractal with QC being arguably worse is my point.

Don`t be first ?
That is for all the modelers, I guess

But my pionts about presets are in the past, and with my Axe Fx II, but I guess that folks that buy and sell presets might feel the same way, it might have got better.
It`s all good

 

[fretworn]

 

[mbenigni]

Naysayer is gonna naaaaaaay-

Amending this as I wasn’t aware how they rolled out that last update, which was a FW update AND the beta for CoCo. These guys need to allow for users to roll back FW if they aren’t going to do public betas. I’m guessing neither @Whizzinby or @mbenigni is using expression pedals? I guess the FW messed with the expression pedal blocks so no matter what they were set to, when you engage a preset using an effect with the expression pedal, the effect is automatically on when you engage the preset.

With no way to roll back FW, everyone is stuck with it until they release a hotfix or go through and re-save each preset/scene with the issue.

I use expression pedal assignments all the time, but I haven't even installed the new f/w yet. Still not really interested in a PC editor, although I am a little curious to see whether it serves well as a librarian to help me clean up my presets and captures. Anyway, I've been traveling for the past couple of weeks, so 2.2 is going to have to wait until I actually manage to sleep through the night again.

 

[Whizzinby]

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.

 

[GTR37]

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.

That is a lot of fixes , kudos to NDSP for actually getting this out so quickly

 

[mbenigni]

 

[DrewJD82]

Or….3?

 

[mikah912]

I was just ready to give them some props for the customer-friendly moves lately (e.g. price drops, giving away a free plugin to recent customers, making tangible progress on plugins). Hell, I still will.

Do I trust either their communication or their bug-killing and firmware development at this juncture? No.