Notifications
Clear all

Proper naming / metadata translation for unified libraries


Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

Hey fellas,

I started to get my Arturia V Collection 8 unified, I also own Falcon and NI Komplete so there’s still a few things to get unified.

I did a few instruments to get the feel and semi automate to get what I want.

One of the things is patch comments / meta data , I started without much of them but changed a few things based on some instruments and practical use.

Regarding metadata and file naming it’s getting a bit more tricky, and curious if there are more best practices do’s and don’ts to scale out with more then a few instruments.

Example: Arturia is Using Strings/Guitar as metadata.

Following the Unify Patch Naming Breakdown this should be GTR instead of STR

For now I’m translating Arturia Strings/Guitar to GTR – Patchname in Unify while maintaining the Arturia meta data in the tags.

Regarding the Arturia instruments for now I’m deliberate using KEYS instead of KEY to be able to sort later on to get only Arturia (or in a later phase Falcon or NI Komplete patches)

Any opinions or guidance to translate certain 3rd party tags more consistent to Unify tags.

I’ve included an screenshot, based on the pigments 3.5 unified pack I’ve included the Master Effects and AUX1 layers along 4 macro knobs.

Based on Arturia tagging this arp would be named SEQ after: Sequence>Arpeggio but that would break the Unify patch naming breakdown guidance.

Before I reach kind of the point of no return i decided to open this post to see if there are better ways / other things to keep in mind before it gets out of control too much and have / maintain the best Unify experience when scaling out.

 


Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

@lu_

I've made a GitHub repository for various kinds of code for batch-processing .unify files, including a few tools for making unified libraries (semi-)automatically: https://github.com/pluginguru/unify-batch

Have a look at the code in the TAL Unifier project in particular. There are a bunch of tables for translating specific words used in patch names into standard PlugInGuru prefixes.


ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

Hi Shane, thanks for your reply and pointing me to the github page. 

I did an quick read and found in the source files and already saw some nice insights for translating metadata, gonna reserve some more time to understand / translate it properly.


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
 

@lu_ 

FYI another forum member (@heyjosh ) unified some of the VC8 collection (see here --> https://forums.pluginguru.com/unify-patchbook/paged/3/ )

I have only recently purchased VC8 and tried them but found some issues which I have corrected. So I have corrected guru files for ARP 2600, B3, Buchla Easel, Clavinet V, CMI V and CS-80 which I will upload somewhere shortly for general consumption.

However, I would be interested in any others that you manage to Unify and if you also manage to come up with a process like Shane developed for Unifying TAL plugins.

Thanks

 

This post was modified 3 weeks ago by JeremyH

ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

@JeremyH ,

Thanks for your reply. 

 

I tried some "older" unified Arturia packs, those ware for VST 3 and i'd like conform to the best practices so VST2.

The url Shane provider is giving me new insights, still have a bit to search out tho.

I'll detail my process till now a bit more with two Ad Hoc scripts i've written.

I'm a autohotkey rookie but managed to make 2 routines:

My setup is dual monitor, 1920 * 1200 , DPI 125%

Unify on my left screen, including file browser and full screen

Arturia VST on the bottom right screen, scaling on 120% (works on most plugins) in the file browser (so top right right with the 3 dots as in the picture i've just added) 

My unified Process till now:

Start Arturia routine with (ctrl & /).

It'll select next preset, clicks on the three dots, and clicks save file as). Sometimes the click on save file as doesn't work, just an enter will do it. From there on i'll copy patch comment first, then patch name.

Start Unify routine: (ctrl & ')

It'll click within unify on save and opens cursor right to the patch name. So just CTRL+Shift the whole patch name and paste ctrl+v.

After that do an windows + v to select the second clipboard entry comment and paste that in comment.

For the metadata tags i have an word document, i did those manually first but made a few typo's here and there.

So in about 10 to 20 second i can semi automated unify an Arturia patch with the meta data i want with most of the time just a few copy and paste's.

I'll invest a bit more time tho to the TAL concept, i've been looking a bit in the Arturia DB and there's almost 15000 presets.

Also when new versions will drop it'll be cool to just have it automated as much as possible and if we could extend this to Falcon we'll be quite happy

I have a few Arturia sound packs so i won't be able to distribute those synths where they in, but appears i have only factory sounds in Piano V2. So i could try to upload that somewhere in the coming days.

 

Unify AHK

This one will react on "ctrl & '  " 

routine:

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.

^'::
Winactivate Unify

sleep 100

click 1455, 161 ,1

sleep 100

Winactivate Preset Metadata

click 671, 84 , 1

sleep 100

return

 

Arturia AHK This one will react on "ctrl & /" 

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.

^/::
Winactivate INST 1 |

click 1150,54
sleep 500
Click 1852, 153, 1
sleep 250
click 1790, 177, 1

sleep 250

return

;Window Size Wurli V 120% on 1920*1200 right screen
; Press CTRL & / to open the save as window. Sometimes the window doesnt open but a pressing enter once will do it then
; from there one do ctrl & a to copy the patch name
; escape a few times and you have the patch name in your clipboard

 

 

 

 

This post was modified 3 weeks ago 2 times by Lu_

ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

@getdunne

I did take an closer look at the github page to understand the TAL unifier concept.

Unfortunate I don’t have any licensed TAL software, I downloaded the Baseline 101 demo today to take an look at the code and how the data’s structured compared to Arturia.

When looking at BassLine_Unifier.cpp, more specific:

    patchComment = "TAL-BassLine factory patches by " + authorName;

Is using an static patch comment name

When looking at the Bassline 101 patches I can understand that, there is no comment info there.

But when it comes to Arturia that is filled with info that I’d like to see populated.

A few things to doublecheck;

TAL is using the JUCE framework, either is Arturia according to autohotkey winspy. So with adjustments with the correct data in an arturia cpp and .h file we should be able to pull at least the presets without comments?

If yes that would already be awesome. I think I found some way to export all Arturia patch names and comments along a bit of more information to CSV.

From there on we could see how far we could get with Powershell to export each patch based on name to xml, parse in the comment data and zip it up again. It’s far over 14000 patches so a bit too much to do by hand.

Here’s a few examples of the comment fields on Arturia patches:

Slow rising sound effect making intensive use of the comb filter. The Tonal Macro and the mod wheel worth trying together.

 

Rhythmic sequence with 2 different layers. Use mod wheel to add a Flanger effect. "Pitch Delay" Macro adds a shimmer effect.

 

An extreme womp bass. Use the Time Macro to create rapid fire womp patterns. Mod wheel adds unison.


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

@lu_

Unfortunately, there is no standard encoding for plug-in preset metadata. Without very detailed support from the plug-in vendor, writing code to generate unified presets is a difficult reverse-engineering job, unique to each plug-in.


ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

Hi Shane, no problem.

Think we should be able to then just cycle with Autohotkey through all individual VST's plain presets and save them with preset name as the filename. 

If it is supported to modify the comment field in an user Unify preset (eg convert unify  preset to xml, update comment field in the XML , convert back to unify). 

Based on the data in the picture i've attatched  it should be do able in powershell to locate an preset based on part of the name and so on.

This post was modified 3 weeks ago by Lu_

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 
Posted by: @lu_

If it is supported to modify the comment field in an user Unify preset (eg convert unify  preset to xml, update comment field in the XML , convert back to unify). 

There are utilities to convert .unify files to plain .xml and back, at the GitHub repo I linked before. However, one of the other users (@zinct I think) has been able to use AutoHotKey to enter patch comments into Unify's save-dialog, so there should be no need to modify the patch XML.


ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

Cheers,

I'm most familiar with Powershell, got a bit more to learn about autohotkey and some reading to catch up on other forum posts.

But first i'm gonna kill some time with my new BBCSO core and CoreStation Unify Pack. 🙂


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
 

@Lu_

For these Arturia synths the standard way to extract information in AutoHotKey, such as preset name and comments, is to select the "Save Preset As..." option within the synth top left hand menu. Then you can copy information from those fields, cancel out of that menu and then paste the information into Unify preset metadata fields on the Save dialog box.  

The best Autohotkey information thread is here in case you didn't find it  --> https://forums.pluginguru.com/unified-libs/autohotkey-unify-patch-browser/  


ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

@JeremyH 

Yes, i already figured that out for the most part. Only clicking in the save as window to copy / paste from within ahk ain't working yet on my side, think i should be able to get that mostly automated soon 🙂

I realize i still have a bit reading to catch up on scripting on the forum here and do a few more Arturia, Falcon, Komplete and Spectrasonics conversions to start with.

Oh btw, i did take an look and for the Arturia Stage-73-v, Jun-6 and Jup-8 i only have the factory sounds so i could share them with the Guru Nation.

What is the proper way to share those? From my mind it was ok to share unfied Arturia factory banks but thought let's doublecheck that first.

Oh and best wishes to all and have a safe & healthy year!

 


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
 

@Lu_

I usually share them here https://forums.pluginguru.com/unify-patchbook/ or here https://forums.pluginguru.com/unify-share/ with a dropbox link to the guru file.

You can see some examples there e.g. these ones...

https://forums.pluginguru.com/unify-patchbook/ni-super-8-unified/#post-10439  

https://forums.pluginguru.com/unify-patchbook/aas-swatches-1-5-2-unified/

https://forums.pluginguru.com/unify-patchbook/aas-ultra-analog-va-3-unified/#post-10009

If I have any doubt whether there is anything which cannot be shared, I will usually run them by Shane first.
BTW I have Unified Falcon factory library for my own use but haven't shared it here as there was another project ongoing to Unify it (I don't know the current status of that project).

Komplete instruments, especially Kontakt, have some unique issues (see other threads on these forums) although Kontakt Player instruments are usually ok.

l would avoid Unifying Spectrasonic instruments unless they are for your own use. 

A very happy and healthy new year to you too!

This post was modified 2 weeks ago 3 times by JeremyH

ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

@JeremyH

Thanks for the reply.

I started with Falcon but there ware still a few things i had/have to overthink so i decided to do the V collection first since it's easier.

Regarding Spectrasonics that'll indeed only be for my own use. I also have like the Bob Moog library so it'd be great to have that for myself into unify.

Since u and a few others shared some nice packs that got me started i thought let's also contribute and try to give something back (factory instruments library's that are ok to share) with the community.

Kontakt will be another beast i think, i own most of the Portal stuff so in time i might take a shot at Exhale and other Output library's. 

But i already saw some references to unify Kontakt library's so it'll be an matter of time and priorities.

 

This post was modified 2 weeks ago by Lu_

ReplyQuote
Lu_
 Lu_
(@lu_)
Active Member
Joined: 4 weeks ago
Posts: 11
Topic starter  

I've emailed the 3 packs to John.


ReplyQuote
Share: