Matthew's tutorial suggestions

[diemoschwarz]

On 30/01/2023 19:47, Matthew Ostrowski wrote:

Hi Everybody,

Had a look at the tutorials, and as you might imagine, I have a few comments. Overall, you've obviously put a lot of work in, and I think it's heading in a good direction!

Firstly, each tuto should really have an individual corpus name -- if you open several without closing the others, things can get a bit weird.

As a sort of overall comment, I wonder if it might be possible to give up on the '90s style patching, and maybe use Presentation mode -- something in Presentation that shows the basic order of events, and featured functions, and then has something in Patching mode that is a bit more legible. Someone unlocking this is not going to feel empowered to tweak it without a lot of patience:

I've attached a very rough draft of how one of those might be done. It would also give one room to comment a bit more thoroughly....

Also, as part of the comment above, I think it would be a great treat for the users to have all of these made pattrstorange-friendly. 

the commenting in the camu.* subpatches are great, although camu.random.filter has the comments in white, which are hard to read, but the general approach is very helpful! 

I do see some partially done things and dead ends which could probably be cleared out however. For example in camu.random.filter, there's a [route play] attached to a toggle and a gate that has no input, and in camu.menu, there is an [r corpus-menu-init] that appears to be neither used or explained (at least in tuto 1). Now that I'm looking at that, I also see another dead end:

that value object isn't set there, but banging it won't produce any output. So I think the subpatches need some cleanup, and window sizes should be set, etc.

I get some strange redrawing in the 'rawdescr' track of tuto 5b:

Some of the advanced things look very cool, but they need more thorough commenting.

It might also be useful to have a tutorial or two using something other than pipo.descr -- it looks like the camu.menu can be updated for that, and an MFCC/PCA tuto would be nice as well.

I'm also getting stack overflows in some examples...

-- catart-som
-- catart-mubu-tutorial 1 for mubu pre 1.9.7

Some of the examples have specialized input objects such as camu.control blocks, jit.sensel, etc. I think those should only be in patches that ar3 specifically about using outside controllers...

I haven't gone over everything with a fine-toothed comb -- I will if you want -- so these are just a few random things I've noticed....

Talk soon,

\M