Thanks for giving it a shot! Could you let me know:
- which version of Ableton you’re using, and
- the model of your Mac computer? (the new M1 chips are not yet supported, unfortunately)
I had a go at building a Windows version – give it a try when you get the chance! I have no way of testing it myself unfortunately 🐒 https://github.com/maxwellpollack/repitch/releases/tag/v0.3.5
Okay… reading more about this, and you were right! I need a Windows machine in order to build Repitch as Windows VST3. I’ll look into using Github Actions for this, or otherwise I’ll build a Windows version next time I have access to a PC. Thanks for all the help troubleshooting!
No problem, thanks for helping me understand your issue!
I realized I made a mistake… the installation location should be C:\Program Files\Common Files\VST3\repitch.vst3, not C:\Program Files (x86)\Common Files\VST3\repitch.vst3. The latter is for 32-bit plugins, but Repitch is 64-bit.
Hope that fixes it 🤞
repitch.vst3 is the folder which contains the “Contents” folder (it’s technically a file bundle, which is why it has an extension).
In your screenshot, it looks like repitch.vst3 is placed one directory too deep. It should read C:\Program Files (x86)\Common Files\VST3\repitch.vst3\Contents...
Try moving repitch.vst3 up a directory, and removing the .vst3 extension you added to the file in the Contents/MacOS folder.
The .vst3 file should work in both Mac- and Windows-based hosts.
In FL Studio, open the Plugin Manager (Add → Other → Manage Plugins). Ensure that repitch.vst3 is in one of the “Plugin search paths” listed. Turn ON the item under “Scan options” labeled “Rescan plugins with errors” and then click the “Find more plugins” button on the top left.
It seems like Repitch fails to load on the first scan, but then passes on rescan. When I have the time I’ll fix this bug, but for now this workaround should get it up and running.