Thanks for the offer to help - we'll come back to it as soon as as possible :)

Hi everyone!

I have a beta build ready that should fix this issue. Please PM me if you have this issue with the last release, I'll send you the download link.

Many thanks and all Best,
Ben

Hello Fred,

After investigation, I have remarked that it could be due to a multi process partially / or no correctly well performed.

On my case, if I launch multi instance on cubase (split mic) it's far away better ;) !

Can you check if it improves your issue ?

You have also raise a good point, maybe a windows update has broken someting on processing !

Regards

[SOLVED !!!]

Good evening,

Thank you very much for this trick ... magic !!!

I explain my approach, which will serve as an aid to those like me who have a problem with the "apparent" processor load of the Synchron Piano, and as a point of support for you, dear developers.

I confirm the undeniable benefit of opening multiple instances as you suggest. I performed the operation directly with Synchron Piano and not with Cubase. I opened two sessions of Synchon Piano, and I distributed the mics equally between the two sessions. And miracle: I have no more crackles !!

I noticed, and this confirms an observation made yesterday, that the processor load displayed in Synchron Piano does not correspond to that of the Windows resource monitor: here, the CPU load remains at 1-2% (intel i9-10900K, 32 GB RAM), while it rises to more than 50% in the display of Synchron Piano. In other words, my processor is only used very little. However, when I use two Synchron Piano sessions: - the processor load displayed in the Synchron software is halved, it is distributed between the two sessions. Suddenly, there are no more crackles; - the processor load displayed in the Windows resource monitor has increased: there is a better match between the requested resources displayed and the actual resources.

I am very happy to be able to play my Steinway piano again, the sound is really excellent. Thanks to the VSL team for their work. And thanks to you, dear, "eagle", for your temporary fix before a next update.

Fred.

Hi Ben,

Are you confident that the original issue is fixed and I can update. I am sorely tempted by the new Bösendorfer 280C (I never thought I'd need another Bösendorfer 😛) but I'd like to confident that updating Synchron pianos is not going to return me to constant crackles as described in my original post.

I don't see a mention of the issue that has been a problem for me and a few others addressed in the changelog here: Changelogs . Does that mean it has not been addressed?

Thanks

Kevin

Hi Kevin,

Sorry, I can't confirm at the moment if this issue is fixed - it might be, I have to talk to our devs.
My suggestion is to look up what version you are currently running, testing the update and if it does not as expected please drop us a mail, we can alway send you the latest version that worked for you.

Best, Ben

Hi Ben, Kevin,

I have updated to v1.1.1522 but unfortunately I don't see any improvement about multi-thread support which not works properly.

I still need to launch multi instance on cubase (split mic) to get good performance.

Regards

Hi,

I I have the same problem. I own both Bosendorfer and the steinway, I have a lot of crackles and the sound is not that great.

My config: W10 - Amd Ryzen 5900x - 64GB - Samsung SSD 860 evo - Focusrite 6i6 1st gen

Thanks

Nico

Hi, 

We're trying to find a way to introduce multi-threading to Synchron Pianos / Synchron Player.

It's not a trivial task, and I can't give you an ETA, but we're doing our best, as always. 

The current workarounds: 

- Play live with less active channels and add those channels when playing back / mixing / bouncing. 

- Play with higher latency

Of course, for best performance, very fast SSD drives (best: m.2) with a very fast connection are ideal. 

Best, 
Paul

@Paul said:

Hi, 

We're trying to find a way to introduce multi-threading to Synchron Pianos / Synchron Player.

It's not a trivial task, and I can't give you an ETA, but we're doing our best, as always. 

The current workarounds: 

- Play live with less active channels and add those channels when playing back / mixing / bouncing. 

- Play with higher latency

Of course, for best performance, very fast SSD drives (best: m.2) with a very fast connection are ideal. 

Best, 
Paul

Hi Paul, the same here, seems the problem still persist.
do you have the ETA for multi-threading ? we are still waiting for this important fix, it's almost unplayable sometimes, please help with this.
Synchron pianos version: 1.1.1529 (playing bosendorfer imperial).
My config: WIN 10 pro - i910900K (running on 5 GHz) - 48 ram ddr4 + Firecuda ssd M.2 - Cubase pro 11

Thanks,
Ethan Steve

Hi, 

Unfortunately still no news there. 

What still works for many pianists: Insert multiple instances of Synchron Pianos and activate one or more mic channels in each, this way you are also using multi-threading.

Best, 
Paul 

I've experienced weird and disquieting behaviors of Bosendorfer Imperial for a while. It started roughly around the time of said update, I rolled back which changed nothing. At times, and I cannot discern why a situation would be any different than the other situation here, hitting a single note on the kaybd controller causes it to make a horrendous garbled noise, in degrees ranging from I should force quit everything if not hard boot, to a kind of lingering amount of corruption not very different than not having enough latency. It shouldn't be that, since nothing else is performing that way in this project.

It may do the same from input off a diff controller, but it seems worse with this Nektar 49-key inputting.

total avoidance of keybord input for a piano isn't viable here

Hi civilization 3, 

We will need some kind of reproduction scenario here, best with a recording of what you hear. 

Please send it to support@vsl.co.at, along with your system specs and a sequencer song.

Best, 
Paul

I'm suspecting there must be brief spikes on the first core, after reading this. I'm using like 3 mics in it, I guess I can use more than one instance, I mean I doubt the added instance would be worse if it distributes it better

this did nothing. I don't think anyone needs a project file, by itself it does it.
One note, velocity = 18, very standard settings in the instrument and it clipped like mad a bunch of times consecutively. I have no idea at all why, it starts doing this out of nowhere after average normal behavior.

basic system specs in signature. Nektar SE 49 key controller. Audio interface Presonus Quantum 2626.

Nothing else does anything resembling this, in my life, ever.

at the time I posted I still showed Cubase 11.0.2, same thing happens in .1 and .0.

Hi, 

That's very weird. Did you try to reinstall the sample content, maybe onto a different drive?

Best, 
Paul

Yeah, I've reinstalled, the program more than once, but I don't have different drives. I have as fast a drive situation as there is probably. If it's something like that it doesn't stand to reason that everything else behaves well. This went crazy upon release particularly but it made other insanely loud sounds, some immediately by note-on, some not. I have symp resonance and that kind of thing almost turned off, it's not unusual settings at all. Dynamics at 100%.

So I deleted the additional instances of it and it may be that this was a worse situation, afterwards I was def not getting some wild overload off of a single soft note-on.