I'm trying to launch a clip with a launch_quantization parameter using the ClipSlot 

live.object: Can only pass record_length to empty slots.: 'fire 4'

 is the first how do I skip it and just provide 

I'm trying to launch a clip with a launch_quantization parameter using the ClipSlot fire function, but I'm getting the error: 

Since fire accepts two parameters and record_length is the first how do I skip it and just provide launch_quantization?

set-the-launch_quantization-parameter-of-clip-fire-function

The launch_quantization parameter is not available for existing clips. See also this thread

https://cycling74.com/forums/firerecord_length-launch_quantization

The fire method takes 3 keyword arguments; record_length, launch_quantization and force_legato. Keyword arguments differ from regular arguments in that they don't have to be passed. So, you can call fire without any arguments or with any number of the keyword arguments. For example, if you wanted to pass just the second argument, you'd specify its name like fire(launch_quantization=0).

I'm not sure if that's possible with M4L alone. If not, ClyphX has an action that does just that and it can be called from M4L. Alternatively, you could modify the _MxDCore MIDI Remote Script (the script that M4L uses to access Live's API) or roll your own script to communicate with the API.

As an aside, if you want to set up a clip launching mechanism that overrides launch quantization and works properly with all of the possible launch modes of a clip, you should use set_fire_button_state of Clip instead of fire. In that scenario, you can override the clip's launch quantization setting via the workaround mentioned in the thread that broc linked providing that the clip's launch quantization is set to global. If it's set to some other value, it cannot be overridden via that workaround.

The fire method takes 3 keyword arguments; record_length, launch_quantization and force_legato.  Keyword arguments differ from regular arguments in that they don't have to be passed.  So, you can call fire without any arguments or with any number of the keyword arguments.  For example, if you wanted to pass just the second argument, you'd specify its name like fire(launch_quantization=0).

I'm not sure if that's possible with M4L alone.  If not, ClyphX has an action that does just that and it can be called from M4L.  Alternatively, you could modify the _MxDCore MIDI Remote Script (the script that M4L uses to access Live's API) or roll your own script to communicate with the API. 

As an aside, if you want to set up a clip launching mechanism that overrides launch quantization and works properly with all of the possible launch modes of a clip, you should use set_fire_button_state of Clip instead of fire.  In that scenario, you can override the clip's launch quantization setting via the workaround mentioned in the thread that broc linked providing that the clip's launch quantization is set to global.  If it's set to some other value, it cannot be overridden via that workaround.


Set the launch_quantization parameter of clip fire function