
Armistice
Son of Yoda
Q. What do you do when your Steven Slate Trigger stops working?
A. Shoot it... (boom tish tish - triggered via SSD4, natch...)
A. Shoot it... (boom tish tish - triggered via SSD4, natch...)
Truly awful experience... so far I've avoided it! I'd have thought they'd put the damn software on the iLok itself... I mean it's a USB stick basically, isn't it?
OK...looks like I got it worked out after a few more hours of troubleshooting.
I called the Pace/iLok phone number (408-377-9774).....and man, they really don't want to take calls, so all I could do was leave a message with their sales department (iLok support doesn't even have voicemail, only the online support), and I said I was ready to return my iLok and the software I purchased....and about 10 minutes later, I got an email response to my trouble ticket.
Not sure if that was just coincidence...but I'm sure someone got my phone call message.
So the iLok support tech looked at the screen shots I sent him of the errors, and he said the Microsoft Certificate Authorities list was probably in need of updates. I think all these software companies assume that everyone has their computers always connected to the Internet, which would automatically update the CA list from time to time.
He gave me a Microsoft link to download an executable that was supposed to take care of the CA list. There was some concern that there could be errors, and of course, if my OS was not genuine, it would crap the whole thing out....but I knew it was, and after running the executable......success!
I was finally able to install the Pace iLok License Manager...which the tech said I needed installed even on my non-networked computer, otherwise the DAW would not recognize the license on the iLok.
So I had to still do some manual driver install after the ILM app ran....but it worked out.
Finally....I had to reinstall my Slate plugs, and then rescan my VST folder for any previously failed plugs....and then everything was working.
I still need to set up my Trigger Instruments folder and all that....but that's minor stuff compared to what I just went through to get the iLok working....and I'm just real happy that the iLok fix didn't trash things that were already working fine on my DAW.
Gotta love software installations and you just have chuckle at some point at the nuttiness of it all....![]()
Well....while the iLok underlying issue might have been related with not having the latest CA list....I have not had any issues with dozens of apps I've installed very recently from various vendors, or ever before since this DAW was first put together, and it's had plenty of installs and never once a problem with CA lists....
....so in my book, the iLok installation was and is poorly coded or not accounting for all compatibility, especially when they state it is, going back to WinXP and even USB 1.
As I mentioned it still did NOT install the drivers automatically as it was supposed to, even after the CA list was updated. I had to do that manually going to my system32 folder, which they don't say one has to do.
Anyone else having the same issue might not know how to do that or that they even should do that.
Not to mentoin....on their website info, there is NO discussion about off-line installs and what is required or steps one needs to take.
In the end it took a lot of time and back-n-forth with iLok to get it sorted.....so I don't see that as an iLok win-win.
I mean, if you think I was being harsh about iLok, feel free to Google "iLok issues" and see how many hits you get, so don't worry that this one thread will give iLok a bad rep.....they've done a lot to earn that on their own.
I thanked the iLok support tech for his help....but I also suggested that they post more detailed info about off-line installs and the potential issues that may come up. In my book, software installs of a simple USB device should not require this much time effort or special steps, and that's all on iLok, AFA how complicated it is.
I have a bunch of USB devices on that DAW....and never once did any of them fail to install because they needed an updated CA list.
Anyway....if anyone only reads my first post and doesn't follow through the entire thread.....that's their problem. I made a point of providing all the details from start to end.![]()
The point is, the reason the issue happened was not due to their poor support or documentation. In the end, it was your particular setup that caused the issue right? They responded quite quickly to resolve 'your' problem.
And yeah...I have yet to delve into the actual Trigger stuff....so you better get ready, 'cuz I'm-a-gonna rank on you if I hate it, since you practically talked me into getting it!
I'm sure it will do what it's supposed to do...which is why I got it, to do some drum replacement, and why I was willing to ride out any iLok issues, since I knew in the end I would have it all working, regardless of any speed-bumps. It was just a temporary installation PITA, and now it's over and I can start using Trigger.
Oh...what's the Intstrument Editor....is that for creating your own sample library?
I only installed it but didn't check it out yet.
Also, I installed both Trigger 1 & 2.
I kinda' like the Trigger 2 GUI better, as the Trigger 1 seems a bit crude on first sight...but I'll see how it is when I acgtually use them.
You seem to prefer Trigger 1....is that just the GUI or also the samples?
Oh...with Trigger 2...do you have the full Platinum or the EX (not sure what you don't get with the EX).
I'm over the initial bitch about iLok...... as I said, I knew there could be some issues, and there were, but I also knew I would get past them and move on. So I don't want anyone to be afraid of iLok....but hey, there's no denying that they've had problems and I think they are working to improve their customer service image and avoid as many issues as possible. I think their iLok License Manager software is an attempt to improve the whole activation process, and they probably will need a few upgrades to it to work out all the kinks.
The Pace/iLok tech said he would post more detailed info about off-line activations and possible issues following my trouble ticket.
Instrument editor is exactly what you think it is. You can record multiple samples of any source, and make them into trigger (tci) files. I am not even sure how many articulations you can add, but it is over 100. In other words, you can create your own trigger samples by playing the same drum 100 times with different types of hits. Off to the side, rim, whatever, and control the range of velocity that triggers it.
Trigger 2 GUI has many more options, though I am so used to using Trigger 1, that it just seemed to interfere with my workflow. No, the samples are not exactly the same, and even if they were, they have different names now. I got used to the ones that I liked the best in Trigger 1, so Trigger 2 just seemed like more work. I have just not had the time to mess with it much yet. Trigger 2 was only a free update. Not bad, just not something I have dug into yet. I am not even sure there is a Trigger 2 Platinum. Just an update that was free for platinum users as far as I know.
I would love for you to give me a critique as to how it works for you.![]()