Cortex Wizard

Less hand, more wand.

Everything your Quad Cortex can already do, minus the hours of doing it by hand.

Reorder setlists and merge presets into scenes. Coming next: swap blocks across presets, batch edits and more.

In beta. Windows only for now; macOS later. Free, with no paid tier.

Join the beta

New beta out 0.9.0-beta.8 · 2026-10-26 What's new →

A wizard made of dots, holding the Cortex Wizard wand

Setlists

Every setlist with all its slots, as a list or as banks, the way your device shows them.

  • Drag to reorder: insert, swap or replace.
  • Rename, delete, set the instrument, load a preset.
  • Rename or delete a whole setlist.
  • Everything stays a draft until you save, with undo, redo and discard.
  • Save in place, or as a new setlist.
▶ Watch the video

Preset merge

Scenes taken from several presets become one preset with scenes: from your setlists, or from the plugins you own.

  • Click a preset to see its scenes; drag a scene onto the new preset.
  • The app works out how to build it and tries it on your device first.
  • It checks every scene, measures the CPU, and tells you where footswitches and pedals behave differently from the sources.
  • It saves into an empty slot. It never overwrites a preset.
▶ Watch the video

What you need

  • Windows 11.
  • A Quad Cortex or a Quad Cortex mini with CorOS 4.1.x, connected over USB.
  • Cortex Control closed while the app works. The app checks and tells you.

How it keeps your presets safe

  • Every operation is simulated first. Name clashes, occupied slots and empty sources are reported, and nothing is written if anything is wrong.
  • Whole presets are moved with the device's own copy and move, never rebuilt from pieces, so MIDI, tempo and expression settings travel with them.
  • Each write is confirmed by the device's reply, and the result is read back at the end.
  • Deleting a setlist deletes every preset in it: the app asks you first, every time.

What's new

0.9.0-beta.8 — 2026-10-26

Preset merge

0.9.0-beta.7 — 2026-10-22

Preset merge

Everywhere

0.9.0-beta.6 — 2026-10-15

Everywhere

Preset merge

Earlier versions

0.9.0-beta.5 — 2026-10-13

Preset merge

  • Choose each scene's colour, among the 8 the Quad Cortex has: in the scene's window, under its name. Until you do, it keeps the colour of the scene it comes from.
  • When the Quad Cortex has no processing power left for a merge of your own presets, and some blocks are bypassed in every scene and kept only because a footswitch can turn them on, Cortex Wizard says which, how much they would free, and offers to leave them out and try again. The footswitch would then do nothing; nothing is left out unless you ask.
  • Before saving a merge, Cortex Wizard checks it is still as it was built. If something changed on your Quad Cortex while you tried it (a footswitch, a knob, the screen), it says what and asks: keep your changes, or save it as proposed (built again, then saved).
  • When a merge reads back different from its presets, the message names the block and the scene ("Petrucci Overdrive is active in scene A, bypassed in its preset"), no longer a number.
  • Some merges could stop at "Try it". Fixed.

Setlists

  • Renaming a preset, or changing its instrument, keeps its tags: until now only the one its plugin gives it stayed.

Everywhere

  • When the Quad Cortex does not answer the first question of an operation, Cortex Wizard asks once more before giving up.
  • While Cortex Wizard works on your Quad Cortex (loading presets, building, saving, moving), a band asks you to leave its footswitches, knobs and screen alone; it goes when the work is done.
  • Report a problem starts from the email address of your last report, kept on your computer: check it rather than type it again.

0.9.0-beta.4 — 2026-10-11

Setlists

  • Move a setlist: drag it in the list of setlists, or Move up / down in its menu. The Quad Cortex has no way to reorder setlists, so Cortex Wizard rebuilds at the end the ones that move (each copied whole, then the original deleted); it asks first and says which. My Presets, the Quad Cortex's own setlist, stays where it is.
  • Duplicate a setlist, from its menu: the copy, "<name> 2", goes last, with every preset as it is.

Preset merge

  • A merge is saved with the tags of the presets it comes from, plus #CortexWizard: they go up with it when you share it on Cortex Cloud, where you can change them.
  • Presets that bring more heavy amplifiers than a pair of rows can run merge now when the amps can be spread: the merge places them so that each pair of rows runs its share, and it opens row 2 for the chain when row 1 is full. Three Petrucci X presets of three artists, refused before, merge. When no layout fits, the plan says so before Try it. When the Quad Cortex refuses a block, the message says it is the processing power, not the number of blocks.
  • With "keep each scene's tempo", a full-size Quad Cortex could leave one scene at the starting preset's tempo, and Try it stopped. Each scene's tempo is now written first, read back and written again where it did not land. A difference found after Try it is said in plain words (the tempo in BPM).
  • A merge built on separate lanes could send one preset's sound into another preset's lane: a Blend (or another block that listens to a block, such as a Doubler) kept the setting it had in its own preset, which on the merged grid pointed at a block of another preset. Each such block now listens to the same block as in its own preset, kept even when it is bypassed, and the check after Try it looks at it. When that preset is silent in a scene, a Blend after its amplifier is silenced too.
  • Presets that together bring more blocks than the rows they use can hold merge now when the row below is empty: the chain continues on it, as with heavy amplifiers - also when the row has a volume of its own, as in every Tim Henson X preset: the row below takes it over, scene by scene.
  • A Multivoicer that plays from MIDI notes in one preset and not in the others came out of the merge with its voices' Active switches off, and Try it reported it: written after the voices, the MIDI setting left them off. The merge now sets it first and the voices after.
  • A plugin's own presets leave out the blocks that are bypassed, even those a footswitch could turn on: the merge takes the sound of the scene you chose. More of them fit: of the artists' folders of Tim Henson X, merged eight at a time, 18 of 23 fit instead of 11. Your own presets keep such blocks.

Everywhere

  • A preset name with a dot is refused, with the reason: the Quad Cortex cuts a name at its first dot ("J.MAYER" became "J"). Saving a setlist stopped on it before.

0.9.0-beta.3 — 2026-10-10

Preset merge

  • Presets that use a split only to fit more blocks in series (the John Mayer X presets, for one) merge now, three and more together.
  • A preset whose split mixer is bypassed in some scenes merges right; Try it used to stop on it.
  • The build moves fewer blocks: the preset it starts from keeps its blocks where its author put them whenever they fit, and the other presets' blocks go to the rows they had in their own preset.
  • What you can drag is blue now, with a grip and a "Drag me" label; a scene's own colour stays as a stripe on its left. Red read as "not allowed".
  • A preset that sounds the same in every scene says it once, with where it went (→ AI).
  • The settings of most cabs are read under their right names (a cab's Level was read as its Position).
  • A preset that sends its signal to "Row 3/4" is refused, with the reason, until the merge handles it.

Setlists

  • Rename or delete a whole setlist, from the ⋯ next to its name or with a right click. Before deleting, a window shows every preset it holds.

Everywhere

  • Motion: presets slide into place when you move one, a preset's scenes open and close, a scene landing on the new preset fades in. None when your system asks for reduced motion.
  • Report a problem thanks you, and says what a test report proved.
  • Checked on CorOS 4.1.1.

0.9.0-beta.2 — 2026-10-07

Preset merge

  • A block the Quad Cortex refuses during Try it is named in plain words.

Everywhere

  • Starts on any PC when extracted from the downloaded zip (beta.1 stopped with a .NET error outside the PC it was built on). Unblock the zip before extracting it (Properties → Unblock).
  • If it cannot start, it says why, with a button that opens its log folder.
  • Writes only on a CorOS version it has been tested on; on another one it reads, and says why it does not write.

0.9.0-beta.1 — 2026-10-06

The first closed beta, for Windows.

Preset merge

  • Presets from your setlists and plugins into the scenes of a new preset; Try it on the Quad Cortex before saving; every scene read back and checked, the CPU measured; saved to an empty slot only.

Setlists

  • Reorder by dragging, as a draft; replace, delete, rename and set the instrument; save as a new setlist; banks view. Moves are planned on paper first and confirmed by the Quad Cortex one by one.

Everywhere

  • Report a problem from the app, with its log.

Questions

Is it official?

No. Cortex Wizard is an independent project, not affiliated with, endorsed by or supported by Neural DSP.

How does it talk to the Quad Cortex?

Over USB, with the same protocol Cortex Control uses, as documented by the community project qc-mcp. A CorOS update can change that protocol; the app is tested on one CorOS version at a time.

Windows warns me before installing. Why?

The beta installer is not yet signed, so Windows SmartScreen shows a warning; choose "More info", then "Run anyway". Some antivirus programs flag apps built this way by mistake. Download it only from this site.

Does it cost anything?

No. It is free, and it will stay free.

What about macOS?

It is planned, after the Windows beta.