Reuse cherry audio
In the livestream today, you posted this:
I can't seem to find that file anywhere in the Unify folders. Where is it?
OK, I RTFM, and found out where to find it under appdata.
Wouldn't I need to eliminate the Dreamsynth part and just have to affect all Cherry Audio synths? Like this:
<PluginRule vendor="Cherry Audio"/>
Interesting bug in the forum software. If you edit a post, anything in <> brackets is deleted. It posts ok the first time though.
Well spotted, and you are 100% correct! I had made the change on my Mac, but not on the PC from which I copied/pasted it to the livestream chat. Here's my updated ReuseAcceptRules.xml, which on a Windows PC you can find by entering
in the address bar of an Explorer window:
<?xml version="1.0" encoding="UTF-8"?> <PluginRules> <PluginRule vendor="Spectrasonics"/> <PluginRule vendor="Native Instruments%" name="Massive"/> <PluginRule vendor="Native Instruments%" name="Reaktor"/> <PluginRule vendor="Rhizomatic" name="Plasmonic"/> <PluginRule vendor="Decidedly" descName="DecentSampler"/> <PluginRule vendor="Arturia" descName="Pigments"/> <PluginRule vendor="Cherry Audio"/> </PluginRules>
BTW, to enter explicit character data like this in Forum posts, use the "<>" (code) button.
Thanks - I was just about to ask the same question! Does it make a difference if you type name= or descName=? Both appear above.
Also in my file I have "Kontakt%" - is the % significant?
I assume the order of the rules in the file is not significant?
The percent-sign (%) is VERY significant. It will match any other characters which may follow those you specify. This is particularly useful when a plug-in might be called e.g. "Serum" on Mac, but "Serum_x64" on Windows.
The name/descName distinction is more technical. Again, the problem is that the exact name by which a plug-in is known inside Unify (or any other host program) might not be what you expect. In the case of Serum, again, the descriptive name (descName) will always be "Serum", but the "name" may be platform-dependent as described above. When in doubt, use descName.
I admit that the whole text-file based, reuse rules mechanism is clumsy, confusing, and difficult to use. It's basically a stop-gap until I can understand the issues in enough detail to be able to implement a better solution. All of this feedback is very helpful.
Thanks for clarifying!
Please note there's a full description of the reuse-rules system in the Unify manual: https://pluginguru.net/unify/manual/doku.php?id=layer-reuse
it works fine anyway. it's very fast .
I was also wondering ,
I have many Spitfire Audio banks in my library. Can I add a line also for Spitfire? like this <PluginRule vendor="Spitfire Audio"/>
WIND 10 Reaper 6 Kronos / Omnisphere 2.8 / Keyscape / Stylus / Ravenscroft / Spitfire Originals collections , BBC SO CORE & ABBEY ROAD 2, FROZEN STRINGS ,SOLO VIOLIN ,SOLO CELLO,Orchestral tool Habitat, Arturia Pigments , Rapid Parawave ,Plasmonic, Surge ,Flow motion,Pianoteq pro,Memorymode,Eight voices,Dreamsynth,Lion,Triad,Royal Albert hall Organ,Kniffonium,Vital
Can I add a line also for Spitfire? like this <PluginRule vendor="Spitfire Audio"/>
You certainly can, but I can't guarantee it will work. Some plug-ins work well when re-used; some do not.
One level up from where the ReuseAcceptRules.xml file lives, you will find a file called PluginList.xml; this is Unify's "known plug-ins" list. There is an entry for each plug-in, where you can find the exact format, name, descriptiveName (use "descName" in your rules), and manufacturer ("vendor") strings.