Forgive me if I might have asked this before… but I am interested in figuring out (or feature requesting?) that these options available in section B within a Scaler instance where I already chose a scale…
…are also available for pass through chords, that are fed from a master Scaler. So for example, if I pass through (via MIDI chaining across plugins) a simple C minor chord (Voicing 1), that I can use that secondary Scaler instance, that is being fed this chord, to now interpret it in a different voicing, or make a 7th or 9th chord out of it etc.
I’m a little unclear here @Bernd What would be the difference to dragging it to section C, then editing for a suggestion or even hitting suggest to get different voicing/extensions?
The difference is one of workflow friction…that would require a lot of editing and lead to static configuration that would have to be manually changed.
My approach is daisy-chaining multiple Scaler instances, with a master Scaler providing the core scales or chord progressions, and then subsequent (dependent) Scalers re-interpreting these chords, while staying in harmony.
So the key difference is that as I change the chords/Progressions in the master scaler, I expect the downstream (dependent) Scalers to automatically adapt to these chords they get fed. If I were to edit in each downstream Scaler the section C chords, that would require a lot of editing overhead, and not lend itself to a more more performance style playing. I also didn’t think the Scaler sync feature would address this, since it still requires another manual (not MIDI automatable) step.
Hey I think I got you. The only live ‘force’ mode that Scaler would do is when Keys Lock, Performances etc are on. So the only changing of a chord you could do in your method is playing a voicing and having the second scaler adapt that voicing to a keys lock or performance setting. Not reinterpreting it in a ‘extended’ way which I think is what you are after. Hope it helps even though I don’t think it does!
Thanks @davide , I will have to try that and play around with those options a bit.
I think what I am after is pretty straight forward, and does not even require any scale recognition let alone performances. All I am looking for is for a given input chord to get a different voicing, regardless of what scales that chord might be part of. It is no different than having a chord in section B (loaded from the Scale selection), calling it up there under a different Voicing setting. Not sure if this would be called “transpose”?
Example: input chord is Cmin (C2, D2#, F2) and transposed output could be C1, D2#, F2, C3).
Now that I am describing it at that level of detail, I think I might have just realized that there might be a Bitwig NoteFX plugin to do something like that…will get back on that later, if it works.
A ha. I get it, like a live transposer. Scaler can detect live chords and apply performances etc so actually what you are suggesting is a great idea and Scaler already has that capapbility. I guess you would either select a profile of which one could be random. That would allow limited players like us to play simple triads and get some nice extensions. @Tristan Could you please add this to our dev board and let’s discuss some ideas for it…
