Hi Paul, that is not it, all my libraries are on my build in MBP SSD. I especially bought a large one to have all libraries at hand without having to carry around an external SSD. Just clicking on the instrument in the Synchron player loads theM correctly without having to specify a path.

Does the incomplete loading maybe have something to do with iLok? I  have my licenses in the cloud but do have it running and am signed in before opening a DAW or Dorico.

I have a annoying issue since I started using iLok. I open a piece in Logic or Cubase which has a number of Synchron instances and when I start playback an umber of instruments are not playing.

When I go to the plugin, it looks like the first screenshot. A number of articulation options are crossed out in red. Only solution I found it to go to each instrument and reload the it in the list by double clicking.  It is sort of random. If I have 10 instruments all VSL Synchron, 2 may load OK and the rest have to opened and with a double click the instrument has to be reloaded.

Hi Simon, as I mentioned I first checked this when I saw your post and  I already had iLok installed at that time. So I cannot confirm that it was also an issue with the eLicenser, on my Mac. I am sure it was as you indicate. 

I did find another a maybe related detail. When VEP is open with or without a file loaded and you click on a vesp file in Finder it does open up correctly in VEP. 

No-one any input on this issue?

Same here Mac OS 12.3.1 latest VEP. Version.I usually open recent projects so I did not notice. I think it has something to do with this VSL helper which seems run each time you open a .vesp file or also a VSL library in a plugin in a daw but which does not open when you click in the finder on the vesp file.

Hi Terence, a first reason for several instances not related to organization is that one of your DAWs might not support more than 16 midi channels per port nor multiple ports. I think the Logic multiport version is still a Beta. It might have changed but when I got my M1 MBP Logic did not accept it.  I had no time to further test. 

As you would normally use the same VEP file for multiple DAWs and multiple music pieces not always using the same instruments It is also of advantage to group your instruments in instances. I usually save a file with all instances on Off and based on the instruments I plan to use in a new piece, activate the instances with the instruments I want to use. Usually I have to connect 4-5 instances per piece linked to the template. 

I have five timpani slots in one SP instance, the 20-32", and am trying to play all at the same time to get more volume.

I have understood that if I activate the parallel mode at the top of the five slots and set all 5 slots to mix in edit they play together in unison.  If that is the case something seems not to be working as I do not notice any volume increase compared to the single instrument. Am I doing something wrong? 

To check I also loaded up 5 instances of the SP each with a timpani. That gives the desired effect. HZ like volume

Although this thread has focused a lot on the use of DP and MAS plugins I do have small comment on the topic in the original title. I have been running Logic on an M1Max MBP in native mode with VEPPro AU version for months now. You do not need to start it in Rosetta mode except when you have other plugins which do not work (Logic normally identified those at startup).  I think as long as the plugin is or supports AU it works in Logic. No need for Rosetta.

On the other hand Cubase and Dorico have to be started in Rosetta to make the VST3 version of VEPPro work.

Hi Jaffar I think you should seek help directly from VSL not in the forum if it is urgent.

regarding the libraries you bought I find it strange that they have to be converted. Old libraries which first ran with an eLicenser yes but new ones just bought should directly show for download in the Vienna Assistant and in iLok under not activated. You then download and activate or then other way around works as well I found.

regarding the Synchron player, have you tried to install and activate one of the free libraries just released? Same process as described above. If that works your issue is pinned down to the way the libraries have been installed. VSL Andreas or Pail can solve that.

I set it up using single instruments with all articulations in 5 VEP instances woodwinds, brass, keys, percussion, strings.  I only used port 1 and maximum 16 channels per instance as I use the same VEP file for a DAW with those limits.  So if there are more than 16 instruments in a section e.g. percussion you can add an additional instance.

In Dorico you add VEPPro as many times as you have instances in the VST rack and you add the expression maps for the corresponding instruments to each channel.  

Next in the inspector you connect each player to the corresponding instance of VEP and you enter the correct  port and channel for the instrument as defined in the previous steps..

Remains only to connect each instance to VEP by tapping the „e“ in the VST rack. The instruments you have in your piece have of course also to be enabled in VEP. (I usually only activate instruments I use  in a piece in my VEP template]

I tested in both Cubase and Dorico. Cubase, with its usual illogic, none intuitive way of working  ignores the articulation keyswitch midi notes when you have the official VSL expression maps linked to the tracks. So you have to remove them from the track to make them work. As in Logic there is an audio performance peak when a VSL instrument kicks in which causes some clicks. After one playback this does not occur anymore.

Dorico works perfectly with the keyswitches but also has some clicks when a VSL Synchron instrument kicks in. You always have to run a piece till all instruments have played a few notes to eliminate the clicks.

I played also with the Synchron player settings Force enable all slots or Force disable all slots. There is no effect on the peaks. Force enable does improve that first notes when an instrument kicks in sound which also is an issue I only have with Synchron libraries.

By the way I have 4096 samples preload and 4 steaming and loading threads in the settings. Maybe that should be changed to solve this issue. The 100% peak shows only on one high performance cores/threads in Logic.

I will try the same piece in Cubase. It is a bit tiresome as I have to set up the instrument rack for 10 instruments and add the expression maps to each track to make it perform in a similar way using the key switches provided by the midi export from Logic which sometimes is a bit buggy.

in Logic I managed to improve the situation a bit by setting the number of threads and cores used to the maximum instead of automatic. No more overloads but sometimes instruments still kick-in only after 2-3 notes when played back the first time. What I noticed is that the system  activity monitor independent from the DAW actually does not show high CPU usage, the peaks are just shown in the Logic internal activity monitor. 

Question is of course if this have anything to do with the switch to iLok or is it the latest Synchron player update which under the hood had some significant changes. 

Same issue on a Mac. MBP M1 Max 64 GB Monterey, Logic Pro latest version

Thé same pièces which had no issues at all before now regularly give system overload when you first playback and instruments play their first notes, a workaround is to go back ton the start of the piece and playback again till the next overload. After all instruments have played their first notes, you can play the pieces from start to finish without issues and navigate back and forth. 

I like the clarity of the second version and the nearly floating high strings in the last measures which is less the case with the EQed version.

Have you ever tried experimenting  with VSL libraries in Dorico. It lacks a bit on the mixing functionalities but that actually brings out exactly what the plugin and samples really sound like . You also have the possibility to have a note sounding longer (or shorter) than officially written in the score which gives a very natural real player sound, difficult to obtain in a DAW if you do nit want to modify the official score. e.g. at the end of phrases before the start of the next. 

I did some more testing and I think I solved the issue myself although the reason for having it in my existing projects with several Synchron Player (SP) tracks is still unclear. To solve it:

• I started with a new project and loaded the SP Plugin with a Strings Pro VCs and immediately pressed the Logic Smart Control shortcut (B).
• Contrary to my earlier test on an exiting track in a project, a number of Smart Control buttons show up. The choice is a bit weird (ByPass On/Off, Master Volume, Expression and DIm.CRT/A-E), however the buttons can contrary to earlier now also be allocated to e.g. VElL.XF. 
• By moving these Smart Control buttons or also by moving the faders in the SP Plugin the automation can now be registered in playback latch, touch and write mode.
• Learning a button on a Midi Controller to do this same task should  be done in the Logic Smart Control inspector by pushing Learn and not in the SP plugin on the fader. Both methods make the button in the SP plugin move and have effect on the playback, but only when the midi controller button has been linked in Logic Smart Control, it will also register automation in playback mode.

The issue seems to be specific to Logic automation which uses both midi CC  type automation and their own. In Cubase Write mode in playback works with the Synchron Player. I assume because Cubase only used CC type automation also when used in Playback Write mode.

Strange that some libraries like BBCSO have a default setup with Logic smart controls preinstalled and linked to Logic own automation but the Synchron Player not.

In Logic you can write automation for numerous plug-in paramètres in playback latch or touch mode. In general the parameters like Expression and Modulation, Vel.XF are automatically mapped in the Logic Smart Control.s view. For the Synchron Player this is not the case. 

You can map the parameters manually and they influence the playback. You can also link them to faders of a Midi controller but the changes are not written to the automation lane in latch or touch mode.  What is needed to do this is that the Midi CC changes are « translated » into Logic automation control changes.

Has anyone been able to solve this issue?

Workaround is to record these parameters in normal record mode « on top » of the already recorded notes but writing in playback with latch and touch functionality ismore efficient. 

I don't have a VSL Piano Library with CC67 but normally you can go to the cc number in the Perform or Control view click on the little arrow and define a new CC under the control (see screenshot for cc. You just have to redefine the default CC11 Expression in the plugin to another CC, otherwise you will control both parameters with you pedal movement.

An interesting investigation which becomes even more complicated if you consider the differences in let us call it starting volume of different articulations of the same instrument. When working on a classical score of e.g. a Beethoven symphony with rapid changes between long notes, legato phrases and staccato runs maybe with a tenuto note from time to time and lots of Sfz bars it is a big challenge to balance. The players balance the volume of these articulations naturally but in e.g, VSL Synchron libraries but also in libraries of other providers you have to reduce the volume (note velocity and in most cases also CC1or CC2 Modulation and CC11 Expression as I personally seldom touch CC7 in the plugin) of all short but often also long notes to balance them with the much quieter legato patches to get a natural sounding phrases. I actually also noticed huge difference in volume of the VSL Pro Strings Legato patches. Try getting Legato Espressivo to balance with standard legato in a phrase You need huge manual changes in volume parameters.

The differences in the strings example presets might also have something to do with the distances from the decca tree and other microphones of the instrument sections and the way VSL libraries handle such distances. On top of this the instrument panning also plays a role. If I understand it correctly with VSL Synchron libraries, the instruments are panned as per their location in the orchestra setup although the panning button in your DAW is in the center. 

The two Horns in SY Brass probably have not been registered at the same time and the final balancing was done in the preset. Horn 2 also has a different timbre I noticed. 

We are now 3 months later and the Synchron player is still not M1 compatible. Is there no Beta version to try out?

In Logic it is no issue as it seems to run both native and Intel based plugins without need for Rosetta except some rare exceptions. In the latest Cubase and Dorico it is a real problem as several plugins of other library suppliers are only M1 or you might have to go each time through a new manual installation to get them to work in Intel mode and back to M1. So if you have a templates with a lot of flexibility with VSL and other instruments it is a rather tiresome process.

When can we expect at least a Beta M1 version of the Synchron player?

It is a huge work to program all yourself in Logic especially because most VSL libraries have more than 3 levels of key switches which Logic cannot do in simple way. The way to do it is more a Logic topic than VSL. You will find the Articulation Set editor in the Logic inspector last point under Track.

There are several not too expensive vendors which offer Logic articulations set for every library you can think of. I use Art Conductor.

I have tested using Logic Musical typing and the Logic on screen keyboard with exactly the same M1Max MBP with 64GB. The Synchron Player (I used Elite Strings as library) now works in both native and Rosetta on my machine. The previous version did not pass the native test by the way but now it works.

What does not work is using the keyboard in the synchron Player to record. It does produce sound but no recording. Unfortunately I am not in my studio. So could not check with my NI KK keyboard.

Thanks Paul

for the very fast response. That would indeed be an option, but I think I will wait till a real Synchron CS articulation is available hopefully for Elite Strings. Maybe I will look into a CS convolution on the Elite String (ES) samples to keep the integrity of the identical ÉS chambre ensemble in my tracks.

The Synchronized products are no doubt excellent but some sections do not have the same number of instruments and probably they have different players and instruments as the ES library and finally they also have a convolution reverb in the final chain to get the Synchron Stage ambience. 

Not sure where to place this request but as Paul has explained the philosophy behind the different string libraries and Versions very well it might fit in this thread. Feel free to move it.

I have the full version of synchron Elite Strings. It is a fantastic library but I unfortunately seldom use it for my compositions as it misses basic articulations con sordino and flautando. Is there any qualitatively good solution for this issue (I saw some plugins to electrically create these articulations) or is there a VSL extension planned to add these articulations to this library in the future? It would really be worthwhile as the full version mixes are great to create a certain atmosphere.