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! 

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

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.

@Jann said:

[...] 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?

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

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?

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

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

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.

@Another User said:

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

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

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

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

@inwinterhesleeps said:

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

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

@Another User said:

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

@Another User said:

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.