What's new

Synchron Player responsiveness

I am on my way to create track templates for my synchron libraries in Studio One. My PCs CPU is a 18 core XEON with 128 GB Ram, a 4 TB sata SSD system drive, 4 NVME drives for sample playback with 2 TB each and 6 * 8TB harddrives (mirrored) for data backups. I inserted a bunch of tracks (50+) with the Synchron Player (VST 3 version) and the time until a gui of a synchron player appears when I select a track is several seconds. So it is barely usable.

It is slightly better in Reaper. But even there - no fun to use.

Kontakt is in comparison much faster.

Does anybody have similar experiences?
 
I have something similar. Also in studio one. It's not several seconds for me, more like 3-4 seconds, but it is slightly annoying.
 
It is definitely an issue. It's not a deal breaker, but I find closing the GUI gives me a black box for about 2 seconds. It's annoying, but whatever....in no scenario am I ever going to stop using Synchron Stage VIs.
 
Yes - my problem is not quite as bad as yours but the Synchron Player GUI is very sluggish on my desktop and laptop. Sometimes when I switch instruments I get 2-3 black-screen windows that appear outside the main window and then disappear very quickly. I think there's a lot of graphical weirdness going on with the Synchron player.

It's not much of an issue for me on my desktop because I don't tweak anything in the GUI. I use MIDI to control everything from the DAW. So it's a pain when I modify my template but I don't do that very often.

On my laptop, however, I have to disable my Nvidia adapter and use only the Intel adapter because I get all sorts of issues when using VEPro. Interestingly I don't seem to have issues with the Synchron player loaded directly in Cubase, only when loaded in VE Pro. However, I do have vastly more instruments loaded in VE Pro than I ever do in Cubase, so that might be a significant factor.

No solutions, but I can confirm graphics issues with the Synchron player. Fortunately I'm able to work around them without any real impact.

rgames
 
The only isdue I have is some 2-3 sec delay after clicking on Synchron Player in instrument rack in Logic before its window appears - it actually started after transition to Ilok, with Elicenser it was snappy. Not a dealbreaker, but sometimes irritating, cause Kontakt, Spitfire and Sine are faster - almost open instantly.
 
My synchron player does not likes my studio one - often there’s delay while loading which I don’t quite understand ...

however I‘ve switch to reaper …

and problem solved
 
The only isdue I have is some 2-3 sec delay after clicking on Synchron Player in instrument rack in Logic before its window appears - it actually started after transition to Ilok, with Elicenser it was snappy. Not a dealbreaker, but sometimes irritating, cause Kontakt, Spitfire and Sine are faster - almost open instantly.
This. Ditto. Exactly. It 1000% started with iLok.
 
This super-annoying problem stopped me finally from purchasing many more Vienna Vouchers. This „hanging-Problem“ is the biggest bullshit ever since VSL exists. I am focussed on Spitfire now. And I will keep it like this. Yes SFA-Players might have less effects, but they are stable and fluid. And they know Multitouch at it‘s best. All Software which is brandnew follow the modern multitouch appoach (like VITAL Synth, Phoscyon 2, Studio One 6 and other new releases.) Only VSL is still Mouse oriented … Even PLAY from Eastwest is updated for Multitouch… VSL is no more the class-primus in these times when it comes to providing the best workflow… Other Players are more focussed on a great functionality than on just Features. What irritates me most is that there are so many updates for this VSL Player… but you see no progress at all. Some VI features are still missing… after so many year. Unexplainable… But the Most,Most,Most worst case is when a Player keeps hanging like this.
 
Anybody using disabled tracks and get that helper app still popup when you enable a Synchron Player track? It seems to be a remnant of the iLok transition, but I don't understand why it needs to still do that. Pretty annoying - and does contribute to the feeling of slowness.
 
Hmm there does look to be a difference in players. Here's a gif of Pianoteq, Kontakt, Abbey Road One, and Synchron. playeropentimes.gif

Pianoteq is instant, Kontakt just barely a hesitation, ARO a bit of delay, and Synchron has a much larger delay than everything before it.
 
With Logic 10.5 on my Mac Thrashcan with Mojave, both Kontakt 6 and Synchron Player open, when clicking the icon in the track, in something less than a second. I don't see any difference between them.

iLok Cloud version. I too seem to remember that opening was a bit faster with the old eLicenser.

Paolo
 
On my laptop, however, I have to disable my Nvidia adapter and use only the Intel adapter because I get all sorts of issues when using VEPro. Interestingly I don't seem to have issues with the Synchron player loaded directly in Cubase, only when loaded in VE Pro. However, I do have vastly more instruments loaded in VE Pro than I ever do in Cubase, so that might be a significant factor.
Not saying it's the cause for sure but I think VEP uses a special integrated plugin format and not VST. So maybe something specific to those plugins explains the different behaviour.
 
I have been doing some experimentation to see how I can best leverage the Synchron player on an Intel iMac-2020 and an Apple silicon M1 Pro. I have a few findings that might be helpful for others:

* The AU instance of Synchron player when run through the AUHostingCompatibilityService (S1v6 or Logic in apple silicon mode) is 10-15% more CPU efficient than the VST3 one through Rosetta (on MacOS Apple silicon, as tested in Cubase12 and S1 v6). GUI responsiveness is also better on the AU. The VST3 also has a weird render-hide-render cycle when first brought up. This might only be nothing but a Rosetta issue, but till VSL releases Apple silicon native, this might be relevant for some.

* On Apple silicon, when Synchron player is configured to only load samples as necessary (“Force disable all slots”) it slightly increases the system CPU load per instance (user CPU time remains close to 0%). When this is multiplied times 80 instances, this adds up to make the whole DAW host unusable. On Intel this behaviour is also present, but much less pronounced, so maybe this an overhead because of Rosetta. If I set to load all samples upfront (“Force enable all slots”), as I have enough RAM, the system CPU time comes down significantly, on both Intel and AS, but most visible on AS.
 
Last edited:
Top Bottom