I have a project with 145 chords in the main track, divided into 21 scenes.
Now I would like to add an additional instrument/sound for each scene — is it possible to implement 20–30 divisi tracks within a single project, or are there any limits on the Scaler 3 side?
Hi Tom, I think so! There are no limits in terms of track counts but dependent upon your DAW hosting/standalone there will be various CPU limitations of course! Lets us know how you go!
In my current project, which is about 80 MB in size and contains 23 tracks (1 main, 22 divisi), I’m now starting to hit some limits.
Scaler 3 (standalone) sometimes responds very sluggishly and with noticeable delay.
I’m working on an Intel Core i7, 7th generation…
…export as a wav-file / 32bit / 44,1hz, anti-clip needs about 390MB space.
I have no idea if this is much or “normal”, but if I want to add some more sound-highlights I think I have to try it on Ableton (import wav-file), an then add some more tracks!???
Hi @TomiGotchi Are you hosting third party instruments within Scaler 3 / with your DAW? If so you are putting the load on a ‘Live Channel’ within your DAW and not using your multi-cores and if that’s the case you are best to you use the MIDI out to take advantage of your DAW multicore spread.
Unfortunately, my DAW only allows a maximum of 16 tracks, so I would prefer to implement the entire project in Scaler.
In Scaler, I mainly use sounds from Soundbox, some of which themselves consist of up to four layers.
It would be good if I could find a few options to reduce the load on Scaler and free up some headroom for additional tracks.
Yeah the problems with DAW architecture is in ‘Live’ mode (when you are using a single DAW track) it does not spread the load across cores and only uses single core performance. That’s not something we can address. It’s the same as using Kontakt with 16 instruments on a single DAW track. What happens if you save the preset within Scaler 3 and then open that preset in Standalone? Does it perform better?
I probably didn’t express myself completely clearly — I am using Scaler 3 only in standalone mode, because I simply think Scaler 3 is absolutely fantastic and I’m amazed at how quickly even a layperson can achieve good results with it.
However, now that I have created a project with 23 tracks, mostly using instruments from Soundbox (which themselves consist of up to four layers), and I’ve reached a limit with Scaler 3, I’m looking for options.
Before opening a project, I always delete the “settings file” and, in between creating, I manually save the project multiple times (under three different names, so that in the event of a possible freeze not everything get lost) — this way I support Scaler 3 in terms of performance.
But I believe that adding two or three more tracks would completely break the project, or make it no longer loadable or editable.
In Scaler 3, you can select sections and simply drag and drop them into Ableton’s arrangement (I’m thrilled at how easy this works)
I can now merge several divisi tracks (which do not overlap in my project) into a single track in Ableton
…which means that, in theory, I can represent the same project with a total of 4 tracks that require 23 tracks in Scaler 3.
This leads to the question or suggestion of whether, in the future, a divisi track in Scaler 3 could be split multiple times, with different instruments assigned to each split.
What I also noticed is that the final product (a WAV file) exported from Ableton is almost identical in size to the export file (WAV) from Scaler.
The conclusion seems to be that creating a divisi track in Scaler 3 consumes a lot of performance, even when the track is only used for about 40–50 seconds across the entire project (total length 18 minutes)!???
Thanks for the investigation @TomiGotchi I haven’t noticed a Divisi track performing any differently to the rest and I haven’t found a brick wall for performance on Standalone but we will do some investigating in the new year based on your notes.