Vienna Symphonic Library Forum
Forum Statistics

194,022 users have contributed to 42,906 threads and 257,896 posts.

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

  1. Home
  2. Notation Programs & Vienna
  3. Sibelius
  4. Assigning Manual Soundset Program Names - Synchron Player + NPPE

  • Assigning Manual Soundset Program Names - Synchron Player + NPPE

    S
    S

    Hi to all,

    Just a quick one. After setting up a basic Noteperformer 4 NPPE (Spitfire SSO) basic Playback config for some reason when I add Synchron as an extra device I can't get it too display the program names for each percussion instrument or String, etc when I want to assign a sound.

    You can see in the pic below it's only letting me choose stock noteperformer instruments?

    Just wondering if this is a bug or have I missed a simple easy fix etc. I have set 'Allow Manual Soundsets' and 'Show Program Names instead of ID's in the options.

    Would love to be able to have these extra auxiliary options from VI Libs I have to fill the gaps between other libraries

  • andiA
    VSL Team
    andiA

    Hello simyoda!

    As far as I know this is a bug in Sibelius. As a workaround it might work to temporarily assign a different sound set and then again the sound set that you want to assign.

    Best regards,
    Andi

    Vienna Symphonic Library
  • S
    S
    @andi said:

    Hello simyoda!


    As far as I know this is a bug in Sibelius. As a workaround it might work to temporarily assign a different sound set and then again the sound set that you want to assign.


    Best regards,
    Andi

    All good. I had to weirdly select a noteperformer instance and change that to 'Manual' I then assigned that noteperformer instance (the 1st 1-16) a new set VE Perc Syzd etc. and then i was able to change it in my synchron instance afterwards. I then obviously set NP back and now it seems to be able to select the VE SYzd set now. Playback config saved! Thanks for your tip of tweaking trickery and the confirmation of bug! Hopefully if anyone else has the same problem it will work for them. I'm on Windows 10 so I'm probably asking for trouble:)

    Cheers Andi,

    Thanks Simon.