Fury

Support

Product page · User manual

Before You Write In

Most questions about Fury are answered by the manual, which documents every control along with the parameter interactions that explain why a knob sometimes seems to do nothing.

Common Questions

The wobble is barely audible

Wobble needs a tone setting that exposes it. Lower Vowel from maximum, raise Growl so the formant movement is mixed in, add some Res, and keep Cutoff low-to-mid rather than fully open.

Width does nothing

Width spreads the Reese side signal, so it needs material to work with. Raise Reese and Detune first. On sub-dominant patches it is subtle by design, which keeps the low end mono-compatible.

My controller does not move the knobs

Fury's MIDI CC chart only responds on the device MIDI input. Route your controller through Preferences → Sync → External Control Bus, then Hardware Interface → Advanced MIDI to Fury. A generic Remote keyboard plays notes but will not move knobs.

I can only play one note

That is intentional — Fury is monophonic, which is what allows its glide, legato, and articulation behavior. For stacked bass, use several instances and link them with the rear-panel CV outputs.

I cannot find the factory patches

Use Fury's own patch browser, or the Rack Extension factory bank in Reason's browser. The User Library view only lists patches you have saved yourself.

Reducing CPU usage

Turn the STATUS display off with the ON toggle. Fury then skips all scope and analyzer processing, which is a real saving on dense projects and costs you nothing but the visual.

System Requirements

Fury runs in Reason and the Reason Rack Plugin on Windows and macOS. Installation, authorization, and licensing for Rack Extensions are handled by Reason Studios through your Reason account.

For purchase, download, authorization, or refund questions, contact Reason Studios. For questions about how Fury itself behaves, or to report a bug, use the form below.

Contact Fury support

Include your Reason version, operating system, and the patch or settings involved. Reproduction steps make bug reports much faster to resolve.