Vienna Symphonic Library Forum
Forum Statistics

195,006 users have contributed to 42,953 threads and 258,084 posts.

In the past 24 hours, we have 12 new thread(s), 43 new post(s) and 66 new user(s).

  • CC in Synchron Player

    If I control the CC faders of the Synchron Player with a midi controller (here Meta Grid Pro), e.g. the volume data CC7 are also recorded as "channel 1 midi volume" (Logic Pro). However, when I move the fader in the Synchron Player, data is written as "1 Vienna Sync: Master Volume". That means I now have two different CC recordings for one CC channel.

    Of course I could always use the faders of the Synchron Player, but that's often too cumbersome for me.

    Is there a mapping that solves this problem?


  • Hi Stefan,

    I highly recommend you use Velocity Crossfade (VelXF) to control your dynamics, and for fine-tuning, there is CC11 (Expression). Best not to touch Volume at all.

    Andreas


    VSL Team | Product Specialist & Media Editing
  • Hi Andreas,

    Thank you for the answer, but unfortunately it has nothing to do with my question ... nevermind.


  • that's because when you use you controller you are transmitting MIDI CC data that drives the fader on the Synchron player, while when you manually move the fader on the Synchron player you are sending automation data to Logic. You need to choose to either use MIDI CC or Automation, mixing the 2 is only gonna give you troubles.

    And i would also take Andreas advice on not touching the volume, just VelXF and Expression, as Volume is set per instrument by VSL to balance the instruments of the orchestra against each other.

    Personally i prefer to map my controller faders to the instrument via smart controls automation, so i can rename my controller faders how i want, and i can take advantage of automation modes, like read,latch,touch,write.

    Which gives me the advantage of being able to edit my automation curves live with the controller, rather then having to re-record my fader movement from scratch or edit with the pencil tool.


  • @Andreas8420 said:

    Hi Stefan,

    I highly recommend you use Velocity Crossfade (VelXF) to control your dynamics, and for fine-tuning, there is CC11 (Expression). Best not to touch Volume at all.


    Andreas

    Andreas - so, does that mean that if you are using VelXF via MIDI CC, that the Expression (CC11) should just be set at one point and left there - would it be at 127?


  • 127 is the default ( = 100% of your volume). You can freely change and automate this value to your liking.


    VSL Team | Product Specialist & Media Editing
  • @Andreas8420 said:

    127 is the default ( = 100% of your volume). You can freely change and automate this value to your liking.

    Thank you...however, that brings up another question:

    What about the Volume slider (I noticed that depending upon which mic mix I choose, the Volume slider is set at a different level)

    Should the Volume slider also be put up to 127?


  • The volume slider (CC7) is set to instrument-specific values and does vary between presets. Which brings us back to the original post and my reply. 🙂

    @Andreas8420 said:
    Hi Stefan,

    I highly recommend you use Velocity Crossfade (VelXF) to control your dynamics, and for fine-tuning, there is CC11 (Expression). Best not to touch Volume at all.

    Andreas

    VSL Team | Product Specialist & Media Editing
  • @Andreas8420 said:

    The volume slider (CC7) is set to instrument-specific values and does vary between presets. Which brings us back to the original post and my reply. 🙂


    @Andreas8420 said:
    Hi Stefan,

    I highly recommend you use Velocity Crossfade (VelXF) to control your dynamics, and for fine-tuning, there is CC11 (Expression). Best not to touch Volume at all.

    Andreas

    Ahhhh ok I misinterpreted your statement to not touch Volume at all to mean to leave it at 127 but you meant to leave it at whichever value VSL set it to for that patch

    Thanks