Vienna Symphonic Library Forum
Forum Statistics

194,015 users have contributed to 42,905 threads and 257,894 posts.

In the past 24 hours, we have 3 new thread(s), 14 new post(s) and 101 new user(s).

  1. Home
  2. Sample Libraries
  3. Synchron Series
  4. [SOLVED] Synchron Strings Pro - Violins 2 Short articulations with unbalanced volume levels.

  • [SOLVED] Synchron Strings Pro - Violins 2 Short articulations with unbalanced volume levels.

    GuinG
    GuinG

    Greetings,

    A couple days ago, I was trying out the short spiccato articulations through all Synchron Strings Pro instruments, and I noticed that at least the spiccato and spiccato agile were not as loud on Violin 2 as it was with the rest of the other instruments. At first, I thought it was related to its overall position, but then I used the pizzicato articulation, that was basically at the same output level of the Violin 1.

    Is this something  you're aware, and should we wait for a quick fix?

    Thank you for your time,

    João Guerra
  • Andreas8420A
    VSL Team
    Andreas8420A

    Hi João,

    The 1st Violins were recorded with 14 musicians, while the 2nd Violins were recorded with 10 musicians.

    14 10 8 8 6

    Best regards,
    Andreas

    VSL Team | Product Specialist & Media Editing
  • GuinG
    GuinG
    last edited
    last edited

    @Andreas8420 said:

    Hi João,

    The 1st Violins were recorded with 14 musicians, while the 2nd Violins were recorded with 10 musicians.

    14 10 8 8 6

    Best regards,
    Andreas

    Yes, I'm aware of that, but even so, they seem to lack the same "bite" when it comes to the spiccato performance. It actually sounds like it's not actually a spiccato because it's a bit longer when compared with violins, viollas, or even cello.
  • GuinG
    GuinG

    Ok! My apologies for my previous posts. It seems that the issue was related with some poorly edited configuration on my end.

    I just deleted the spiccato matrix tree and loaded the patches again, and it's now working as it's supposed.

    Basically, it was the Attack on the Edit menu that a wrong value.

    Again my apologies, and nice to get back to working order!

    Thank you for your time, patience, and great libraries!