clip_trigger_quantization of selected clips with M4L?

[nbyte]

Hi,

I'm building a M4L-Patch to chop clips with push. So far everything works fine. Only one thing I would like to add: I want to set the clip_trigger_quantization of the selected clip with push!

I have looked in the API but I found only a property of song but nothing for clips.

Are their other tricks how I can realize this?

[wehkah]

It is not possible to set the properties for the follow actions / clip quantization. I hope this will come with future updates.

I recommend you to use this API doc to find the function you need there is a MAX patch called LOM Tester which is very helpfull too!

http://cycling74.com/docs/max5/refpages ... model.html

http://www.maxforlive.com/library/devic ... lom-tester


cheers
T

[chapelier fou]

fire(record_length, launch_quantization)

[S4racen]

fire(record_length, launch_quantization)

Interesting! How?

Cheers
D

[chapelier fou]

it's new in L9 (see LOM changes).
I've played a bit with this, it works pretty well. Record length is in beats (float) and launch quantization, well i can't remember. It's pretty easy to figure out what the syntax is, though.

[S4racen]

Just found it, pretty cool!

Cheers
D

[chapelier fou]

my pleasure !

[nbyte]

Thanks to all for the infos.
I will test it ...

[nbyte]

fire(record_length, launch_quantization)

I have problem using it!

When I use "call fire(float, float)" I get the MAX message:

"live.object: 'Clip' object has no attribute 'fire(1.'
live.object: doesn't understand "1.)"

How to use it right?

Thanks in advance....

[chapelier fou]

remove the brackets i guess ?

[regretfullySaid]

I can't get firing with the launch_quantization to work. I'm not sure if it only works for a blank slot because I think you have to provide a setting for record_length even if I just want to launch without quantization.

Is anyone able to launch the clip with no quantization using this setting? I understand I can change the clip's global quantization but it's more ideal to override 'per fire' in this situation.

I've tried 'call fire 0 0' and variations between one or 2 ints/floats but no luck.

[chapelier fou]

I am having the exact same problem. The only conclusion i made is that you have to specify a recording_length as well, which makes the patching really more complicated, as max will display an error message when you're just launching a clip and not recording.
In my opinion, call fire 0 0 should just work as expected.

[dataf1ow]

You could quantize the fire message using onebang and plugsync~

[regretfullySaid]

I was actually quantizing the fire using 'pipe' and ''delay'. The reason I mentioned both is because between the 2 the actual 'quantize' settings for both objects don't seem to do their job. The closest I got to actually quantizing the message to fire was using 'pipe i'; the 'i' standing for integer. Well, that's the only time I could actually get the message to quantize, but it also gives a 'bad number' error. So, if I use a 'pipe 1' (or 0 or any int), it doesn't quantize, and when I use 'i' it does quantize. SMH. What I ended up doing was use a 't b l b' to
1. set live_set clip_quantization to 0
2. fire the clip
3. set clip_quantization back to whatever setting it was at previously, by banging an int that receives the clip_quantization observation (but filter out zero so it doesn't receive 0)

I shouldn't have to do that if there's supposed to be an option to override the clip_launch in the clip setting. So why is it there?
But that isn't the only lack of function lying dormant that's documented in the API.

Still can't do some scrolling,
changing grid_quantization doesn't work,
a couple other little things,

yet funnily enough, even though M4L is supposed to be more 'legitimately supported' than python scripting, you can do some things with scripting the API that you can't do with M4L.
So, you can either reap that benefit by learning python, or not have that functionality not provided by the add-on you paid an extra couple hundred for.
And even though M4L is upposed to be legitimate support for hacking the API they won't directly talk about it at all. Woohoo!

[dataf1ow]

So why don't you use plugsync~ and onebang? I've used this to quantize recording, button presses and sample launching with great success.