Vienna Symphonic Library Forum
Forum Statistics

185,260 users have contributed to 42,390 threads and 255,473 posts.

In the past 24 hours, we have 4 new thread(s), 21 new post(s) and 48 new user(s).

  • Double and triple stops in solo strings

    How do I produce playback of double or triple stops with a solo violin instrument?


  • Just write it that way in your DAW or notaion program


    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • That was easy!! Should have tried it out before posting. Ah well.


  • If you have a library that includes non-vibrato patches then you might want to consider using those for double/triple stopping passages as it's very difficult for a string player to use vibrato there.

    Also, audition the results carefully if you're using performance legato as the legato algorithm is good but can get confused by double/triple stopping sometimes, resulting in some slightly strange effects. Consider G and E going to A and F - the legato should be from G to A and E to F, but depending on the relative start times of the notes in the second chord, you may get G to F and A to E.


  • Interesting and helpful comment. Thanks.

    Paul


  • You could use the Detache samples to write them. The amount of attack and lack of vibrato are really nice for that task.


  • That was interesting too. As it happens I'm working on a solo violin passage with double stopping tomorrow and I'll certainly give detache a go.


  • The "VI_perf-detache" patch seems pretty much perfect for my double stopping violin passage. Playing it legato rather than trying to mimic the detache style actually gives a good impression of the fingers repositioning on the strings, and the delayed vibrato corresponds well to the physical reality of double stopping.


  • last edited
    last edited

    @Angelus said:

    If you have a library that includes non-vibrato patches then you might want to consider using those for double/triple stopping passages as it's very difficult for a string player to use vibrato there.

    Also, audition the results carefully if you're using performance legato as the legato algorithm is good but can get confused by double/triple stopping sometimes, resulting in some slightly strange effects. Consider G and E going to A and F - the legato should be from G to A and E to F, but depending on the relative start times of the notes in the second chord, you may get G to F and A to E.

    That's good to know Angelus thank you😊

    As a person who doesn't know the first thing about strings this information is quite handy to me.  I just assumed there wasn't a difference🤔


  • last edited
    last edited

    @daerp said:

    How do I produce playback of double or triple stops with a solo violin instrument?

    Hi Daerp

    It seems tha you are just starting in using samples. So here is a link for getting real and interesting results with samples just by switching between some short single articulations: 

    http://www.beat-kaufmann.com/vitutorials/vi-tips & tricks 4 ...No.39 and probably No. 37 as well

    Of course, feel free to check out other chapters as well.

     

    I wish you a lot of success!

    Beat


    - Tips & Tricks while using Samples of VSL.. see at: https://www.beat-kaufmann.com/vitutorials/ - Tutorial "Mixing an Orchestra": https://www.beat-kaufmann.com/mixing-an-orchestra/
  • One other thing that I've just found you need to take account of when double stopping if you are using "speed" to switch between different matrix cells is that the speed detection algorithm can get confused. So if you have a very small time offset between the notes of a chord, as you sometimes seem to need to do to help the performance legato work as desired, this can be interpreted as a sudden speed increase and so the wrong cell can be selected. I suppose the ultimate workaround is to use separate VI instances for each part, but that really seems like overkill.

    I've also noticed that the speed detection algorithm includes non-sounding keyswitches in its calculations as well, which surely it shouldn't, but I guess that's one of those things that's been in there for a long time and so it can't be changed without affecting a potentially large number of existing performances.