lefauxdjaber

http://cycling74.s3.amazonaws.com/support/LOMChanges.pdf

I found that you can call fire with arguments to define record length and quantization.

However, after much trial and error and searching the web I haven't found a way to get call fire to be quantized apart from the global quantization.

Banging the message "call fire 8, 8" makes the first argument work as it'll record for 2 bars, but the next one returns an error of "doesn't understand 'int'".

Weirder yet when leaving out the comma, it makes the clip record for a bizarre amount of time and begin recording instantly.

Anyone know what's up with this and know of a way to make live.object understand the second argument?

On this page
http://cycling74.s3.amazonaws.com/support/LOMChanges.pdf
I found that you can call fire with arguments to define record length and quantization.
However, after much trial and error and searching the web I haven't found a way to get call fire to be quantized apart from the global quantization.

Banging the message "call fire 8, 8" makes the first argument work as it'll record for 2 bars, but the next one returns an error of "doesn't understand 'int'". 

firerecord_length-launch_quantization

Launch Quantization on the Clip Level is unavailable so that's not correct in the description there...

I figured as much, but when I also saw it in the updated LOM I thought there might be a way to do it.

Know of any plans on making that happen? I found a way around it but my patch would be nicer and if that was an option.

Hey thanks for the response.
I figured as much, but when I also saw it in the updated LOM I thought there might be a way to do it.

Know of any plans on making that happen? I found a way around it but my patch would be nicer and if that was an option.


second number is in clip_trigger_quantization integers (i.e. 1= 8 bars, 5= 1/2 bar, etc)

Only allowable for recording, can't call fire on already existing clips with launch_quantization settings different than the global settings. So the utility of launch_quantization is limited.

Ok update on this
This works but is setup as follows

first number is in beats
second number is in clip_trigger_quantization integers (i.e. 1= 8 bars, 5= 1/2 bar, etc)

Only allowable for recording, can't call fire on already existing clips with launch_quantization settings different than the global settings. So the utility of launch_quantization is limited.


Unless you change the global quantisation on a clip by clip basis, automating the return to a default value of your choice after the clip was launched using a delay object or something of the kind.

Yeah, that will work. You might even be able to do this with a trigger object, with no delays. The order would be: set global launch quantization to desired quantization, fire clip, set global launch quantization back to whatever it was before.

fire(record_length, launch_quantization)