Max for Live Tips & Tricks

[gavspav]

Code doesnt work for me either but reading the pcontrol help file kind of got me there.

But is there a way of getting the encapsulated patch to show in in its presentation mode state?

Edit - to answer my own question = set the open in presentation mode property of the encapsulated patch.

I'd like to know how to set the default size of the floating patch window though. Anyone?

[LOFA]

I messed up. I had used the copy compressed option while under presentation mode, I think.

This works on my end (and here is a link as well) to save space.

[pid]

hi gaspav:

Code: Select all

<pre><code>
----------begin_max5_patcher----------
686.3ocyV0zbaCBD8r7uhMJ9nqGijbrcaukKsS6jY54Nocvn0Qzf.MBTrcyz
+6EPRMxMeozD6zCFYVVd71Gvtb8ffvkpMnNDdK7UHH35AAAdSNCAM8CByoaX
Bp16VHSkmiRS3n5wL3Fi292fS+7GO8Ss1WojFM+mnaLRz3IMlkU4bo.MdrHM
FKJQsERpgqjeuDYlZ9PlPryChl3ZaafyuAIUkoEpV7KnFVFWdQGXVL2MUxLe
6TONQjN.wS87Ws7Gugjzk9RZtm9ge.EWgFNiBmgUXnyieMXfqYzqmn063mP5
e7GefieFsDWUINBzpb6JjiZnPo07kBDLJv1WCUE.UlBaUU.iJkJCbAZfsXIr
lKSUqgkT1kGAnt.YbpPrE3q7dmwSsnjgflUpDhkzRsGIiR45.boeTujgttND
LpxwiGC1kwMWpw6hiGzKrjaM2j0trtMJsCDNjQuxhifxvzVTMpBPfqLG0FyB
tDYpJoOvOYetgO0uUGGsvuUmj39rH5d1wIG3c72CBk5RvJrYnnXEWfV4dud9
OpQHlOsG2.VbvS.3Oo4Fl5NwqwBZI0byQt8apgEypEi5OQm7PRyr8jzzDo2R
Zl.II1Z.Sb+dJpPziTUo93PbbOppzJn0lLaKvZLBC+yDtqBN0IbcMyq+6h6V
Qm9ZnnSsJ5zWTEMZ1jNYZ1KRZeUzjCrh1oT.Lj.CifgwvvjQs0HvMH6eQoeI
zrSpq32bEu9UT2mtsup6Kw0V3ukrYx35lxtO+7aQ2q5L5wNUkTqMy848lQdv
mF0GEpwEs84.Mb33ybrXm3EBemq43u3ZQYZsE37Nxqm.9WL7WOM2Chy9tZtV
UUxZWxlLKvMgQJpMbo+ZaGeh2wG6ikRQY25E47zBEWZZnvNDbzSlQI+2wn3d
vHxyfQ1N+ZvuAX2++.B
-----------end_max5_patcher-----------
</code></pre>

[gavspav]

Hey thanks - only just spotted this.

We should really bring this Tips & Tricks thread back - its been a while now.

If only I could think of some more tips......

Struggling a bit to think of anything but err:

- Buffers and named jitter matrices can be shared across devices.
- Putting a print window in the Gui of a device enables you to see the Max window in Live.
- When in Max, you can find which object threw an error by highlighting the message in the Max window and clicking show information.
- You can search your patch for objects in the patcher window - can be useful eg for finding every instance of a named receiver
- Turning the camera off before going from Live to Max or back makes it alot less likely to crash on my system.
- Editing an abstraction or complete device which also has an instance in a running Live Set (not surprisingly) seems to cause problems. Turning the device and/or the audio engine off normally seems to avoid them.

Sorry these aren't exactly mind blowing - surely you must have some better ones!

[gavspav]

Still keen to revive this thread!

How about this one:

So far we have no access to the file path of clips in Live.

However if you follow a consistent naming policy then you can derive the file name from the clip name (which you do have access to).

As long as the file resides somewhere in Max's file path (settable from within Max), M4L will find it.

For example your file is called 'anything.wav'
- you call your clip 'anything'
- you check the clipname via the api.
- you add the extension of your choice.
- voila

I use something like the following:

Code: Select all

<pre><code>
----------begin_max5_patcher----------
1154.3oc4Yt0iiZCEG+4jOEHTeLMBega8s1uFUqhHAmIdKXivNYyzU628hOF
XRh.BDnSWo9vLdN9F+8ONmisY995Ut6kWYJWmey4OcVs56qWsBpxTwpZ6Ut4
IWOjknft4lyTpj2XtarscTJzhjbFz1uWxSxZZQbNmKxXZXX3OpTdV2TK5lIQ
w+aXRP3sd0Ua6o98BlUfttNeotohD8gSbwa6JYGz1VIwlQ5PCBME9dleih15
0NFdJHR49u9qHhqoterds4WaF4ROiegsUmruYEdIorco+Xa2s5Qct5I8tL2X
+4XlLQO3Z1ODYVlDJTf7ifhvtWzwtsSTYkr0rxcLQx9L1sRrfePetrwkncZT
IWXo6Rz5R99yZ1G+kplW0.y.kryL4wlpap+1mpRyJfwU+h9AIcNulCa+VxEC
G1lKqKKHs1MR69AesPJXBfNnscM8mEbsR+tcQ2UGxqdka8CC21c6bAL1Nas4
sHti13UO5p3iafdWyf5jrT2ma0Cy2EthOvTkKSexhIQHj5DMWJ109H65QkIE
uMJMYdjCwmLt3uLSjZHMKS6cIwEGk8pRYYJqruQBu36cnpBFKMiCddd1lgjC
MESLSgf8spHtl3MM6J3Q5dPlumKXNG4YLCEb1V0BSnp3+hjOEO07oadRNUJ1
lSEaSrDPLEXutyuD4tbjprRqLG.DSCLnOKv.nfDQME1rv8wkvWgKOrMaKXdi
oeEr7Yr+aPLfDTfoH.Mz9uAKnqBjNppAiP9oCJTrcCZevOIfNjeBcAgh1YuS
1+IgN6SDu87vGeaDSH3qPva86GKnk1WoROm5GMN+gLK8ENE2c7w6IoVdJeH.
XvD6YYGLVhDsj4WLvwwfocppLM5Sb0tT1E9AlygDgTvOTc.lpsMqNikygLdw
NUlTqb9EDX8JTcBAgduZPHodeKa3WbfcyrdvYvhhyRYAqT+tSQVx6FUY3U0o
XRYW+IEV3XHMNh5aKnCAKD1aIiNkIoFP5LdmvkKNdg83fqeZuOFN.OX76mWZ
+oxD7DYx3x8isNXnvOx82Ga7+W3fBJV4kpqIrXQe3WYCfQjtBEBQfgC57DG9
+wcGsdPQdiXyw6xOA8nZYJd7SdAODS82CMk7b4gFoYuhyFmOdNoLklKfqOeS
ePluQApsSm3ooLwM2J0MmmVH4Bsp40MxDBPsYIn1.Bvx4Kc9tcrhM9NczsXi
llVCreVMJB1UvuxC0u1ZlZMbDf8d3OBtZIo8lZMT1XMSsRGgVCmpV8LpiDgt
wG.rloVCFgVoSSqjvHPc90Z0q0ZlZEMBsFLQtF.pCGa2qwpbvZAzJZDbcJ4A
BqOdJnUpM1ZIzJIZDhEMUvBgSXee62b2q0ZtIsFSl.xTcCn1SYDaU6MVyEsi
I9hD8RpESnV052ZMW05MBGA+oxVepQe1aMPIQMFyTqfLdlVAmkoDh4aOLE0F
hECjErVB09zCFf8l5tB.MQDvsk3YO278V1+yODOaOoyOKLYLdzSdgDajWXzM
9HgQyOI7C.c.mjor+VMKseT2ljEgOR1Jier9e.rxyUyO
-----------end_max5_patcher-----------
</code></pre>

[mastahlee]

Still keen to revive this thread!

How about this one:

So far we have no access to the file path of clips in Live.

However if you follow a consistent naming policy then you can derive the file name from the clip name (which you do have access to).

As long as the file resides somewhere in Max's file path (settable from within Max), M4L will find it.

For example your file is called 'anything.wav'
- you call your clip 'anything'
- you check the clipname via the api.
- you add the extension of your choice.
- voila

I use something like the following:

Code: Select all

<pre><code>
----------begin_max5_patcher----------
1154.3oc4Yt0iiZCEG+4jOEHTeLMBega8s1uFUqhHAmIdKXivNYyzU628hOF
XRh.BDnSWo9vLdN9F+8ONmisY995Ut6kWYJWmey4OcVs56qWsBpxTwpZ6Ut4
IWOjknft4lyTpj2XtarscTJzhjbFz1uWxSxZZQbNmKxXZXX3OpTdV2TK5lIQ
w+aXRP3sd0Ua6o98BlUfttNeotohD8gSbwa6JYGz1VIwlQ5PCBME9dleih15
0NFdJHR49u9qHhqoterds4WaF4ROiegsUmruYEdIorco+Xa2s5Qct5I8tL2X
+4XlLQO3Z1ODYVlDJTf7ifhvtWzwtsSTYkr0rxcLQx9L1sRrfePetrwkncZT
IWXo6Rz5R99yZ1G+kplW0.y.kryL4wlpap+1mpRyJfwU+h9AIcNulCa+VxEC
G1lKqKKHs1MR69AesPJXBfNnscM8mEbsR+tcQ2UGxqdka8CC21c6bAL1Nas4
sHti13UO5p3iafdWyf5jrT2ma0Cy2EthOvTkKSexhIQHj5DMWJ109H65QkIE
uMJMYdjCwmLt3uLSjZHMKS6cIwEGk8pRYYJqruQBu36cnpBFKMiCddd1lgjC
MESLSgf8spHtl3MM6J3Q5dPlumKXNG4YLCEb1V0BSnp3+hjOEO07oadRNUJ1
lSEaSrDPLEXutyuD4tbjprRqLG.DSCLnOKv.nfDQME1rv8wkvWgKOrMaKXdi
oeEr7Yr+aPLfDTfoH.Mz9uAKnqBjNppAiP9oCJTrcCZevOIfNjeBcAgh1YuS
1+IgN6SDu87vGeaDSH3qPva86GKnk1WoROm5GMN+gLK8ENE2c7w6IoVdJeH.
XvD6YYGLVhDsj4WLvwwfocppLM5Sb0tT1E9AlygDgTvOTc.lpsMqNikygLdw
NUlTqb9EDX8JTcBAgduZPHodeKa3WbfcyrdvYvhhyRYAqT+tSQVx6FUY3U0o
XRYW+IEV3XHMNh5aKnCAKD1aIiNkIoFP5LdmvkKNdg83fqeZuOFN.OX76mWZ
+oxD7DYx3x8isNXnvOx82Ga7+W3fBJV4kpqIrXQe3WYCfQjtBEBQfgC57DG9
+wcGsdPQdiXyw6xOA8nZYJd7SdAODS82CMk7b4gFoYuhyFmOdNoLklKfqOeS
ePluQApsSm3ooLwM2J0MmmVH4Bsp40MxDBPsYIn1.Bvx4Kc9tcrhM9NczsXi
llVCreVMJB1UvuxC0u1ZlZMbDf8d3OBtZIo8lZMT1XMSsRGgVCmpV8LpiDgt
wG.rloVCFgVoSSqjvHPc90Z0q0ZlZEMBsFLQtF.pCGa2qwpbvZAzJZDbcJ4A
BqOdJnUpM1ZIzJIZDhEMUvBgSXee62b2q0ZtIsFSl.xTcCn1SYDaU6MVyEsi
I9hD8RpESnV052ZMW05MBGA+oxVepQe1aMPIQMFyTqfLdlVAmkoDh4aOLE0F
hECjErVB09zCFf8l5tB.MQDvsk3YO278V1+yODOaOoyOKLYLdzSdgDajWXzM
9HgQyOI7C.c.mjor+VMKseT2ljEgOR1Jier9e.rxyUyO
-----------end_max5_patcher-----------
</code></pre>

This is almost exactly what I am doing with my Ms. Pinky Revised patch. The only difference is that I have a list of possible extensions (.aif, .wav, .mp3) that are appended to the clip-name in turn to determine the path. I think the code is pretty slick, and is fully encapsulated within a patcher object (the patcher name is something like get_clip_path) for easy cut-and-paste. You can take a look at my patch here: http://dl.dropbox.com/u/105916/patches/ ... vised.amxd

The patch itself won't work unless you have the Ms. Pinky externals, but the code relevant to determining paths from a clip's name will work.

[LOFA]

If for some reason your edit button is greyed-out, just press pause, delete the object and press undo. Now your object can be edited again.

[LOFA]

Use the sprintf object. It helps for creating objects that need to have their paths adjusted. Trust me. It's cool like the zl object. Very cool. I recommend learning them both thoroughly.

[gavspav]

Right clicking the top bar of a Max device in the Live GUI gives you the option to open the Max window.

[gavspav]

Deleteing a device and the undoing it triggers a loadbang message.

Is there a better way though?

[mzed]

Deleteing a device and the undoing it triggers a loadbang message.

Is there a better way though?

The code below, using the universal object, works for a patch and its subpatches. Probably good enough for one device.

<pre><code>
----------begin_max5_patcher----------
304.3ockRsrSCCCD7ryWgkOWpriDkDtw2ApB4DujZjy5nXGHPU+2I1wglBHQ
4heL6Lq2YjOlQXU1Qvwn2SejRHGyHjHT.fjtSXsxwZizEowZAmS1.rMy07vn
Oh6.TQMVopRhMzvxBkmsn2o+.BzD4a4IXbnUiFvGaa9YP6feAUjPqZpsFa+7
XJl5.kusnjKJ2ENwSmlJP2mTzI80GzXyS8PsOo61fvhv.PEhx3VwJIyuq+8N
XlOi8UIsJZQa0K2jWr1VnrMxl8PuVZXgBmxxBKatx3Dg2lZ6ORyAT+Jz6jFp
3+DiheMF4+UnH32E11ECkb9pPYsyKuNmG0xLZ76+qhOe.+x3vYG5qWx7kHld
dDTfyqQoWaw0jJufzAsRA3Zy1pUcVM5SCAc+EiX1orOAl4HrnB
-----------end_max5_patcher-----------
</code></pre>

[gavspav]

Oh those heady days when this thread was active!

So what have you learnt in the past couple of years?

I've accidentally discovered that saving a device or part of a device as an abstraction improves my workflow whilst using m4l.

I can leave the 'original' version of the abstraction patch open in Max and carry out any adjustments and save them.

The changes are automatically carried over to the M4L device.

This means much less need to open the m4l device in the Max environment - a workflow killer for me anyway.

Of course I guess it's possible to crash Live like this but hey let's face it, it's quite easy to crash Live anyway going from Live to max and back again.

On a similar tip I find putting some or all of my device in a subpatch and adding this to the presentation window means that you can have a look at the insides of your device whilst Live is running without having to go Live>Max>Live.

You can even put meters, number boxes, bangs in so you can work out what the hell is going on!

These work for me anyway!

[ned rush]

i dont know if this is to anyones interest, but following ableton blogging supacut live i made a little video about some of the basic ideas behind, mainly recording audio live and mangling it using groove.

http://www.youtube.com/watch?v=l1H3Yxr_ ... AHOZLQ100=

maybe it might be interesting to some.

cheers
ned.

[madlab]

i dont know if this is to anyones interest, but following ableton blogging supacut live i made a little video about some of the basic ideas behind, mainly recording audio live and mangling it using groove.

http://www.youtube.com/watch?v=l1H3Yxr_ ... AHOZLQ100=

maybe it might be interesting to some.

cheers
ned.

Sure it is. Thanks Ned.