iLok 2, VCC, and PT 9.0.6 not playing well together...

[E.rOk.stA]

I've been wanting to try Slate's VCC since March of last year but like with any new software, I figured I would wait 6-9 months for the bugs to be worked out.

I decided to download the demo, even though I had to drop $50 to get the iLok 2. I figured I would need it eventually for PT 10 when I upgrade that.

The download went well, i updated to the latest Pace drivers and got everything squared away on my iLok account.

I pulled up a session with 70+ tracks and 5-6 busses. I wanted to work this thing out! I got the plugin on every track and learned how to group them. I was excited by what I was hearing, although I wasn't able to really dig in 'cause it was Christmas. I had family obligations.

The next day, I was off of work. I figured I would try and print a mix and hear what happened. While demo'ing this plugin, I decided to update PT 9.0.5 to 9.0.6 as well.

All was fine and good as I played with the different consoles, A/Bing my results. I ran out of time so saved everything and closed out the session. Little did I know this was the last time it would work.

A few days later, I pulled it up again. As PT loaded the session, a screen appeared. My SSL Duende plugins weren't authorizing. I clicked on the codemeter icon, normally blue but now red on my taskbar. It opened a window and I clicked repair license. It did then turned blue. Sweet.

I closed the session and again loaded it back up. Now, as it was loading, every track that had VCC on it was triggering an "ilok not found" window! What?! I reached around the back of my computer, unplugged and replugged the ilok into another USB port. Every once in a while, I would have to do this if my computer locked up (very rarely).

Ever since then, Pro Tools will not recognize the ilok2. It recognizes my original ilok with all 43 licenses no problem.

I emailed support for ilok, they told me to contact the software developer. Now mind you, my computer recognizes the ilok2 as does my ilok account. The ilok2 is lighting up as well so I don't think it's broke.

I emailed Slate and after a couple weeks and 8 emails later, recieved a new demo license but it required a surrender of the old demo. I tried that and the ilok account gave me a message saying that there was no license to surrender, even though I could see it on the ilok!

I contacted Slate again and this time recieved a new 30 day demo that doesn't require any surrender. I activated it.

Pro Tools will not recognize it or the ilok2 for that matter. I've tried everything. I uninstalled and reinstalled the drivers. I'm at my wit's end. I just don't know what to do. Can anyone shed some light on this situation for me? One other question, when I unplug the ilok and plug it into a new USB port, should it automatically install a driver 'cause mine doesn't?

Thanks.

[popmann]

Did it get unplugged from the network? Known issue with only ilok2...if Win7 puts your NIC to sleep on disconnect (OS default) it will stop recognizing. It needs a MAC address active on the system.

[bentley]

Just a hunch... the iLok driver somehow rolled back to a previous version when you repaired it. VCC requires the most recent iLok driver or you'll get that error. Is this on a PC or Mac?

[Synth Buddha]

ILok2 is the reason I did not get the VCC and made the decision to go for something else instead. I already have the first iLok, and it's caused me enough grief to not ever want to support the clowns at Pace again in any way whatsoever. Secondly, I hear that the iLok2 in terms of technical problems is even worse. So I wasn't going to take a piss all over myself by signing up for even more misery and paying for it at the same time.

It really pissed me off, because I loved the VCC when I heard it in action. I'm not going to blame Slate for using a copy protection scheme (that blame goes to all the ******s that keep stealing software), but I am disappointed that he chose to go with the iLok2 exclusively. I'd buy the software today if that wasn't the case (and I came within a minute of doing so, only pulling out when I figured I should stop to check if I could use the iLok I already have).

And I'm still pretty pissed off about this (as I'm sure you can tell ), but I do have principles. I'm not supporting PACE again with so much as a ****ing cent - and I don't care if someone gives me the iLok2 - I don't want it. I can still make music without products that need the iLok2, and that's how it's going to be.

Anyway... Sorry for the rant - I hope you get your problems sorted, E.rOk.stA.

[E.rOk.stA]

Originally Posted by bentley

Just a hunch... the iLok driver somehow rolled back to a previous version when you repaired it. VCC requires the most recent iLok driver or you'll get that error. Is this on a PC or Mac?

PC. I did notice when I "uninstalled" the drivers for ilok the re-installed them, it did say repairing. Maybe I didn't uninstall it completely? How would I go about that?

[E.rOk.stA]

Originally Posted by popmann

Did it get unplugged from the network? Known issue with only ilok2...if Win7 puts your NIC to sleep on disconnect (OS default) it will stop recognizing. It needs a MAC address active on the system.

Makes sense. I just disabled the sleep function last night in win7.

[bentley]

Check the driver version for your iLok in device manager and make sure it's at least driver date 6/28/2011, version 5.9.5.3483. Even if you've run the latest driver install, I've seen an issue where it doesn't update itself.

[E.rOk.stA]

Originally Posted by bentley

Check the driver version for your iLok in device manager and make sure it's at least driver date 6/28/2011, version 5.9.5.3483. Even if you've run the latest driver install, I've seen an issue where it doesn't update itself.

Ok, will do. I'll let you know if that works.

[E.rOk.stA]

I checked the driver version and it's the latest. I'm at a loss..

[E.rOk.stA]

BTW, I did uninstall the client helper originally because it was interfereing with codemeter, the virtual dongle that authorizes my SSL Duende plugins.

[bentley]

I'm stumped as well. Had a similar issue that was a result of the iLok software not installing the latest version of the driver. I did numerous uninstall/reinstalls and it kept finding the old iLok driver and installing it which would give me the same error message when using both Slate VCC and MCDSP V5. If you confirmed that you have the latest driver then your problem is different that what I experienced. Do you have something besides PT you can try and load up VCC in?

[E.rOk.stA]

I downloaded Reaper to try that and same message, "iLok not found. Please insert iLok with license and click OK." You know what? This happened briefly with McDSP's 6030 compressor when I demo'd it around the same time. In fact, that demo ended up working but the license was on my iLok 1. I think I might slide some of my other licenses over to the 2 and see if they work. Maybe the iLok2's jacked..

[popmann]

There are two ways to change sleep thing...one works, the other doesn't...how did you turn it off? Needs to be the advanced tab "sleep on disconnect" = disabled. Not, interesting the power management tab.

[E.rOk.stA]

Yeah, the sleep's disabled. I transferred a Soundtoys license over to the iLok 2 just to make sure it wasn't the iLok. It worked fine. It looks like the issue is with VCC. It doesn't work in Reaper either so it's not Pro Tools. Other licenses are working on the iLok so it isn't that. Every driver is correct, I've done everything on my end that I can possibly do..

[GPl]

Yeh, I had the same issue but after finally getting the latest ilok2 drivers to install, everything worked fine. It's got to be something along those lines...

[E.rOk.stA]

Originally Posted by GPl

Yeh, I had the same issue but after finally getting the latest ilok2 drivers to install, everything worked fine. It's got to be something along those lines...

Dude, over the past 2 days, I've uninstalled and reinstalled those drivers over 9 times.

[Daflo]

I did the same I try to up grade from pro tools 9 to 9.0.6 and now it fails to even install pro tools wtf!!!!!!!

[popmann]

Sound toys doesn't REQUIRE. An ilok2. This is a PACE issue. If I were a betting man, I'd but a bunch on this.

Maybe they need some other hardware ID in addition to the MAC addy...anything else changed on your system?

[E.rOk.stA]

Originally Posted by popmann

Sound toys doesn't REQUIRE. An ilok2. This is a PACE issue. If I were a betting man, I'd but a bunch on this.

Maybe they need some other hardware ID in addition to the MAC addy...anything else changed on your system?

I know they don't require the iLok 2, I just wanted to make sure the thing actually worked.

[E.rOk.stA]

Spent 4 more hours tryin' to figure it out........if I figure it out, I'll let you know. I put another ticket in with Slate..

[wxyz]

Are ypu on Vista or Windows 7?

[E.rOk.stA]

Originally Posted by wxyz

Are ypu on Vista or Windows 7?

7, I went straight from XP to 7. Never even fell for the Vista slump..

[wxyz]

I couldn't get it to work with Vista, but Windows 7 is ok...sorry

[bentley]

Agree with popmann that this is more than likely a PACE issue. I realize saying that doesn't help you any but this thing is still screaming driver issue to me. VCC relies on the latest iLok driver to be functioning perfectly as all other licenses will run using an older driver. In my situation, the latest driver would say it installed properly when in fact the new install would crap out at the launch of C++ redistributable and revert back to a previous version. This allowed all my other plugs to function except for Slate VCC and McDSP. As off the wall as this may sound, you could try installing another McDSP demo to your iLok2 and see if it triggers the same error. It's the only other plug I've seen trigger the error due to a driver issue. If it works then it might help determine if it's unique to VCC. Grasping at straws here...

[E.rOk.stA]

Yeah, I think I'll try that. I've systematically narrowed things down to point the same direction you're thinking.

[popmann]

Originally Posted by E.rOk.stA

I know they don't require the iLok 2, I just wanted to make sure the thing actually worked.

Understood...the ones that require it are a different type of license system only a "2" provides the manufacturer. My East West QLSO worked fine on the 2 while VCC did not.

[E.rOk.stA]

Wow, the plot thickens. McDSP V5 won't load up either. I know they need the latest iLok drivers too. The funny thing is that I've downloaded and installed them but I think it's rolling back to the previous version mid-install.

[E.rOk.stA]

Here's the deal. I download the latest drivers from ilok/PACE. They're labelled Sept. 9, 2011. When I check the version in device manager, it's June 28, 2011. As it's installing, a blue window comes up and says at the top "repairing driver". I think it's rolling back to June 28 at that point.
Do I need to uninstall all the drivers and then do a clean install??

[GPl]

That's what I did...clean install

[E.rOk.stA]

How exactly did you do that? Maybe I'm doing it wrong.