Feature Request : Total Steps & Steps per Measure assignable per layer per pattern

[mattfaisandier]

Firstly, infinite gratitude to the creators.

In my experience I've noticed that Stochas confines a layer to a set duration (total steps) and meter (steps per measure) which is then global for that layer across all 8 patterns. This prohibits users from enabling a layer to transform metrically when a new pattern is chosen.

I feel the creative potential of this tool would be significantly enhanced if both the total steps and steps per measure could be assigned to the layer nested inside each pattern.

Can the creators, suitably empowered by the the nuances of the code , see a pathway towards actualizing this request?

[baconpaul]

Thank you!

ahh right so you would have, like, a 16 note 4/4 layer and a 12 note 3/4 layer or some such, each with separate concept of beat and as you switch you get associated changes?

Right now there's not a lot of active development on stochas, alas, but that's an interesting class of idea, and I agree that polymetric sequencers are a real opportunity.

[mattfaisandier]

Greetings.

ahh right so you would have, like, a 16 note 4/4 layer and a 12 note 3/4 layer or some such, each with separate concept of beat and as you switch you get associated changes?

My understanding of Stochas suggests you've described the existing behaviour - pattern changes 'bring across' the total step and steps per measure data configured for each layer. Therefore, each layer is confined to a step duration and steps per measure regardless of the pattern chosen.

I see a lot more versatility in the application if step duration and steps per measure were able to be set per layer, per pattern.

If this request was implemented, here's how I would engage Stochas to facilitate a musical situation.

I would intuit the layers as containers for timbral information (the vertical domain, sonically - highs, mids, lows ) and the patterns as containers for rhythmic complexity ( for eg, pattern 1 being the most simple / fundamental expression of a motif, and pattern 8 being the most evolved / sophisticated ).

For example Pattern 1 Layer 1 might be 4 steps / 16 steps per measure Pattern 4 Layer 1 maybe 18 steps / 16 steps per measure Pattern 8 Layer 1 maybe 18 steps with 12 steps per measure (I think that would be a triplet feel)

With anything and everything in between these nodes.

For now my (volatile*) workaround is to switch between user presets in the FX window (I'm hosting Stochas in Reaper) . Not ideal but a step towards the aforementioned.

*If I fail to save any changes to the user preset before switching to a new user preset the changes are cast into the endless void for perpetuity...

[baconpaul]

right gotcha so basically have step count and division count be independent

very interesting. Like i said there isn't alas a lot of active development on stochas right now but these are interesting ideas for sure.

[rudeog]

@mattfaisandier This is a good suggestion. Right now the architecture of the internals of Stochas is such that layers are a top level concept with patterns being contained within each layer. Therefore, as you have correctly understood, the patterns inherit the steps, time signature, etc from the layer that they belong to. In order to make this change, some internals would need to change. I'm not saying its impossible, but as Paul said, there is not much active development right now (hopefully that will change though). I will suggest a different workaround that may be a little easier:

• Make sure patterns and layers are linked on the settings panel. This means that when you change a pattern it will change on all layers
• Set two different layers to have different time signatures, lengths etc.
• On the first layer, program your notes on pattern 1, leaving pattern 2 blank
• On the second layer, program your notes on pattern 2, leaving pattern 1 blank
• When you switch between pattern 1 and 2 on all layers, it should now give you what you want Obviously this has its limitations, but might be a little more stable than your workaround.