Hise.Activate

[Lindon]

OK so....

We have a player - that will be free - so not using any Authenticate services, but.....

We want to have Full Instrument expansions load into this player that do require HISE.activate...

So questions....

Can I use these services in that way?
Does the Full Instrument expansion contains the required HISE.activate code?
Can it save more than one authorisation file in the players AppData folder?
Will the Full Instrument Expansion even find it when it loads?

[Christoph Hart]

@Lindon that‘s actually a feature that I‘m currently developing - you have a single license that is tied to a user and the activation server stores a list of registered expansions and only allows to load the ones which are registered to the users machine.

[Lindon]

@Christoph-Hart Great!, of course the customer want to know when that will be available? Even roughly....

[Christoph Hart]

@Lindon It's already in the C++ code and the activate server backend also supports expansions as product addition, but we haven't used it in a real project yet, so you can expect it to be a bit rough around the edges.

I would point to the completely rewritten docs that explain this all, but then you'll complain that the 127.0.0.1 link doesn't work...

[Lindon]

@Christoph-Hart lol - thanks.

Whilst we are here, can I ask for a feature(if its not included). My customer plans on having several Collection/Library releases, so collections of "instruments"(Full Instrument Expansions here) and would like their end-customers to be able to activate all the instruments in a Library by activating the library just once.

[Christoph Hart]

@Lindon the idea is that the user doesn‘t activate any expansions - he just fetches an encoded list of registered expansions from the activation server but I haven‘t figured out a way of how the server gets that information as this would involve cross server communication which I deferred until there‘s an actual use case

[Christoph Hart]

Actually nevermind just looked again you can unlock each expansion with a serial key. It‘s currently once per expansion but either you can add a input field where you can paste multiple serials for each expansion or we add a meta serial system that unlocks multiple expansions at once.

[Lindon]

@Christoph-Hart OK well the use case is a free "player" and users can then buy(and activate) either a Library of Full Instrument Expansions, or single Full Instrument Expansion.

So they will offer Libraries of Instruments and Single instruments, and they'd like to activate either the library (so once for all instruments in the library) or the single instrument.

So users can buy the entire library, or if they dont want all instruments in a library, they may decide to buy a single instrument

[Lindon]

@Christoph-Hart said in Hise.Activate:

Actually nevermind just looked again you can unlock each expansion with a serial key. It‘s currently once per expansion but either you can add a input field where you can paste multiple serials for each expansion or we add a meta serial system that unlocks multiple expansions at once.

Ok my customer and I are voting for the meta serial please.
I suggest this might (best) work by activating one item in a library activates them all.

[dannytaurus]

@Lindon I'm following your posts about this because I'm thinking of implementing something similar.

I thought one of your early requests was that a user can load content from multiple expansions at once, and that's not possible with Full Expansions, right? Or have I misunderstood?

[Lindon]

@dannytaurus said in Hise.Activate:

@Lindon I'm following your posts about this because I'm thinking of implementing something similar.

I thought one of your early requests was that a user can load content from multiple expansions at once, and that's not possible with Full Expansions, right? Or have I misunderstood?

you are correct you cannot load content from multiple Full Instrument expansions at once.

[dannytaurus]

@Lindon So have you (or stakeholders) abandoned this requirement? Or was it just curiosity?

[Lindon]

@dannytaurus we have modified the requirement.