I can also report what sounds like overlapping layers in the Tutti full range preset

> Long notes reg vib from C1 to E

Keep up the great work!

Originally Posted by: daviddln

Well, for example, there are much more dynamic layers in SyS I. So, it's very useful for very expressive passages. And I really love the soft sustain and legato patches. So, I think I'll still use them. As I said, I don't have SyS Pro yet, but I'll tell you more when I get the library. And as another example, even though I own SYNCHRON-ized Chamber Strings, I still use VI Chamber Strings I. Both libraries bring something different. I guess it will be the same thing with SyS I and SyS Pro.

Best, David

We'll see, then. I'm still willing to bet that a vast majority of early adopters will mainly use SS Pro once they have purchased it, and a vast majority of newcomers will mainly buy SS Pro and not SSI.

What I'm trying to say is SS Pro is a full product, not an extension. If it wasn't meant to kind of replace SSI, then it wouldn't be so exhaustive content wise. That's why I feel previous SSI customers should not have to pay such a steep price for the better working clone.

Best

Can you please be more precise? What things in Synchron Strings I will you keep using, that are not already in Synchron Strings Pro?

Right. But it still all comes down to the same conclusion: Synchron Strings Pro is only a thing because Synchron Strings I ended up a failure. No one will buy it now, and rightly so. Early adopters did, and will not use it anymore. Pretending otherwise would be fallacious in my opinion.

I'm thrilled that VSL took the time to make things right. Where does that leave said early adopters, though? With the need to buy two libraries in order to take advantage of a product that actually makes sense in the otherwise superb Synchron line.

I think €145 is a hefty price to pay on top of a first purchase that won't find any more use in the future. I'm sure the VSL team can understand that.

Again, I admire VSL's ability to pause, listen, and reboot this library.

I'll just add this one thing: €145 for the owners of the first iteration feels steep. It's certainly the most expensive library update—the way I honestly see it—I've had to consider. If Synchron Strings I had proven practical, Synchron Strings Pro wouldn't have been released. I feel it should be offered for less to those who originally paid for a library that they will not use again, which certainly is my case.

Keep up the great work

Congratulations VSL, you listened! This is the Synchron Strings I many were expecting.

Are the sforzato articulations new recordings?

According to the demos the tone of those 2 libraries is gorgeous. It's lush, warm and organic, definitely the flavour I would have hoped for Synchron Strings, which in my opinion sound surgical and thin in comparison.

Thank you, Paul

It works wonders with Power Drums and it would be very nice to have dedicated content for the Percussion library.

All the best

Still no news on a control app, could we maybe get an eta? Is it actually going to happen?

Thanks

Very nice modern flat design, simple and well laid out. Hopefully a taste of the overhauled VSL website!

Hello,

Any news on a Synchron Player iPad Control App? I'm personally looking forward to it!

Cheers

I'll add my vote, plus another one for a Synchron player app

Best

I second all the positive feedback on the Cantabile violins. I think their sound is warm and lively, the patches perform extremely well.

Congratulations on a long awaited, yet very well done update. Let's hope all other sections are in the pipe :)

Best

Hello,

If a project was made using "Kontakt5.component", Logic will conveniently open "Kontakt.component" (v6) in lieu of "Kontakt5.component" if the latter is not present in the Components folder / deactivated in Logic plug-in manager, which is super useful.

Is there a way to have VEP6 behave in the same way? It would be a huge time saver with large Kontakt-based templates.

Thanks

May I request the 3 Chopin demos for both the Yam and Steinway with the exact same settings?

Thanks in advance!

I can confirm the issues aforementioned on macOS 10.12.6

Originally Posted by: cm

Originally Posted by: 9u10m

I remember VSL saying they couldn't remotely deactivate licenses. I'm glad they can now...

though possible it is still not allowed to remotely deactivate licenses - this would be an intervention in a foreign computer system. however it is now possible to disable keys.

This is from an email exchange with Marnix two years ago (I'm not trying to be a smart *** or anything): "Also it's technically not possible to disable the licenses or the key via remote".

My point is that now it is indeed feasible, I would have expected this service to be offered –and charged for– on a case-by-case basis. VSL choosing to turn it into a new stream of revenue rather than providing actual customer care feels inappropriate.

Originally Posted by: Dominique

What I don't understand: 5. clearly states that VSL can and will deactivate a lost/stolen/broken dongle. Why don't you just do that when necessary, instead of making us buy an insurance biannually? If Steinberg charges VSL for deactivation of licenses, why not just pass these fees on to the customer that needs the service when it is actually needed?

In my opinion customers should not have to buy an insurance against the deficiencies of a copyright protection system that VSL needs, not us. VSL should.

Ditto. I remember VSL saying they couldn't remotely deactivate licenses. I'm glad they can now, but I certainly feel such protection should automatically be granted for any library purchase. I get why VSL might have to charge for it, I don't understand why they turn it into an insurance plan.

Originally Posted by: prodamu

I can reproduce this,
I load the Strings all VelXF patch and choose one of the Short or Pizzicato articulations with the Velocity Crossfade set to Off.

The drop outs do not always come directly, somthimes I need to play around for a while before they occur. It doesn't matter if I play fast or very slow.

The drop out is random. If I just repeat the same note, over and over again, some of them will sound and som of them will not sound.

I use two mic positions, Main and Surround, sent to different outputs and then routed to different speakers. The drop outs will be very clear because of the different speaker pairs and in my case it's always the Surround samples that drops. The Main samples never drops for me.

My scenario exactly, except I also use the mid mics so the drop outs are even more obvious

Originally Posted by: Simon Ravn

Unfortunately I think only VSL can improve SyS - and that will require huge amounts of new recordings. Let's face it, it's not gonna happen.

I certainly wouldn't settle for that.

When I am commissioned for a project and the client thinks it needs rework --whatever the reason, we talk about it and I usually get back to said project, according to what was discussed. Sometimes I feel the client is wrong because they don't know much about music. But they pay me, I deliver.

I don't think VSL has ever released a product that raised so many eyebrows. Those who voiced their concerns here and elsewhere spent money, sometimes long before the product was released. Lots of them have already had the chance to use a few other strings libraries, and thus usually provide VSL with informed, knowledgeable feedback. Sadly, what they have been getting in return so far is silence, and in my view an opportunity to raise more eyebrows (Synchronized Chamber Strings). 

The competition aside, everyone wants Synchron Strings to be a great product, which at this point I think it is not. Almost all of their other libraries are, and the rest of the Synchron line certainly is. So yes, I hope VSL do consider recording new material that fixes the library's shortcomings, because any other approach will sound like a slap in their customers' faces.

I'm back to work!