Anyone have any tips ?
Sometimes they appear sometimes not.
Once they appear they stay there but if I rename and rebuild they are gone and I spend hours trying to make them show up.
I tried that killall command. I also tried dragging the file from the caches folder into the trash. I also tried clicking
βFull audio unit resetβ in Mainstage.
I have put all other components into the trash so I can scan faster .
I also have this horrible looking command which I run too and I am sure someone will tell me is a terrible idea.
Hardware Overview:
Model Name: MacBook Air
Model Identifier: Mac14,2
Model Number: Z15T0005NLL/A
Chip: Apple M2
Total Number of Cores: 8 (4 performance and 4 efficiency)
Memory: 24 GB
System Firmware Version: 8419.80.7
OS Loader Version: 8419.80.7
Serial Number (system): XCK2P29KG5
Hardware UUID: 493211E1-4015-535F-B450-63371CC8416B
Provisioning UDID: 00008112-0008318026F9401E
Activation Lock Status: Enabled
I tried putting copies in both the user library and the root library
Well I think I found the reason why.
JUCE wasnt complaining about the parameter version hints it was just building the component file.
I THINK that adding them solved it and made the plugin appear in auval
ie changing
Yes, that makes sense. With JUCE 6 based plugins, we used to pass a string as the 1st argument when creating a parameter object. Since JUCE 7 we have been using the ParameterID class. I thought that we had seen a compiler warning while building. Maybe you can see if your compiler warnings could be increasedβ¦