Notifications
Clear all

[Sticky] Patch and preset sharing guidelines  

  RSS

getdunne
(@getdunne)
Member Admin
Joined: 12 months ago
Posts: 1239
January 27, 2020 11:51 pm  
  1. Attach zip archives to your posts (even if only posting one file), as some users may not be able to download files of other types.
  2. Include a brief description in your post, and ideally also in a READ ME file included in your zip archive.
  3. ALWAYS save with Library = "User Library".
  4. List all third-party plug-ins your patch (or layer preset, etc.) requires, and which formats (VST/VST3/AU) you used.
  5. VST is the preferred choice to ensure patches created on Mac can be used on Windows, and vice versa.

Regarding #3: Unify gets the library name for each patch from inside the patch file, NOT the folder the file is in. So if you save a patch with the Library field set to "Unify Standard Library", it will show up as being part of that library even if the file itself is inside some other folder. This is guaranteed to confuse people! The nice thing about setting Library = "User Library" is that every Unify user will normally have a "User Library" folder, and if they put your patch (.unify file) in there, the library name which shows up in Unify will be the same as the folder they put it into--no surprises.


Quote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 28, 2020 3:39 am  

I like the idea of Unify users being able to share presets. However, on looking at the over 100 presets I have created, I realized sharing might not be as simple as it sounds. Most of my presets use a mixture of various vsts I have that might be common to many users, but my patches within the vsts are from many patch vendors or unique patches I have created from scratch. For example, for Zebra, I have purchased many libraries and even from Skippy I have purchased over 30 omnisphere libraries. I guess even those who have both vsts might not have purchased the same add on libraries I have purchased.

As a proof of concept, I have attached a single preset that uses a Standard Library patch from Skippy along with a standard Omnisphere patch, so anyone with Unify and Omnisphere can certainly use the preset. I just want to see this share path works.


Rob liked
ReplyQuote
Rob
 Rob
(@rob)
Member
Joined: 12 months ago
Posts: 81
January 30, 2020 6:27 pm  

@larry-ludwick

Tried to load the .unify preset, by double click, no luck

It says: It’s not known if this application can open “GTR - STR - DI Dreaming.unify”

There was also no Unify logo on it, so it was not yet recognised being the Unify file format I assume

 

I'm on a Mac and I noticed there is 1x VST2 from Omnisphere included and 1x VST3 Unify St GTR - DI Dreaming so those are cross platform compatible

 

I tried to manual drag/drop the file in the preset browser, nothings seems to happen, it's not there

But: after that manual load action it seems it's recognised and it has now the Unify logo on it

And double click opens now Unify: so far so good

But it's not loaded, I can't find it in Unify

 

Btw I guessed that Unify should recognise already on first time this file format

Maybe Shane can shed a light on this?


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 30, 2020 7:32 pm  

@rob

That's why I wanted to test patch sharing. I was hoping some others would load patches that I might test on my end.

I looked at my patch in Windows 10. The file in my User Library says it is GTR - STR - DI Dreaming.unify. I looked at the files in the Unify Standard Library they are all in a format *********. upf . Windows does not recognize .unify or .upf as associated with the program Unify, but I would imagine Unify looks in the User Library for a .unify file. 

My own feeling is the patch I sent must be placed manually in your "User Library" folder and not loaded through Unify.

I would also expect after you manually place the file, you must hit the "Rebuild Patch Database". This is the icon that looks like a target in the upper right corner of the Unify Window.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 8 months ago
Posts: 27
January 30, 2020 7:35 pm  

I've created 2 posts with presets a couple of days ago. But it still says "unapproved" next to the title. Hmmm…


ReplyQuote
Rob
 Rob
(@rob)
Member
Joined: 12 months ago
Posts: 81
January 30, 2020 7:53 pm  

@larry-ludwick

Yes, via that manual route now Ok

1)  copy preset / patch to "User Library" folder

2) Rebuild Patch Database = needed

 

It now shows up in the browser and it functions also 🙂

 

In the settings the Data folder path is already pointing to /users/shared/pluginguru/unify ...  but rebuild db was needed

Maybe stopping / starting Unify was also Ok, because of that path ... I will try

 

edited post with latest test steps:

removed patch - rebuild db - stop/ start Unify

copy patch again - start Unify - no show up - rebuild db = ok

 

Well, thats it for now 🙂


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 30, 2020 9:25 pm  

@rob

That's great, … something I hope will be added to the online manual soon on how to share.


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 30, 2020 9:26 pm  

@klasus

Weird your presets have not shown up yet. Maybe Shane has some insight on that.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 8 months ago
Posts: 27
January 30, 2020 9:54 pm  

@larry-ludwick

I've created the Posts int the "Share your Unify Patches" Thread. It didn't make sense to me to post them here under this "Guidelines" Post. And  if you do that, it seems these posts have to get approved first.


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 31, 2020 3:38 am  

@klasus

As far as I know, my post was not a replay to the stickee "Patch and preset sharing guidelines".  True I did not give it a title, but it seems it did not require any approval. Let's see if Shane appears to clear this up.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 8 months ago
Posts: 27
January 31, 2020 7:37 am  

@larry-ludwick

But if you look at the first reply in this thread, there's your preset. So you either posted it here or it was moved here. 😉 


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 31, 2020 1:48 pm  

@klasus

It was not a reply, it was a post. If I replied it would have a "@getdunne" in the first line.  This is a reply to you because it has "@klasus" in the first line. We still don't know what happened to your own post and that is what I am more interested in.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 8 months ago
Posts: 27
January 31, 2020 1:55 pm  

@larry-ludwick

  1. This was not my point. My point was, that you posted it in a thread about posting guidelines. Which is a subthread of the patch and preaet sharing section. Get it now?

 


ReplyQuote
Larry Ludwick
(@larry-ludwick)
Trusted Member
Joined: 9 months ago
Posts: 78
January 31, 2020 3:08 pm  

@klasus

I just posted the same patch as a new topic in the Patch and Preset Sharing thread.  It posted immediately without review. Maybe you should try to post now, maybe when you put yours up it was not setup properly yet.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 12 months ago
Posts: 1239
January 31, 2020 3:13 pm  
Posted by: @larry-ludwick

@klasus

I just posted the same patch as a new topic in the Patch and Preset Sharing thread.  It posted immediately without review. Maybe you should try to post now, maybe when you put yours up it was not setup properly yet.

Thanks, Larry. We're using a free third-party Wordpress plug-in for these forums, and (as with so many things...) we're not experts on it.


ReplyQuote
klasus
(@klasus)
Eminent Member
Joined: 8 months ago
Posts: 27
January 31, 2020 4:33 pm  

@getdunne

I've deleted the original Posts and created new ones. Posting now works!


ReplyQuote
Share: