[sharing is matrixing (obviously)] matrix~ in gen
As there were some requests for this and to give back to the great forum people from which I learned so much, here is a matrix~ like gen script.
This is in a codebox, although I wanted to have it as a matrix8.gendsp file, but couldn't get it loaded by gen~. Path issue?
That's interesting. The glories of peek and poke )
Somewhere on the forums there is extensive discussion on how to load a .gendsp for editing. I guess you can can try opening the file, copying and pasting it, which could be the lazy way. But really it's intended as an archive one doesn't open and just uses something like 'require_once; in a codebox.
I posted something similar at the end of this chat: https://cycling74.com/forums/fm-in-gen-self-modulation -- using the matrix to dynamically re-route a feedback FM patch. Squelchy.
@Diemo: the path thing is odd -- I just tried and it worked here:
- double-click gen~ to open, save as 'matrix8.gendsp'
- save main patcher as 'test_matrix8.gendsp' in the same folder
- close main patcher & re-open -- it works
Do those steps not work for you? Could it be there's something else called 'matrix8' in the search paths?
I posted something similar at the end of this chat: https://cycling74.com/forums/fm-in-gen-self-modulation — using the matrix to dynamically re-route a feedback FM patch. Squelchy.
Sure I saw and played with that fantastic patch! It convinced me that all genexpr is the way to go. That'll be the next step: to integrate your oscillator code into the gen matrix8 cell function to have full individual matrix modulation, feedback, delay, and filter. Stay tuned!
@Diemo: the path thing is odd — I just tried and it worked here [...]
I know now what I got wrong: I had presumed that one can have genexpr source code in a text file and reference the filename directly in gen~, without needing that trivial codebox wired to in1, ..., in8, out1, ..., out8.
(So I mistakenly had text files in a .gendsp (I only know gen since Friday, please forgive me), but even as .genexpr it doesn't work that way. Why couldn't it? That's a feature request... =-)