Vienna Symphonic Library Forum
Forum Statistics

180,757 users have contributed to 42,140 threads and 254,362 posts.

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

  • Sibelius and Automation of VE Pro Faders

    I have discovered something that I thought I would pass along.

     

    The Problem:  To work the faders of VE Pro from Sibelius (my version is 7.51), you send a message, attached to something on a staff in the form "~CXX,XX" - no space between the characters, where "CXX" is the controller number (notice you use C not CC), and "XX" is the value.  Example:  ~C7,90.  That value will place the fader at 0.0 db, since the CC values are a fraction of that value over 127 times the total distance of the fader.  You can experiment with values to figure out what db value you want.  Since each staff sends on a different MIDI channel to VE Pro, you must match your automation port and channel information when you set up automation in VE Pro, to the port and channel in Sibelius.  (Each group of instruments should have its own port, e.g., woodwinds, so that the translation of staff graphics converts to an appropriate command for borth VI Pro and VE Pro.)

     

    So far, so good.  However, mysteriously, some of my commands, although apparently on the proper staff, were not sending commands to the appropriate fader.  I discovered two solutions to the the problem.  First, for empty staffs at bar 1, choose a rest within it, NOT the TIME SIGNATURE.  Choosing the time signature seems to send the message to the first channel no matter which staff you choose.  Second, in Sibelius turn on View-Invisibles-Handles.  What was happening to me, for some reason, Sibelius was MOVING the attached CC command to a different staff.  If you look closely, having turned on "Handels", you will see a very thin line connecting the CC command to a staff.  In my case, Sibelius was moving the command to a different staff, so the command did not go through to the desired channel.  Just make sure that your commands are all connected to the staff you want.  Adequate staff spacing seemed to fix the problem.

     

    This post took more text to write than the actual fix, but the basic idea is to CHECK that the command is CONNECTED, by the thin line, to the correct staff.  Then you are in business.

    Steve


  • ErisnoE Erisno moved this topic from Notation Programs & Vienna on
  • ErisnoE Erisno moved this topic from Finale on
  • ErisnoE Erisno moved this topic from Notation Programs & Vienna on
  • ErisnoE Erisno moved this topic from Dorico on
  • ErisnoE Erisno moved this topic from Notation Programs & Vienna on