(I tried PM'ing Blue Cat Audio a while ago but either I messed it up or my msg got lost/filtered) My question is: am I allowed to share a folder of just the binary files of Blue Cat Audio's plug-ins here on this forum? It will have all the duplicate assets cleared, and KUIML skin files re-written to point to the new consolidated binaries file whenever possible. This is intended to save a lot of space while still keeping full compatibility for these plug-ins.
If I can have permission: I'd post a link here with a copy of this consolidated binaries folder for other users to download, w/ instructions how to set it up. Since BCA plug-ins are protected with an email-linked license, I presume just having the binaries won't give anyone access to a plug-in they shouldn't have; this is solely intended for existing users of BCA plug-ins. But since they're not my assets I want to ask permission before sharing any of them
Question RE: consolidated binaries for BCA plug-ins
-
JTBrownell1998 JTBrownell1998 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=596065
- KVRer
- 21 posts since 4 Jan, 2023
-
JTBrownell1998 JTBrownell1998 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=596065
- KVRer
- Topic Starter
- 21 posts since 4 Jan, 2023
Btw, I know Blue Cat Audio themselves have mentioned in the past their plans to create a consolidated folder/installer for their plug-ins, but one of the biggest hurdles there is doing so while still maintaining backwards compatibility for old version users.
Well, I've come up with a method for accomplishing the consolidated binaries folder part that works pretty well on Windows 11 with the latest versions of BCA's plug-ins, but I don't know how much backwards compatibility it will have.
See attached is a screenshot of an example default skin file I've changed: As you can see, I'm using "$_USER_DOCUMENTS_PATH_$" which is recognized in KUIML by default (idk since which version of KUIML, though) to point to a consolidated binaries folder, which I've placed in the Blue Cat Audio folder within the user documents path. I also had to change/edit the paths of many files within the accompanying KUIML files, as well as the KUIML files for the Components (when applicable). And after a bunch of trial and error I'm happy to say that for me this method is working quite well!
Well, I've come up with a method for accomplishing the consolidated binaries folder part that works pretty well on Windows 11 with the latest versions of BCA's plug-ins, but I don't know how much backwards compatibility it will have.
See attached is a screenshot of an example default skin file I've changed: As you can see, I'm using "$_USER_DOCUMENTS_PATH_$" which is recognized in KUIML by default (idk since which version of KUIML, though) to point to a consolidated binaries folder, which I've placed in the Blue Cat Audio folder within the user documents path. I also had to change/edit the paths of many files within the accompanying KUIML files, as well as the KUIML files for the Components (when applicable). And after a bunch of trial and error I'm happy to say that for me this method is working quite well!
You do not have the required permissions to view the files attached to this post.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6336 posts since 8 Sep, 2004 from Paris (France)
Sorry for the delay. I have indeed missed your PMs (I must admit there are so many channels to get n touch these days that "unofficial" ones are sometimes missed: the best way to get in touch is a forum post or customer support).
I'd be very cautious about modifying the skins, because as soon as we do an update you will have to update them too. Also, there are probably a couple of things that will not work fine for some plug-ins, as there are other places that need to access the data paths that are currently not shared.
You can definitely share your work, no worries, but we won't be able to do any support for these modifications.
I'd be very cautious about modifying the skins, because as soon as we do an update you will have to update them too. Also, there are probably a couple of things that will not work fine for some plug-ins, as there are other places that need to access the data paths that are currently not shared.
You can definitely share your work, no worries, but we won't be able to do any support for these modifications.