Sylenth1 cannot be run on a virtual machine (fixed)

[eBlue]

I'm sorry but requiring users to disable features on their computer to run your software isn't 'copy protection', it's lazy programming that only impacts customers that have already PAID you money. It sounds to me like the programmer is simply too cheap to pay for industry-standard copy protection like iLok or eLicensor. Right now there are too many competitive and less intrusive synths out compared to Sylenth1 v3.

This was a bad and amateurish decision by whomever made it and should be corrected immediately. Otherwise, it appears that my support for LennarDigital has come to an end.

[garryknight]

This was a bad and amateurish decision by whomever made it and should be corrected immediately. Otherwise, it appears that my support for LennarDigital has come to an end.

I have a feeling that many other people who feel the same way will just silently vote with their feet.

[Nielzie]

This was a bad and amateurish decision by whomever made it and should be corrected immediately. Otherwise, it appears that my support for LennarDigital has come to an end.

I have a feeling that many other people who feel the same way will just silently vote with their feet.

Many (windows) users will probably be sticking with the good old v2 anyway, I guess.

[xx JPRacer xx]

^ No, because many Windows users won't have the extensions enable anyway, so no problem.

[Nielzie]

^ But also no c/r, just simple key file authorization

[chk071]

This was a bad and amateurish decision by whomever made it and should be corrected immediately. Otherwise, it appears that my support for LennarDigital has come to an end.

I have a feeling that many other people who feel the same way will just silently vote with their feet.

Many (windows) users will probably be sticking with the good old v2 anyway, I guess.

I have a doubt that there's many people using virtual machines on their DAW computers. Actually, i'd be surprised if it hits the 5% mark. IMO, it's rather the usual thing, by shouting loud, people try to make a point as if they were the vast majority. Don't get me wrong, perfectly fine stating that it's a problem for you, or asking why it has to be, but that's different to dramatic and theatrical departures as presented in this thread.

[Nielzie]

This was a bad and amateurish decision by whomever made it and should be corrected immediately. Otherwise, it appears that my support for LennarDigital has come to an end.

I have a feeling that many other people who feel the same way will just silently vote with their feet.

Many (windows) users will probably be sticking with the good old v2 anyway, I guess.

I have a doubt that there's many people using virtual machines on their DAW computers. Actually, i'd be surprised if it hits the 5% mark. IMO, it's rather the usual thing, by shouting loud, people try to make a point as if they were the vast majority. Don't get me wrong, perfectly fine stating that it's a problem for you, or asking why it has to be, but that's different to dramatic and theatrical departures as presented in this thread.

I just tried to explain that it's not the virtual machine issue but the fact that the copy protection changed from simple keyfile protection to online challenge/response that will probably withhold many to upgrade to the new version that only has updated to a resizable GUI anyway. I could be wrong but many seem to be more sensitive about the (change of) copy protection of plugins these days than turning off features on their machines to make a plugin work

[chk071]

Ah, nevermind then.

[Ciberithm]

I run both VMs and DAWs on one of my Windows computers, and also run DAW and VMs on my Macbook. Am I in the minority? Probably. Is that an excuse for writing bad code? Absolutely not. Not adding a feature to a product that will only be used by a minority is a business decision, but not fixing a bug because it only affects a minority is just bad business.

With that said, I am currently running the version 3 beta on my Windows box without any issues, although I am using Live and the OP is using Studio One. The VST does initialize VERY slowly, probably because of the copy protection. I don't have a problem with copy protection - I use iLok and eLicenser, as well as many apps with challenge response activation. But the protection code in Sylenth1 stinks in the beta version. I'm optimistic the code will be better if it ever make it to a production build.

EDIT:
I just checked Studio One 3 and it loads fine there as well, and without the long delay. I'm running VMware Workstation 12, the latest Windows 10 public build, and on a 4GHz i7 with 32GB ram.

[chk071]

I run both VMs and DAWs on one of my Windows computers, and also run DAW and VMs on my Macbook. Am I in the minority? Probably. Is that an excuse for writing bad code? Absolutely not. Not adding a feature to a product that will only be used by a minority is a business decision, but not fixing a bug because it only affects a minority is just bad business.

That's 2 claims there. "Bad code" and "a bug which isn't fixed". And clues why you believe that is the case? Probably the code does exactly what it's supposed to do.

Hmm but somehow Sylenth1 v3's C/R system has this problem where other systems do not seem to have it. Please take some time to investigate, might very well be worth the investment in the long run

This has nothing to do with the C/R system. It's also not a bug, it was done intentionally.

[Ciberithm]

I run both VMs and DAWs on one of my Windows computers, and also run DAW and VMs on my Macbook. Am I in the minority? Probably. Is that an excuse for writing bad code? Absolutely not. Not adding a feature to a product that will only be used by a minority is a business decision, but not fixing a bug because it only affects a minority is just bad business.

To be clear, I did not state that the Sylenth1 code is bad, CR or otherwise. But I stand by my statement that not fixing a bug because it only affects a minority of users is bad practice. The only issue I am having is the excessive load time, but that may be a Sylenth1/Ableton Live combination issue.

[xx JPRacer xx]

^ There's nothing to "fix" since it's not a bug but design that way.

[DavidEkl]

So this just bit me. It's been working fine for ages and today i get this errormessage when i'm quite far into a project. Currently flipping a coin on whether to downgrade Sylenth1 or try to get the new version working by disabling virtualization everywhere Sylenth1 could possibly find it. As i'm a software developer that's not something i'm too keen on doing.

I suppose a third option is to ditch it entirely.

[DreamlandFantasy]

I've just had the "Sylenth1 cannot be run on a virtual machine" message too (Windows 10 64-bit, using Renoise). Very frustrating when I was just about to work on some music.

Like others have said, turning off virtualisation is not an option (I can't even understand why this should be an issue), so here's hoping this "feature" is sorted out.

[DreamlandFantasy]

I've found a workaround to get Sylenth1 v3 working that does not require disabling virtualisation in the BIOS. I'm using Windows 10 here and this is what I done:

- Open the Windows control panel
- Go to Programs and Features
- Click 'Turn Windows features on or off'
- Look for 'Hyper-V' and uncheck it

Once done, just restart the computer and all going well Sylenth1 v3 will now work without complaining about not being able to run on a virtual machine.

Kind regards,

Francis