Notifications
Clear all

Arturia ARP 2600 V3 Unified

8 Posts
3 Users
2 Reactions
3,770 Views
(@heyjosh)
Trusted Member
Joined: 3 years ago
Posts: 61
Topic starter  

I actually did factory plus a few 3rd party presets, but since those are still being sold, I excluded them here and only the factory ones have been included. Still not too bad, over 500 presets if you own the ARP 2600 V3 individual instrument (I have the V collection 8 and plan to work on each instrument over time). 

I suppose if you want the library to start with "Unified - " Then just rename it in the zip before installing as a .guru file. 

I also mapped the 4 performance macro knobs to the first 4 macro knobs in Unify. Probably could have done more, but I figure let's get these out there. Feedback welcome. There is still time before I start the next instrument.


   
Maranada reacted
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 
Posted by: @heyjosh

I suppose if you want the library to start with "Unified - " Then just rename it in the zip before installing as a .guru file. 

Unfortunately it's not that simple. Renaming the library folder does not change the library name. I used our in-house LibraryRenamer tool to change the name to "Unifed - Arturia ARP 2600 V3" and rebuilt the zip file. The rebuilt zip is attached below: RENAME it, deleting the "_.zip" suffix (5 characters), to make it into a .guru file which can be drag/dropped straight into Unify.

You used the VST3 version of the ARP 2600 plug-in to create this library, which means users will have to register that into Unify's known plug-ins list if they haven't already, or the patches won't load. We usually prefer the VST(2) version whenever available, but this is not a big deal. The VST yields slightly smaller patches, but in this case only 47 KB instead of 59 KB (20% smaller), so not that important.

The LibraryRenamer, MetadataUpdater, and PatchReformer tools can be downloaded from the links below (but please note these don't come with any instructions):


   
ReplyQuote
(@heyjosh)
Trusted Member
Joined: 3 years ago
Posts: 61
Topic starter  

@getdunne

Thank you, sir! I will make the adjustments for future releases. I do want to use VST3 for myself, is it really that much of a bummer for everyone else to have it as VST3? Does it not automatically grab the VST2 version if that is installed? Trying to avoid having to make 2 versions of everything.

Also, before I go breaking something, what exactly does the PatchReformer do? I follow what the other 2 apps do.

Thanks!


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

@heyhosh

Using VST3 is not a big deal at all.

Unify could (and I hope someday will) be better at handling multiple plug-in types. Right now, if both VST and VST3 versions of a given plug-in are both registered in Unify's known plug-ins list, you will always have to choose from a sub-menu with those two options every time you want to add an instance of the plug-in to a patch.

The PatchReformer utility takes one "reference" patch, and converts a number of input patches so they have the same structure ("form") as the reference patch, with only the patch metadata (name, author, etc.) and the instrument plug-in and state on the INST1 layer retained. For example, when creating a unified library, the usual first step is to create simplistic patches with just the INST1 layer and appropriate metadata. Once this is done, you might "dress up" just one patch with additional layers and macro assignments. You could then run the PatchReformer program, point it to that one "dressed up" patch as the reference, and process all the others so they all have that same form.


   
ReplyQuote
(@heyjosh)
Trusted Member
Joined: 3 years ago
Posts: 61
Topic starter  

@getdunne

Thank you for that explanation. I now have two more to upload, having Unified them, still as VST3, but with the library name done as you mentioned.


   
JeremyH reacted
ReplyQuote
(@despondo)
Trusted Member
Joined: 4 years ago
Posts: 46
 

@heyjosh

Thanks for doing the Arturia libraries! I, for one, try to use VST2 for now since I use Reason as my main DAW. It currently does not support VST3 (hopefully that will change soon), so I usually only install VST2 to save Hard Drive space. Thankfully, Unify allows me to host VST3 (and AU) inside of Reason, so adding the VST3 versions for some instruments is not too big of a deal.

@getdunne

Is there some way to batch convert patches to reference an alternate version of a plugin? Not sure what is involved to batch them to point to the VST2 vs the VST3. Not too big of a deal, but was curious.

http://www.soundcloud.com/despondo | https://despondo.bandcamp.com | https://xenomantra.bandcamp.com | https://nomadica.bandcamp.com | https://xenophase.bandcamp.com


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4432
 
Posted by: @despondo

Is there some way to batch convert patches to reference an alternate version of a plugin?

Unfortunately, there is no fully generic way. In some cases, I may be able to reverse-engineer a plug-in's patch-data format well enough that I can write custom code to do it. This only makes sense if the effort to convert is much less than the effort to rebuild and re-save all the patches manually.


   
ReplyQuote
(@despondo)
Trusted Member
Joined: 4 years ago
Posts: 46
 
Posted by: @getdunne
Posted by: @despondo

Is there some way to batch convert patches to reference an alternate version of a plugin?

Unfortunately, there is no fully generic way. In some cases, I may be able to reverse-engineer a plug-in's patch-data format well enough that I can write custom code to do it. This only makes sense if the effort to convert is much less than the effort to rebuild and re-save all the patches manually.

Understood. Hopefully you'll be able to solve the multiple plugin types option later. 🙂

http://www.soundcloud.com/despondo | https://despondo.bandcamp.com | https://xenomantra.bandcamp.com | https://nomadica.bandcamp.com | https://xenophase.bandcamp.com


   
ReplyQuote
Share: