This time I am having problems with Midifire. When starting Midifire it seems to scan for my plugins but after that when I'm inserting the AU Midi Effect module and clicking on the wheel in the plugin window, the plugin list is empty though I have lots of Midi FX plugins available in LPX.
MidiFire only supports AUv3 plugins so it will not show the same list as LPX which supports both AUv2 and AUv3. Gradually more AUv3 plugins will appear (and v2 plugs will move to v3). In addition, MidiFire only supports MIDI FX plugins (not instruments).
Now, StreamByter (and each of my mfx Series plugins) is an AUv3 MIDI FX, and if you have that installed, it should definitely show up in the list. If you have StreamByter installed (and you can try the free mfxMonitor plugin too) and the list really is empty, let me know and I can look into this for you.
Downloaded mfxMonitor and it is not showing in the list. But I discovered that Midifire is still scanning in the background. And then at some point it crashes. So I guess it doesn't even come to the point to recognize mfxMonitor.
I know that Midifire is still scanning because sometimes I see plugin screens popping up. For example my eLicenser plugins are asking for authorization, because MidiFire does not have access to Synsopos.app. Oh and when I click on the Acitivity Log on the right I can see in yellow Scan AudioUnits. Lately Midifire did not crash. It just seems to scan, but still there are no plugins available. The list is very short anyway. I have purchased Audeonic mfx plug-ins. I think they are more useful for me than Midifire anyway. As I’m mainly working with LPX and these plugins can be inserted into LPX, whereas Midifire is only standalone.
BTW, I'm asking myself why Midifire scans all AudioUnits when it only can use AUv3 Midi FX anyway...
> BTW, I'm asking myself why Midifire scans all AudioUnits when it only can use AUv3 Midi FX anyway...
MidiFire asks macOS (via Apple's API) for plugins that are 'Music Effect' (sometimes called 'aumi') but if you are seeing non MIDI FX activity then Apple must be scanning all of them anyway and only returning the relevant ones.