Please forgive me devs if I speak blunty, but my general impression is that SC3 doubled (or quadruplicated, or even worse) the number of clicks/processes needed for everything, even the simplest things
That, added to the several GUI items difficult or impossible to spot/read, makes the upgrade not very inspiring to me
It feels like they released it a bit early and that they have been taken by surprise by the number of users who wanted features that are not yet there (Sync being one of the biggies). But if there is one thing we know from Scaler 2 itâs that the development of Scaler 3 will be ongoing and will bring many big improvements and additions over the next few months and years.
I just hope that Davide and the team can keep their sanity over then next couple of weeks because we can be a demanding lotâŚ
Iâm currently using the trial version and when it runs out I will probably hold off buying S3 for at least few months. Iâm very much in the groove with S2 and S3 at present does not bring very much more to my particular party. I may end up upgrading to S3 on iPad, where the multi-track stuff is more useful to me and the UI layout makes more sense, and sticking with S2 on PC.
Sync was just one example and this is probably the wrong thread to discuss it but, since you ask:
It Spreads the CPU load
One click stem mixdown
Access to DAW built-in FX (this is a major one for me)
A more comprehensive mixer
Sidechaining
Instrument combining/stacking
S3 now effectively contains a âmini-DAWâ but it can never be as comprehensive or flexible as the mixer in a full-blown DAW.
Donât get me wrong, itâs a great addition to S3 but itâs not always the best solution.
The other reason Sync is important is for Ableton users due to the shortcomings in Abletonâs MIDI implementation.
Another reason is auditing: testing various combinations of patterns and plugins in the arranger is just impossible, because if you change the idea about the patterns/instruments in a track you must delete the track and remade it: a big waste of time and patience
I am also dissapointed that a sync option is not implemented as an alternative and was also hoping for a way to route midi like unify can, maybe it will come.
Thanks for that, itâs helpful to understand the different workflows people use Scaler to support.
I have predominantly used Scaler in Logic in the past but, since picking up a Move, have been increasingly doing things in Ableton - and struggling a bit with the midi implementation.
I have been really enjoying the arranger in Scaler 3, but I tend to use it to pull together ideas, or build out an idea from the Move, and then drag the midi into Ableton tracks to progressâŚ
Yes, indeed, always useful
I also tried a no-DAW workflow, and I was close to it thanks to Cantabile Solo, but it doesnât swallow my UJAM guitars, so I was forced to come back to Bitwig, one of the few able to sand-boxing plugins, so virtually unsinkable
Iâd agree with some of this⌠and for sure, take what I write with a grain of salt, as most folks seem to love the new release⌠and note that I havenât read the manual yet (as the colouring is difficult to read and the âheadingsâ and other structural elements are often missing.. and the diagrams are sometimes unclear)⌠but anywayâŚ
The interface design is sort-of confusing and almost unusable, specifically:
The âChord Setâ is a âdouble-selectorâ of sorts, in that if you donât use the â1 octave keyboardâ selector, the âsectionâ selects both chords AND key, so for that functionality, itâs sort of in the wrong place; maybe you want to play something in a specific key.. but as soon as you go away from the keyboard selector, the keys are changing in the âChord Setsâ.
Many will see the âall blackâ interface as âcoolâ but itâs often unusable, as itâs not easy to discern the object âdividersâ; this means exclusive radio button options are not clearly different from what should be checkboxes. Basic theming is something that needs to be incorporated fairly swiftly.
In a similar vein, some objects that select numbers are using left/right âbuttonsâ (as â<â and â>â) when selecting octaves.. .but the tempo selecting is a clickânâdrag thing⌠AND is vertical instead of horizontal.
The âpagesâ (tabs) (in particular) and the interface (in general) needs more âtool tipsâ or actual labels so that people new to the application donât have to âpress a button without knowing what it will likely affectâ. The labelling of âtoolsâ is again, pretty ordinary throughout the interface. The âaddâ (â+â) button in the âArrangeâ âtabâ is unlabelled and who knows what it does? âŚuntil you tap itâŚ
More on the âaddâ in âarrangeâ⌠The concept of a âmotionâ is inconsistent and confusing. In âarrangeâ itâs like another âvoiceâ or âtrackâ in the âarrangementâ, the sound for which you can only change within the âmixerâ⌠but when working with the âMain Trackâ anywhere in the interface, a âmotionâ is actually an articulation, how to play the notes and is not a separate track.
Basic interface design is wanting too.. in that in some cases you have to clickânâdrag an object to a space.. but in another place, you need to double-click on something to make it âstickâ.
In short, the âphysical usabilityâ (not the âmusical usabilityâ) of the application is really pretty ordinary.
This was my takeaway as well. Tooltips are critical for this UI - there are so many buttons and gizmos that I really did not know what I was clicking on.
Took me about 15 minutes to figure out how to add a track in the arrangement area.
The main tabs are also a huge disappointment. Tiny unintelligible icons with no textual elements at all. I really have to study these to âget itâ.
Lots of fine tuning to be done to the UI if this is to gain some long-term fans
I think the tooltip setting is included in the presets so if you turn it on, âsave as defaultâ then never recall a preset it should stay on. But it makes no sense for it to be stored with the presets. And, yes, it should probably be on by default.
Another bizarre âsave as defaultâ (that seemingly occurs all by itself) is the use of a third-party plugin in Standalone mode if the user - god forbid - decides to save a Preset.
Not only did I not know about âsave as defaultâ - this scenario REALLY expands on what gets saved âas defaultâ - so much so - that I still cannot open Scalar 3 standalone without a hard crash.
Not to sound stupid but how do you increase the size? I have looked everywhere but no luck. With the 3 screens or sections on top of each other the general size is difficult for me to see. I may get use to the workflow if I could see it.