Notifications
Clear all

How To Not Clutter The Professional Libraries and Presets With Your Own Experiments

4 Posts
2 Users
0 Likes
256 Views
(@zenwarlord)
Active Member
Joined: 2 years ago
Posts: 8
Topic starter  

I've not gotten my feet wet with this, and now I realize I don't get what "save as" does; normally I think of it as creating a new copy - in this case it would be a copy of a multi I'm working on that I added an instrument to.  I thought I would try and save it to a different library but although I've been able to create a .unify doing so, that isn't visible within Unify in any of my DAWs. 

So its rather pointless if I can't create my new hierarchy to easily locate my new multi.

I looked in the manual but the "save" instructions are not matching what I'm seeing.  There's a save button, at which point this opens up a dialog which offers a "save as", and a "save layer patches".  I tried both, and although I can get my new preset to show up in the library that was the source of my original multi, I can't get my new multi to appear elsewhere (like in a folder named User or User Library) with a more memorable name - I really don't care if it lets me create a generic "user library" structure, or if I name my presets starting with 001, 002 (so I can find them not buried among the pro libraries. 

I know that in an earlier version of Unify I DID successfully do the above.  I see those .unify files from within Unify when I browse to those User Folders.  Its the new ones I've tried creating today are not visible in those folders.

However after my attempts I don't think I have any idea what these are doing in relation to my need, which hopefully someone else will understand, which is to essentially create a new folder or naming hierarchy outside of the original library that the original multi came from.

I didn't want to take a college class in how to create a full on new library (assuming that's not a simple button click).  But rather, I just want a quick way to place my work in a more findable place, related to what I'm working on.  If I use multi's from 10 libraries, but I'm working on a compilation for an hour and a half long film project, its easier if I rename them after my project.

This topic was modified 1 year ago 4 times by zenwarlord

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@zenwarlord

Thank you for reporting this. Saving patches and creating your own libraries (always recommended, rather than saving into published library folders) should be straightforward. If you attempt to save a new patch, and it does not show up in your patch list, this may be a folder-permissions problem, which you should fix ASAP.

Basically, you need to check the permissions settings for Unify's main data folder, and ensure that your user/login has write access to this folder and all of its sub-folders and their contents. The methods are different for Mac and Windows, and there is some variation among different OS versions. Which platform/OS do you use?


   
ReplyQuote
(@zenwarlord)
Active Member
Joined: 2 years ago
Posts: 8
Topic starter  

[Now works - but I don't know why or what's really going on sadly, aside from it being a windows permissions thing as you said - and I never found any files marked "read only", only the main folder with the black square beside the words "read only" which Microsoft says doesn't suggest that many files in that folder are actually read only - apparently it may mean that 'some file' in the folder structure is 'read only' though].

 

@getdunne 

I use Windows 10, and I have Bitdefender.  After I had that issue I noticed that my data folder was not moved from a drive for which I had some weird issues that were basically unsolvable from a Windows help forum perspective - possibly triggered by something between Bitdefender and Windows 10.  Any person who I found had the same error was given a runaround, and because it requires individually addressing all files affected (addressing folders doesn't work, and addressing the entire drive doesn't work) I opted to stop using that drive for anything other than simple storage. 

So I copied the data folder info and still found I had this issue.  

Since you mention the "read only" access issue, I checked and even this moved content is having the "read only" issue.  I added the exception to Bitdefender (as I always do), and followed all the suggestions on youtube, but the plugin guru data folder is getting changed back to "read only" every time I mark its contents  to turn it off, then exit the explorer properties, then go back in. 

As I said, I didn't figure out how to solve this on the drive that developed this issue - but I could do single files at a time and that worked just great.  Except I had thousands of videos on that drive and cannot waste time applying the change to individual files. 

 

Unfortunately Unify is similar in that sense - there are lots of files and its not worth doing them all one by one.  I may try to re-install everything but I have a few dozen plugin guru unify libraries and a few dozen free libraries as well.  So it could take a few hours to re-create this only to possibly have it happen again.  

Now, do I think Bill Gates is responsible.  

Yes I do. 😀

I'm trying one more youtube suggestion as we speak.  

[In refreshing my memory on this, the black box when looking at folder properties doesn't necessarily mean that files in that folder are treated as "read only" so I will need further help to debug this - in my previous issue that I mentioned with video files, I could not play the videos, and if I copied them elsewhere I still couldn't play them.  When I changed the user permissions in various ways per the Youtube instructions it didn't work - then someone showed how to change it to some highly insecure situation where the Owner was "everyone" and that made it so the videos played normally. 

I did the same in this case, and now I can save my Patch Files to the User Library data folder... But I wish I could get windows to function normally.  In the past I even tried the DISM and SFC / scannow and the whole lot of complex suggestions and nothing worked but changing the permissions of those files to "Everyone".    Its a pity that Microsoft itself appears unwilling to inspect and find the cause of such issues - they're forever locking the forum posts of people experiencing problems even though the threads receive feedback markings showing that many still have the issues, with no re-direct to a more up-to-date indication of how the problems are solved.]

This post was modified 1 year ago 2 times by zenwarlord

   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@zenwarlord

I'm glad to hear that you are making some progress, and I agree that Microsoft seems to be getting less willing to deal with user feedback. This is very unfortunate, and will not end well.

Note that Unify's patch libraries could all be flagged read-only, because those files generally don't get updated. The most important file that must be read-write is Presets.db (the patch database itself) which lives in the Libraries sub-folder of Unify's main data folder. Hence the main data folder itself, and each of its sub-folders (especially the Presets folder and its contents) should also be read-write, to ensure that Unify is fully functional.


   
ReplyQuote
Share: