Do we really want more instruments in Scaler? I am worried that this will result in bloatware, increased development compexity and cost, for what benefit? I know some users use Scaler as a perfomance tool, but can they not use Scaler with external instruments for these performances?
Having two versions of Scaler (with and without an instrument set) sounds logical, but complex? I leave that to the developers to figure out (I like simplicity in applications: remeber that in trying to satisfy everyone usually results in satisfying no-one).
I see the current set of instruments basically being good for auditioning an arrangement (rather like the Cakewalk TTS synthesizer).
I would like to add one feature, which I have already added to the Feature Requests topic.
I would like to be able to save and import Chord sets with any Edits to the chord set: transposition, inversions, timings. performance playback, which have been set in the EDIT page.
At present there are two options for saving and importing:Save State or Save Chord Set. However if you import a saved state the import is destructive and clears the existing state before importing the new state. Thus any edit or existing chord seta are lost, so it is impossible to add to an eisting project.
Alternatively if you have simply saved the chord set and then import it you can add to an existing project, but there are no edits that may have been associated with the chord set. So if you compose a nice phrase that you want to save, because it does not quite fit into current song you have to save the state to save any edits. I believe that many composers draft several vesions of a phrase before settling on a final phrase in a composition. However they may not completly discard the unused phrases, they can be used in other songs.
The second feature I would like to propose is for the user to be able to programme complex arpeggios or motifs. I realise that this is significantly expanding functionality and may be complex to develop so I see this as a “nice to have” request.