Questions about DWO3

Helpdesk
48

Cool, thanks! I will give it a try.

49

Lucidcharts and Visio come to mind

50

this is one that came out recently that I will try if I ever find graphviz to not be the ticket.

having a working palette is the most important piece that I need. It just doesnā€™t work for me if I have to remake the memory palace each time I want to use it in a patch.

but Iā€™m also not going to pay a subscription fee for something like this.

I added the graphviz workflow to my stream deck yesterday so now Iā€™ve got 50 defined modules, a patch initialization template, and some generic IO patching all at my finger tips.

I should be able to patch along with the next LZX 3 patches video in real time with just a bit of cleanup and organization at the end!

Iā€™ve documented just shy of 100 patches at this point for the community and would love to find something that can actually make graphviz unnecessary.

In my opinion a generic flowchart app will not do that for anything more precise than super broad scope DIVER > keychain > contour > FKG > ESG type patch diagrams. If this isnā€™t the case Iā€™d love to see some examples!

sorry for the hijack
when Iā€™ve got the rest of the generic IO in place and have done a couple patches up with the new stream deck setup Iā€™ll release the full profile on here in an accompanying thread.

7 Likes
51

WHOAH. That is incredible. I had no idea that existed. What an amazing resource. How can you promote this so everyone knows about it?

2 Likes
52

Iā€™ve made posts about it on here and the Facebook and the discord. I mostly have been bringing it up on the discord lately as Iā€™ve added the more recent 3 patches videos.

LZX Patch book (WIP) here is that original post

5 Likes
53

Iā€™m on the discord, but never, ever check it. Too many platforms. Also the UX is horrible. Also not archived, so what happens on the discord stays on the discord, until itā€™s purged and / or swept away by the next wave of posts.

This is the only platform thatā€™s even remotely archival. Even that is dodgy. As I recall, the previous iteration of the LZX website went into a hacker-induced memory hole. Same thing happened to me, itā€™s a sad state of affairs.

Honestly, this stuff needs to be documented in PRINT. You can laugh, but itā€™s the only non-volatile format. Plus, a book can be held in one hand while patching / twiddling with the other. Laptops, tablets and phones are terrible at this. I bet if you self-published this you would at least make back the production costs.

At the very least, a resource like this should be prominently featured here and on the FB channel. Obviously needs to be identified as user-created, unofficial content. But deserves to be put in the spotlight. My $0.02

2 Likes