Audio software should never get in the way of making audio.

Install the plugin. Not an ecosystem.

nClear Audio plugins can be downloaded and installed individually.

A helper application may exist in the future to make installation, updates, backups, and computer migration easier — but it will remain optional.

Deleting that helper must never stop an installed plugin from working.

The manager is optional. The plugin is the product.

Your plugin should not stop working because a server did.

nClear Audio does not require always-online DRM, hardware dongles, or a permanently running licensing service.

Commercial plugins may require activation, but offline activation is a first-class supported workflow.

After activation, an internet connection should not be a condition for making music.

I'd rather make piracy slightly easier than have a plugin stop working five minutes before a show.

Updates shouldn't rewrite your mix.

A project that sounded right yesterday should not sound different merely because a plugin was updated.

Bug fixes, improvements, and new features should preserve existing project behavior whenever technically possible.

If a change fundamentally alters DSP behavior, parameter mapping, or project recall, it should ship as a separate major version with its own plugin identity rather than silently replacing the old one.

Old versions should remain available when they are needed for project recall.

No forced updates.

There should always be a recall path, not only an upgrade path.

Take your sound with you.

Every nClear Audio plugin should make its state portable outside the DAW.

The common product shell should support, where applicable:

• Copy State
• Paste State
• Export User Presets
• Import User Presets

"State" means the complete meaningful plugin state, not only the controls currently visible on screen.

Preset imports should avoid creating unnecessary duplicates.

The underlying preset/state format should be versioned so that future plugins can migrate old data safely.

Comparison should be fair.

Audio processing can easily fool us.

A signal that is slightly louder often feels clearer, wider, punchier, or simply "better" even when the processing itself did not improve it.

That is why nClear Audio treats comparison as part of the processor rather than an afterthought.

Effects should provide A/B state comparison or a proper bypass workflow, and gain matching / Auto Gain wherever it is meaningful.

The same principle applies to product demonstrations. Before-and-after comparisons should make the plugin's contribution clear. Changes in the source material, undisclosed additional processing, or unmatched loudness should not be presented as improvements made by the plugin.

Descriptions should explain what an effect does and where its limitations are. Creative control names are welcome, but the documentation should explain what they control, not disguise familiar processing as a secret formula.

If a processor sounds better only because it got louder, it doesn't sound better.

Use the quality you need.

Where oversampling materially improves the processing, nClear Audio plugins should expose internal oversampling rather than forcing the user to run an entire DAW project at an unnecessarily high sample rate.

Some processors gain nothing from it.

Every processor that benefits meaningfully from oversampling should provide it internally.

Quality settings should make their trade-offs clear. Modes that significantly increase CPU load or latency should explain both the cost and the benefit.

Documentation should distinguish between supported configurations, configurations that have actually been tested, and those that have not yet been tested. Important known limitations should be available before purchase.

The interface should fit your screen, not the other way around.

nClear Audio plugins should support interface scaling and remain usable across different display sizes and pixel densities.

Scaling is not a bonus feature. It is basic usability.

Where possible, common preferences such as UI scale should behave consistently across the nClear Audio product line.

Know what you are buying.

You should understand what you are buying before you pay.

License type and duration, the number of computers, included versions and updates, activation requirements, and important limitations should be explained in plain language alongside the purchase offer.

A paid major upgrade may introduce new features. Its release should not revoke an existing perpetual license or require a subscription to keep using the version covered by that license.

Keeping your license is not the same as guaranteeing compatibility with every future operating system.

Important terms should not be a surprise you discover after the plugin has become part of your workflow.

Honest prices. No manufactured urgency.

I don't use invented “regular prices,” endlessly resetting countdowns, or fake shortages of digital copies to pressure people into buying.

Discounts can be genuine. When I offer one, its terms should be real. A time-limited offer should have a real end date.

A plugin should earn its purchase by being useful, not by making you afraid of missing out.

Your studio is not a storefront.

Installing a plugin should not add unrelated products or demos to your DAW without your consent.

Sales messages should not interrupt your work, cover the controls, or repeatedly demand attention. Clearly labeled Pro features and upgrade information you choose to open are fine; intrusive sales prompts are not.

Downloading or buying a plugin does not, by itself, mean signing up for marketing emails. Service messages are for delivering and supporting the product. News and offers should be a separate choice.

You installed a tool, not an advertising platform.