Wtf with Corpus ? (v11.1.5)

[VT2]

Just recently install Live from scratch (v11.1.5), and found strange issue with Corpus - he works only till sound is active at track (and exactly if we put it to already playing track). But it stopped works after press stop in transport and press play again.
As well, if we put Corpus to track in stopped transport state, wait a little, and press play - he do not do anything (just does track as muted).
What is that ? It's just for me or no ?

Win10 latest here.

[Rivanni]

Corpus stops producing sound when the buffer size is set to a high value (greater than 1024). This is a known issue that is fixed in the current 11.2 beta.
In Live 11.1 5 the only thing you can do is lower the buffer size.

[VT2]

Corpus stops producing sound when the buffer size is set to a high value (greater than 1024). This is a known issue that is fixed in the current 11.2 beta.
In Live 11.1 5 the only thing you can do is lower the buffer size.

Oh damn. I actually use 1024. My main buffer value for years lol (that usually suitable for heavy spectral processing plugs).
But glad to hear that it fixed, thanks for that.

(Did check at 512 - yes, it works).

[VT2]

Decided rollback to 11.0.12 again yet, and no probs here, Corpus works at 1024 just fine.

Moreover, preliminary it seemed to me that Corpus sounding a bit better in this version, like his effect here more pronounced. But, this is may be some illusion, i not sure. Anthough, not exclude that this error with buffer does somehow impact to his general processing character, who know.
Perhaps, will make some test records, before update to next build again, when it will released.
Just, this effect one of most interesting thing in Ableton collection in my opinion. I use different DAWs, but sometimes back to Live, literally because this.

[chapelier fou]

It's supposed to be fixed in the latest Beta.