183,203 users have contributed to 42,282 threads and 255,007 posts.
In the past 24 hours, we have 5 new thread(s), 20 new post(s) and 68 new user(s).
Hi,
We had to fix a serious bug in that version, but you should not get worse performance because of that (should in fact be a little better now).
Have you altered the streaming settings? If so please change the settings back to the default values -> Settings -> Engine:
- Streaming Threads: 4
- Loading Threads: 4
Best, Ben
Just thought I'd add that I also had the crackles and strange cut outs after updating to the latest version 1.1.1518. I noticed that it wasn't that bad or noticeable while playing without the sustain pedal but as soon as I started using the pedal I got immediate cuts in audio and CPU spikes to 100% (normally never goes higher than 40-50% on my i7).
I am also using the Steinway D and tested with the presets 'player surround to stereo'.
Rolled back to 1.1.1508 and the issues were gone, great that we have the option to go back so that helped.
I did not have time to follow up on this until today. I've installed the previous version. With about half an hour of playing the problem appears to be gone.
Definitely something not right with the latest player update and going back a version resolves the problem for me.
For added context I'm using Bösendorfer Imperial full.
I've had the same problem. Without changing any settings on my computer, the update caused performance problems running the same patches. I switched back to the previous version (1.1.1508) and all is right with the world again.
What was wrong with the previous version that it needed to be updated?
God Bless,
David
Same issue here. The piano is now unplayable. I have peaks even when playing a major triad!
I managed to reduced the CPU level to something manageable by settings the streaming and loading thread to 4 and also setting the Preload Size to 16384. I still have peaks to 80% when playing a lot of notes. Also with 2 mics position I set the max voice per mic at 64 instead of the defat 128.
May I ask, does this issue only occur once after starting the player, or does it occur over and over again while playing?
How many voices are approximately used when the peak occurs?
Thanks,
For me personally, the issues occur often over and over again while playing on the latest 1.1.1518 version.
On every other version I notice that when opening the Synchron Piano software that it spikes to 100% just once which is normal. It also spikes like normal when opening on 1.1.1518 but then continues to spike whilst in use.
I always use 128 which is the default and have left everything else as default.
Regards,
Bit of an aside, but still performance related.
Some larger preload options would be very welcome. 64gb-128gb ram configurations are very accessible these days. I imagine most of us are happy to focus system resources on improving the live playing experience, If ram helps at all, let's use as much as possible.
Since I am now clicking the donât update button each time I run the player. That means I am very likely to miss the update that fixes the original problem but does not then create the issue discussed here.
Could someone from VSL post in this thread when there is a new update. I would greatly appreciate it.
TIA
Hie Ben,
I have the same problem whith lot of crackles since I have updated my system : windows 10 20H2, Synchron Pianos v.1518.
My config : Windows 10 (20H2), Intel i9 10900K, RME Fireface, RAM 32 GB, all SSD drives.
I switched back to two previous versions (1.1.1508 and 1.1.1496), but I have the same problem (screenshot attached at this post). I think the problem is windows and the last update, I don't remember having had the problem with version 1909...
The piano is actually unplayable...
Could you send me the download link to the beta build ?
Thanks !!
Fred.
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
