The download speed through the assitant is indeed not very fast compared to speeds in apps of other VST library providers. Even with a very fast internet connection it took some time to get all string libraries uploaded.  The speed you see at the bottom of the display in the app also varies a lot over time if you have a large library to download (I think you also see the number of servers change?).

Maybe this helps: If it seems to go asleep I noticed that pausing and starting again can wake up the process.

.You are exactly describing what all Mac M1 users experience. I have an M1Max with 64GB RAM but experience the same issues of peaking overloads and incomplete loading of VSL instruments in Logic in M1 mode. I even have fprojects with multiple VSL instances (10-15 Synchron instruments) which are not playable anymore in M1 mode. They open very slowly (1-2 minute) but if you start playback you get the infamous ball spinning eternally.

After a lot of experimenting with the setting s in M1 mode, I found that the only solution is to run Logic in Rosetta mode, Somehow they way the VSL libraries load is different. It opens very fast and actually see your Synchron player instances load during the opening of the project and although you might face an overload on the first playback after opening, the project runs smoothy after simply restating payback and you can work on it and save it.

I am not sure what is happening at VSL but there seem to be serious developer issues. The is a complete radio silence on M1 issue. Worse the last still none M1 compatible update of all major players and VEPPro was even withdrawn due to major bugs.

It is really getting time to at least issue an. M1 Beta version of the Synchron player as we all have thousands of Euros more or less blocked. in libraries which cannot be used properly since close to two years on M1 Macs. The last „no news and no deadline“ message from VSL was in August as far as I can trace in the many posts on this topic!

Many plugins now have separate M1 and Intel plugins and switching between native and Rosetta just to use a VSL instruments is very tiresome. Logic runs the Synchron player without Rosetta but CPU is peaking. at the first few notes and regularly gives CPU overloads even with 64 GB CPU. Versions of files with Synchron player tracks saved in Rosetta mode have difficulty opening and playing in M1 mode and just opening the plugin often leads to a DAW crash. I had to stop using VSL instruments in new compositions.

VSL team when will we finally have a M1 and now M2 compatible VEP Pro and Synchron player?

I use Addictive Drums2 which has a brushes and sticks jazz packages with loops and playable setups. Also nice for playing live with just a guitar or soloing for fun with guitar and or bass..

I was suffering since months from this issue. Up to a point that I switched back to BBCSO and looked into other orchestral libraries. Only VSL Synchron had the 100% core load peaks and especially in Rosetta overload issues but I might have solved it.

I noticed no relationship with the number of threads in the VSL settings. I tested 4-10. However the number of threads and other audio settings in Logic seem to be a key issue. On a Logic experts recommendation I used to the maximum for my M1Max 10 threads since some time. That gave reproducible overload points in Rosetta and other playback issues ( partial instrument articulation load) in native mode. So I switched back to processing threads on Automatic, I/O buffer size 256 samples and process buffer range Large in Logic audio preferences.

With those settings I stil get 100% peaks of in general one core per instrument when it kicks in which VSL should really work on as this only happens with their Synchron instruments but playback continues without clicks nor overload. Even if as many as 5 new instruments to let us say 10 already playing kick in.

I have also experimented with all sort of Synchron settings with between 4 and 10 threads and preload sizes but that had no effect on the overload issues. I now use the recommended preload for my SSD i.e. 3072 samples, 6 streaming and processing threads and force enable all slots. By the way I have an MBP with 10 cores M1 Max and 64 GB memory and 4T SSD.

I hope this helps.

I agree that the speed with which the VSL software is adapted to M1 is disappointing however they are certainly not the only company having problems getting their software adapted. Apart from Kontakt all Native Instruments soft and Hardware still needs Rosetta.

Do you really have such big issues using Rosetta with Dorico?  I am running a Dorico 4 project using Rosetta with 70 instruments in the VST rack, 49 VSL Synchron and the rest BBCSO and a few Kontakt Percussion instruments. It takes bit of time till the project is playable but I have no big issues when it is ready to play. Sometimes  a few clicks when 2 or more instruments are played at the same note for the first time in a session (a CPU peak). You also see it very well in the Logic CPU monitor. When you play it a second time there is no peak nor clicks.

Before my M1Max I had to use VEPPro for this size of project as I had only 16 GB on my Intel MBP but with the new M1Max and 64 GB this is not needed. 

I did test VEPPro with a similar size template but only with Logic (so no Rosetta needed). The main reason at the time was that the Synchron player did not work directly in Logic whereas it did work when accessed through VEPPro. Now the Synchron Player works directly in Logic. 

I absolutely agree. I just switched back to BBCSO for the strings for several scores which need longer con sordino passages because neither Elite, nor Pro, nor FX Strings have CS. I really do not want to use an additional library in the middle of a piece just for this articulation. There is a simulation app from numerical sound but I am not sure it works with the Synchron libraries. They only advertise VSL VI support. Sound is not bad however.

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.