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

Random patch reset to Init - Surge XT - Logic Pro X - MacOS Mojave 10.14.6 #6845

Closed
kookin opened this issue Feb 16, 2023 · 5 comments
Closed
Labels
Bug Report Item submitted using the Bug Report template

Comments

@kookin
Copy link

kookin commented Feb 16, 2023

Bug Description:
After save and relauch of a Logic project with multiple Surge XT instruments, all Surge XT patches get reset to init. Seems to be an intermittent occurrence.

Nothing that I tell which triggers this. Unfortunately I don't have more helpful info.

Surge XT Version

  • Version: 1.0.1.60228e8
  • Plugin Type: VST3
  • Bitness: 64-bit

Reproduction Steps:
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Expected Behavior:
Goes without saying that this shouldn't happen.

Screenshots:
If applicable, add screenshots/GIF/videos to help explain your problem.

Computer Information (please complete the following!):

  • OS: MacOS Mojave 10.14.6
  • Host: Logic Pro X
  • Version: 10.5.1

Additional Information:
So far this has happened twice within the space of the last month. I will update if it happens again.
I am using an external SSD which contains my project data.

@kookin kookin added the Bug Report Item submitted using the Bug Report template label Feb 16, 2023
@mkruselj
Copy link
Collaborator

mkruselj commented Feb 16, 2023

Which version of Surge is this (see About screen)? You haven't edited the bug report so it's showing the version from the issue template (1.0.1.60228e8) and that it's VST3, which we know Logic doesn't load.

@baconpaul
Copy link
Collaborator

But 1.0.1 AU had this exact bug in lpx in some situations. It is fixed in the current stable release

@baconpaul
Copy link
Collaborator

So if you upgrade to 1.1.2 this will no longer happen. (I am assuming the vst3 is just a typo and the 1.0.1 is not)

@kookin
Copy link
Author

kookin commented Feb 16, 2023

1.0.1.60228e8 was my actual version. VST3.. my bad.

Thanks for the quick responses. I've upgraded to 1.1.2, will report back if it happens again.

@baconpaul
Copy link
Collaborator

Great I’m going to close tbis but please do reopen if you see it again - I found it myself after we shipped 1.0.1 and also lost work so I’m sympathetic and sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template
Projects
None yet
Development

No branches or pull requests

3 participants