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] 0.7.12 crashes Gig Perfomer 4 #539

Closed
CarlGalilee opened this issue Dec 7, 2024 · 1 comment
Closed

[BUG] 0.7.12 crashes Gig Perfomer 4 #539

CarlGalilee opened this issue Dec 7, 2024 · 1 comment
Labels
bug Something isn't working priority:low Low priority issues

Comments

@CarlGalilee
Copy link

Description

v0.7.12 crashes Gig Performer 4 (windows 10)

To reproduce

  1. Open Gig Performer 4
  2. Either add an instance of NAM to a new/existing rackspace or load an existing rackspace with NAM already present
  3. Double click on the NAM plugin instance to open NAM's GUI
  4. Gig Performer shuts down before the GUI opens and launches the 'Gig Performer Has Stopped Working' window

Expected behavior

v0.7.12 works fine within Reaper.
Rolling back to v0.7.11 works as expected in Gig Performer 4

Screenshots

If applicable, add screenshots to help explain your problem.

Computer & other info

(please provide the following information):

  • OS: Windows 10
  • GPU RTX2070
  • Plugin version: 0.7.12
  • VST3
  • DAW: Gig Performer 4
  • Audio interface: Axe I/O
  • Sample rate: 48Khz
  • Buffer size: 64 samples
  • Provide a model that the bug happens with: None loaded
  • Provide an IR that the bug happens with: None Loaded
  • Does the bug not happen under some other conditions?: Rolling back to v0.7.11 resolves the issue
@CarlGalilee CarlGalilee 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 7, 2024
@sdatkinson
Copy link
Owner

Probably similar root cause to #541. Fix was shipped in #543. If you can build the latest commit, then give it a test and lmk if it works.

@sdatkinson sdatkinson removed the unread This issue is new and hasn't been seen by the maintainers yet label Dec 20, 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

2 participants