Vienna Symphonic Library Forum
Forum Statistics

190,271 users have contributed to 42,728 threads and 257,081 posts.

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

  • Prime lower limit too low (and some overlaps with Flow keyswitches)

    last edited
    last edited

    Hi,

    As in the title, Prime Violoncelli's lower range overlap Flow keyswitches. Maybe the keyswitches should go to the right side, like with the Contrabasses.

    But there is a more general issue, that is that the instruments seem to have the lower limit one octave too low. Take for example Flute 1:

    Paolo


  • last edited
    last edited

    By default, middle C is C3


    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • last edited
    last edited
    @Bill said:

    By default, middle C is C3

    I've long ago set C4 as the middle C. As you can see in the diagram I posted, Synchron Player takes care of this. I would also believe that the instruments are playing in the expected octave. It's just the lower limit (maybe the higher, too?) that is out of place.

    By the way: I think that VSL has always followed the MIDI standard of naming C4 as the middle C, instead of Yamaha's C3. A quick check to the manuals seem to confirm this.

    Paolo


  • I'm just showing the default as I see it, It would explain you issue..


    Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
  • @Bill said:
    I'm just showing the default as I see it, It would explain you issue..

    The note name you see depends on the visualization preferences in your Synchron Player. The MIDI note number is in any case the same (Middle C = MIDI Note #60).

    The problem I'm experiencing is likely the same with any naming standard.

    Paolo


  • This is how Violoncelli look like:

    The lower range is clearly overlapping the keyswitches. In any case, this is not a natural range for cellos, whose last lower note is C2 (or, if one wants them detunes, just a little lower).

    Paolo


  • Hi Paolo!

    I cannot reproduce your problem here.

    Do you have Synchron Prime Edition 2.0 installed and the old content uninstalled?
    Which OS are you working on?
    Which Synchron Player version do you have installed exactly?
    Which preset did you load exactly?
    Did you do any steps after loading the preset?

    Best regards,
    Andi


    Vienna Symphonic Library
  • last edited
    last edited

    Andi, thank you for your answer.

    The old Synchron Prime folder was renamed by Vienna Assistant, while the new one was being installed. I then deleted it from the content drive.

    My OS is Mac Monterey 12.7.6 on an Intel Mac.

    Synchron Player is v1.3.1674.

    To enable Flow, I don't load a Precision preset. I click on the rainbow, touch the Strings section, and select, say, "Violoncellos (8 players)".

    When the Flow UI appears, I choose any or the presets, play any note, and see the range appear.

    By the way, the Pizzicato preset doesn't show the range.

    No other operation. This happens both with Synchron Player used as standalone and as a Dorico plugin.

    Here is a video:

    Wrong range in Flow

    Paolo


  • Hello Paolo!

    Thanks for your detailed description and the video. I can now see what's going wrong. You seem to have the following Synchron Player setting enabled:
    Engine/Force disable all slots

    This setting doesn't work properly with Flow View. When the slots get enabled, the ranges get stretched. For now I recommend turning this setting off. We will look into it. Sorry for the inconvenience that this might have caused.

    Best regards,
    Andi


    Vienna Symphonic Library
  • Andi, just a note to say that the update of yesterday didn't solve this issue. I see the Synchron Player version has not been changed, so maybe it was just a minor fix.

    Paolo


  • Hi Paolo!

    The issue you have reported needs to be fixed in Synchron Player and cannot be fixed with a library update.

    Best regards,
    Andi


    Vienna Symphonic Library