Should we start a wiki page of known Unscannable plugins that otherwise work in the DAW?

[the-simian]

Basically that. I have quite a few installed plugins and there are a few .dll files that consistently trip up Owl Plug when the Native Discovery feature is enabled. I do not believe this is the fault of Owl Plug. In this specific case they are

• ABLPro_x64.dll* and ABLProFX_x64.dll* (https://www.audiorealism.se/audiorealism-bass-line-pro.html)
• WavesShell2.dll (basically its an entry point for all the Waves stuff and Waves is kind of weird how it works anyways)

Both of these files did produce a log file that when I read them didn't really make me think it was OwlPlug's fault - I think its just these particular plugins. I expect others to come across the same thing. Maybe we could have a standard format like

• PLugin Name
• Manufacturer
• The logfile error or the dump.

What do you think of something like this?

[DropSnorz]

It's a good idea ! I receive a lot of reports from users due to plugin crashes. A page to centralize known issues will be great.
I've created this page on the wiki. What do you think about it ? Feel free to complete it or re-organize things 😉

[the-simian]

@DropSnorz This looks great! We should put a link to this in the app, that or consume the markdown and display it inside the app. I can see you've given me the ability to edit the Wiki, so I'll put in the ones I know about and look over the issues and add others. Thank You for being so responsive and accepting of my help on this

[DropSnorz]

Yes, we can at least add a reference to this page on the crash report ui. It can be a starting point to create some sort of blacklist based on the plugin filename to skip native scan by default.