May I add my 2 cents…
Independent MIDI Out - should be prio 1, as for many DAWs it’s perfect usable and (as Kai mentioned) theres a solution for the few DAWs that can’t handle.
Independent Audio Out - would be perfect to route to different DAW channels and process FX outside the Scaler"Verse" - might be easier than “duplicate scaler”?
Multi MIDI Out - nice to have, but more experimental to my taste
And here’s an additional wish
Maybe there’s a way to route MIDI Out from the VST loaded in Scaler… This would be a way to load an arpeggiator vst inside Scaler and trigger an instrument track.
An alternate solution would be to create a vst chain inside Scaler (like Plugin Buddy does).
Whatever you guys do: Scaler is awesome as it is now, and really getting even better with S3. Thanks!
@davide, Of that list I’d say Independent MIDI Out is the most important (even though Ableton can’t use it).
In Scaler 2 I make extensive use of Sync. I’m excited to have only one instance of Scaler driving several DAW tracks but I wonder if you should keep the Sync functionality in S3. It would help Ableton users and also allow folks to use S3 in the same way as they use S2. Although I expect Sync would be a PITA to add to S3 at this stage!
Something not on the list that is worthy of consideration is the ability to chain two or more instrument VSTs in the same Scaler track. The reason to do this is the existence of various VSTs that generate MIDI, like arpeggiators and similar. You could also have a mode where the instruments are in parallel so one Scaler track can play two or more VST instruments simultaneously, in a “stack”.
These are all just suggestions. It’s hard for a dev to cover absolutely every use case.
And I’m amazed Ableton have not improved their MIDI implementation. It feels like a relatively simple task to support MIDI channels properly.
I think ideally to suit most would be to have a choice of midi out on or off and if turned on select which channel 1-16. So a button within Scaler on each track, I’m not a programmer so I don’t know how difficult it would be to implement.
Welcome to the forum @Danuto and thanks for the input. I agree.
That’'s exactly what I am thinking, but it seems overwhelmingly that Independent Midi Out is a huge ‘want’ from our users. Syncing at least Section C across instances is important to me but I think moving it to a post release priority and seeing how users use S3.
Yep, there’s a three dot menu on each track. Midi Out Channel X / Off. We just need to think about the main track as that outputs to all at the moment.
If Scaler 3 will be unable to send different patterns to its different internal tracks, and if the sync feature will be removed, I think I’ll never use this feature/release because I currently use multiple Scaler 2 instances to send DIFFERENT patterns, and often different note-ranges, to different plugins, something that is mandatory due to the different note-ranges of instruments
For example, the note-range of a trumpet is totally different from the note-range of a synth, and a pattern suitable for a trumpet can be unsuitable for a synth: I don’t know if I explained it correctly
You’ll still be able to duplicate Scalers, we are planning on having independent midi out and you can add any modifier / transposer after Scaler. We just need to prioritise for what the majority would want and ensure a good environment that works. Minor workarounds are ok for me because if the noise is there to introduce something we can respond quickly post launch. Time is precious right now!
Super cool!
The MIDI editing is a game changer that will boost the boring fixed banks of most plugins I have and use live (that is, without editing in my DAW after)
Great news. I think the MIDI editor is very useful and easy to use.
I think the price for the Scaler 2 owners is fair.
I’m glad with this new Scaler 3 capabilities.
Hello, I like that you have improved the editing of notes in the pianoroll and can use the modifications as new presets.
But, however, you do not fall into the situation that each user could use their own presets in the event that a midi file could be imported!!!
And I don’t want to be annoying or obsessive neurotic, but can you tell me if you can create note by note a small passage in the stacato style, or in any other style by painting each note one by one? Using your motion presets seems great to me, because I think they are all very good!!!, but please create the function of being able to import a small midi and thus, you can save a lot of time without having to paint them in the pianoroll!!!
As you already know, there are millions of midi files created as riffs, arpeggios, base lines, etc, etc… why not be able to use them???
On MIDI editing it’s excellent that you can drag individual notes around and that they go red to show you are no longer “in chord” but is there a way to constrain the notes to the chord/scale, either by snapping to them or changing colour when they match? I quite often manually edit S2 phrases after dragging them into the DAW and the most common edit is to change the last couple of notes in the last phrase so they go up instead of down (or vice versa) so I usually want them to still be notes in the chord.
This is unresolved for me. We’ve talked about this at length, one solution was to show the chords in the background and be able to fold the view to the scale. Another was to allow users to attach to a key and then it will transpose by the same amount the chord does. What happens before release and post release is a tight call!
We have a user track coming soon. If we do allow a midi import at launch it will be non-responsive in that it won’t latch to the chord track. The mechanics in Scaler are live and it’s not as easy as importing and tagging. It needs to consider many things. We we may have MIDI file import at launch, certainly one onto the user track but I don’t want to rush this aspect when there’s so much other stuff going on.
I just saw the next update video, with the news and the pricing.
Will the actual pricing be revealed on PB at some point? Because currently, the pricing is as shown in this screenshot. And that is not the just announced 29 USD. Unless this is an oversight.
Also… will we PB users that have to upgrade via PB still be able to “move over” to ScalerMusic? No mention of that in the last video. Only in this thread.
.
Technical question for you folks:
Was Scaler 2 dependent on certain GPU routines from a certain OS version? Or was there a minimum GPU requirement? Scaler 1 is lighting fast on old OS versions (think Win7, Win8), Scaler 2 on the other hand is excruciatingly slow usability wise (Win7 especially). The UI is also not smooth in terms of animation on a 10th gen i9 on Win11 with a GTX1080FE (no changes to the visual settings). Yet the CPU load is below 10% (my old 1st gen i7 rig) and 2% (my 10th gen i9), and there doesn’t seem to be any RAM bleeding (RAM usage is pretty much capped at 280MB). Hence my question. Also as sanity check.
I currently shrug this off due to the “attached code” that was originally never planned for Scaler 2. I really hope this is not an issue on Scaler 3 though.
I don’t know your specific case, but using and testing many different DAWs in the past, I realized that the problem was almost never Scaler, but the plugins (notably sample-based ones) that waste a lot of RAM and/or CPU
Sorry, can’t confirm this one. Especially since I ran Scaler solo. Either wrapped in NanoHost, Cubase (10 or 14) without anything running in parallel, or MuTools Mulab with a direct connection to the output. The culprit is Scaler 2 itself.
I found out that Scaler 2 definitely needs the AERO environment on Windows 7+ (Aero/Metro Hybrid on Win10+). I have two profiles on my i7 (1st gen) rig - one where AERO is turned off, and one where it’s active (because Steinberg DAWs insist on AERO). In the “non-AERO” mode, Scaler 2 legit runs in about 5fps on all sub-windows. On the other profile (studio profile), most of the UI is usable - albeit a bit slow (think about 10fps-ish, and switching between windows takes about 2-3s). Unless I use the EDIT window, then everything comes to an absolute crawl and clicking on just one thing there results in 10s loading times each time (feels like 3-5fps!). The Settings Panel is also really slow, no matter the active window.
On my i9 (10th gen) with Win11, I still have have choppy behavior of the UI… most notably the Settings Panel and once more the EDIT window. This is also apparent in the Scaler 2 Course videos – and those were made on macOS. But the general usage is definitely more enjoyable and feels like running at around 20fps at least.
Before you ask: I tried VST2 and VST3, there is no difference. Both CPU’s are massively overclocked (by 700-900MHz!), there is enough RAM headroom on both rigs, GPUs are “over-spec’d” for what I actually use them for (GTX760 in the i7 rig, GTX1080 in the i9). Scaler v2 doesn’t exceed 285 MB RAM, even after using it for 30+ minutes. The CPU usage is going a bit nuts on the EDIT window though (and only there!).
It’s legit frustrating. And I hope this is not the case for v3. Hence me asking if there are/were “special routines” needed - CPU, GPU, OS Graphics engine, etc.
