search

gregrecco67 / AudiblePlanets

An expressive, quasi-Ptolemaic semi-modular synthesizer.
GNU General Public License v3.0
109 stars 4 forks source link

Version 1.1.0 fails to scan on REAPER 7.18, Windows 11 #10

Closed Someone65 closed 3 months ago

Someone65 commented 3 months ago

The version before this scans successfully but 1.1.0 fails to scan properly. It outright crashes REAPER if you try to load it from if you had previously scanned its older version successfully but update it by replacing the file.

gregrecco67 commented 3 months ago

I just updated to 7.18 and confirmed I was using the plugin downloaded from the Releases page and could not replicate this error on Windows 11 using either the VST3 or LV2 version.

Someone65 commented 3 months ago

I tried entirely deleting the cache and rescanning every plugin, as well as redownloading the release from Github twice and nothing seems to be working. Is there anything else I need to install to get it to run? Any info I can give besides the fact that I'm on Windows 11 64 bit? I also tried disabling out-of-process plugin scanning and then scanned only Audible Planets 1.1.0 and it just causes REAPER to crash entirely.

EDIT: 1.1.1 is also crashing.

Someone65 commented 3 months ago

I tried installing 1.0.22a and it's not crashing so something changed between these versions that's causing this.

gregrecco67 commented 3 months ago

For version 1.1, the underlying framework, JUCE, was updated to version 8. Other than that, the only significant changes were to the UI layout, so you're not missing out on any new functionality if you stick to an older version that works. That said, you might try the 1.1.1 LV2 plugin in Reaper. If you find any crash report in Windows Event Viewer, that might give me some more information, but without being able to reproduce the bug, I'm unlikely to be able to fix it.

Someone65 commented 3 months ago

I checked the event viewer and saw it was something to do with VC Redist, so I repaired my VCRedist install and restarted my PC and that apparently just fixed it.