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

Update 2.1.0 Big Problems #35

Closed
HumanalizerVisualien opened this issue Nov 8, 2022 · 3 comments
Closed

Update 2.1.0 Big Problems #35

HumanalizerVisualien opened this issue Nov 8, 2022 · 3 comments

Comments

@HumanalizerVisualien
Copy link

First, thx for your incredible work...version 2.0.0 was great, even if i had to remap my controller with around 400 bindings, cuz of course, i optimize it every new build...

  • But now with 2.1.0, all the faders and potis does not work, also the configured send midi to LED's...
  • So i reinstall 2.0.0, and ok, first i don't delete the 2.1.0 files, so it shows still the newest update in preferences
  • So i reinstall 2.0.0 again, this time i delete the files in my application folder and it shows the right version...but big surprise...
  • importing the 2.0.0 bindings-file witch i export BEFORE updating on 2.1.0 fail completely, like a empty file!
  • Check for Updates-Button does not work on 2.1.0

So, i have to restore my system, guess that will fix it...

Apple MacBook Air 2020 M1, Ventura 13.0, OBS 28.1.2 arm64, Akai Profesional MIDIMIX

@HumanalizerVisualien
Copy link
Author

So here what i find out:

  • No visible changes in the bindings-list or even empty list after importing bindings -> just need to close the window
Import.mov

@nhielost
Copy link
Owner

nhielost commented Nov 8, 2022

Thanks for the fast feedback!

I am aware of the importing bindings issue and the Check for Updates button issue, but is there something else that I'm not aware of that is wrong? What about 2.1.0 is not working for you?

nhielost added a commit that referenced this issue Nov 11, 2022
@nhielost
Copy link
Owner

This issue has been resolved as of the latest update (v2.1.1). If this issue persists, please create another issue.

Again, thanks for the feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants