I thought it might be useful to have one thread where Studio One users can share their insights about working in Scaler 3. I’m loving the potential of Scaler 3, but I’ve been encountering a lot of instability problems; it crashes my DAW at some point in almost every session. I’m wondering if others are experiencing this, and if you’ve found solutions?
I’m on Studio One 6.6.4. Here are the crash sources that seem to repeat themselves a lot:
Auditioning motions. Especially bass lines, I get frequent crashes, sometimes as early as the second line I’m auditioning, sometimes the 4th or 5th. Then again, there are occasions I get no crashes.
Adding tracks in the Arrange Page. I’m usually good up to 2-3 tracks. A fourth track almost always crashes the DAW, usually when I hit the play button.
Kontakt 7 instruments can be wonky. I can’t find a consistent pattern, but guitars have been a challenge. I’ve been successful putting various NI Session Guitars on Scaler’s Main Track. But adding guitars as the instruments on subsequent tracks creates a fair amount of system instability.
I’ll add other problems (and solutions!) as I find them. I hope others will do the same. Thanks!
One insight I will add - especially regarding Studio One - is to avoid using AU for any plugin. Not just Scaler 3.
This format is designed for Logic and while yes - it is “technically” supported in S1 - third party vendors rarely (if at all) do any Q&A for any AU plugin within Studio One and even Presonus themselves do not spend a whole lotta time with this format.
This is not to imply that the fine folks at Scaler Music did not perform AU testing within S1 - this is more a known industry thing. Third party plugin vendors will simply not worry whether their AU works in Studio One - but they will REALLY care that it works right in Logic.
VST3 on the other hand is heavily tested in S1 across the board and should be the go-to - whether Mac or PC
Y’know, thanks for this reminder. I’ve always used VST3’s, but for some reason, I’ve been using AU’s with Scaler 3. I’m going to go back to VST3’s and see if this helps with some of the stability issues.
EDIT - SPECIFICALLY FOR STUDIO ONE USERS REGARDING MIDI OUTPUT: As @SonicMojo posted on another thread, USE THE VST3 PLUGIN OF SCALER 3, NOT THE AU PLUGIN. The AU will not allow you to easily export separate midi tracks.
I’m using S1 v7, and it’s only crashed once so far. That was when I opened a song that had Scaler 3 on a track. The same song has opened without error several times since. Using the VST, not AU.
Scaler 3 MIDI performances are not transferred correctly to S1 track usig drag&drop from Arrange page using the ‘arrow’ tool on the Main Track Section. Chords can be dragged. Yet, with performances it works fine from Explore page. (Win10, S1 6 Pro, VST).
Scaler 3, Windows 11, Studio One Pro 7.latest. Crashing almost every time I use Scaler, and frequent sound loses also where I get no sound from Scaler.
I’m even having issues with Logic Pro 11.1. 6 months ago I stopped using my Intell 2016 Mac Pro and bought a silicon Make Studio. Each time I upgrade the Mac OS or Logic Pro version - more 3rd party Audio Units cause Logic to freak out and re-initialize Audio setup. I’ve bought Scaler 1, 2, 3. Each one is a mystery to me. Been watching more videos, learning bits here and there. .
Us ‘old timers’ remember doing music before there was MIDI around. Going on 40-46 years now. It had made making music more complex, but what we can do now is profoundly better than before.
We are running into this non-compatibility issue again. Every app, VST, or Virtual Instrument has its own installation program, 3rd third-party companies in a rabid scandal to make their product ‘unique’ and special.. I liken this to - what if different companies decide to re-design elements of cars. Say, let’s metasize our braking system to be a button on the steering wheel. or be placed somewhere else. We NEED more standardization.
I’m sick of having to learn the sometimes obtuse operation of each different piece of software I use to make music.