scale values for every cell in matrix?

jit.gen and the scale operator

thanks, Rob!

Alright, I think this is loosely still on topic.

I'm using a matrixctrl object to manage a gates, and have modified the phasor~ based clock (originating from Gregory Taylor's Step by Step book) which is capable of subdividing the bar down to any tuplet up to 128 (at present).

I feel like the logical next step would be to scale (or down/ up-sample) the pattern (column-wise -- quantizing the cell data to the lower/ scaling to the higher, rather than just truncating or extending), which led me here.

I've read through the jit.gen reference and have seen the list of operators under jit.op, but have seen nothing with regard to the scale operator. Have I managed to overlook something or?

I will say I found the jit.gen example snippet (gen.waves) and have achieved the desired scaling behavior (X-wise) by detaching [swiz y] and [sin], but I'm struggling to figure out how to situate(/ format) jit.gen to communicate with (receive/ send cell data from/ to) matrixctrl.

Hey Aaron, (jitter) matrix != matrixctrl or matrix~, they are quite unrelated.

My apologies. To clarify — am I wrong in thinking that I should be able to convert a matrixctrl list to a format that jit.matrix is able to understand, and populate said matrix with those black & white values? (To then process and convert back.)

Perhaps there’s a more efficient way (using zl/ other forms of list processing) to wrap/ scale/ fold and/ or whatever else to a matrixctrl list, but I’m not that adept and such methods haven’t occurred to me.

The thing that gave me the idea was using jit.noise/ jit.matrix to populate matrixctrl with cells — I assume if that’s possible, the reverse should be possible as well. My apologies if I’m mistaken.

That could be a starting point.

The other way around:

But the question is – what do you want to achieve: neither (imo) jitter matrix nor matrixctrl are primary meant as a step sequencers, but can be used that way. If you want to scale values of vertical position you can do fe. this:

Thanks so much for the help and suggestions, guys.

This is the general concept -- Basically pattern resampling (up or down in resolution/ step length):

In Gregory Taylor's book, he uses [matrixctrl] to manage gates (or counts that sound) in tandem with [live.step]. I was wanting to have the option of modulating the step length/ column count without truncating or extending the pattern.

My current thoughts are:
1. The conversion back to matrixctrl list appears to be getting thrown by the changing column count.

2. It'd be nice if there were a way of toggling whether repeats were represented or
ignored when returning to matrixctrl.

3. Perhaps this isn't necessary, and there's a way of doing this without using a conversion to jit.matrix. (Perhaps KLSDIZ's suggestion of using scale would work in this manner, but I figured I'd go ahead and share this, incase my desired result was unclear.)

while it can be cool to use a matrix to handle or store and recall data in bunches, i dont think it is required to do it for a simple 2 D matrix.

i also dont think you need to use float32 to store 0s and 1.

it starts making sense when you use one matrix to store 10 such sequences, each of 5 rows, in 10 dimensions.

also, if you use use a matrix as "database" anyway, you could as well get rid of the matrixcontrol object and use the jit.pwindow as GUI object:

[route mouseidle]
[unpack 0 0]
[/ 10] [/ 10]
...