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

[BUG] Works as standalone but crashes as plugin on Ableton #473

Open
AlexBrutelle opened this issue May 26, 2024 · 7 comments
Open

[BUG] Works as standalone but crashes as plugin on Ableton #473

AlexBrutelle opened this issue May 26, 2024 · 7 comments
Labels
bug Something isn't working priority:low Low priority issues

Comments

@AlexBrutelle
Copy link

Describe the bug
After install, NAM works perfectly fine as a standalone but the VST3 plugin makes Ableton crash.

To Reproduce
Steps to reproduce the behavior:

  1. Install NAM (as a custom vst3-only install and/or in a full install)
  2. Open Ableton and load/refresh your plugin.
  3. Select the NAM VST3 plugin and drag it on an audio track
  4. See error message from Ableton: "Serious error occured, Ableton will close after this closing this window".

Expected behavior
Start using the NAM plugin inside Ableton 11 Lite.

Screenshots
Non-applicable

Desktop (please complete the following information):

  • OS: Windows 10
  • Plugin version [latest from GitHub repo as of day of this post)
  • VST3
  • DAW: Ableton 11 Lite
  • Audio interface: Focusrite Scarlett 2i2
  • Sample rate : 44.1 kHz
  • Buffer size: 256 samples and/or 512 samples
@AlexBrutelle AlexBrutelle 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 May 26, 2024
@sdatkinson sdatkinson changed the title [BUG] [BUG] Works as standalone but crashes as plugin on Ableton May 26, 2024
@sdatkinson sdatkinson removed the unread This issue is new and hasn't been seen by the maintainers yet label May 26, 2024
@sdatkinson
Copy link
Owner

Plugin version [latest from GitHub repo as of day of this post)

So should be 0.7.9

@AlexBrutelle does this happen in any other DAWs or just Ableton? Can you get a crash dump?

@AlexBrutelle
Copy link
Author

AlexBrutelle commented May 27, 2024

Yes it's 0.7.9! i don't use any other DAW but i'm attachng the bug report!
Ableton Crash Report 2024-05-27 001618 Live 11.3.25.zip

@AlexBrutelle
Copy link
Author

Sorry I marked as completed by mistake

@AlexBrutelle
Copy link
Author

What do you think about the bug report ?

@corthax
Copy link

corthax commented Sep 14, 2024

Same here in Reaper. NAM v0.7.9
Project set to 88.2kHz
Plugin says [INFO] Resampling to 48000 Hz
Eventually crashing Reaper after few minutes

@sdatkinson
Copy link
Owner

@corthax would you mind opening a separate issue for yours?

And in addition to the usual questions in the form can you also include:

  • Does it happen in a fresh project with nothing but one track with NAM on it?
  • Check whether it happens when the DAW sample rate matches what's requested by the model (48k for your case)?
  • Share the model that's being used (also: does it happen when no model is loaded?)

Thanks!

@corthax
Copy link

corthax commented Sep 21, 2024

Well, I did some tests and it looks like it's not NeuralAmpModeler to blame but ParametricOD. Eventually crashing Reaper in 10~60 minutes. Fresh project, no other plugins, just ParametricOD v 0.1.3

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