Live API: ime signatures changes

Learn about building and using Max for Live devices.
Post Reply
HfMT
Posts: 10
Joined: Wed Jan 26, 2011 11:28 am

Live API: ime signatures changes

Post by HfMT » Wed Jan 26, 2011 11:36 am

I just joined this forum. Being a Max/MSP developer for quite some time, I'm currently working on music editor for Live. There are a few things I noticed while working on my patch, for instance it would be nice if meter (time signatures) changes could be inserted and queried via the Live API (I'm not talking about initial settings).

Georg

broc
Posts: 1151
Joined: Mon Jul 26, 2004 8:37 am

Re: Live API: ime signatures changes

Post by broc » Wed Jan 26, 2011 1:03 pm

In the Song class there are properties 'signature_denominator' and 'signature_numerator' with access get, set and observe.
Doesn't this provide what you want?

http://www.cycling74.com/docs/max5/refp ... model.html

HfMT
Posts: 10
Joined: Wed Jan 26, 2011 11:28 am

Re: Live API: ime signatures changes

Post by HfMT » Wed Jan 26, 2011 6:35 pm

Well, this is what I meant by initial settings; but what if I want to change the meter in, say, the 6th measure. The are no ways to query or to set these changes; or am I wrong?

toscanini
Posts: 410
Joined: Thu May 05, 2005 5:42 pm

Re: Live API: ime signatures changes

Post by toscanini » Wed Jan 26, 2011 7:36 pm

You put a transport, the bar number changing to "6" or any position you like triggers a "set signature_numerator $1"

this should work

broc
Posts: 1151
Joined: Mon Jul 26, 2004 8:37 am

Re: Live API: ime signatures changes

Post by broc » Wed Jan 26, 2011 8:32 pm

Just did a quick test and found that set signature_numerator does *not* work as expected.
It doesn't change the signature at the current position, but at song start. Apparently a BUG.

On the other hand, observing signature_numerator seems to work correctly.

toscanini
Posts: 410
Joined: Thu May 05, 2005 5:42 pm

Re: Live API: ime signatures changes

Post by toscanini » Wed Jan 26, 2011 9:30 pm

Set seems to work here:

<pre><code>
----------begin_max5_patcher----------
825.3ocyXsrbaCBEcs7WAiltzMCfdX4tJs+FYxjAKQroiD3JgZSal7uWdH6n
DKEisrYxFQ.g78bObtOHOOKHbk3IZSH3af6.AAOOKHvrjdgft4AgUjmxKIMl
sEtpUJE7v41WwaqDsxRpz7RT2prByVEq94WSR2sU69j+cK0ZtvUD95Pv8cud
KQlugwW+PMMWZ2AJawMv4.zxL8.Ft649uQYcFeuw0q8xrY5GyczY3z+n.4ND
JoOYrb31Z5VJu.zPkt6nw615iBtjSpLtY32qYjRvODkEixCeLGfRrtsgCRsD
RVONPasF1+L+XHMEconl1pUz5gce7.tejituhaanbIQxD7d9IFBstVrdHAdf
ed.sw3pCm2qhTNMqpsp+Yz3j53FaDRsO16aBEws2pnK0APtnphxkGHNUZVPE
UN1YC7vyl3roc1fRsgdnTCckc.cM.EmrnOCmMUF12x43nyMZdJxRa9NbbzoI
KuJxuSkvfSSiEAsgjQnIE+O.qF0IEwoWlf8qUQmFZoBy.jyTdzYWwwvYyOVk
mtpuKLgvwmWkG7ELwmIoGHeiB7TvsfUD2y.FcgpNgsIxfotjBDmf5I7F5i9j
n7j0DdyVQ8HM6rb.9DMwzicCOVJHi7GCsKWzqK6Hc+oWOwNhifSti3jkdtgX
UnWs.DyA29qVBWpHQyDRqTzHI0prV8lHYUT.7lc+HkLNMWzxk8SicTVBmMoj
aNcsByyDSXIdoGDJUzlFxZ5.Y9kfF1ZNQ1VSePYFZMQJpAeA4rnJ85b4itFR
xrY+hwlgTOPUinCKY+ldi5EZD5b71UgZvHSofnznWCH8R1lwXFAoPqu.JrtA
n4oGNkauhuJjTThsottltvP+c60OP+nYngIlnCIlytP2tZXGgfhs2rxne55W
XJ7i4CMobe2+TGiw0q+VRqQzVmuCxcIR.uZ9BZijw22Hxc6in5smMrhBJuei
WUrhsBUs6NH.tevCPWQjtM2iBojTuhoDWnoX+xSIweBwTjKmcwdESwtfI+Jm
vNfHjeIInK4AzGbH+kH.4Jl7XxIm3I+d1oac93XB5ULgbrrxInlzsdkn5.S0
UgZ.mtX+r2fU0jWl8ePZdCcS
-----------end_max5_patcher-----------
</code></pre>

broc
Posts: 1151
Joined: Mon Jul 26, 2004 8:37 am

Re: Live API: ime signatures changes

Post by broc » Thu Jan 27, 2011 12:47 am

@toscanini

I've tried your patch. It changes the numerator at the specified position, but for the *whole song*.
So if you go back on the timeline, the previous signature is lost.
I wouldn't consider this as correct behavior.

Unfortunately, the intended behavior is not at all defined in the documentation..

pid
Posts: 354
Joined: Thu Nov 05, 2009 9:51 am

Re: Live API: ime signatures changes

Post by pid » Thu Jan 27, 2011 9:05 am

this was one of the first things i tried out when the m4l BETA came out. i even tried it interfacing with 'MaxScore' which is what i presume Georg is doing.

...it was also the first moment i realised m4l would not be what i wanted it to be. however it turned out it was great for other things.

i think it is LIVE that is at fault here, not max. live is not made for music which deviates from a constant 4/4. i do not think it ever will be, either, as the sanctimonious 'purity' of the main makers always seems to prevail. it means that the arrangement view is pretty pointless for max users. "max for reaper / nuendo" anyone?

i just use m4l for effects now... like some sort of lame synth-edit type programme. but i secretly still love it.
3dot... wrote: in short.. we live in disappointing times..

broc
Posts: 1151
Joined: Mon Jul 26, 2004 8:37 am

Re: Live API: ime signatures changes

Post by broc » Thu Jan 27, 2011 11:04 am

ShelLuser wrote:From what I can tell M4L does not support the time signature changes which you can setup in Live's arrangement view; only the so called Locators ('cue_points').
In fact, I was thinking that time signature changes could/should be inserted like cue_points.
But cue_points are actually different by design, ie. children of the Song class (=objects).
So I understand that time signature changes behave differently, not a bug but a limitation.

toscanini
Posts: 410
Joined: Thu May 05, 2005 5:42 pm

Re: Live API: ime signatures changes

Post by toscanini » Thu Jan 27, 2011 9:22 pm

And you could use scene names to change the meter. If you remove all the clip buttons from a scene the selection of it (can be done through the API) will only change the meter, not interfere with the rest of what you are doing.

Post Reply