Scaler 3.2 / Standalone Win extreme latency upon chords playing

Scaler 3 Support Bug Reports
1

Hello,

I register this as a bug as it’s way beyond any comparison with 3.1.2 : playing chords either from the chord set or current scale selection is horrendously lagged and slow (whatever rhythm I could play before vanishes into some FIFO queue to be played seconds later (!))

No source of latency coming from either console input (keyboard or mouse) nor master midi keyboard since individual notes (out of bindings) are rendered immediately by Scaler.

I guess there’s some investigation and optimization to conduct here because waiting for the ultimate rendering is not an acceptable workflow for such a tool.

(also perhaps related : frequent zombie notes occur, requiring ermergency “bang” stop button)

I like the “scenes” feature but for the moment that version is just unusable for me.

Thanks

Kino

1 Like
2

Hi @Kino. To be clear, are you saying that triggering any chord in Scaler 3.2 results in very high latency, whether clicked with the mouse or played using bound notes via MIDI, but playing individual notes results in no latency issues?

Are you only experiencing this latency issue when running Scaler 3 standalone? Or does it occur when running as a plugin inside a DAW as well?

If it is only occurring in standalone, which audio driver and audio interface are you using? And what is your audio buffer size set to? We suggest using the ASIO audio driver option for the lowest latency performance, but you will need to set a low buffer size as well e.g. 256/512 samples or lower.

3

Hello @Tristan,

Thanks for your prompt reply.

I confirm this occurs the same way with the plugin within FL Studio as with the standalone app on Windows 11.

There too, be it from pc keyboard, mouse or MIDI keyboard, featured chords play with extreme latency (up to 1 sec) whereas individual notes a rendered immediately.

For that reason, I think neither the driver nor the buffer size are relevant (but I actually tried to tweak them in vain, for peace of mind).

Don’t you reproduce that behavior on a Windows configuration ?

(because hardly can I imagine that to be related to my platform since it didn’t happen with version 3.1 of Scaler)

Thank you for your investigation

Kino

4

Hi @Kino no sorry I am not seeing any latency issues in Scaler 3.2 on Windows 11 as a plugin or standalone. Would you be able to send us a video of the issue you are experiencing to help us understand exactly what is going on? Hopefully there is an easy fix, but right now I’m not sure what the issue might be.

5

Hello Tristan,

I’ve prepared a short video but the forum’s rules won’t allow video material to be uploaded.

How should I proceed ?

Thanks

Kino

6

Thanks Kino. Are you able to upload to a cloud storage location like DropBox or Google Drive and share the link? You’re welcome to DM me the link if you’d prefer.

7

Hello Tristan,

Here you go : https://drive.google.com/file/d/1Yk75Gzwe1bfrlBLgphTT8IR6cBrLX5RF/view?usp=sharing

Any trouble reaching the content, please tell me.

Thx

Kino

8

Hi @Kino. It looks like you have Latch mode and Play Quantize enabled. Play Quantize is stopping the triggering of chords until the start of the next beat or bar to help with timing, and latch is keeping chords sustained. With latch mode enabled can click a sustained chord again to stop it.

But please try disabling Play Quantize and latch mode in Scaler’s settings. Hopefully this will resolve the issue for you.

9

Holy Cow ! that’s exactly it !

Thanks for nailing this down, Tristan.

K.

2 Likes