Notifications
Clear all

Pharlight Unified

5 Posts
3 Users
5 Reactions
696 Views
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
Topic starter  

With John and Shane for review.


   
getdunne reacted
Quote
(@despondo)
Trusted Member
Joined: 4 years ago
Posts: 46

   
JeremyH reacted
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
Topic starter  

@despondo I think John is focussing on finalising my Unified U-He libraries at the moment (I have now completed all the factory patches for Diva, Repro1 & 5, Bazille, Zebra, Dark Zebra and Hive 2).

So if you would like Unified Pharlight "as is" I could post a link in the other thread. It's one of the larger Kontakt Play Series libraries at 375 patches although I haven't yet figured out why some Unified libraries patches take up much more space than others. For example, Pharlight Unified (375 patches) is 153Mb whereas Repro 1 Unified (501 patches) is 11Mb and Hive 2 Unified (2,321 patches) is 70Mb. Maybe there is more metadata stored for some libraries than others.


   
Maranada and Despondo reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4435
 

@zinct

Unify's patches are logically similar to a DAW's project-files. Each plug-in is asked for its current state, and it returns a binary blob which gets saved with the patch. The size of the state-blob varies enormously from one plug-in to another, and is up to the plug-in developer; we have no control over it.


   
JeremyH reacted
ReplyQuote
JeremyH
(@zinct)
Member
Joined: 4 years ago
Posts: 514
Topic starter  
Posted by: @getdunne

@zinct

Unify's patches are logically similar to a DAW's project-files. Each plug-in is asked for its current state, and it returns a binary blob which gets saved with the patch. The size of the state-blob varies enormously from one plug-in to another, and is up to the plug-in developer; we have no control over it.

@getdunne Thanks for clarifying Shane.


   
ReplyQuote
Share: