Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
new e-licenser
Last post Sun, Dec 13 2009 by inwinterhesleeps, 57 replies.
Options
Go to last post
3 Pages<123
Posted on Thu, Oct 22 2009 00:31
by ozmoz2008
Joined on Thu, Oct 22 2009, Posts 1
I have the same problem with GVI3. I see the license within my elicenser program, but when I load GVI in Cubase it says that it doesn't see the license. I never had that problem with my old Syncrosoft software.

This is really frustrating when paying for a program and you have these type of stupid problems cause by a new software that is supposed to be working better than the last one.

How can we repair this? Is there any ways?
Posted on Thu, Oct 22 2009 00:47
by florian
Joined on Thu, Feb 20 2003, Posts 48

Does anyone know how to easily create some kind of script to start both instances with a short delay? That's how I solved it for the Mac: An automator script starts the 32 bit instance and 4 seconds later the 64 bit instance.I put that script into the autostart, works! 

Posted on Wed, Oct 28 2009 23:04
by cm
Joined on Fri, Dec 20 2002, vienna, Posts 9137

a simple method (but not accepted by some antivirus software) - write a little vbs-script:

Option Explicit
Dim objShell
Set objShell=WScript.CreateObject("WScript.Shell")
wscript.sleep
36000 'time in ms
objShell.Run "C:\Programs\ect ...." 'full path to program as found in the shortcut of the start menu
Set objShell = Nothing

save as eg. VEPRO32delay36s.vbs and add a shortcut to the script into the autostart folder

 

hth, christian

and remember: a CRAY is the only computer that runs an endless loop in just four hours ...
Posted on Wed, Nov 11 2009 09:36
by Jann
Joined on Sat, Jan 18 2003, Posts 50

Will VSL keep the same licensing method from Steinberg for the coming year?

The reason for asking is because Korg have announced that they will be changing their software copy protection from the old syncrosoft method (USB key) to a challenge-response system, and an important reason in doing so is that Steinberg apparently will make some changes next year.

Comments from Korg support make it clear that replacing the licenses of stolen dongles was a very time consuming matter, and coupled with the bad customer support this was reason for Korg to make the move to take back control instead of relying on a third party like Steinberg.

Personally I have had abysmal experience with Yamaha customer support (which is why I no longer buy Yamaha products anymore), and since Yamaha is the owner of Steinberg (and Steinberg customer support also seems to follow Yamaha's example) Korg feared the worst for the future.

So, I was wondering about VSL.

Posted on Wed, Nov 11 2009 17:10
by Dietz
Joined on Tue, Aug 06 2002, Vienna / Europe, Posts 7973
Jann wrote:
[...] Personally I have had abysmal experience with Yamaha customer support (which is why I no longer buy Yamaha products anymore), and since Yamaha is the owner of Steinberg (and Steinberg customer support also seems to follow Yamaha's example) Korg feared the worst for the future. [...]

Sidenote: You know that Yamaha owned Korg for several years, and still holds shares?

-> http://en.wikipedia.org/w/wiki.phtml?title=Korg

/Dietz - Vienna Symphonic Library
Posted on Wed, Nov 11 2009 17:41
by Jann
Joined on Sat, Jan 18 2003, Posts 50

Yes, ownED (past tense, early nineties).

As to the current relationship between Korg and Yamaha I do not know the details, and I don't know how many shares Yamaha still owns (if any).

Judging from the comments made by Korg customer support concerning the software protection and the management decision to change it back from USB-dongle to challenge-response I can only deduce that it is clear that Yamaha has zero influence in Korg decisions

But this was not the point of my post.

My point was the apparently Korg felt it was very necessary to change back from USB-dongle to challenge-response based on experience PLUS the prospect of upcoming changes which will be implemented by Steinberg next year.

I thought that perhaps, if this was Korg's reaction -which is quite drastic-, VSL might also have second thoughts about the cooperation with Steinberg in matters of software protection?

Posted on Wed, Nov 11 2009 18:21
by DG
Joined on Wed, May 12 2004, Posts 8608

I would hate to have some sort of C/R type of copy protection. The last thing that I need is to have to jump through all those dratted hoops any time i want to use another system or change something in my setup. For example I recently gave a few seminars on film composing, and had to install stuff onto the laptop. Nuendo and VSL was dead easy, and took a matter of minutes. All the C/R stuff was an absolute nightmare, including emails to the developer having to explain why I needed another install.

Dongle all the way for me.

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Wed, Nov 11 2009 20:09
by cm
Joined on Fri, Dec 20 2002, vienna, Posts 9137

currently i don't see any reason making it necessary to change the licensing process.

agreeing to DG i can confirm it took me far more time contacting various support teams to de-authorize, re-authorize. re-install or actually even install applications on computers without internet connections at all than solving dongle issues.

 

take the key, plug it into another machine, install eLC and VE and go - where and when i want to do so.

need to re-install or upgrade your operating sytem? no problem at all.

add a slave computer (maybe we want to call it satellite) to your setup? re-distributing your licenses is a matter of minutes.

 

for software / applications there might be reasons for C/R (which i don't see currently remembering my last premiere installation), but for content it would be useless and more than confusing ...

christian

 

and remember: a CRAY is the only computer that runs an endless loop in just four hours ...
Posted on Thu, Nov 12 2009 08:19
by Jann
Joined on Sat, Jan 18 2003, Posts 50

Thanks for the reply.

In addition to Korg, Yellow Tools also have changed their policy with regard to protecting the software and now offers the option of elicenses (C/R) instead of their WIBU dongle. Since I never got the license manager for the WIBU dongle to work properly I can only applaude that decision.

The way I see it there are pros and cons both both methods.

One thing which worries me about dongles is that I have the equivalent of thousands of Euros on a little piece of electronica in a plastic capsule which can get lost quite easily. I understand from the comments made by a Korg representative that it can take quite some time to replace a lost/broken dongle with licenses, and when you're in the middle of a project the last thing you need is some administrative procedure paralyzing the workflow.

There also have been times that I simply forgot to take the dongle with me, leaving me the option of returning home to get the dongle or not use the software for the duration of my stay away from home.

Given a choice my preference is still for the C/R method.

But I also understand that from a developer's perspective a dongle may be more attractive since it's harder to crack.

Since I heard negative rumours about the upcoming changes with regard to the syncrosoft/steinberg dongle I thought that perhaps VSL would know more about it and perhaps as a result also reconsider the current protection method.

Posted on Thu, Nov 12 2009 09:21
by DG
Joined on Wed, May 12 2004, Posts 8608
Jann wrote:

One thing which worries me about dongles is that I have the equivalent of thousands of Euros on a little piece of electronica in a plastic capsule which can get lost quite easily. I understand from the comments made by a Korg representative that it can take quite some time to replace a lost/broken dongle with licenses, and when you're in the middle of a project the last thing you need is some administrative procedure paralyzing the workflow.

 

This is all perfectly true and is something that Steinberg really needs to be hounded about. There have been lots of hints about how it could work, but so far Steinberg has not delivered. At the very least they need to be able to issue temporary licences. FWIW you should get a spare dongle, so that if there are any problems, at least you could work with a temporary licence, should VSL be kind enough to issue one.

Jann wrote:

There also have been times that I simply forgot to take the dongle with me, leaving me the option of returning home to get the dongle or not use the software for the duration of my stay away from home.

 

Unfortunately no developer can be held responsible for user incompetence. Wink

Jann wrote:

But I also understand that from a developer's perspective a dongle may be more attractive since it's harder to crack.

 

 I think that all developers would agree with you. However, it also depends on which dongle we are talking about. for example an iLok "protected" product is likely to cracked within days of being issued. The other issues is that should you wish to sell your VSL licences (assuming that VSL allows you to do so) it is more likely to retain its perceived value if it is dongle protected software, thus protecting your investment (well, it's not really investment, but you get my point).

Jann wrote:

Since I heard negative rumours about the upcoming changes with regard to the syncrosoft/steinberg dongle I thought that perhaps VSL would know more about it and perhaps as a result also reconsider the current protection method.

 

These are just rumors. As no new system has been released yet, and therefore hasn't been tested by users, there is no point in having any opinion, negative or positive, on it. However, I do know that Cubendo users have been very vocal with Steinberg about their dongle policies, so like you, I am interested to see what they come up with,.

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Mon, Dec 07 2009 11:48
by inwinterhesleeps
Joined on Sat, Dec 03 2005, Posts 68

Having serious problems with the new elicenser (currently latest version). When I try to launch VEPro it says it can't find the key when it used to do it just fine. So I moved it and now it recognises it. BUT license scan loops forever and I have to force quit. I'm getting really tired of these problems with this hopeless copy protection. It should just damn well work with the amount of money people are paying for this software.

Tom

Posted on Mon, Dec 07 2009 12:22
by cm
Joined on Fri, Dec 20 2002, vienna, Posts 9137

the usual question and tip for OS X users: have you re-booted before updating the software and repaired permissions after?

also did you shut down / quit all related applications before downloading the license - which OS X version are you running btw?

christian

and remember: a CRAY is the only computer that runs an endless loop in just four hours ...
Posted on Sun, Dec 13 2009 05:35
by inwinterhesleeps
Joined on Sat, Dec 03 2005, Posts 68

Yes, I know about all that stuff. Been using Macs for a very long time. I don't often have trouble on my setup because I understand Macs quite well and am very careful about what I do on the computer. This is an elicenser problem and I should not have to deal with it. I'm running OSX 10.6.2 all other software is the latest versions. Key is plugged into the back of my Apple Display which should most certainly be a tested configuration.

The latest event is that the key no longer shows any of my activated libraries. Just a blank key. Unbelievable.

Tom

Posted on Sun, Dec 13 2009 14:06
by DG
Joined on Wed, May 12 2004, Posts 8608

inwinterhesleeps wrote:
Key is plugged into the back of my Apple Display which should most certainly be a tested configuration.

 

Why? Is VSL supposed to test every monitor that has a slot for a USB device? You don't seriously expect VSL to purchase every make of monitor on the market and test them all?

I certainly agree that there shouldn't be problems with a protection device, and if it doesn't work plugged into your computer, then it should be fixed. However, suggesting that they should get the same brand of monitor as you in order to test is stretching it a bit far  

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Sun, Dec 13 2009 14:39
by inwinterhesleeps
Joined on Sat, Dec 03 2005, Posts 68

DG why do you constantly come to the rescue of VSL when it is really not needed? If you have some solutions then by all means contribute (and sometimes you do this), but I see in a lot of your posts that you are trying to justify the status quo somehow and this is really not appropriate especially if is a problem on a platform you do not use.

I would actually expect a little bit of testing on VSL's behalf but I would expect even more testing from Steinberg to make sure the protection device they sell to companies like VSL actually works at least on a typical setup. To suggest that I want VSL to test every single monitor in existence is just plain silly and a little bit immature on your part. There are a lot of Mac users with Apple Displays out there. It is not unreasonable that such a setup should be included on the test-bench (especially for Steinberg).

Tom

Posted on Sun, Dec 13 2009 15:01
by DG
Joined on Wed, May 12 2004, Posts 8608
inwinterhesleeps wrote:

DG why do you constantly come to the rescue of VSL when it is really not needed? If you have some solutions then by all means contribute (and sometimes you do this), but I see in a lot of your posts that you are trying to justify the status quo somehow and this is really not appropriate especially if is a problem on a platform you do not use.

 

Of couse it's appripriate. You, and others are suggesting that a change of "protection" is needed when for the majoriyty of users, it isn't. Furthermore the proposed change to iLok may well be a disaster for Windows users, as it has been in the past, so of couse I'm entitled to give me views. If you only want to hear from people who agree with you, then don't post on the forum. Contact support provately.

inwinterhesleeps wrote:

I would actually expect a little bit of testing on VSL's behalf but I would expect even more testing from Steinberg to make sure the protection device they sell to companies like VSL actually works at least on a typical setup. To suggest that I want VSL to test every single monitor in existence is just plain silly and a little bit immature on your part. There are a lot of Mac users with Apple Displays out there. It is not unreasonable that such a setup should be included on the test-bench (especially for Steinberg).

Tom

 

It's just as unreasonable that I suggest that they should test using Dell monitors.

However, I would be interested to hear from someone who is using an Apple Display for them to test using Windows. That would confirm, or not, that it is a software problem, not a hardware one.

One last thought. Assuming that VSL and Steinberg tested, as you suggest, plugged into an Apple display, and found that it didn't work using OSX. The advice they would give would be not to plug it into the monitor. However, that's already the advice you've been given, and you didn't want to hear it. What else do you suggest they could do? If it doesn't work, it could be the fault of Syncrosoft/Steinberg or it could be the fault of Apple. What happens if it is Apple's fault? How can either Steinberg or VSL fix that?

DG

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Sun, Dec 13 2009 16:00
by inwinterhesleeps
Joined on Sat, Dec 03 2005, Posts 68
DG wrote:

Of couse it's appripriate. You, and others are suggesting that a change of "protection" is needed when for the majoriyty of users, it isn't. Furthermore the proposed change to iLok may well be a disaster for Windows users, as it has been in the past, so of couse I'm entitled to give me views. If you only want to hear from people who agree with you, then don't post on the forum. Contact support provately.

Again with the childishness. I am posting on a forum to highlight a problem and to possibly help others. Obviously the reason you are so opposed to this "highlighting" is that you fear things might change and since things are working well for you on PC that must not happen. So you have an agenda and therefore suggest that it is unreasonable for VSL and Steinberg to test the copy protection device on what is most likely a very common setup.

I'm sure you wouldn't be playing the "works for most people" card if this problem affected you and that's why I find your defensive comments inappropriate. 

DG wrote:

It's just as unreasonable that I suggest that they should test using Dell monitors.

However, I would be interested to hear from someone who is using an Apple Display for them to test using Windows. That would confirm, or not, that it is a software problem, not a hardware one.


On the PC side you have a totally unmanageable number of hardware permutations so, indeed, I would not suggest testing a Dell monitor because that would be arbitrary. With Apple there is a case for testing with an all Apple hardware setup to, at the very least, ensure compatibility with what one could call a standard system setup.


I have managed to get the key to work again after a lot of stuffing around. It was working for a long time with no problems plugged into a generic USB hub. That's the reason I assumed it should work plugged into the back of the Apple Display. Recently something was done with the elicenser software that has stopped the key from working on USB hubs altogether it would seem. This is an elicenser software problem and should have been detected during the testing phase. 

DG wrote:

One last thought. Assuming that VSL and Steinberg tested, as you suggest, plugged into an Apple display, and found that it didn't work using OSX. The advice they would give would be not to plug it into the monitor. However, that's already the advice you've been given, and you didn't want to hear it. What else do you suggest they could do? If it doesn't work, it could be the fault of Syncrosoft/Steinberg or it could be the fault of Apple. What happens if it is Apple's fault? How can either Steinberg or VSL fix that?

DG

I find your tone slightly offensive, and your arguments unhelpful. As much as you would like to blame Apple, this is clearly an elicenser software problem.

3 Pages<123
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.