MOTUnation.com

James Steele wrote: ↑Thu Aug 03, 2023 4:12 pm Yeah. I saw a post about that on Gearspace. It looks at package receipts, etc from installers. I also saw that one user said it reported plugs that weren’t installed. I really don’t have a need for it, and I think it’s a small developer and I’m kinda hesitant to use it.

I also got a warning from it saying I had to be careful about deleting bundles, that in some cases, deleting a bundle would render the Mac unusable. This was in the case of removing a category from the list of things to be ignored (I was trying to get it to ignore the many Apple Loop bundles). Too much overhead trying to figure out what this app does so I’ve deleted it.

bayswater wrote: ↑Fri Aug 04, 2023 8:47 am

James Steele wrote: ↑Thu Aug 03, 2023 4:12 pm Yeah. I saw a post about that on Gearspace. It looks at package receipts, etc from installers. I also saw that one user said it reported plugs that weren’t installed. I really don’t have a need for it, and I think it’s a small developer and I’m kinda hesitant to use it.

I also got a warning from it saying I had to be careful about deleting bundles, that in some cases, deleting a bundle would render the Mac unusable. This was in the case of removing a category from the list of things to be ignored (I was trying to get it to ignore the many Apple Loop bundles). Too much overhead trying to figure out what this app does so I’ve deleted it.

Yeah... I read a bit about it in the post at Gearspace, and normally I'm pretty OCD and have been known "to fix things when they ain't broke" and often get myself in trouble when I do so. So when I read about that app, I just was leery about it. First off, I did a clean install of everything back in July 2022 when I got this Mac Studio, so I probably don't have all the built up residual "junk" on this Mac that I had on my MacProt5,1 which had been the beneficiary (?) of numerous past uses of Migration Assistant.

It seemed like a solution to a problem that I really wasn't having and a bit too risky for me. But it does raise the issue that it would be very good if more developers included uninstallers with their software.

Not the same but feels the same:

Older session re-opened with missing plugs - clear missing. Then if you duplicate a mix, or change mixes, it always asks about the missing plugs even though they’ve been cleared and no longer exist.

Not sure if this helps but I had the same problem...I removed an old input device in both the AMS and bundles and it still showed up in MIDI input on multi-record mode. I selected all tracks and assigned the same MIDI input to a valid controller, and lo and behold the "ghost" controller vanished from the available device list in the tracks window.

BTW - when I open an older project the pop-up window has me reassign the old controller. I guess the sequence or project remembers it. New projects do not show the ghost controller.

To find that hidden FB-01 reference, first, check track routing, automation lanes, and project settings for any remnants. Also, scan your plugins/effects for any lingering FB-01 references.