Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on startup or adding VST to Reaper[BUG] #416

Open
dumr666 opened this issue Dec 29, 2023 · 2 comments
Open

Crash on startup or adding VST to Reaper[BUG] #416

dumr666 opened this issue Dec 29, 2023 · 2 comments
Labels
bug Something isn't working priority:low Low priority issues

Comments

@dumr666
Copy link

dumr666 commented Dec 29, 2023

My PC specs:
Thinkpad T470s, wtih integrated Intel graphics card and i7 processor, with 16 GB of ram.
Operatin system, windows 11, fresh install.
Audio interface Focusrite Scarlet 2i2 2nd Gen (48kHz, 32 Samples, ASIO from Focusrite)

Describe the bug
Whenever I try to open NAM as standalone, it just crashes, whenever I want to add NAM as plugin through FX window in Reaper, it also crashes. If I select setting in Reaper under Setting -> Plug-ins -> VST -> Default VST to generic UI, then I can add NAM, which means something on interface in NAM doesn't like something on my PC. Anyway, both Reaper and NAM dumps are added to this report

To Reproduce in Reaper
Steps to reproduce the behavior:

  1. Go to Reaper
  2. Click on FX button on track
  3. Click on add Neural Amp
  4. Reaper crash

To reproduce in Standalone:

  1. Just open NAM
  2. -> Crash immediatly

*Expected behavior
to work :(

Desktop (please complete the following information):

  • windows 11
  • 0.7.7 (also tried with 7.4)
  • Standalone, VST3
  • Reaper

Additional context
Added crash dumps
NeuralAmpModeler_x64.exe.13288.dmp

@dumr666 dumr666 added bug Something isn't working priority:low Low priority issues unread This issue is new and hasn't been seen by the maintainers yet labels Dec 29, 2023
@stefanoberli
Copy link

@dumr666 You probably need to update your graphics drivers. I've had this same issue on two windows 10 computers, one of them a fresh install (a thinkpad x260). Just install the newest "Intel HD Graphics Driver", and it should work.
On my other computer I had to install the latest Nvidia driver.

@sdatkinson you might want to mention this somewhere (that the graphics drivers need to be up to date), I believe many Windows users have the same problem, and the solution isnt that obvious.

@sdatkinson
Copy link
Owner

@dumr666 does @stefanoberli's suggestion seem to be on the right track?

@stefanoberli, is there some info you'd recommend folks share that would help identify whether this is the issue?

@sdatkinson sdatkinson removed the unread This issue is new and hasn't been seen by the maintainers yet label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:low Low priority issues
Projects
None yet
Development

No branches or pull requests

3 participants