Model or dataset
sdatkinson/NeuralAmpModelerPlugin avatar
sdatkinson/NeuralAmpModelerPlugin

Neural Amp Modeler Plugin: two plugin formats, installers from a fork, and a documented GPU crash

Plugin for Neural Amp Modeler

3,069 stars303 forksC++MIT

At a glance

What is it?
This is the plugin front end for a guitar amplifier emulator, built on the iPlug2 framework and distributed as a VST3 and an Audio Unit plug-in for Windows and macOS. The page is short and unusually candid about what is rough: the standalone application is described as less stable than running inside a host, a crash before the window opens is blamed on the wrong graphics device with a control panel fix, Linux users are sent to another author's repository, and the pre-built installers come from a fork hosted on a separate site rather than from the release list.
Who is it for?
This is the right repository if you run Neural Amp Modeler inside a DAW on Windows or macOS and want to build or install the plug-in yourself. Three things to check first.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sdatkinson/NeuralAmpModelerPlugin3,069 ★ · +62
Star history
Repository2026-09-252026-11-15
sdatkinson/NeuralAmpModelerPlugin3k3.1k

62 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two plugin formats ship, and three more are promised in a footnote

The first line defines the scope. It is a VST3 and Audio Unit plug-in for Neural Amp Modeler, built with the iPlug2 framework, so the shipping target is two of the common plug-in formats on two desktop platforms. A footnote at the bottom of the About section widens the ambition, noting that it could also support AAX, CLAP, Linux and iOS soon. Read against the platform section, that footnote is aspirational rather than descriptive: Linux support does exist on the page, but as a separate LV2 plug-in living in somebody else's repository, and the plug-in formats named in the footnote are not the ones currently built. So a user shopping by format should read the platform section rather than the footnote, and a user shopping by plug-in format gets VST3 and Audio Unit only.

Pre-built installers come from a fork, and the sentence introducing it is broken

The installation story is the odd part of this page. There is no install command anywhere, and the building section points instead at build scripts kept in a scripts directory inside the repository and at the workflow definitions that show how the build runs. Then a section headed pre-built installers says that if you want one from this repository without having to build it, the author has made something called Gateway, a fork of this repository, available at a users page on a separate site. The sentence itself has a grammatical hole where a verb should be, and the availability word is misspelled, which suggests the paragraph was edited quickly. The substance matters more than the typing: the binaries a user is most likely to download are not on the release list of this repository, which is unusual enough to be worth knowing before you start.

Windows 10 and macOS 10.15 are the floor, and Linux lives elsewhere

The supported platform list gives two floors with version numbers: Windows 10 at 64-bit or later, and macOS 10.15, named with its release codename, or later. There is no Linux entry in that list. Instead, Linux support is a sentence pointing at an LV2 plug-in in a repository owned by a different person, which is a different plug-in format on a different code base maintained separately. So the answer to whether this project covers Linux is yes by association and no by construction. Anyone packaging a Linux workflow should treat the two projects as distinct, since they share a purpose and nothing else that the page describes, including release cadence or version numbers.

Four submodules and four per-platform configuration files

The repository tree explains the build's shape. There is a gitmodules file and four directories that read as external dependencies: an audio DSP toolkit, a core library, a matrix maths library and the iPlug2 framework itself. A build therefore needs the submodules populated, which is the kind of step a page that prints no commands is implicitly asking you to handle through its scripts and workflows. Alongside them sit four per-platform configuration files with different extensions for the four targets: a macOS property list, an iOS property list, a Windows props file and a makefile for a web target. There is a REAPER directory as well, which is the host whose integration gets its own build inputs, plus a models directory, a template project, a code-workspace file for the editor and a container setup script with a devcontainer definition.

The standalone application is documented as the weaker path

The rough edges section is the most useful part of the page, and it starts with the standalone build. Its input and output do not inherit the stability that most plug-in hosts give a plug-in, so it ends up sparser on features than the same code running inside one. The advice given is direct: for complex routing, running the VST3 or Audio Unit plug-in inside a plug-in host is still the most reliable option. That is a statement about audio routing rather than about the model, and it means the two ways of using the same application do not behave equally. It also frames the standalone build as a convenience rather than the primary path, which is worth knowing before choosing it as the only installed copy.

The crash before the window opens has one cause and one fix

The second rough edge is a specific crash and it comes with a diagnosis. If the application crashes before its interface comes up, the page says the likely cause is an unsupported graphics configuration, and it names the usual case: a dedicated graphics card, such as an NVIDIA GPU, while the system is using the integrated graphics on Windows. The fix is a configuration change rather than a code change. Go to the control panel, select the application or the digital audio workstation, and make sure it is set to use the graphics card. The author then invites an issue with more detail if the reader knows more, which leaves open the question of what happens when the dedicated card is already selected.

Two releases on one day, after a twenty-month gap

The release history has a shape worth noting before you pick a version. Two of the three most recent tags fall on the same day, an hour under seven hours apart, both in the patch series. The one before them is from December 2024, so the project went roughly twenty months between releases and then cut two in an afternoon. The tags are conventional semver with a leading zero on the minor version, and the release titles repeat the number with the word Version in front of it. The last push to the main branch is dated 2026-08-23, months after the newest tag, which is the normal pattern for a project whose tagged releases track packaged builds rather than every change.

Editorial conclusion

This is the right repository if you run Neural Amp Modeler inside a DAW on Windows or macOS and want to build or install the plug-in yourself. Three things to check first. Where you get binaries, because the release list is not where the installers live and the page points at a fork on a separate site, which is a different distribution arrangement from a GitHub release. Which host you run it in, because the page says the standalone application is the less reliable path and recommends the plug-in inside a host for anything with complex routing. And what your graphics configuration is on Windows, because a dedicated card paired with integrated graphics is named as the cause of a crash before the interface appears, with a control panel change as the fix.

Frequently asked questions

Is there a plugin for Neural amp Modeler?

Yes. This repository is the VST3 and Audio Unit plug-in for Neural Amp Modeler, built with iPlug2, supporting Windows 10 at 64-bit or later and macOS 10.15 Catalina or later. On Linux the page points to a separate LV2 plug-in in a repository owned by a different author.

how to install neural amp modeler plugin

The page prints no install command. It says build scripts live under the scripts directory of the NeuralAmpModeler project in this repository and that the workflow definitions show how to build. For pre-built installers it points at Gateway, described as a fork of this repository, available through a users page on the neuralampmodeler.com site.

Is the standalone mode of the Neural Amp Modeler plugin as stable as the plug-in?

The page says no. The standalone's input and output do not inherit the stability of most plug-in hosts, so it is sparser on features, and for complex routing it recommends running the VST3 or Audio Unit plug-in inside a host as the most reliable option.

Why does Neural Amp Modeler crash before its window opens?

Usually an unsupported graphics configuration, and the page names the common case: a dedicated graphics card such as an NVIDIA GPU while the integrated graphics are being used on Windows. The fix is to open the control panel, select the application or the DAW, and make sure it is set to use the graphics card. The author asks for an issue with more detail if the reader knows more.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. sdatkinson/NeuralAmpModelerPlugin on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sdatkinson-neuralampmodelerplugin.svg)](https://hysenlabs.com/projects/sdatkinson-neuralampmodelerplugin)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sdatkinson-neuralampmodelerplugin.svg)](https://hysenlabs.com/projects/sdatkinson-neuralampmodelerplugin)

Was this useful?