Binding Scaler passage to external piano yields choppy output

Scaler 2 Support
1

Hello,

I have a passage in Scaler that plays properly when the output is routed to an internal Scaler keyboard while binding.

However, when I link that passage to an external instrument (Arturia Piano V) the instrument only sounds for a short moment when I press a bound key.

I have searched the web and the forum and have tried as many variations in Ableton and Scaler as I can come up with.

I imagine this is something simple but I am not seeing it.

Gracias!

2

Hola @kkatzer

Just wondering - is it Scaler 2 or Scaler 3 that you mentioned (I suppose S3, but want to be sure in order to put it to the right category). Like this, maybe some other Ableton users could help you.

Also, is this Ableton on Windows or Mac and which version?

3

Apologies for the ambiguity.

My configuration is:

Scaler 3.3.1

Ableton 12.4.3

Windows 11 Home edition

4

The set I was running when I encountered this problem was a test set and it has been deleted.

But, I recreated a similar issue in a different set.

The chopping audio may have been due to an instrument overloading my CPU.

I have a simple set with five tracks.
The tracks are all built inside of Scaler 3.
All of the tracks reference non-Scaler instruments (Kontakt, Hive…).
One of the tracks contains an instance of the SkyDust Stereo VST. It appears to be the problem.

When SkyDust runs within Scaler 3 the CPU spikes above 100% and the audio is chopped up.

When I move the SkyDust instrument out of Scaler and into Ableton the set runs around 55% of CPU usage.

I imagine that is what was happening before.

Either the Sound Particles folks are not prepared for their device to be housed inside another VST within the DAW or the Scaler folks missed something in the way SkyDust behaves.

_______________________________________________________________________

I don’t believe it is a resource issue on my system, but weird is part of the computing world.

My PC Configuration is: Intel 13th Gen i9 Processor, 128GB RAM, 8GB graphics card.

All of my plugins are up to date.

5

So… my solutiion (which is obvious) was:

  1. I set the Scaler track that had used SkyDust (A) to use an internal Scaler instrument.

  2. Then I created an Ableton track with SkyDust (B) as its instrument.

  3. Then I routed the MIDI channel info from the track which formerly house SkyDust Scaler (A) to the new Ableton track (B).

After that the set behaved.

I would still like to know why SkyDust housed inside of Scaler 3 brings the house down, but in the end I would have moved the instruments into Ableton anyway so it is really no big deal.