XOR Userforum

Full Version: User scales
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6
Would be great if there is a way to limit note inputs to a pre-defined scale. Per-track would be ideal obviously, but per-project is also a great start!

User defined scales would be added awesomeness Smile.
(04-19-2019, 06:38 PM)shankzz Wrote: [ -> ]Would be great if there is a way to limit note inputs to a pre-defined scale. Per-track would be ideal obviously, but per-project is also a great start!

User defined scales would be added awesomeness Smile.

Yeah, on the list already (as it was requested several times Wink )
(04-21-2019, 07:47 AM)XORadmin Wrote: [ -> ]
(04-19-2019, 06:38 PM)shankzz Wrote: [ -> ]Would be great if there is a way to limit note inputs to a pre-defined scale. Per-track would be ideal obviously, but per-project is also a great start!

User defined scales would be added awesomeness Smile.

Yeah, on the list already (as it was requested several times Wink )

Lol, yeah I should have searched better before posting. Count me in as another vote. I guess Smile.
This is the only thing missing for me atm! That and random sequence generation.

I used leafcutter John's tracker for max msp before getting the nerdseq and miss my max msp tables filled with all sorts of scales. I only now realise how bad I am at composing melodies without locking notes to certain pitches...
I know you have a lot on your plate, but I too am very excited for user defined scales, or at least the ability to transpose in key with tables. It would be so lovely!!

+1 from me for sure Angel
(08-12-2019, 01:33 AM)spilthyfred Wrote: [ -> ]I know you have a lot on your plate, but I too am very excited for user defined scales, or at least the ability to transpose in key with tables. It would be so lovely!!

+1 from me for sure Angel

Can you explain 'transpose in key with tables' please?

I think they are also some things unclear about scales.

1 - Notes would play quantized in the selected scale ( Note is being quatized automatically to the next closed scale note)
2 - Only scaled notes (with the selected scale) can be selected when editing in the pattern screen.

This all regardless any user scales..because these will be only a part of the possible scales.

And i didn't start about very exotic user - scaling to allow microtonal notes yet.

So how do you have these things in mind and more interresting...how should they fit into the user-interface/workflow.
I am not quite sure how to think of user-defined scales. I see three different ways this could work:

1) Notes are limited to a given scale. If you select C-major, you can only input C, D, E, F, G, A, and H. I can see this as somewhat useful, but perhaps not super critical, as you could always look up the scale elsewhere.

2)  Notes can be transposed in scale, meaning that if you are in C-major and start with C-E-G, then transposing up by two semitones gives D-F-A. Importantly, it changes from major to minor, because D-minor is the second chord in the C-major scale. I can see this as being super useful, for example for arpeggios, with an external way to do the transpose (e.g., using CV in).

3) It selects notes randomly from a given scale, so when it randomly picks a note, it picks from this scale. It would be particularly useful, if it could then increasingly focus the choice on the more salient notes (root, third, fifth), similarly to when the "steps" function in Marbles is turned CW.  

All of this may be more important as more generative features are added (using CV-inputs and random) since it then becomes more important to keep it in scale.
(08-17-2019, 02:00 PM)XORadmin Wrote: [ -> ]
(08-12-2019, 01:33 AM)spilthyfred Wrote: [ -> ]I know you have a lot on your plate, but I too am very excited for user defined scales, or at least the ability to transpose in key with tables. It would be so lovely!!

+1 from me for sure Angel

Can you explain 'transpose in key with tables' please?

I think they are also some things unclear about scales.

1 - Notes would play quantized in the selected scale ( Note is being quatized automatically to the next closed scale note)
2 - Only scaled notes (with the selected scale) can be selected when editing in the pattern screen.

This all regardless any user scales..because these will be only a part of the possible scales.

And i didn't start about very exotic user - scaling to allow microtonal notes yet.

So how do you have these things in mind and more interresting...how should they fit into the user-interface/workflow.

I don't think it would be completely necessary to have the notes that are played be quantized after imputing a pattern. I feel like that would be sort of messy somehow.

I do think that it would be best to be able to select notes within a selected scale while editing within the pattern screen as you mentioned. This would make editing patterns and melodies much more efficient.

There could be a list of common and maybe some uncommon scale types to choose from, and then the user would select the root note.

As for user defined scales, the user could simply select any number of steps/intervals out of a choice of twelve steps in series - and then select the root note.

As mosorensen mentioned, this all becomes much more useful when transposing patterns and making arpeggios:

My understanding is that tables can be used to transpose melodies and to create arpeggios, however it often leads to stepping out of key when a 'straight semitone transition" takes place. So if there was a key set in place, then that would mean 'transpose up one' would move to the next note in the selected scale, 'transpose down three' would move a note down three steps and so on. This would be amazingly helpful in creating generative melodies that stayed in key.

The usefulness of scales also applies to using parameters like random. If you could randomize a note to jump up or down to another note in a selected scale would be awesome. To maybe also have a way to set a window of steps within the scale that the random parameter would step to would be even more awesome. This coupled with a probability setting for when this random stepping would occur would make generative synthesis a breeze Cool.

.

It would be an added bonus to somehow be able to toggle whether or not the chosen scale was being imposed, so that when editing a pattern, one can occasionally add notes that aren't  in the chosen scale still --- and a toggle would possibly allow for some fun experimentation while arpeggios were being generated. Who knows, I am speculating at this point. Hope this all helps..
I’m unsure of limiting note input to a scale. Any music software I can think of applies a scale / transposition after the note information. This way you can change the scale and the notes adapt accordingly.

But maybe there’s a way to do both?
(10-03-2019, 02:57 PM)Kid Yoshi Wrote: [ -> ]I’m unsure of limiting note input to a scale. Any music software I can think of applies a scale / transposition after the note information. This way you can change the scale and the notes adapt accordingly.

But maybe there’s a way to do both?

Agree, it would be cool to be able to apply scales as fx or maybe project wide, keeping it nondestructive.
Pages: 1 2 3 4 5 6