Not a solution, but an added diagnostic. I load VI / Syncrosoft with my Activity Monitor open. Yes, the key programs (Logic, VSL server and VSL daemon) will say "not responding," but at least the progression of their numbers can be observed. I use that, the prompts (or lack thereof) and the behavior of my hard drive to figure out if I'm loading or if it's a crash.

I was going to upgrade to 5.0.0.1 until I read about Tim's experience.

"The other day, I clocked an *average* load time for full-wack Advanced Matrices at about 30 seconds each." That's interesting. I'm running a dual 1.8, and each VI instance takes about fifty to seventy seconds. So accounting for your faster computer, I think the numbers add up.

I can also tell which VI is loading or hanging. The EXS instrument right before the VI in the channel strips (per layer in Environment) stops loading at the very, very end of the progress bar for a time. This way I know which VI is loading (or causes the issue -- though I doubt it's the VI at all, but Syncrosoft that's causing the problem).

For the record, I always get the thing going *eventually*.

At about nine VI's per song (and the other EXS' loads), my boot time is about ten minutes. I'm sure golem will improve on this. I do hope 1.1 comes out soon. Slow loads make crashed loads so much harder to diagnose. The above are the Neanderthal tools I use to guess what's happening.

Thanks Bruce. It is a bit of a drag. My next step was to wipe my main drive containing the OS and all apps, but before doing so I'd sent a note to Syncrosoft and got a response which I've posted on the forum HERE.

Copy protection is necessary and important. It is my strong feeling that VSL deserves to have its library protected in a reliable and functional manner that makes it difficult or impossible to pirate their wonderful product by those who have no intention of honoring copy protection laws. Those who have pruchased VSL's products deserve also to have their investments protected as well. For myself, I would want NO ONE to gain access to what I've paid dearly for in an effort to use it at my expense.

With that said, I wholly agree that the licensing process should be without reproach. What good does it do for a manufacturer and its faithful supportive customer base should the software be rendered unusable by anyone-- including the rightful owner of the licenses?

I must give Syncrosoft due credit for disclosing their awareness of the problems caused by their system. Many companies would deny such problems exist and would content themselves by blaming the issues solely on user error.

Users on this forum, including myself, have wasted precious time and money by troubleshooting issues on a case-by-case basis, unique to their systems. Uninstalling and reinstalling software, tracking updated versions, chiming in with customer support and forums, paying for a technician's assistance, canceling days of income producing creative work, warding off encroaching deadlines, replacing perfectly functional hardware believed to be faulty-- these are understandable and necessary parts of the process, but personally I'm into my second week of these issues, and for as patient with my computer and with myself as I have been, I confess that I'm at the point where my patience has quite run out.

What complicates the issue is that not everyone is having these troubles. But this fact does nothing to help those who are. I've invested the same funds others have to less than acceptable results-- and it's all because I've been "protected" from using my own software. The success of others is small solace when my projects are at a virtual standstill. For how many more days or weeks must I endure VI sitting dormant-- dysfunctional and unused-- all because of glitches with a third-party authorization process that doesn't work?

It's just a total waste, and with every day that passes my lo$$es only increase. At this point, I cannot wait for Syncrosoft to effect a solution that ought to have worked *more* reliably and universally well before now. Changing libraries at this point just for the sake of meeting project deadlines is akin to moving out of a brand new house back into a one-bedroom apartmement. The entire situatiion is shameful, embarrassing, and wholly unacceptable.

Sorry for the rant, but all I have to go on is the faith that things will get sorted out eventually. In the meantime I've paid for a library I cannot use with no assurance of when I might be able to use it.

Couldn't have said it better myself.


Bottom line - is rolling back to 4.9.x solving the problem?


If so, could someone tell me the steps in 'rolling back'

(unistall existing, VI registering libraries issues, etc.)

[8o|]


Rob

The pdf help file on the SYnc site was helpful. Rolling back seems to have fixed the issue [:D]

You can't pay me to update to a higher release (I don't care if they say 'all clear' - too much down time.

Rob

Hi Rob:

Since my last post I've had a nap and some fresh air. I feel like Hal from 2001 Space Odyssey: "I'm feeling much better now, Dave..."

Someone else mentioned that using the earlier version of SLCC worked for them. I will give it a try, but not today. I first want to get away from the "silicon inferno" and get my projects done on time. I'll be going back to PE and supplimenting it with Vitous Philharmonik for now. Since getting VI, my hard drive setup has changed considerably. Glad I backed up all those files.

Before "downgrading" to the earlier SLCC, I will need at least half a day to assemble the code files that Syncrosoft has requested, after which I'll give it a few days in case a solution is effected. As long as my projects don't come to a halt any more, I'm not going to rush through this. I want nothing more than for the VSL team to win. Okay, maybe a million dollars would be one exception, but Christian, Herb, Paul, Marnix and all the guys have bent over backwards for our sake. They have to know how much they are appreciated for their support and creativity. They deserve SO much more out of this, as do their customers.

I've really grown quite fond of VI very quickly. It's just so cleverly thought out-- and I ache even more to put it to good use.

One day soon it will all work out.
One day soon it will all work out.
One day soon it will all work out.
One day soon it will all work out.
One day soon it will all work out.......

(I keep telling myself.)

Gott im Himmel... bitte helfe mir!!!!

JWL -

Just checked a third PC - roll back fixed that too. [:D]


Rob

@Rob Elliott said:

JWL -

Just checked a third PC - roll back fixed that too. [:D]


Rob

This is good news. Thanks, Rob.

How were you able to do a full uninstall? On Mac, some authorization files remain hidden. Most uninstallers I've experienced don't "unauthorize". In fact, my SLCC still gives me warning that an authorization was interrupted two uninstalls ago. Can't get rid of it...

Am having the same problems :

Syncrosoft License Control - Error

-> No protection device connected.

What do they mean, it's different on different systems? That's BS. I just have straight Quad G5 -- it should WORK. I hope they post a fix very soon. I just started a project using the Vienna Instruments and now can't open my Digital Performer file without getting a non-stop beachball.

Sorry guys I am on PC.


Rob

@garylionelli said:

Am having the same problems :

Syncrosoft License Control - Error

-> No protection device connected.

What do they mean, it's different on different systems? That's BS. I just have straight Quad G5 -- it should WORK. I hope they post a fix very soon. I just started a project using the Vienna Instruments and now can't open my Digital Performer file without getting a non-stop beachball.

Hey Gary:

Is your Vienna Key connected via a powered or non powered USB hub?

If it's in a hub, have you tried unplugging the hub and plugging in the Key directly into the Quad? If that works, then we know it's not the key itself. It *might be* the hub (if you have one).

Powered hubs seem to work best, but one thing I noticed was that SLCC had trouble reading more than one level of connectivity-- in other words, it *saw* the hub as an unknown device, but did not see the Key connected to it. At least at one point earlier this week, I could start VI in DP with my iLok and Vienna Keys connected to the powered hub, but I could not register with Syncrosoft unless the Vienna Key was the only one connected-- directly into the computer (not the keyboard).

There is one odd behavior which I've not mentioned online yet:

In DP, VI *may not* load if you've changed your audio settings in AUDIO-MIDI or with your Instrument Track Output assignments-- if they are different for whatever reason than they were when you last saved the project. For example, I was running everything with Built-In Audio for a while until my PCI-424 card came back from MOTU. Once I installed it and the drivers, VI would not load until the PCI-424 was selected, Audio Bundles were recongifured, AND the track output assignments were done. After that, I saw the yellow "please wait, loading instruments" windows.

However, that was several days ago when troubleshooting a different issue. What we may be experiencing now is more closely related to SLCC . But, I hope some of this information will come in handy for you at a time when you need it most.

Cheers,
JWL

PS-- if this is a case of changing audio output assignments, you may want to create a new project in DP, create the new audio settings with AUDIO-MIDI and DP's Hardware and Settings Preferences and Instr. Track assignments, then restart your VI project.

I can second the hub issue. I was successfully loading and running Logic with multiple VI's. But then I'd try to load another VI and SLCC would come up and say it couldn't find the key. It was a big crash. I could Force Quit Logic, but the only way I could remove the SLLC window was to turn off the computer.

So I switched the key to the front USB port on my Mac. It stopped the crashing while composing. My issues are now limited to the initial launch of Logic.

Thanks for that info JWL. I did change settings in AudioMIDI setup, but if that's it, then SLCC is too sensitive as none of my other iLok plug-ins have any issues. I reinstalled some of the software and tried plugging the key into different USB ports, some powered-hub based, directly, etc., and was finally able to load Vienna after numerous attempts. Not sure why it's working now, but it sure doesn't inspire confidence. Hopefully they'll shore this thing up quickly. Thanks again.

My pleasure, Gary.

Sad story with (I think) a happy ending...?

Curiousity got the best of me, so I started troubleshooting SLCC issues. One moment, all of my licenses appear in the LCC screen. Another moment, there were NO LICENCESES PRESENT!!!

So I followed the PDF instructions, which suggested removing the following three files from the Library/Receipts Folder:

LCC.pkg
NOS.pkg
POS.pkg

Then, I download version 4.9.7.6 for OS X and reinstalled. I made sure that the Key was plugged into the computer and not the hub (just in case), and that only the mouse and keyboard were connected. RESTART--!!!! (In fact, SHUT DOWN for a minute or to and REBOOT just to totally dump stubborn RAM data.) Immediately, my authorizations reappered when I launched LCC without having to use LCC's Wizard.

Version 5.0.0.1 has some severe misread problems. 4.9.7.6 did allow me to at least view my authorizations and to start VI successfully in Standalone mode, but I've not attempted booting a VI project in DP just yet. Call me chicken, but I think I'd like to go to sleep on a good note. If VI chokes in DP, it would be better to have had a decent night's rest. [:P]

@Plowman said:

I can second the hub issue. I was successfully loading and running Logic with multiple VI's. But then I'd try to load another VI and SLCC would come up and say it couldn't find the key. It was a big crash. I could Force Quit Logic, but the only way I could remove the SLLC window was to turn off the computer.

So I switched the key to the front USB port on my Mac. It stopped the crashing while composing. My issues are now limited to the initial launch of Logic.

Likewise, I can confirm your experience as well.

Seems like some features of VI simply override OSX...

--no force-quit from host app
--omni floating windows take screen and function priority-- even over DP's own omni-floating transport controls
--DP's transport key commands are rendered dysfunctional if the last window clicked was the VI console. Clicking in and out of VI just to play-edit-play-edit-- what a process. VI seems to retain much of its Standalone priority
in this regard...

Gotta give it VI for its show of muscle!

"Clicking in and out of VI just to play-edit-play-edit-- what a process."

Yep. It's the same in Logic.

Okay, here's a tidbit that may be too soon to observe. It won't help JWL, or maybe anyone else. But this thread is as good as any to note it.

As discussed, I've had inconstant success loading VI in Logic. But my last three power-ups have been smooth (er... not fast, just smooth). The only difference? I'm out of demo licenses. Now christian was prompt to send me more authorizations, but I haven't loaded them yet.

I realized that some of my buggy start-ups were generating obscure L2 authorization prompts. So I wanted to see what would happen if I held off the demo stuff. Three successful starts is not a scientific proof. But I'm going to hold off the demo renewals through the weekend and perhaps load them next week for further observation.

"Gotta give it VI for its show of muscle!" Truly, it yields to no other window. I half-expect it to stay there after I turn my monitor off.

@Plowman said:

"Gotta give it [to] VI for its show of muscle!" Truly, it yields to no other window. I half-expect it to stay there after I turn my monitor off.

I think VI is using The Force!

I started up one of my VI projects today in DP. 20 seconds of spining beach ball went by before licenses were scanned. Another 2 minutes or so went by before the data and consoles *began* to load.

At this point, I'll not complain about the load times. I'm just happy that it's loading at all--!!

Wow. I was just thinking this very same thing about three minutes ago, after another successful start.

I can understand why VI data takes so long to load... sort of. But I get "Scanning Licenses" for about two minutes also.

It's a USB key. The licenses are there. SLLC asks the key, "Are the licenses there?" And the key says, "Yes." This takes two minutes? What exactly are SLLC and the key discussing?

VI is splendid, and I'll be buying more. But there comes a point when load times are prohibitive in a commercial setting, when auditioning and changing cues for cllients in the room.

Could any VSL tech explain in lay-person's terms why the key takes so long to authenticate? Will 1.1 improve on the "Scanning Licenses" time as well as faster data loads?