If you use VE Pro you don't need VE Pro Event Input or multiple instances.

I use one running copy of VE Pro with one instance that has 48 midi ports each defining up to 16 instruments.  Were I still using Sibelius, I could define each midi port e.g. 1MolCp3Pipe11 (I'm using MidiOverLan) against a specific soundset so in theory up to 48 different soundsets - if you're using vendor-supplied soundsets they tend to be based around an orchestral section so simply split the 48 available ports into some for woodwind, some for strings and so on.

i.e. first VE Pro instrument specifies port 1MolCp3Pipe11 channel 1, the next channel 2... then the 17th would be in my case port 1MolCp3Pipe12 channel  1.

Updated: a Reset and Rescan all plugins fixed my issue - wasn't picking up on a VST3 folder correctly

On installing the new version using Vienna Assistant, I find that the standalone Vienna Imperial Piano works fine, but it's not configured correctly for using as a plug-in in Vienna Ensemble Pro.

When I look at the channel in the mixer Vienna Imperial Stereo is not listed under "Integrated" plugins and I get "Errors occured while loading plugin: Toolkit: Vienna Imperial <br><br> Could not open plugin.

Anyone else having this issue?

If I reinstall the eLicensor version it again works OK in Vienna Ensemble Pro.

Yes, just tried V7.1.1390 and the standalone immediate crash issue is fixed - opened and saved successfully.

Is there an update on when VEP Standalone will work with iLOK?

As others have reported it either crashes uncontrollably immediately on opening older project files if eLicensor is installed or fails with an error message if uninstalled (not practical, as people may need it for other plug-ins).

The server version is fine for some scenarios e.g. Dorico, Cubase but there are others where the standlone approach is required.

It isn't practical to 'just carry on using the eLicensor' since people need the latest iLOK only versions of VEP if for example they're using MIR Pro 3D.

I previously had the Synchron player + Great Rieger Organ (latest versions) working fine under Windows 10 via a RME Digiface USB interface. Similarly on a Windows 10 desktop with a different RME interface (Raydat).

On moving to a new laptop under Windows 11 (latest version), both are usable within Vienna Ensemble Pro (standalone or server) but when using in standalone mode give an error others have reported (different specifics) when selecting audio routing - namely, "Audio routing unavailable. (Could not initialize selected audio device). "

I have the latest RME driver which supports Windows 11 and have tried reinstalling it to no effect.

The Vienna Imperial standalone also works fine when selecting 'channels' to see the inputs/outputs.

I have tried the suggestion stated elsewhere on the forum to delete the Synchron player + Organ player directories under Appdata and reinstall but this makes no difference.

Any suggestions?

<deleted>

+1 on the CPU / System %

The relelase notes also indicate that MIR should recognise Natural Horns but doesn't work for me (using VEP/MIR in standalone mode) with latest update applied... other Historic Winds instruments OK per earlier updates

Yes I do find it more readable now - thanks for listening

I do appreciate how much work goes into a site refresh like this and my comments were specific to the forum pages which in my case is my normal form of interaction with the site.

Well done to the team for the overall work

People's reaction to website design is by its nature highly subjective as can be seen from the responses, but Michael is correct that people are perfectly entitled to express their views particularly when they are genuinely supportive of the company and want to raise what they see as legitimate issues.

I fail to see what is "great design" about the excessive use of white space - see the screen paste below. This reminds me of the 'lowest common denominator" that Microsoft went for with Windows 8 across PCs and tablets.  It meant people using PCs and laptops who wanted an efficient interface felt compromised.

As I scroll down this page it seems ridiculous that the main content is such as small % of the visible screen estate - maybe it looks different on a different OS or platform e.g. tablet (I'm Windows 7 / laptop).

If I didn't care about VSL and have such a high expectation of their work I wouldn't have bothered commenting and I fully accept that people will have different views, but personally I think it could be better.

Wish I could say the same - I generally like everything VSL does but this is not a step forward.  Having blank columns either side looks like you want to run advertising down the side, which makes the content more bunched up.  The text is uncomfortably small in some columns e.g. on this community page and the colours don't make it easy to read.

If it ain't broke, don't fix it

Martin

Two Intel 480Gb Series 520 SSDs - working off a 4 port SATA III PCIe card (motherboard didn't support SATA III and had run out of interfaces).

The VSL samples are spread over the two SSDs - brass and strings sharing one and the rest on the second.

At present the OS / applications are on conventional drives.

Dave

Andy, thanks for the feedback. I'll play around with the settings to reach a compromise that works best for my setup. In my case your 'few seconds' was the difference between waiting an unacceptable 20 minutes to load a fairly large template at the start of a session and a more reasonable 5 minutes when I started using SSDs. In hindsight using the most aggressive pre-load buffer settings is clearly not the best route - a path I'd taken to maximise the number of instruments sample variations I could safely run given my current memory configuration.

Andi

This is performance related. I increased the pre-load buffer size in Directory Manager from 1536 to 2048 for the Dimension Strings and later the other strings using the same SSD and it improved significantly. As it's a performance limit, I've switched off velocity cross-fade as well.

The moral of the tale would appear to be that Dimension Strings is very demanding of the system - looks like a 3rd SSD and/or increase in memory will have to be on the cards at some point especially when you release the rest of Dimension Strings!

Dave

To put some context on the earlier comment, I use Sibelius to drive Mir Pro using Andi's standard presets, the latest Strings soundset, the updated house style and latest versions of all software including the recent VIP Pro update and the noises occur even when not switching between cells and are not limited to the sustain patches. The staves were created using the Dimension Strings entry and all routing between Sibelius / Mir Pro / VIP Pro / expected matrices / cells appears to be working as expected.

I copied a staff showing the problem to an empty manuscript and the problem appeared to largely go away - then added further individual DS violin lines and the problem seemed to re-occur getting worse as the number of DS violin lines increased. While this seems to suggest a performance limitation as stated earlier I'm already running all samples on SSDs (2 x 480Gb) and it seems unlikely to me that a few DS violins would max out when I've happily run fairly large numbers of instruments off this configuration. The only change I've made to the default presets was to set velocity cross-fade on but this doesn't stop / increase the problem.

Any ideas?

I've experienced similar issues - it's not necessarily system overload as I'm running off SSDs and passages of a given intensity of instruments / notes appear fine while others sound like someone's whacked the wall - and the disk / CPU / memory usage off the monitor don't appear to particularly jump at these points, I'm using 8 individual DS staff lines and the problem seems to occur irrespective of whether velocity cross-fade is switched on which I appreciate adds to the load.

Thanks Andi

Andi

I notice that in the Orchestral Strings preset Sib_OS_Bassi_L2 the D0 matrix cell A4 uses a cello patch instead of double bass, so any articulation e.g. Marcato triggering the cell and playing below the Cello range doesn't sound.

Regards

Dave

Thanks both - for now, more than happy with the dramatic improvement using the drives standalone

Cyril

Thanks for the comments. I'm expecting a SATA 3 PCIe card any day so will switch on receipt as the motherboard isn't SATA3.

Not keen on RAID configs but given your indicated speed improvements may try that in due course.

Dave

To add to other's observations of SSD impact using VSL, the following is initial impressions not forensic analysis but they've made a huge difference.

Hi Andi

Sibelius 6.2.0 (I hate the ribbon so don't want to upgrade to 7!)

Windows 7 64-bit

VE Strings soundset / presets / (VSL house style imported) should be per your latest versions

Running into Mir Pro / Vienna Ensemble Pro 5 / VIP Pro 2

Regards

Dave

Andi

I notice that the VE String soundset (whether Orchestral, Appassionata, Solo etc) doesn't have a legato.vibrato definition but does have numerous legato.vibrato.custom definitions.

If I hit a legato / vibrato combination e.g legato as technique text and vib as expression text it switches to one of the custom (empty) cells in the matrices if I'm using the matched presets.

Your user guide says vibrato is default anyway but shouldn't this definition be included? If I add it then it seems to work as I'd expect.

Dave

Hi Andi

Keep up the good work with the soundsets and tips. Most of the subtle problems like this are more often around trying to use a file created earlier with new config / soundsets. I logged it only in case some poor other soul hits a similar problem. I've found that if Sibelius' mixer doesn't automatically select what you expect, it's unwise to assume you can fix the problem by tweaking the settings e.g. with multiple similar instruments e.g. 4 individual horns, if the second instrument defaults to the first instrument' channel it won't fix the problem just by incrementing the channel on the second instrument. It behaves like the earlier second instrument problem prior to release 5.2.5 - ie the sound goes through the first channel regardless but articulation switching doesn't work. It might be worth adding to your 'try this' list that in such instances users should always look for the underlying problem. With similar but different playback configurations (e.g. I have ensemble and individual instrument ones very similar) it's easy to not realise that the underlying instrument staff mapping is not what's assumed e.g. ...trumpet rather than trumpets etc. I can't see either why just changing the label fixed the probem since I assume it's the actual sound mapping which leads to Sibelius's mapping of best sound - I can only report that it seemed to fix the problem

Andi

The Tuba and Contrabass Tuba entry caused some strange behaviour on my system. Using a score created against a previous soundset combination / playback configuration, I created a new playback configuration with multiple midi connections, two of which used your woodwinds & brass soundset. On the 'brass' one, when applying the "tuba and contrabass tuba" from the soundset when I restarted Sibelius, and opened the score the playback configuration data appeared empty (but wasn't in the playback directory) ie even the other midi interfaces which didn't use your new soundset didn't show up on the right hand side so all instrument mappings appeared lost. I edited the soundset and renamed it to Tuba rather than Tuba and Contrabass Tuba, retried and everything worked as expected.

Dave