patch hierarchy view/tree

Jul 31, 2013 at 9:15am

patch hierarchy view/tree


Does a particular table/list/view exist such that it displays the hierarchy of patches and sub-patches? It would be very cool if I could see some tree type view of how patches are nested.

Extra bonus would be some type of feature that allows me to easily visualize which variables/send/receive are being used by what patches.


Jul 31, 2013 at 3:25pm

that’s a great idea– please include this as a feature request uncle 74

Jul 31, 2013 at 3:36pm

Thanks, but I assume that means there is no current way to do this?

Jul 31, 2013 at 4:35pm

not that i’m aware of– the only thing that is related (but doesn’t really come at all close to what you’ve proposed) is you can double-click on a send or receive to see the other sources/destinations.

it could be like a navigation panel or window that shows you where you are in relation to the whole patch– you could click on a node to open that subpatch window, to access it directly rather than having to navigate through a bunch of parent patches

Jul 31, 2013 at 4:41pm

this is a great idea!

Jul 31, 2013 at 4:44pm

and something like the “Parameters” window you can open up from the view menu when using m4l, but displaying send, receive, var and pvar info.

Aug 5, 2013 at 8:10am

Floatingpoint – that’s pretty much exactly what I envisioned! Oh well, I guess we can just hope that this gets built in to some future release.

Aug 5, 2013 at 10:40am

if you really want it, someone should send an email to c74 support, so it can be registered as a feature request…

Aug 5, 2013 at 11:44am

This would be fantastic. Love the tree idea with clickable nodes to access subpatches or abstractions. Or you click and you get the list of pvar, v, and send/receive objects; double-clicking opens the subpatch. Heck, what about a list of all the objects in the patch, filterable by type? Could you even see the current value states of objects like pattrstorage does? Etc…

Great feature request. Though I wonder…probably a lot of this could be done through JS, because it can “browse” through the patch hierarchy, find objects by type, etc. Might be interesting if someone tried to roll their own…

Aug 5, 2013 at 5:15pm

fwiw, just sent in feature request to support…

Aug 5, 2013 at 6:09pm

I’m glad I’m not the only one who thinks this kind of thing would be useful. I appreciate you submitting the request, Floating Point.

Aug 5, 2013 at 6:16pm

It’s not too hard to build a simple patch mapper using JS. Here is a quick one I knocked up. It shows all the patchers and all the objects contained within them (with their scripting names if they have them).

Does anyone know if it’s possible to get an objects arguments along with it’s name and scripting name, this would make things very interesting…

Aug 5, 2013 at 6:49pm

You could try loading the patcher file into a JS object and parsing it with JSON.parse()



You must be logged in to reply to this topic.