Notifications
Clear all

Loom II Unified


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

I share with you here my Unified Loom II (863 factory patches) by Air Music Technology. 

(see below for updated link)

Note: I didn't do the "Meet Loom II" folder as those patches are duplicates from other folders and I also didn't include the legacy folder (from Loom I). 

 

This topic was modified 11 months ago 2 times by JeremyH
This topic was modified 7 months ago 2 times by JeremyH

mschiff, EdDrake, mj_prod and 2 people liked
Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

OOOH! Loom II, yay!

Is there any way to use the folder name to define PlugInGuru-style prefixes for the patch names (PAD, STR, KEY, etc.)?


JeremyH liked
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 2 years ago
Posts: 326
 

Thanks a bunch, Jeremy. 

 


JeremyH liked
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
Topic starter  
Posted by: @getdunne

OOOH! Loom II, yay!

Is there any way to use the folder name to define PlugInGuru-style prefixes for the patch names (PAD, STR, KEY, etc.)?

@getdunne

I have now added a simple option to my script which allows the user to enter a Category name which is appended to the patch name for all patches in that folder.

Your naming conventions document could be useful here but there are some folders that would require a bit of thought. Here are the folders for Loom II for example (with my categorization thoughts in brackets)...

02 Leads     (LEAD)
03 Basses    (BASS)
04 Wobble    (?? BPM)
05 Pads       (PAD)
06 Moving Pads (BPM PAD?)
07 Atmospheres  (??)
08 Polys     (POLY)
09 Organs  (ORGAN)
10 Bells      (BELL)
11 Percussive (PERC)
12 Swells    (??)
13 Waves    (??)
14 SFX     (SFX)

I'm also finding quite a lot of duplicate (or even triplicate) patch names in some instruments which requires manual intervention to resolve. That's a real problem with Analog Lab V for example; the script stopped around 30 times when doing the 858 Bass patches; it starts to become a manual process again! Adding a folder/category name to each patch name would help with the duplicate name issue in some cases but not others (e.g. ALV), so I'm wondering how else to handle the case where Unify finds a duplicate patch name and won't allow the patch to be saved so the dialog box sits there while the script continues to run oblivious of the fact. It also causes an issue because the main script I use looks at a folder and expects to run from beginning to end. So if it is interrupted at patch number 736 of 858 then there's currently no way to restart it at patch #737. I then use an alternative script which reads a text file of patch names edited to start from where it was interrupted rather than read the names directly from the instrument folder; another manual process.

Incidentally, doesn't your Unify utility allow the patches to be renamed en-masse after the fact? 

This post was modified 11 months ago 3 times by JeremyH

ReplyQuote
thsve
(@thsve)
Member
Joined: 2 years ago
Posts: 236
 

@zinct, @getdunne

Hello,
I took the liberty of changing the prefix of the patches and files with my "Swiss knife" utility 😎 .

02 Leads     (LEAD)
03 Basses    (BASS)
04 Wobble    (BPM BASS)
05 Pads       (PAD)
06 Moving Pads (BPM PAD)
07 Atmospheres  (FX)
08 Polys     (SYNTH)
09 Organs  (KEY)
10 Bells      (BELL)
11 Percussive (PLUCK)
12 Swells    (FX)
13 Waves    (BPM SYNTH)
14 SFX     (FX)

There are probably many "BPM candidates" in the folders, but I don't know an easy way to distinguish them.

https://www.dropbox.com/s/npd614jggcmwbia/Unified%20-%20Loom%20II.zip?dl=0

 

Win 10/Cubase Pro 11/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/etc


getdunne liked
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
Topic starter  

@thsve

Sounds good Thomas 👍  Can you post your version of the Loom II Unified library, thanks?  

I'm thinking of doing some of the other Air Instruments which, although old, have some great content and can usually be picked up very cheaply.

There's XPand2, VacuumPro, Velvet, theRiser, Transfuser and probably a few others.  @tjeri24 is already doing Hybrid 3 which is another good one.

Has anyone here tried Drum Synth 500 or Sonivox Stratum as they also seem cheap at the moment? 


ReplyQuote
thsve
(@thsve)
Member
Joined: 2 years ago
Posts: 236
 

@zinct

Follow the link in my post above to get the library.

Win 10/Cubase Pro 11/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/etc


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

@thsve Thanks Thomas. Saved me the job of re-doing all of mine.

This post was modified 11 months ago by JeremyH

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

@zinct

I'm also finding quite a lot of duplicate (or even triplicate) patch names in some instruments which requires manual intervention to resolve. That's a real problem with Analog Lab V for example;

The first thing is to ensure that these same-named patches are not actually the same patch.

Is there any way your script could form an extended patch-name based on the primary instrument used?

doesn't your Unify utility allow the patches to be renamed en-masse after the fact?

Well it does, but the state it's in right now means that only I can use it, and I can't keep up with your prodigious output!  🤩 😜 😎 


ReplyQuote
JeremyH
(@zinct)
Member
Joined: 2 years ago
Posts: 460
Topic starter  
Posted by: @getdunne

@zinct

I'm also finding quite a lot of duplicate (or even triplicate) patch names in some instruments which requires manual intervention to resolve. That's a real problem with Analog Lab V for example;

The first thing is to ensure that these same-named patches are not actually the same patch.

Is there any way your script could form an extended patch-name based on the primary instrument used?

doesn't your Unify utility allow the patches to be renamed en-masse after the fact?

Well it does, but the state it's in right now means that only I can use it, and I can't keep up with your prodigious output!  🤩 😜 😎 

@getdunne

🤣 😀 😎 

Yes these are unique patches with the same names but on different instruments. The issue with Analog Lab V is that you can either Unify them a folder at a time (x 21 instruments) which would take forever or, say, all the Bass instruments for all 21 instruments (858 patches). The latter is a better approach for automation as you can get a lot done with less manual input (in theory anyway). The problem is that you are much more likely to run into duplicate patch names (and I did). For those instances, I manually named the patch with the instrument name in parentheses e.g. Basso and Basso (Prophet V).

However, to extract the patch name from ALV I am effectively getting AHK to click on "File --> Save Preset As" in ALV so that I can copy the patch name from the screen that pops up. Unfortunately though, patch name is the only field on that screen that is copyable text so I am unable to copy the Instrument to append to the patch name. 

I have investigated and found that AutoHotKey has a way to grab and OCR an area of screen (to turn the bitmap into text) so that might be one way to do it. I am looking further into that. For example...

https://www.youtube.com/watch?v=YO--VBqJW7o  

Alternatively, I know that Thomas (@thsve) has used Python to read the patch details from other instruments so maybe that would be a better approach. I have at least now found where ALV keeps its patch files on disk.

This post was modified 11 months ago by JeremyH

getdunne liked
ReplyQuote
thsve
(@thsve)
Member
Joined: 2 years ago
Posts: 236
 

@zinct

I don't own Analog Lab V, but downloaded the demo. I will see if I can understand the structure and how to automate the patches. The first impression is total confusion 😎.

I have found the "preset files" and a readable database, but I have not been able understand how they correlates to each other. This is probably because the demo version does not contain all the presets.

I will look into this further.

Win 10/Cubase Pro 11/Wavelab 8/Spectrasonics all/NI 13/Izotope MPS2Serum/Cthulhu/MusicLab guitar vsts/etc


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

@thsve

Thanks Thomas, much appreciated. 👍 


ReplyQuote
zipidowski
(@zipidowski)
Active Member
Joined: 7 months ago
Posts: 8
 

How to get these? Both dropbox links says file deleted.

Would be great if all AIR software gets unified. Plugins are all the time at sale and are very affordable and quite good.


JeremyH liked
ReplyQuote
Erik van Wees
(@erik-van-wees)
Eminent Member
Joined: 2 years ago
Posts: 40
 

@zinct,

Thanks again Jeremy,

One of the reasons I bought the Akai VIP app, was to breathe life again in the very good AIR plugins; has anyone looked already at the VIP format (a fore-runner to NKS i gather) in order to maybe extract preset db structure? If not, I can have a look and see ...

 


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

@erik-van-wees and @zipidowski 

I think my DropBox filled up so I deleted the libraries that I posted a while back. Presumably Thomas did the same.

I have re-uploaded Loom II (now as a .guru), also incorporating Thomas's categorisation changes.

Here is the link.

 

https://www.dropbox.com/s/9tix55uj2db5qqw/Unified%20-%20Loom%20II.guru?dl=0
 

I tried Akai VIP but didn't really gel with it so no longer use it.


ReplyQuote
tjeri24
(@tjeri24)
Eminent Member
Joined: 2 years ago
Posts: 22
 

Thanks for Loom2. I had planned to switch it to Unify but you got the job done. Good.


JeremyH liked
ReplyQuote
heyjosh
(@heyjosh)
Trusted Member
Joined: 8 months ago
Posts: 61
 

Yes, thank you. This is awesome. Although, the GUI is stuck small. Anyone have any ideas on enlarging it?


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

Yes, thank you. This is awesome. Although, the GUI is stuck small. Anyone have any ideas on enlarging it?

Could you please do me a favor, and try loading Loom 2 inside a ComboBox, and let me know if it still shows up small?


ReplyQuote
terrybritton
(@terrybritton)
Member
Joined: 3 months ago
Posts: 64
 

This is utterly spectacular! Loom II is long one of my favorite and most used synths (as is Vacuum Pro). You have made me sooooo happy!

Terry


JeremyH liked
ReplyQuote
zzz00m
(@zzz00m)
Active Member
Joined: 1 month ago
Posts: 7
 

Loom II.. Yummm... tasty!

Nice work, Jeremy!

Fyi, those presets with -RD at the end were contributed to Loom II by sound designer Richard Devine. There's something like 100 of them, I believe.


JeremyH liked
ReplyQuote
Share: