194,063 users have contributed to 42,909 threads and 257,908 posts.
In the past 24 hours, we have 4 new thread(s), 19 new post(s) and 92 new user(s).
I think we can assume the transition to iLok will take place sometime after iLok is running native on Apple Silicon. I'm keeping an eye out for PACE to announce M1 compatibility before I begin clamoring in earnest for eLicensor-to-iLok timeline info.
The transition to iLok will happen first.
I think we can assume the transition to iLok will take place sometime after iLok is running native on Apple Silicon. I'm keeping an eye out for PACE to announce M1 compatibility before I begin clamoring in earnest for eLicensor-to-iLok timeline info.
The transition to iLok will happen first.
Good to hear. What would be good to hear is this: I know a lot of people have asked about a date for when the iLok transfer will happen and it's been said we'll be told about it here and via email but no date has been given. Not asking for an exact date but can you at least tell us if it will happen this year?Good to hear and thanks.Hi,
It will happen this year!
Best,
Paul
Hi,
It will happen this year!
Best,
Paul
Hi Paul,
Is there any possibility you will allow machine activation or is VSL firmly decided on cloud or key only?
God Bless,
David
Hi,
It will happen this year!
Best,
Paul
Hi, Paul,
Can you give us a more precise timeframe? Perhaps 1st quarter, or 2nd?
Cordially,
Tunai
Count yourself lucky we at least got a sometime this year acknowledgement. If I had to take a further guess I'd say second half of the year.Count yourself lucky we at least got a sometime this year acknowledgement. If I had to take a further guess I'd say second half of the year.
Let me poke the man unabashedly, my friend, lest he sees through the ruse.
Poke Ben and Paul too much and they'll just tune us out and you don't want that to happen. Like I said we're lucky we got a ball park response; they could have just blown us off and used the old 'it'll be out when it's ready' and left things just as murky as before.Poke Ben and Paul too much and they'll just tune us out and you don't want that to happen. Like I said we're lucky we got a ball park response; they could have just blown us off and used the old 'it'll be out when it's ready' and left things just as murky as before.
And you are certain of all that because?
In any case, Paul or Ben won't "blown us off", that is not how VSL behaves. I'm certain we should get at least a courteous response, which is not worse than 'it'll be out when it's ready' which is the current deadline.
As customers, we shouldn't be afraid of asking information about changes that affect the products we own.
Hi everybody,
We cannot give you an exact date.
As soon as software is involved, unexpected things happen all the time. Especially in those final steps.
We don't want to upset or disappoint you by promising something we cannot deliver in time, so we don't make promises. Instead we take the time that's necessary to provide you with what you can rightfully expect: A comfortable transition process from eLicenser to iLok.
Thanks for your understanding.
Best,
Paul
We don't want to upset or disappoint you by promising something we cannot deliver in time, so we don't make promises. Instead we take the time that's necessary to provide you with what you can rightfully expect: A comfortable transition process from eLicenser to iLok.
Thank you for taking your time on this. It would be a huge mistake to rush such an important thing so - for what it's worth - I'm very, very glad the company is not (rushing). Imo, this transition is the correct move for many reasons and it's very important that it go off without a hitch (or as few hitches as possible).
- Sam
I am not looking to be critical, but both e-licenser and iLok have been around a very long time, so I am surprised that transitioning from using one copy protection scheme to the other is such a big deal. But admittedly, I have no real knowledge as to what is involved.
Although someone earlier in this thread said otherwise, it seems logical to me that VSL would wait for iLok to be M1 native, which is yet to happen, before transitioning.I am not looking to be critical, but both e-licenser and iLok have been around a very long time, so I am surprised that transitioning from using one copy protection scheme to the other is such a big deal. But admittedly, I have no real knowledge as to what is involved.
I am not looking to be critical, but both e-licenser and iLok have been around a very long time, so I am surprised that transitioning from using one copy protection scheme to the other is such a big deal. But admittedly, I have no real knowledge as to what is involved.Although someone earlier in this thread said otherwise, it seems logical to me that VSL would wait for iLok to be M1 native, which is yet to happen, before transitioning. But it works with Rosetta 2.
Although someone earlier in this thread said otherwise, it seems logical to me that VSL would wait for iLok to be M1 native, which is yet to happen, before transitioning.
Although someone earlier in this thread said otherwise, it seems logical to me that VSL would wait for iLok to be M1 native, which is yet to happen, before transitioning.
I am not looking to be critical, but both e-licenser and iLok have been around a very long time, so I am surprised that transitioning from using one copy protection scheme to the other is such a big deal. But admittedly, I have no real knowledge as to what is involved.
Good idea, but why don't you spend the time getting the e-licenser server working again so we can use new sample sets purchased?
It's not been working today, and you don't mention this on your website - which I reckon is a pretty poor show really.
