There are a few videos on RUclips that I'd like to like multiple times and this is definitely one of them. Hours of trying to do some M4L programming and your overviews are awesome to get the basics of objects and why [t b l] is everywhere in Max patches. Thanks!
Damn this is great 👍 You are a fantastic teacher, truly. And these energetic lessons really pack it in brilliantly. Max has needed this forever already. And especially now. Too many tutorials know too much, but lose the clarity in transmission, unless one is already at the same level ... Which may often be true. But for true beginners Max tutorials & docs can be very frustrating because they lack context. Zillion & 1 smart tips do NOT help when one has just stepped off the mystical boat. What is great is that you highlight key foundation, but alert to why and how in gracious but exciting way. Like grace notes in a song.. Seriously gratefully Please keep building out this tight fast fun knowledge.
The stuff in this clip is exactly the foundation that I need to get me running with the Max environment. It is Sooo useful!!, I'm breathless and need to lie down to settle (far away from Max), and will try and add to this comment. (BTW do "Max", and "Max/MSP" mean exactly the same thing?) Thank you, Andrew Robinson. Kindest regards, Mikey
Thanks so much for your very useful tutorials, I’m always getting back to them. In this very video you elaborate on ‚operations’ objects. Do you know about an object called ‚mf accum? It is used in an old max 5 or 6 patch (video). The objects function seems very specific (floats between 0.1 and 0.9 just add up just between 0 and 1)and different to the max 8’ ‚accum’ object. Max 8 doesn’t allow to ad ‚mf’ so since I wasn't able to find a propper substitute for ‚mf‘ the whoe patch is not working in max 8.. Many thanks for your time and help!
@@EvenStarLoveAnanda I think you can also write a message with min and an number attached to id, then plugging it in and pressing it, so it overrides the object. I've seen in teh help section that it is used for a few things.
Part of the problem with MAX is that they didn't give a very descriptive name to these objects. For example, gate is actually a distributor and switch is actually a collector. Gate and switch are correct but they refer to a much more basic function. This is why MAX is hard to understand for a common sense person.
So far this Max is confusing as hell, I guess to anybody coming from a traditional programming language. Let's take the gate. It's got this hint for its left inlet "0 Closes gate, Non-zero Opens Gate Outlet" but it's not just that! It appears to be transmitting its own state when you hit it with a button (or bang message) like this _button -> gate(left inlet) -> print_ You really do not expect this. It mixes its state with the data it operates on. What is worse the documentation says nothing about this peculiarity 😦
That is interesting, I myself had not been aware that sending a bang into the left inlet reports the state of the gate. I could see how stumbling upon this when you are new could be confusing. Max has a lot of peculiarities that don't seem to make sense at first but once you get down into the really nitty gritty technical stuff it becomes more clear as to why things are the way they are.
There are a few videos on RUclips that I'd like to like multiple times and this is definitely one of them. Hours of trying to do some M4L programming and your overviews are awesome to get the basics of objects and why [t b l] is everywhere in Max patches. Thanks!
Damn this is great 👍
You are a fantastic teacher, truly.
And these energetic lessons really pack it in brilliantly.
Max has needed this forever already.
And especially now.
Too many tutorials know too much, but lose the clarity in transmission, unless one is already at the same level ... Which may often be true.
But for true beginners Max tutorials & docs can be very frustrating because they lack context.
Zillion & 1 smart tips do NOT help when one has just stepped off the mystical boat.
What is great is that you highlight key foundation, but alert to why and how in gracious but exciting way.
Like grace notes in a song..
Seriously gratefully
Please keep building out this tight fast fun knowledge.
Keep the good feelings flowing, Andrew! Your explanations are very clear and helpful. Thanks!
this is the first time I've ever understood zmap thank you!
😄loving this relaxing random piano poem at the end. Thank you for your work. This is ace !
its great ! can't wait for audio section ! keep doing it man. that's great
thank you so much, this series is helping a lot to get started !
Thank you! So glad this resource is available to help me get into Max!
Thanks for making this video, super helpful
Super Awesome Brother, Thank You! I'm sure I'll have a few questions soon man!
The stuff in this clip is exactly the foundation that I need to get me running with the Max environment. It is Sooo useful!!,
I'm breathless and need to lie down to settle (far away from Max), and will try and add to this comment.
(BTW do "Max", and "Max/MSP" mean exactly the same thing?)
Thank you, Andrew Robinson. Kindest regards,
Mikey
Absolutely perfect.
Thank you sir.
These are great dude. Thanks!
Thanks so much for your very useful tutorials, I’m always getting back to them. In this very video you elaborate on ‚operations’ objects. Do you know about an object called ‚mf accum? It is used in an old max 5 or 6 patch (video). The objects function seems very specific (floats between 0.1 and 0.9 just add up just between 0 and 1)and different to the max 8’ ‚accum’ object. Max 8 doesn’t allow to ad ‚mf’ so since I wasn't able to find a propper substitute for ‚mf‘ the whoe patch is not working in max 8.. Many thanks for your time and help!
this is great!!
So in scale you are defining a specific ratio, but not the limits of the operation, makes sense.
You can always limit the output by additional operations.
@@EvenStarLoveAnanda I think you can also write a message with min and an number attached to id, then plugging it in and pressing it, so it overrides the object. I've seen in teh help section that it is used for a few things.
Part of the problem with MAX is that they didn't give a very descriptive name to these objects.
For example, gate is actually a distributor and switch is actually a collector.
Gate and switch are correct but they refer to a much more basic function.
This is why MAX is hard to understand for a common sense person.
Thank you!
Fantastic tutorials! As a side note, at x1.75 playback, you sound like Ben Shapiro lol.
😂😂
ahahah props to you for being able to follow a max tutorial at 1.75, too! :P
yes
cool
So far this Max is confusing as hell, I guess to anybody coming from a traditional programming language. Let's take the gate. It's got this hint for its left inlet "0 Closes gate, Non-zero Opens Gate Outlet" but it's not just that! It appears to be transmitting its own state when you hit it with a button (or bang message) like this _button -> gate(left inlet) -> print_ You really do not expect this. It mixes its state with the data it operates on. What is worse the documentation says nothing about this peculiarity 😦
That is interesting, I myself had not been aware that sending a bang into the left inlet reports the state of the gate. I could see how stumbling upon this when you are new could be confusing. Max has a lot of peculiarities that don't seem to make sense at first but once you get down into the really nitty gritty technical stuff it becomes more clear as to why things are the way they are.
useful content! But please stop touching the mic; the noises are distracting.