Notifications
Clear all

Strange behaviour regarding duplicated entries in tag list


Ditto
(@ditto)
Active Member
Joined: 1 month ago
Posts: 14
Topic starter  

@getdunne Hi Shane

I have just been Unifyng Daichi Synth1 public domain libraries and there is a lot of them. To get around the issue of not yet being able to use sub-folders I enclosed the library name in square brackets and entered that onto the Tag labels box. Often in the drop down tag menu I would see duplicate entries of the library name but with some characters in lower case instead of capitals. As I progressed in my mission I decided to change how I did the preset names. For example my first method was to have the patch number first and then the descriptor space hyphen space patch name such as "097 ARP - Firefly". After doing ten libraries I soon realised it was a bad idea and started going back and re-labeling patch names to "ARP - 097 Firefly" format updating each patch as I went. The interesting thing was as soon as I did the last patch name in the library the duplicate file name disappeared and I was left with one name and that matched exactly how I had labelled the library in the Tag box originally. I thought this might be of interest and maybe shed some light on how to resolve the duplicate filename issue.

best regards,

ditto


Quote
Topic Tags
bug
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

When you say "duplicate file name" I think you mean "duplicate patch name"? Your operating system will not permit two files with the exact same name in a folder, but you can have two patch files (with different file names) that have the same patch name. Whenever this happens, you'll see two copies of the patch name in the browser - one for each of the two files.

Regarding Synth1, I should mention two things:

  • You don't have to create one gigantic library. You could make several smaller ones instead, and name them e.g. "Synth1 Vol.1", "Synth1 Vol.2", or something like that, so they will appear in the expected order in the list (which is sorted alpha-numerically).
  • Note that for old-fashioned VSTs like Synth1, each Unify patch actually stores the entire bank, not just one preset. I'm looking into ways to override this in future, but for now, you might want to think about making a smaller unified library, where each patch = one Synth1 bank.

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

I've been doing some experiments with Synth1, and I was wrong about the patch/bank issue. What I described is true for Dexed and OBXd, but apparently not Synth1.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

I got a bit further; see https://forums.pluginguru.com/postid/9552/.

I can create the basic unified libraries quickly now, but there is still a ton of work to do, to apply the correct prefixes (PAD, KEY, etc.).


ReplyQuote
Ditto
(@ditto)
Active Member
Joined: 1 month ago
Posts: 14
Topic starter  

Great job Shane. I've been picking my way through the public domain libraries. Some of the patches are hard to classify and the process is long and laborious. I aim to do a couple of libraries a night so it will take sometime. I'll bundle up what I have done so far and send them to you.

Best regards,

ditto


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 
Posted by: @ditto

I'll bundle up what I have done so far and send them to you.

Are you working from the libraries I've unified, or others you did yourself? If the latter, I won't be able to spare the time to pore over them to compare against what I've got here. I can put a few hours into unifying, but I can't coordinate the entire effort.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

We have to figure out some way of avoiding duplicate patches/banks. The patch names are all very short, so duplicates are highly likely. That's one big reason I've been trying to keep the banks together. Although I do rename the banks (because the original bank names are all over the place), I've been trying hard to make the new names clearly/obviously related to the originals.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 
Posted by: @ditto

I managed to get six of your unified libraries classified this evening. Where would you like me to send them?

Just zip and post here. They're small enough.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

Thank you. Those look good at first glance. Continuing to use my library names will help in knowing which ones are done.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 
Posted by: @ditto

I found that if I change the preset names in Unify and update it doesn't change the name in the source folder. Changing the names in the source folder doesn't change the names in Unify browser. So if I change the names in Unify with the new category and update am I right in that the change is saved to the source folder whilst the names there continue to show SY1? If that is so are you happy to go that way or do you wish the names in the browser to also show in the source folder?

Displayed patch-names in Unify are just one more aspect of the "metadata" stored in the patch files themselves, just like author, category, tags, and comments. Hence changing the patch-name doesn't rename the file. This decision (which confuses everyone) was made because it allows patch names to include any characters that you can type, whereas certain characters (forward and back-slashes, for example) are not legal in file names, and the set of restricted characters is different for Mac and Windows.

To rename a patch AND the patch file at the same time, you can do the following:

  1. Click on the patch in the browser, to load it.
  2. Right-click the patch and choose to DELETE it. (The patch now only exists in memory.)
  3. Click SAVE, edit the patch name, click Save As, and confirm.

The only additional step is #2, which I'll admit is counter-intuitive, but doesn't take long.


ReplyQuote
Ditto
(@ditto)
Active Member
Joined: 1 month ago
Posts: 14
Topic starter  

That makes sense now you've described how the file system works. I'll get back on the conversions later today.

 


ReplyQuote
Ditto
(@ditto)
Active Member
Joined: 1 month ago
Posts: 14
Topic starter  

@getdunne

I now have a strategy for dealing with duplicate patches/libraries. It begins by extracting patch names from your Unified files which I can then copy paste into a spread sheet. By conditional formatting I colour cells with duplicate names in red. Duplicate folders are easily observed this way and are then removed from your Unified library folder. What remains I will do a name search per duplicated name in Unify after having installed the completed & categorized libraries into the unify Libraries folder. From there it will be a case of listening to each and removing any duplicates I here. This should trap most of the dupes. Obviously if there has been a name change at any time then these would be missed. I have attached the spread sheet. You will see there is a problem with the AZ Studios V2 and V3 unified files. For some reason it seems the V2 and V3 (all 256 patches in one which of course Synth1 can't handle) libraries got combined into one V2 library which means that the V3 library showed up as a duplicate. Later I will send you around another thirty libraries that I have, including my AZ Studio libraries, if you could find some time to Unify these I'll add them to be processed with the rest.

I have found problems with a number of libraries that IMHO I would find unusable in their current state. For instance some have Tempo Delays with huge amounts of feedback, overly long release times on the Amplitude ADSR, and other incompatible tempo  effects. The over all effect overwhelms the basic sound and makes it hard to categorize its type let alone use musically. I propose in these instances turning off the offending effects. I don't have the time to do much else and I really don't want to go too far away from the authors original patches.

The E. Ballasina library appears to be from a random generator judging by the patch names which consist just of time and date of its creation. I suggest we either ignore this library or you can use my modified version where I have re-named the patches with more friendly names and in several instances have had to use two Enhancer compressors in series with huge amounts of make up gain just to make them audible. Some patches I altered to a greater extent.

Another thought we could add any of these modified libraries into a separate bonus package.

Regards,

ditto

 

 


ReplyQuote
Ditto
(@ditto)
Active Member
Joined: 1 month ago
Posts: 14
Topic starter  

 

@getdunne

Here  is the link to the additional public domain libraries I have for Synth 1. Some libraries from kvr may be duplicates. I've also included AZ Studios V2, V3, lk-Phuterama and lk-X-ploded from your previous batch as these all had problems as described above. If you could get these Unified I'll add them to my project folder.

https://www.dropbox.com/s/cjhixx33goeo90t/New%20folder.zip?dl=0

Thanks for all you do Shane.

regards,

ditto

This post was modified 11 hours ago by Ditto

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2523
 

@ditto

I'll have a look, but I can tell right away most of those are just duplicates of banks I already unified. All those "kvr..." banks are duplicates I had already myself and threw out. I think you have a few genuinely unique ones, though, and I'll try to get those done.


ReplyQuote
Share: