For anyone who is interested or is maybe considering Unifying AL V themselves; I got to around half way (3,600 patches) and then realised that the Unified patches weighed in at over 1Gb!!!
So I estimate that the full thing (7,455 patches) would have been over 2Gb. I consider that a bit too much and I wonder whether it would cause some issues with copyright (like the Omnisphere libraries) due to the amount of patch detail that is being saved. Also, with so many top notch synth alternatives available (e.g. U-He) and their Unified disk space requirements being minimal I decided to abandon Unifying AL V.
I did discuss this with Arturia Support. Analog Lab V ist Not interesting to ne unless the Sounds are very good. I have the light Version 4 and they do not offer an Update to 4 and V they have me for testing 6 months for free i just not use. Its not unified and i do not see support of Arturia.
The only thing ist that they did promised that they do a Interface for visual handicaps people like me. The GUI they use in V is from usability quality gar away.
I asked their support for a list of patches in a format that I could use to automate the Unification process a bit more easily but they were not able to help. Anyway, I was able to work out a way to do it but it was still quite labour intensive.
There are some good sounding patches but quite a lot of meh ones as well. With Unify plus some of the other high end synths e.g. Omnisphere, U-He, Synapse etc you probably have all you need.
It's good that they promised a better visual interface and I hope that they deliver on that promise for you.
I estimate that the full thing (7,455 patches) would have been over 2Gb. I consider that a bit too much...
There are some good sounding patches but quite a lot of meh ones as well.
Perhaps what's needed is a "unified, best of" library rather than a full "unified, factory" library?
It's defensible, because
- the full unified factory library would be impractically large
- everyone who owns Analog Lab V has access to all patches already anyway, and
- everyone is free to add any missing patches they choose to the library.
Your thoughts?
I estimate that the full thing (7,455 patches) would have been over 2Gb. I consider that a bit too much...
There are some good sounding patches but quite a lot of meh ones as well.
Perhaps what's needed is a "unified, best of" library rather than a full "unified, factory" library?
It's defensible, because
- the full unified factory library would be impractically large
- everyone who owns Analog Lab V has access to all patches already anyway, and
- everyone is free to add any missing patches they choose to the library.
Your thoughts?
Yes, that would be a good idea. It might take a fair bit of time though as it would be a manual process.
There are two banks, one called Factory with 7,455 patches and another called Analog Lab Factory (with the new AL V logo) containing 2,397 patches. Perhaps the latter bank, or a subset of it, would be a good starting point.
@getdunne Since Analog Lab V is dual layer capable, may I suggest those with that product create new patches utilizing this capability as opposed to just Unifying the already existing single layer presets...once done, they could be shared...it could also be ongoing as more people participate.
@getdunne Since Analog Lab V is dual layer capable, may I suggest those with that product create new patches utilizing this capability as opposed to just Unifying the already existing single layer presets...once done, they could be shared...it could also be ongoing as more people participate.
It's not up to me to decide this, so you don't need to tag me explicitly, but I can give some general advice.
Creating multiple layers within a multi-layer-capable third-party plug-in like Analog Lab or Omnisphere 2 is perfectly fine, but has two drawbacks in the context of Unify:
- Unless the plug-in is multi-threaded (and to the best of my knowledge, Analog Lab is not), the same CPU core will be used for all layers. Creating separate layers in Unify may thus be more efficient.
- If you make a single multi-layer patch inside a third-party plug-in, and then a single Unify patch which loads it, it won't be as easy to load the two layers individually. You will have to open the third-party plug-in and remove the layer you don't want, as opposed to just option/alt-clicking one Unify layer.
do have a link for this please
For anyone who is interested or is maybe considering Unifying AL V themselves; I got to around half way (3,600 patches) and then realised that the Unified patches weighed in at over 1Gb!!!
So I estimate that the full thing (7,455 patches) would have been over 2Gb. I consider that a bit too much and I wonder whether it would cause some issues with copyright (like the Omnisphere libraries) due to the amount of patch detail that is being saved. Also, with so many top notch synth alternatives available (e.g. U-He) and their Unified disk space requirements being minimal I decided to abandon Unifying AL V.
can you share this unify