[Sticky] OFFICIAL: ALL Unified Libraries (w/Links!!)

Is there actually a difference between "Native Instruments Noire - Kontakt 6" and "Native Instruments Noire (2 Libraries :Felt and Pure) Sample Library (Kontkat 6)"? The dropbox locations and file names are the same.

Also, the "Arturia Pigments V3 with 200 V3 Patches" readme file says nothing about the 200 V3 Patches. Won't Pigments V3 be required to use this library?

Terry

@terrybritton - Thanks for pointing out the discrepancies - I'll remove one of the Noire links and since the name says Pigments V3 in the file name and says you must own the plug-in for the library to work that people will know that. The ReadMe is really just basic information that is CC'd into each of these libraries I've assembled.

@pluginguruforums 

According to your mail today about the livestream, MM PADS for Kontakt is Unified and should be downloadable. This is how it looks:

I downloaded it, but no .guru file available.

@zzz00m - I requested permission to officially release a Unified Vital library and was asked to not do so. So we won't be releasing it as a Unified library at this time but you can still save out your favorite patches as Unify Patches for your own personal use.

@thsve - You probably purchased one of the bundles I have not gotten to updating the link! Please try again on Monday and I will hopefully have the links to all the bundles updated!

@pluginguruforums 

John, I have updated the Dune 3 Unified Factory Library to include the 40 new factory patches in v3.5.

Here's the link https://www.dropbox.com/s/j2gnfsd6zttiw3w/Unified%20-%20SA%20Dune%203.guru?dl=0  

These are the 40 new patches:

https://www.synapse-audio.com/dune/dune35new.txt

Cheers!

I have also Unified the Pigments 3.5 updates. Message me if anyone wants it.

Posted by: @zinct

I have also Unified the Pigments 3.5 updates. Message me if anyone wants it.

I would be interested, but cannot for the life of me find how to message you via this forum or your profile.

Terry

@terrybritton

Actually, I don't think you can on here.

Anyway, I have had a rethink about this...

Version 2 of Pigments was the first version that was Unified and had 1000 factory presets. In Unify this was named "Unified - Pigments". This doesn't seem to be on the PG website.

Version 3 included another 200 factory presets and I made these a separate library called "Unified - Pigments 3" for ease and to keep the size down (Arturia unified libraries seem to take up quite a bit of space). This is what is on the PG website under Unified libraries. 

Version 3.5 adds another 150 factory presets and I have unified these under the library name "Unified - Pigments 3" so that they can be merged with version 3 above.

However, on reflection I think it might be less confusing to make a new Unified library called "Unified - Pigments 35" which has all 1350 factory presets in it. This is easy to do and would only take a few minutes. End users would just delete any Unified Pigments folder they have in their Unify/Libraries folder and drag/drop the new guru file onto Unify to have a single Unified library with all 1350 presets.

Thoughts?

@zinct Yes is my thought!! Simple as that buddy 🙂

@zinct Absolutely a fantastic idea! 🙂

Terry

@terrybritton  @djtobes  @getdunne

As a precaution, I'm just checking with Shane/John that it's ok to post this as I'm not sure why the original Pigments Unified library was removed. 

@zinct The link was there a few hours ago, but seems to have been removed?

EDIT: Oh, now I see the note. I'll wait! 

@zinct like to have the like to the pigment 3.5 unify.

Chaps, please bear with me.

I am awaiting a reply from John but I imagine his focus today will be on MM Keys and Unify v1.7. 

@zinct ME2 like to have them.. Are they VST3? the current patches don't work for me? i use only the VST3

@hammer

The Unified Pigments patches are for the Pigments VST. We prefer VST2 over VST3, when available, because VST2 patch data tend to be smaller, and more compatible cross-platform (Mac/Windows).

@getdunne Ahhh allright that clarifies. thanks for answering 

My Unifying "beta tester" has pointed out some differences between the first set of Unified Factory Pigments patches and subsequent ones which became apparent after merging them all together. So I am going to rework all of them to be more standardised. 

Ok the reworked Unified Pigment 3.5 Factory Library is ready (thanks @zzz00m for testing it and providing feedback).

@getdunne  If you don't have any objection I could just post a link here and John can decide at leisure whether he wants to put it on the official list or not?

Incidentally, I took advantage of the recent deal on V Collection 8 upgrade, so I am planning on continuing the work started by @heyjosh in Unifying each of those synths. 

@zinct It should be OK to just post a link directly here, since these are factory presets.

Thanks Shane @getdunne

Ok, here's the new version with standardised patches; all 1350 Factory patches now have Pump House (macro knob on 2nd page), AUX effects layer and macro knobs as per the first Unified version.

The only thing that should be different now is that the comments field is not populated from the factory patches for Pigments v2, 3 and 3.5.

Drag and Drop the guru file onto the Unify UI and it will create a new Unified library called "Unified - Pigments 35". You can remove any previous Unified versions as this now contains all of the factory patches up to and including v3.5.

UPDATE: Now available with MPE enabled on all presets - see updated link in the message below.

Now I am beyond the factory as I have bought a lot of extra Arturia preset packs for Pigments and also Vintage Synth Pads presets and Luftrum and ...  Pigments 3.5 is quite a synth with huge variety.
I recommend VintageSynthPads.com and Luftrum.com as a couple places to get a lot of great synth presets for lots of synths
Oh yeah, I have all the PluginGuru stuff for Omnisphere and Unify and ...
Geosynths.com is also good.

Posted by: @mrfuzztone

Now I am beyond the factory as I have bought a lot of extra Arturia preset packs for Pigments and also Vintage Synth Pads presets and Luftrum and ... 

These are perfect examples of paid add-on packs which should not be re-distributed in unified form (as I'm certain everyone understands now).

HOWEVER, if you do happen to create unified versions of such add-on sound packs, please do offer them to the original vendor, and suggest they might want to include them with the sound packs, as we now do for PlugInGuru packs. Most will say no, but the more times they see it, the more they may eventually consider saying yes!

I note that GForce have put up a load more patches for Imposcar, which I have now installed - I guess that means the .guru file needs an update by some keen person!  There are 5 sets, each containing 20-40 patches, by my estimate.

Is there an easy way to change all unified Pigments 3(.5) presets to have MPE enabled? I checked both the 3 and 3.5 libraries, and MPE is disabled on all. I would like it to be enabled by default, but don't feel like having to do that for all presets manually.

Posted by: @crazyray54

Is there an easy way to change all unified Pigments 3(.5) presets to have MPE enabled? I checked both the 3 and 3.5 libraries, and MPE is disabled on all. I would like it to be enabled by default, but don't feel like having to do that for all presets manually.

Unfortunately there is no "easy way" to do this automatically.

@zinct This sounds like something that could be done with AutoHotKey. Can you help?

@getdunne @crazyray54

I'm currently doing some beta testing which is taking up quite a bit of my time. However, when I get some spare time I'll rerun the AHK script.

On the MPE settings tab what should all of those options be set to? 

@zinct that would be awesome! The default settings are fine, as Pigments follows the MPE standard:

• MPE Enabled
• Zone: Lower
• No. Channels: 15
• Bend Range: 48 semitones
• Slide Mode: Absolute
• Slide CC: 74

So you only have to Enable MPE.

You might also want to check the naming convention for inconsistencies:

• BPM KEY, not BPM KEYS
• BPM STR, not BPM STRINGS
• KEY, not KEYS
• STR, not STRING or STRINGS

Once again, thanks so much for doing this. It is really wonderful.

Here is a simple AHK script that will process the UNIFY patches, set MPE to "Enabled" and resave the patch. Tested with Pigments demo since I don't own it. The demo doesn't allow save so I can't run it myself. If you know AHK, you know how to manipulate it and run it.

Thanks Thomas! @thsve

That should save me some time.

@zinct 

Hi Jeremy. You know what you have to change for your environment. Beware that mouse positions are relative to active window. If you want it relative to screen, change ”CoordMode”. Saw that it is many patches, so it will take a while to run😀.

@thsve

Thanks Thomas. I had a quick play and spotted the coord mode change! Once I have it working reliably on my system, I will probably leave it running overnight. Otherwise it makes the PC unusable for anything else in the daytime 🙂

UPDATE: The script is now working.  I have retained some of the longer delays to avoid any problems while unattended so I estimate it will take approx 3.5 hours to run.  

@crazyray54

I will run the script tonight. If it is successful I will post the updated library tomorrow. The process won't correct those naming inconsistencies which I will see if I can do manually tomorrow with Thomas's editor (ditto for the original Unified library). The Library will be called "Unified - Pigments 35 MPE" to distinguish between it and the non MPE version. 

@crazyray54 @getdunne

I attach the updated guru for Pigments 3.5 Factory patches with MPE enabled on all of them. I have also corrected the naming inconsistencies mentioned above.

Drag and drop it to the Unify UI and it will create a Unify library called "Unified - Pigments 35 MPE".

I suggest that people use this instead of the other Unified Pigments 35 library as the MPE enabled version seems to operate the same even if you don't have any MPE hardware. I have linked to this message from the one above.

Enjoy!

https://www.dropbox.com/s/ada9v1070mcwxh4/Unified%20-%20Pigments%2035%20MPE.guru?dl=0  

@zinct you are amazing! It works like a charm. I don't think there are any disadvantages of having MPE enabled, so I agree this is the one for people to use.

May I ask why you added AUX and master FX?

Posted by: @crazyray54

@zinct you are amazing! It works like a charm. I don't think there are any disadvantages of having MPE enabled, so I agree this is the one for people to use.

 

May I ask why you added AUX and master FX?

I didn't add these, they were in the original Pigments 35 Unified library and also in the earlier versions. 

If you mean why are these included in Unified libraries in general:

AUX FX - allows you to dial in effects on the AUX1 layer using the rotary 1 control on the instrument track.

Master FX - allow you to apply mastering effects such as EQ, compression and limiting.  

Note that if you add multiple patches to a Unify preset it is smart enough to only include one AUX1 and Master Effects layer. 

Do you guys actually use Pigments in this way? It is so slow to load. For instance Surge loads fine because it has a much smaller footprint. It would be nice if plugins could be cached.

BTW, maybe we should open a separate thread for Pigments, rather than spamming this thread. Would it even be possible for a mod to move the messages? I believe protocol dictates a thread for every plugin.

Posted by: @crazyray54

Do you guys actually use Pigments in this way? It is so slow to load. For instance Surge loads fine because it has a much smaller footprint. It would be nice if plugins could be cached.

Plug-in caching was added in Unify v1.3. See https://pluginguru.net/unify/manual/doku.php?id=layer-reuse. Here is my ReuseAcceptRules.xml file, for example; it included Pigments:

<?xml version="1.0" encoding="UTF-8"?>

<PluginRules>
  <PluginRule vendor="Spectrasonics"/>
  <PluginRule vendor="Native Instruments%" name="Massive"/>
  <PluginRule vendor="Native Instruments%" name="Reaktor"/>
  <PluginRule vendor="Rhizomatic" name="Plasmonic"/>
  <PluginRule vendor="Decidedly" descName="DecentSampler"/>
  <PluginRule vendor="Arturia" descName="Pigments"/>
</PluginRules>

Not all plug-ins work correctly when instances are reused this way. This is why we consider the technique still experimental, and let you set it up yourself using configuration files.

BTW, maybe we should open a separate thread for Pigments, rather than spamming this thread. Would it even be possible for a mod to move the messages?

Moving messages is possible, but it's more trouble than it's worth, and people can get upset if things do not remain where they left them. I recommend you do this yourself, by making a new thread and posting in it, then use the "link" button at the top right of your post to get a URL for it, and put this in a new (final) comment on the original thread.

Posted by: @getdunne

Posted by: @crazyray54

Do you guys actually use Pigments in this way? It is so slow to load. For instance Surge loads fine because it has a much smaller footprint. It would be nice if plugins could be cached.

Plug-in caching was added in Unify v1.3. See https://pluginguru.net/unify/manual/doku.php?id=layer-reuse. Here is my ReuseAcceptRules.xml file, for example; it included Pigments:

Not all plug-ins work correctly when instances are reused this way. This is why we consider the technique still experimental, and let you set it up yourself using configuration files.

That is awesome! I did not know it was already implemented. It was easy to follow the steps and it works like acharm---Pigments now loads much faster.

BTW, maybe we should open a separate thread for Pigments, rather than spamming this thread. Would it even be possible for a mod to move the messages?

Moving messages is possible, but it's more trouble than it's worth, and people can get upset if things do not remain where they left them. I recommend you do this yourself, by making a new thread and posting in it, then use the "link" button at the top right of your post to get a URL for it, and put this in a new (final) comment on the original thread.

I hear you. If I have more Pigments-specific requests I will make a new topic.

Posted by: @zzz00m

Spitfire Audio Labs (unified) appears to have been deleted. Link is dead.

Link above is fixed now.

Posted by: @getdunne

Posted by: @zzz00m

Spitfire Audio Labs (unified) appears to have been deleted. Link is dead.

Link above is fixed now.

Actually link has been updated as of 1/31 with a new updated LABS that includes Philip Glass's Acoustic Piano. It's appears to be only 2 velocity levels of samples but still plays okay (not great for me). I made 4 bonus patches that expand on the LABS patches by incorporating some of the samples / patches included with Unify's Factory library.

😀

Keen to get into all of this! Just a heads-up, I found a few broken links/deleted Dropbox folders: those for Surge, LABS, and Pendulate. LABS I was able to get to from the Philip Glass update post.

Cheers

Hi.    

I'm using a Linnstrument and the 'Arturia Pigments 3.5 MPE Enabled.guru' is currently MPE incompatible because the setting of the Pigments patches for Pitch Bend Range is 48 semitones whereas the maximum setting on the Linnstrument is +/- 24 semitones.  Upon reading, this may seem correctly matched, but it is not.

In general, there seems to be some confusion in the industry around PB Range labeling, and sometimes what works correctly is when the sender and the receiver are seemingly "off by a factor of 2".

In this case, however, my Linnstrument (actual testing here) is maxed out at +/- 24, when driving this Unify library the PB results are not correct and the only changes available on the Linnstrument (downward to +/- 12, etc.) make the situation even worse.

So, the only adjustment that will fix this situation is on the patches side, to reduce the setting from PB Range setting in Pigments from 48 semitones to 24 semitones.   I have confirmed this in fact (using a single patch).   Obviously, hand-editing 1350 patches is not-to-be-desired.

Is there a bulk editing capability that would allow the library to be re-made with this corrected setting?

I would *really* love to have all those Pigments patches in Unify, MPE correct (for the Linnstrument) and ready-to-go!

@sj1

I've moved your post to a new topic here https://forums.pluginguru.com/postid/14019/