Hi all, just wanted to point out Tristan has made a great little tutorial on all the various ways of recording and exporting MIDI within Scaler 3. Particularly useful for those that are new to Scaler 3.
Useful for all of us.
Thank you for spending the time and effort to compose this video but the video itself shows how extremely complicated things are
For example there are two record buttons in this workflow and both look basically identical . I could make any other comments but they will be wrongly interpreted as rude for the sake of being rude when I’m trying to be helpful
I realised tonight
The way to fix the layout is to imagine you’re designing a PHSYSICAL machine
Maybe insert a virtual screen into actual app?
I don’t know but this is not a simple video to follow
At all
And it’s made by the foremost authority on earth
The people who actual create the product
This is why I think typically the iPad version is so much more sophisticated in design and user interface
The design mentality adopted for it is more geared towards thinking in Practical physical terms
I would make whoever is in charge of iPad design in charge of design for the whole of scaler
The thing that keeps coming up for me, in my workflow, is within the gap between stages 1 and 2 of this video. Correct me if I’m wrong in my approach
A chord progression of bound chords is recorded into the DAW.
(This is my go-to way to come up with progressions)
In order for Scaler to be functional in creating more parts, this progression now has to be manually entered into Section C.
(This process breaks my flow)
I feel that it could be a simple function to introduce where the progression is captured by Scaler, in the rhythm that it was performed in.
Scaler 2 allowed for performances to be triggered by the MIDI of these bound chords, but seamingly not in 3