Open AJMfox opened 1 year ago
Hello! Yes, I think the current version of Wolf Shaper VST3 has some issues on MacOS...
Can you please test this build, which is based on the latest source code? https://github.com/wolf-plugins/wolf-shaper/suites/18107211264/artifacts/1043744554
If Ableton is able to recognize this build, I will publish a new release of the plugin (v1.0.3) which includes the fixes.
Hi! I tested the build and did a fresh install, it sadly didn't fix the issue, the plugin is still showing as missing. Additionally, when I open this build of the plugin on the Macbook the GUI is missing (vst2, vst3 and standalone). Audio is still coming through.
I'm working with a Macbook Air M2 by the way.
Lastly, I noticed that whenever the plugin window is active, all my hotkeys stop working like Spacebar for Play/Pause, or generally any hotkey at all and I have to either close the plugin window or click into the Ableton project for them to work again (I noticed this with the current release too, it's also on Mac and Windows, might open a separate issue)
OK, thank you for testing the latest build. I will do some research regarding this issue. This is a bit difficult, since I don't actually own a Mac :(
Lastly, I noticed that whenever the plugin window is active, all my hotkeys stop working like Spacebar for Play/Pause, or generally any hotkey at all and I have to either close the plugin window or click into the Ableton project for them to work again (I noticed this with the current release too, it's also on Mac and Windows, might open a separate issue)
This other issue has been reported today: https://github.com/wolf-plugins/wolf-shaper/issues/172
Understood! I can test out more builds no worries, I'm just absolutely not a programmer myself haha I just really like the plugin so far so I'll help wherever I can!
Hi! I tried to open an Ableton project I'm working on my Windows 10 PC on my Macbook, and Wolf Shaper shows up as missing (all the other plugins show up just fine). I tried it in an empty project again, also the other way around, and it also wasn't working. I'm only using default installation paths so normally it should find the plugin no problem. When I tried this with the vst2 version of the plugin (even manually renamed the dll on Windows to match the one on the Mac) it was working just fine and Ableton recognized it as the same plugin and loaded it without problems.