Bug Reports

Computer: Mac mini v4 OS: MacOS Sequoia Kernel: Darwin 24.3.0 DAW: Reaper 7.35 Although the Neon manual and elsewhere claims it to be an AUV3 plugin, my newly-bought Reaper does not recognise it at all, not as an instrument, not as an effect. I've tried adding the Applications directory where Neon installed itself to my Reaper plugin path list but still nothing. I've searched the bug list here but see no references to this problem.

UI freezes a lot, especially when AUM playback is enabled, making it very difficult or impossible to select options.

as much as I love the concept, as much I'm distracted from the weak performance of the app. Using it in AUM and the moment things get a little busier and I add a 2nd or 3rd modifier the data entry becomes impossible to use, as the selection of parameters to assign are no longer accessible. Haven't seen or heard any reaction/announcement to fix this issue for a number of months and wonder why things are so suspiciously quiet? Currently it's like having bought a car (or any other driving vehicle) but be able to move only with walking speed : - (

On the auv3 version the user interface is starting to become laggy slow and unrensponsive when i open any menu tab. as soon as i close the tabs the app is going back to normal.unfortunately this issue is making the app unusable at the current moment.

In AUM the options seem to get stuck sometimes and could not find a way to clear them

When doing the plugin scan it crashes Endlesss