I’m glad to see better programmers than myself exploring this sort of sequencer! In fact, I will probably switch over to using GridPie for my own music eventually. I wrote a similar sequencer for the Monome myself, called Phrases, in another programming language it was just an informal project. It seems pretty amazing, and I’m excited to see what features appear in its future versions. ![]() I just now discovered GridPie, after overlooking it for a few months. PS: I moved the posts which dealt with Grid Pie into this thread (this feature depend on scheduling to be implemented first) Schedule slots: on a grid controller, simply press two buttons in the same row, and any slots in Just like how you can schedule multiple patterns in Renoise, this feature will enable you to (this feature depend on streaming output to be implemented first) So, depending on the song’s tempo, notes & automation data output is being written to the pattern just prior to being played.īecause the pattern is being written prior to being played, we are able to support pattern scheduling Splitting the output into smaller chunks means that Grid Pie could avoid those dangerous CPU spikes I think I would settle for an approach which copies any modification in the GRID PIE pattern to the originating slots, and vice versa (bi-directionally).Įdit: Sharing my development roadmap for all the major features that could arrive within the next few versions: ![]() ![]() Similar recording features have already been discussed in this topic’s previous page (hello dby!!). matrix slots) ? This is of course possible. Automatically write changes to the gridpie pattern back to originating patterns (My suggestion).Īh, now I think I understand you - you want to copy, not the patterns but the pattern-tracks (a.k.a.
0 Comments
Leave a Reply. |