Thanks.

Do I need VE Pro for that?  I have a licence for VE Pro 5 which I used back in the days when I needed multiple networked computers to run all this stuff.  But I stopped using it because of the lack of high DPI support, and the normal VE Pro seems to do everything I need nowadays since I can run everything on a single computer.  (Or could with VI, anyway!)

Individually disabling every unwanted channel (when I have around 100 channels over 7 instances) would be something of a pain (even with MIDI commands), but it might be manageable if I could disable entire sections (e.g. choir) when I'm not using them.  From what I can see, simply disabling the Master Bus channel has the effect of disabling all the channels that are routed through it, but not knowing exactly what's going on behind the scenes, it's hard to be sure if this is an approach that would work.  After all, it doesn't make much sense that disabling a channel reduces CPU requirement, when that channel isn't being used in the score in the first place!

Mike

Hello Mike!

Yes, you will need VE Pro 7 to do that. As you have suggested, you can group sections in folders and enable/disable the whole folder.

By the way. VE Pro 7 also supports HiDPI resolution.

Best,
Andi

Hi Andi

OK thanks.  So I need VE Pro 7 to do what exactly? - just to send the MIDI commands to disable channels? Disabling "manually" seems to work OK with the normal VE.

Also can you explain exactly why the CPU activity is still so high even when most of the channels are not in use in Sibelius?  That was never the case for VI - I was able to set up dozens of instruments on the off-chance that I might need one and the only overhead was the loading time when I first launched Sibelius.  But with Synchron, that approach no longer works and it is going to force a whole new way of working.

So I'd like to know exactly why this is the case.  It seems to me that it's a bug! - and if it's a bug, then hopefully you might fix it, which would make it easier for me to justify spending a lot of effort setting up a Synchron-based setup.

But if it is some weird technical restriction of the Synchron engine - that the mere fact of loading an instrument into a channel makes the CPU usage go through the roof even if most of the instruments are not being used - then I think I might stick with VI at least for now.  So far, I haven't exactly been overwhelmed by any increase in the quality of the output compared with VI.

Mike

PS just found another anomaly: my score contains a French horn part (Horn in F from Sibelius instruments list).  But instead of loading the program Horn (sound ID brass.horns.french horn) from the manual sound set, it's loading program Wagner Tuba (sound ID brass.horns.wagner tuba)!

Hello Mike!

I've got good news. Our developer looked into the CPU usage of Synchron Player components and he was indeed able to improve the CPU performance for instruments that use Room Reverb and remain silent. This optimization will be included in the next Synchron Player update. It should make a big difference for your template.

I'm not sure, if I understand the problem in your latest post. The Sibelius instrument "Horn in F" has the Sound ID "brass.horns.french horn". The program "French Horn" from the sound set "VE SY Special Edition" has exactly the same Sound ID. If an instrument plays on the wrong channel, this can have different reasons. Please check out the Troubleshooting chapter of the "Optimizing Sibelius Playback" manual.

Best,
Andi

Hi Andi

Great news about the CPU problem.

I think I fixed the french horn problem - I had to change the two French Horn entries from the manual sound set to other (random) instruments, then save, then reset the channels to the correct ones.  There's definitely something going odd there, though - probably yet another Sibelius bug that Avid can't be bothered to fix.

Mike

I seem to have encountered another problem with Sibelius and the Synchron SE.  It's ignoring all my dynamic markings!

I have a test score which starts ppp and has a hairpin over several bars going to fff.  Uses the newly installed VSL house style, which was imported with all options checked.

When I load up my VI-based Playback Configuration, it works fine.  When - using the same score - I switch to my Synchron-based Playback Configuration, all I get is a single constant volume level.

The playback config (as per my other recent post) has several instances of VE (not Pro) each of which has several instance of the Synchron Player assigned to difference channels.  All the Syncrhon Player instances have Vel.XF on controller 11, expression on 12, and master volume on the default of 7.  Vel.XF is switched on (lit blue).

What have I missed?  It can't be anything in Sibelius, because the same score works fine with VI (unless there's something you're supposed to change in Sibelius if you're using SY rather than VI).

Mike

Hi Mike.

I have had quite a few issues with the new Synchronised SE libraries with Sibelius too, and have spent ages on some of them trying to get them to work as per my original VI Pro scores.

What i have found, is that sometimes, for what ever reason, things sort themselves out if you cut out the offending staves and copy them into new ones. 

I found that it was mostly strings that where causing the problem, and if i added the full version of a specific library to my playback configuration (for example, if i added the full Solo Strings and used the VE Strings sound set), then the Solo Strings work beautifully and fully as expected. However, if i then added the SE versions of Orchestral, Chamber and Appassionata to my config and for those libraries use the Special Edition Plus sound sets in my config, then i could have problems with Sibelius selecting the wrong instrument in the channel mixer. And dynamics and articulations could also get played incorrectly in this example too.

Like you, i've also had real trouble running the synchron version of my configutration in Sibelius without a load of pops and clicks and the CPU meters jumping of the scales, so its great to see that Andi and the guys have identified an issue with the Synchron Player that there working on a fix for.

I have to say that i can only imagine the work that's involved VSL's end to get there software to work with Sibelius, and i think that what they've achieved with the SE versions is superb, so i cant wait for the new sound set to come out with the Dimension strings special editions 5 so i can see if i prefer the VI Pro or Synchron versions...as i cant help feeling that my wallet is going to take a hammering!

Kindest Regards

Paul

Hi Paul

Can you get the dynamics to work at all?  And if so, are you using the velocity x-fade settings as recommended on page 30 of the "Optimising Sibelius" PDF? - i.e. Vel.XF assigned to controller 11?  I've created a totally new score with a single oboe, 5 notes going from ppp to ff, VSL House Style, one Synchron Player device in the playback config, loaded with the standard Oboe (French) factory preset, but with the Vel.XF controller changed to 11 and Expression changed to 12.

This is exactly as per the VI settings, and excalty as per the instructions in the "OPtimising Sibelius" PDF, as far as I can work out.

But it plays back with all notes on a constant volume!

Oddly, if I leave the VelXF controller at the default (2) and expression at 11, then it seems to work ... but in that case why are VSL telling us to make that change?

Hi Mike.

I've just made a new score as per your instructions, and i cant get the dynamics to work either...that is odd!..(they don't work at all! with or without changing the vel.XF settings) and something i must admit i haven't noticed yet, as ive been working on implimenting the synchron libraies (where they seem to work fine...but i'll go back over every stave to check as some are large) with exisiting scores and as such, havent written anything new with those libraries yet.

I think i remember seeing a thread that referenced issues with the Vel XF, that Andi seemed to resolve, so perhaps the answer lies there (im sorry mate, i cant find the link but its not that old) and when i find it i'll post a link for you here and have a go at sorting out my playback config, but I must admit, that i like the VI Pro versions so much (they work so well with Mirx and if im honest, i prefere the sound of them too!) that ive only just recently started to work with the synchron versions (although i've had them almost since launch)

I'll post back here mate once i've had a chance to play about with it a bit more.

Kindest Regards

Paul

Hello Mike and Paul!

Please use the Synchron Player presets as they are with Sibelius. That includes CC2 for Velocity XFade. Otherwise dynamics will not work properly. Mike, where did you read that you should change Velocity XFade to CC11?

Best regards,
Andi

Hello Mike!

The quoted paragraph mentions VI presets with CC11 assigned to Velocity XFade, but not that you should assign CC11 to Synchron Player presets.
If you look a bit further down on the same page, the following is written:

Note for SYNCHRON-ized Special Edition users: The steps described in this chapter are not necessary with the sound set “VE SY Special Edition”. Velocity X-Fade gets automatically turned on for rolls and turned off again after the rolls.

I will try to make it a bit clearer for the next manual version.

Best,
Andi

OK - yeah, it's not terribly clear exactly what you're supposed to do, and the note about Synchron SE, as written now, specifically applies to the drum and percussion rolls, not to other instruments.

In my case it's probably just a hangover from years ago.  I've been using Sibelius with VSL SE since 2007, when I'm sure it was necessary to manually change the VelXF controller to 11, so I just assumed it was still the same.

Thanks for your help.  Dynamics now working. Looking forward to the Synchron Player update with the memory fix!

Mike

Hi

It seems that we don't have Sibelius presets in synchron like in VIP...and the VIP Sibelius presets does not work in Synchron...so there are some issues when the score is playing (e.g. wrong articulations etc...)

What is the trick?

Best

Thx

Another issue for me:

Whan i have a VEP7 instance with 16 channels mixed with WW, BW and strings, all the strings don't play...

An idea?

Thx

Hello tousroud!

The sound sets for the Synchron Player collections work with the factory presets. So no dedicated Sibelius presets are needed.

It can have different reasons why articulations don't switch as supposed. Please check the Sibelius instruments in your score and your Sibelius playback configuration. Further help can be found in the Troubleshooting chapter of the "Optimizing Sibelius Playback" manual.
https://www.vsl.co.at/en/Notation_Related

Best regards,
Andi

the steps necessary to get things to work seems too convoluted and cumbersome. regarding sound sets and Sibelius.I can't get the cells activated.. dont like having to be online to get an app to work either.

Hello scrimdy!

I'm sorry to read that you are having difficulties.
It's not necessary to be online to work with our software.

You can find our Sibelius Integration tutorial at the following link:
https://www.vsl.info/en/tutorials/guides/sibelius-integration/introduction

If you need more help, please send an e-mail to support@vsl.co.at and describe in detail what you have done and what doesn't work for you. Screenshots will help us to help you.

Best regards,
Andi

This might be an ok thread for a general observation concerning VSL and Sibelius set-ups for the older VI versus Synchronized libraries. Switching playback between anything VI and anything Synchron(ized) in a Sibelius score  is actually very time-consuming and therefore carries a strong disincentive to do this. I have most of the older Special Edition and some of the Synchronized one, but have not really used the latter for this reason. It's unlikely I would buy any more Synchron samples because of this set-up issue.

I know much of this is not a VSL problem but Avid / Sibelius. From time to time posters have wished for VSL to design their own notation playback software to improve integration for playback. A lot of work, I know, and it has always been said to be unlikely. But the development of the two library groups (VI / Synchron) is a further reason why it remains desirable.