194,434 users have contributed to 42,921 threads and 257,969 posts.
In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 71 new user(s).
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,
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,
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
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
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.
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.
I notice one of the two fixes in build 1529 just now was some release characteristic, oddly enough as I first noticed it after updating to that (have rolled back at least once). That's coincidence & not necessarily cause. But it strikes me as something crazy happens on release (albeit not strictly limited to such). Updating and will see again.
This is definitely one of the weirder things I've experienced in this.
For instance in the standalone, not connected to my system on the other side of the room, using the onboard of the MBP with its speakers, there is only normal behavior. Except, weirdly, some of the notes in the bottom octave have a release characteristic of a semitone fall which I had not noticed before. Updating back to 1529 now with fresh library files.
Oh, stupidly I have left out that this is in VE Pro 7.0.1056, connected variously to those three versions of Cubase Pro 11.
Has been the case in more than one project now.
I think at this point it's only going to change in projects like this with better cores distribution, because in isolation/the standalone it doesn't occur. It's fighting and losing a battle with other things in a VE Pro project with reasonably playable latency. Def significantly more frequent an occurrence here with duplicated channels of one mic each, or the mics selection has no impact really; the overload factor is multiplied.
I also get crackles, evaluating the Imperial and Steinway D on demo licenses, first time running Synchron Piano Player (stand alone, no other applications running).
The Sync Piano Player CPU meter shows a lot more CPU activity than the system CPU monitoring tool, which shows very little CPU load and low temp. Quickly playing around with buffer sizes and delays, crackles persist.
Win 10, Amd 5800X, 32 GB RAM, SSD, RME HDSPe AIO Pro.
Having a hard time deciding between the Bösendorfer och Steinway before the sale ends, a player bug doesn't help. Any news on the problem?
