Thanks Andreas! I downloaded the update and I tried it out. I notice that there is perhaps a difference in performance between the stand alone player and the Logic Pro plug-in. Is this a possiblity?

Yes, multithreading is always enabled for the Standalone Player - but it must be enabled when using the plugin (under Settings > Engine)

For me the newest update of the standalone synchron piano player re-introduced CPU spikes that were also there in a much earlier version.

I'm on a M1 Max Macbook Pro 14''.

I downgraded to the version before and the spikes are gone. (They manifest as short noises).

Maybe it's just on my system...

Hi MichaelT,

That is strange. Do you remember the version that showed these spiked?

Could you please send us some reproduction steps or post a video of what you are seeing?

After trying this version, I have to agree with Michael. I'm experiecing way more spikes as compared to previous versions 😞

Hi JaviAV,

Unfortunately I didn't hear back from @MichaelT, but we'd like to find out more.

Would be great to get a quick video from you that shows what's going on, with the standard information about your setup!

@JaviAV Best sent including detailed documentation via email to support@vsl.co.at to discuss the cases internally.

Dear Paul

sorry to not coming back before, quite busy at the moment...

I already went back to the previous version, so I can't say exactly what version produced the spikes, it was just the newest update that was offered in the updater in mid April.

I'll go back to the current version at some later point and will report if it happens again, just can't do it at the moment, because I need to do some recordings and don't have the time.

Kind regards, Michael

@Andreas8420 said:
@JaviAV

Are you on a Mac as well and is everyone running the plugin inside a DAW?

Best,
Andreas

Hello

Here are some tests

===

Computer = 2019 13-inch MacBook Pro, Core i7 (2.8 GHz quad core), MacOS 12.7.1, 16 GB of RAM, external Samsung T7 SSD

---

Interface = RME HDSPe RayDAT inside a PCIe/Thunderbolt case

Sampling rate = 48000 Hz

HW buffer = 64 samples

---

3 stereo microphones: Tube, Mid 1, Room-Mix

Max Voices/Mic = 128

Max Voices/Key = 12

Synchron Pianos version = 816

===

Test = pedal depressed, playing clusters and glissandi at maximum speed and listening to "clicks" (unwanted artefacts because the CPU cannot process the sound fast enough)

===

Abstract (see below for details):

- Synchron Pianos Standalone is the worst

- Using Synchron Pianos inside Pro Tools helps but is not enough (even with Vienna Ensemble)

- Using Synchron Pianos inside Vienna Ensemble Standalone can help

- Using Synchron Pianos inside Vienna Ensemble inside Reaper can help

- Closing the Synchron Pianos UI often helps a lot

- There are three configurations that really work on this computer

- There does not seem to be any difference between multi-core and single-core mode

===

Vienna Synchron Pianos Standalone (multi core)

> clicks

---

Vienna Synchron Pianos (multi core) loaded in Vienna Ensemble Standalone

> less clicks; lots of clicks if the Synchron Pianos UI is displayed

---

Vienna Synchron Pianos (single core) loaded in Vienna Ensemble Standalone

> maybe more clicks than the previous configuration, but this is not night and day difference

---

3x Vienna Synchron Pianos (single core), one for each microphone, loaded in Vienna Ensemble Standalone

> no clicks; many clicks if the Synchron Pianos UI is displayed

[working configuration]

===

Vienna Synchron Pianos (multi core) loaded in Reaper (v6.83)

> clicks (less than when using Synchron Pianos standalone); lots of clicks if the Synchron Pianos UI is displayed

---

Vienna Synchron Pianos (single core) loaded in Reaper

> clicks (exactly the same as the previous configuration)

---

Vienna Synchron Pianos (multi core) loaded in Vienna Ensemble Standalone loaded in Reaper

> no clicks, except sometimes if the Synchron Pianos UI is displayed

[working configuration]

---

Vienna Synchron Pianos (single core) loaded in Vienna Ensemble Standalone loaded in Reaper

> no clicks, except sometimes if the Synchron Pianos UI is displayed

[working configuration]

---

3x Vienna Synchron Pianos (single core), one for each microphone, loaded in Vienna Ensemble Standalone, loaded in Reaper

> no clicks, except sometimes if the Synchron Pianos UI is displayed

[working configuration, but this is useless]

===

Vienna Synchron Pianos (multi core) loaded in Pro Tools Ultimate (Version 2022.5.0)

> rare clicks (less than the VST running in Reaper); slightly more clicks if the Synchron Pianos UI is displayed

---

Vienna Synchron Pianos (single core) loaded in Pro Tools

> rare clicks (less than the VST running in Reaper); slightly more clicks if the Synchron Pianos UI is displayed

---

Vienna Synchron Pianos (multi core) loaded in Vienna Ensemble Standalone loaded in Pro Tools

> very few clicks; worse if the Synchron Pianos UI is displayed

---

Vienna Synchron Pianos (single core) loaded in Vienna Ensemble Standalone loaded in Pro Tools

> very few clicks; worse if the Synchron Pianos UI is displayed

---

3x Vienna Synchron Pianos (single core), one for each microphone, loaded in Vienna Ensemble Standalone, loaded in Pro Tools

> very few clicks; worse if the Synchron Pianos UI is displayed

@Andreas8420 said:

@Andreas8420 said:
@JaviAV

Are you on a Mac as well and is everyone running the plugin inside a DAW?

Best,
Andreas

Hello Andreas. Yes, on a M1 Pro MacBook Pro running Logic X. How would you like me to report the issue? It's essentially when playing repeated cords in Chopin's prelude in E-minor. In previous versions, the CPU would choke occasionally. Now, where you would expect some improvement, the CPU chokes even earlier while playing the piece!

@JaviAV

Does the choking only happens when the host (sequencer, DAW) no longer is in focus, but in the background?

Hi Andreas. It seems to happen much more prominently when the actual plug-in is not at sight i.e., the VSL piano plug-in isn't being displayed. Any thoughts what may be causing this?

Latest update (May 17th) seems to have fixed this problem for me, thanks VSL!

Indeed! Runs much better, thank you!