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.

@9u10m said:

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.

Hi, I don't want to interfere in the discussion about the money, but there is one thing I have to say: it is not true that nobody will use Synchron Strings 1 anymore. There are people (I can't say how much, I can't count them of course), who appreciate all the good things of Synchron Strings 1 and use it with pleasure (and I'm one of them). 

@9u10m said:

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.

Hi, I don't want to interfere in the discussion about the money, but there is one thing I have to say: it is not true that nobody will use Synchron Strings 1 anymore. There are people (I can't say how much, I can't count them of course), who appreciate all the good things of Synchron Strings 1 and use it with pleasure (and I'm one of them). 

I totally agree. I love Synchron Strings I. I don't have SyS Pro yet, but I'm sure I'll keep using both in the future.

Best, David

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

@9u10m said:

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

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

@daviddln said:

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

Just out of curiosity: Is it known how many velocity layers the Synchron String Pro articulations will have? I couldn't find that information in the description of the product or the sample content list. I find 9 layers a bit of an overkill, but two (like most of the SYNCHRON-ized Instruments I own) can be a bit scarce at times.

@Sandrew said:

Just out of curiosity: Is it known how many velocity layers the Synchron String Pro articulations will have? I couldn't find that information in the description of the product or the sample content list. I find 9 layers a bit of an overkill, but two (like most of the SYNCHRON-ized Instruments I own) can be a bit scarce at times.

Hi

The number of velocity layers is described precisely for each articulation in the manual of the library.

Best, David

Oh, ok well I know all i wanted to know now :) Thanks for the quick reply.

I find the demos sound really fantanstic and very expressive btw :)

Hello Paul,

could you tell us how many velocity layers Synchron Strings Pro comes with?

I totally agree. I am one of the early adaptors who was disappointed with Synchron Strings I and I actually un-installed it and never could use it in my projects. I learned my lesson of not being an early adaptor ever again. My love and trust for the company and its' name made me never question any product they release and with such a company I was willing to buy their libraries instantly without a second thought.

That being said, I am very excited for the new Synchron Pro library but I too find it a steep price to pay for something I should of had with the first Library. How I think about it is if I should buy this new library and pay on top of the price of the original library just to use one of them and feel better that at least I got something in return for my initial investment. I don't think I can do that, it will make the price for me too big to make sense. But what I am hearing from this new library is tempting me.

Thanks

Hi Paul

The demo's of the new Synchron Strings Pro left me speachless - its absolutely stunning and the closest to the real thing I have hear to date. So I will be "upgrading" from strings 1 post haste.

But now please tell me that you plan to do a con sordino extention to this library - right? 

It would be so gorgoues :-)

best regards

Bjarne

Dear VSL-Team,

I spend quite some money for you libraries in the last years but this time its really worth it. In it´s ease of use its a real gift, even i payed for it. Hihi. Congratulation!. 

01 1st Violins-14 Pro XF sus

C#1 Long Notes > F2 XFades > B2 Flautando X pp > Flautando  : the Flautando patch is mapped up to G7, causing it to sound when the Release key switches for pianissimo F7/G7 are chosen (when the crossfade using CC 20 is low enough to allow the Flautando to be heard). 

Never mind. Noticed that I made a mistake on my own.

However, I will leave it to a question. Does the Synchron Strings Pro do anything different compared to the VI series in regard to VXF? I feel like the VI series seamlessly replaces samples to more and more expressive when moving up the VXF slider. Synchron Strings Pro feels more like additional samples are added on top of another moving up the VXF slider the same way.

Is there a difference here or is it just my interpretation?

Hi Jhonny, 

Glad you could resolve your problem. Do you want to post an example of what you hear?

The Velocity XF process is identical, but of course multiple mics create a different sound than 1 stereo channel that is sent to a reverb. 

Best, 
Paul

I concur with Plowman, there appears to be a small error in one of the factory presets.

In the factory preset: "01 1st Violins-14 Pro XF sus"; tree path: "Long notes/XFades/Flautando X pp/Pianissimo", the mapping of "Release" dimension keyswitches "Normal release" on F7 and "Soft release" on G7 coincides with Flautando voiced notes F7 and G7. The consequence is that Flautando note F7 or G7 will speak audibly if the dimension keyswitch F7 or G7 is operated while the "Dynamic XFade" dimension control is set to give Flautando a proportion of the mix.

Obviously the user can work around this either by moving the "Normal release" and "Soft release" keyswitches out of the way of Flautando notes F7 and G7, or else by restricting the highest-note keyboard mapping of Flautando voices to E7.

No biggie. I'm sure it'll be fixed in a future library update. :D

Thanks for the confirmation, Macker. Yes, restricting the range of the Flautando is the better solution, as it preserves the F7/G7 template found elsewhere. 

Hello plowman and Macker!
The little mistake in the 1st violins preset (flautando XF pianissimo range) will be fixed with a library update.
Best regards,
Andi

Cheers Andi 👍😊