Hey Mooko. When you switch, you are actually restarting the application, so it’s true that Grid Pie is resetting each time it’s started.
But what you are suggesting should be possible, it would require that Grid Pie is initially performing a “song scan” to locate which slots are enabled.
I’m currently investigating how to make Grid Pie integrate better in a Duplex setup, so thanks for the idea.
Now, you should be able to map the application to other devices than the Launchpad, since you can now control X/Y position with a fader/knob.
See the LPD8 configuration for an example of how to do it (oh, and LPD8 owners, please take a look here)
The bug, where the held button was deactivated when released, is gone, and holding a button now copies the pattern (much faster!!)
I’ve also done some tweaks in order to make the usage more smooth. For example:
Hitting “play” will force the playback to begin in the GRID PIE pattern.
When “follow_pos” is enabled, follow playback will be disabled at all times
The application will shut down in an orderly fashion when you load a new song, or delete the GRID PIE pattern
You can MUTE/OFF tracks, and Grid Pie will leave them alone
I’m trying to make this Duplex version of Gridpie work with TouchOSC, but it’s my first attempt at lua and I don’t know what I’m doing.
I have created GridPie.lua to go alongside MixerTransportMatrix.lua here: http://pastebin.com/FV4FaMSi and have modified TouchOSC.lua to include this file. Duplex accepts this file without throwing any errors and in the interface of Duplex, the TouchOSC GridPie buttons work as intended, however, my TouchOSC app on my iPod does not trigger the buttons. If I select Mixer Transport Matrix from Duplex the iPod works fine so I know it’s not a connection issue. Could you please tell me what I need to add/fix to make this work?
Hey Mooko, I have to give you the same reply as I gave you a week ago:
The reason that Mixer, Effect etc. seem to “remember” their settings is simply, that they are designed to represent the current state in Renoise (the selected track, device etc.). Grid Pie, on the other hand, is doing stuff temporarily.
The solution to your problem will require modifications to Grid Pie. Stay tuned for updates…
I agree, Conner did something wonderful when he came up with the idea for this tool
Also, don’t be afraid to suggest new features - for example, I’d like to see scheduled triggering (wait until pattern reach it’s end, or X number of beats)
I’d like to add that this is not really an issue anymore - Grid Pie (the Duplex port) is now actively setting the playback position to the GRID PIE pattern, so it’s actually possible to create and manipulate blockloops even when follow_pos is enabled. You’re still missing out on visual feedback on the current position, though.
Okay, first thing I notice is the dark red color in the virtual control surface. AFAIK, the APC can produce only the following three colors for those buttons
Yellow = 1,1,0
Red = 1,0,0
But the colorspace for those buttons on the APC20 have been defined as 2,2,0 in the control-map. That’s actually wrong, isn’t it - it should be just 1,1,0 ?
If you try and change that, the virtual control surface should only display colors that the APC is actually capable of…
As for the application’s colors, this is actually quite easy to change - if you open GridPie.lua and look for “palette”, you’ll find the colors specified as RGB values. Try and experiment?
Once you find a set of colors you like, just PM me and I’ll make some code so we can define the palette especially for the APC. Right now Grid Pie comes with a palette which is primarily good for the Launchpad + monochrome devices. APC is sort of inbetween But it’s hugely useful to be able to see where there’s content and not.
If we look at the original Grid Pie script, it only has ON and OFF states. I think any device should respect that…
IMHO a selected slot should always be lit, no matter if it’s empty or not. Otherwise, how can you see that you are toggling it?
So, I guess the following could look really ugly but be more functional ?
But Grid Pie isn’t the Matrix, they perform different jobs. You are right that the matrix have “dead spots” (which doesn’t do anything when pressed), but think about what’s actually happening:
-> In the Matrix app, I’m simply toggling the state of an empty matrix slot. In other words, it has no consequence
-> In Grid Pie, I copy that particular pattern-track to the GRID PIE pattern. Since the track might include automation data, it does something.
So, in Grid Pie it’s actually always important to see which are enabled and which ones that aren’t.
Finally, it’s also how Grid Pie works on devices with no color. Good point is to keep the device configurations consistent.
Maybe I’m a bit fuzzy about the details. Don’t worry. These are opinions (what stuff looks & works nicely is a personal matter), but I trust you to understand why they makes sense as the default values.
But I’ll make it a feature in Duplex to customize the colors on a device-config basis. For instance if I for some reason wanted the Monome Mixer colors to be inverted (when all buttons is lit, it’s a very bright controller, I can tell you!!), I would become able to specify this in my monome-mixer config. And eventually, maybe even visually, via some palette UI.