If 4.9.x works why EVER update (question for VSL???)


Rob

Well,

there´s quite a few reasons to update: Faster startup, faster loading times, more stable key management, to name just a few... Also, as host programs and OS´s are updated regularly and they are used on different setups in varied combinations, it really makes sense to at least find the version that is best for you.

Now, especially as Syncrosoft are working hard to offer solutions, it´s at least worth to give it a try and also give them feedback.

Just my 2 cents,

Paul

@Paul said:

.... it really makes sense to at least find the version that is best for you....

Paul

This statement makes the most sense of all. If 5.0.2.0 causes as many problems as it fixes, then it seems reasonable to stay with the version that works. It took quite a few days for me to get things loading consistently, and I'm not sure how soon I want to risk additional delays with another Syncrosoft update.

I'm still using 4.9.x.x which works well enough on current string scoring sessions, but maybe when the rest of the VI Cube arrives it might be worth risking another week of SLCC trial and error.

I do commend Syncrosoft for working hard to resolve these issues and for at least being honest with its customers. But 5.0.0.1 sent many of us into a shell-shocked tail spin with the same promises of better performance, making our first experiences with VI rather unpleasant. My load times for 8-10 instances is about 1-2 minutes, so unless people are reporting faster loads than this with 5.0.2.0, I'm going to stay with 4.9.x.x until it totally falls apart.

@Paul said:

.... it really makes sense to at least find the version that is best for you....

Paul

This statement makes the most sense of all. If 5.0.2.0 causes as many problems as it fixes, then it seems reasonable to stay with the version that works. It took quite a few days for me to get things loading consistently, and I'm not sure how soon I want to risk additional delays with another Syncrosoft update.

I'm still using 4.9.x.x which works well enough on current string scoring sessions, but maybe when the rest of the VI Cube arrives it might be worth risking another week of SLCC trial and error.

I do commend Syncrosoft for working hard to resolve these issues and for at least being honest with its customers. But 5.0.0.1 sent many of us into a shell-shocked tail spin with the same promises of better performance, making our first experiences with VI rather unpleasant. My load times for 8-10 instances is about 1-2 minutes, so unless people are reporting faster loads than this with 5.0.2.0, I'm going to stay with 4.9.x.x until it totally falls apart.


Ditto [[;)]]

Well, it took 11 days, but additional issues arose with 4.9.7.6. I decided to try 5.0.2.0.

Results?

Wait time to license scan: 40 seconds, up from 20 seconds
Wait time to sample load start: 3 mm 5 sec, up from 1 minute
Wait time to sample load end: 3 mm 55 sec, up from 2 minutes

Total memory used on 10 instances: 687 MB

Short of wiping my entire hard drive and starting from scratch, I'm not sure what to do at this point having tried all suggested fixes.

The only thing I can imagine doing at this point is to reinstall 4.9.7.6.

@Another User said:

.... it really makes sense to at least find the version that is best for you....

I'm no longer certain what version that might be...

The only way I can pay for the Vi Cube is to put it to work, but Syncrosoft is in my way. Sorry guys.

Well, I didn't upgrade to the VI,but reading all these treads, I'm really wondering why the Vienna team ended to choose the damned syncrosoft key system:this is an unstable system, althought updating all the time it still comes with new bugs like an endless wheel ........why not choose Ilok; I'm not a big fan about dongles but at least Ilok works.My 2 cents.

@watercolours said:

Well, I didn't upgrade to the VI,but reading all these treads, I'm really wondering why the Vienna team ended to choose the damned syncrosoft key system:this is an unstable system, althought updating all the time it still comes with new bugs like an endless wheel ........why not choose Ilok; I'm not a big fan about dongles but at least Ilok works.My 2 cents.

I've had no problems with Syncrosoft, either with VI or with Nuendo, so I think that it depends on your system. However, I do know many people who have had problems with iLok (and all other CP methods) so I guess that there is no sure fire solution available yet.

DG

Well you're right probably it depends on each system;so far I do know a lot of people having problems with syncrosoft (including myself with the "Korg digital legacy" virtual instrument that I can't use since 3 weeks) and about Ilok I don't know any people who had problems other than dealing with Ilok to get replace licenses when they had key stolen or accidentally broken.I myself use the Ilok key for my Protools system and it never bother me since more than 2 years.
Don't get me wrong, I prefer the other protection systems like challenge/response, but I understand it's too easy to find cracked versions......

I would agree with Watercolours, it's really a shame to see yet an outstanding product ruined (for many) by faulty/buggy copy-protection. I run the ilok as well, and it's rock tight and haven't been the cause of any problems in the 2 years I've had it.

The strangest thing is that because my load times are now inconsistent and increasing (am experiencing 10 minute waits now-- reduced number of instances from 10 to 7, 162 MB less than before), I can't sort out what other troubleshooting can be done. Obviously, these issues depend upon individual systems, but if there is some other AU or USB conflict other than the hub issue I can't figure it out.

I'm not getting the crashes from a couple weeks ago, so I can't even send in a crash report or nail down an error message. The increasing load times have me completely stumped.

I've mentioned this on other threads for different reasons, but it applies here as well: once the full 10 volumes of the Cube are installed, some increase in load times IS expected. But I dread the thought of having to wait 3 times as long (30 minutes or more) for a full orchestra to load.

I've held off with installing the Winds 1, and I don't think I'm going to install anything else until this gets straightened out. I'm just glad that I didn't trash my PE drive.

Regarding the Syncrosoft controversy - I'm not real sure why VSL ever chose to use it in the first place when iLok works so successfuly with so many major manufacturers. Perhaps it's the fact that they share a common first language. Maybe a local sales rep was able to bend their ear more effectively. After all many of us in the forum have English as our native tongue and would find it extremely difficult to post our issues in German. It's only natural for VSL to try to find a local product first.

However, for all the issues iLok may have, I personally, have never heard of extended loading times, touchy placement of dongles and extensive hunting for dongle assets before work could commence. Usually iLok problems have been in the form of 'where are my assets and why haven't they been downloaded yet?' Often the problems with iLok have been the subscribing manufacturers themselves, not iLok. I feel pretty safe with VSL downloading the proper licenses.

Once the assets have been downloaded to an iLok the creative process goes forward without any time blockage for loading. I don't see that being the case with my new Syncrosoft experience. Everytime I load Logic and VI I say a little silent prayer not knowing in advance the outcome or the length of the episode.

I was hoping that the $11K investment would buy me a different kind of excitement than I get every morning presently.

Good people at VSL, is it too late to reconsider?

Thanks for the great library and thanks for the high standards and vision it has taken to produce it.

I hope that all the negative chatter regarding Syncrosoft that might inhibit people from purchasing VI can be changed. I know that the more money VSL makes the more libraries and support we'll have in the future.

Best regards always,
Jack