|
|
Apr 11, 2013 at 10:13pm
Cannot observe property clip_trigger_quantization, is this an m4l Bug?
This patch works perfectly in Live 8. In Live 9 I get “bad number” errors. This patch is a test that should show a number that represents the Clip trigger quantization. To me this feels like a bug. Any thoughts? Thank you!
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
694.3oc0W1sjaBBEG+ZySgiWac.AASuq80XmNNnRMriAsBIc+XZe1Kfwroay
lkjl3zdShb.47+7iCGvmWDDU18.WEE9wv6BCBddQPfyj0Pvt1AQqYOT0xTtg
EslqTrFdT7XeZ9CZmcvjkdltZkP1TLvqziyLJijPWBIYj3vzk3DPNFhnwgYf
DPbHjj.B+xt2taitkq0O1yGe0nn8c0OvUboloEcRamvc1E0NAzUd+GnSh3qc
Rsjs1MIQeZPvZC+bWa8T2xMqERiebgT5Ql+CDeJHOAffnTi3QKS.jbDEZdDR
Svjb.c4qh.qqUhmbtFZCv8tbL1b9DZM9iEKr+D6I4k7uahw+.7shs7jtREeX
Ke3TKB4zWVDvPK4SAoI3rbDFahg7StJDe3JwADGBv+ML2KXMMXEaKutv3USL
Uvz5AQ4F8X1avdlEDUzyGTBklKq36Y8HruRHWGVF15IpgjkIYmCpKYxl2D2j
7Kg1vyh1W.mdqhB8CclEC8igUsh9ByBVSCen3aaXRs3owMxdlvBnVJBonyoh
wgfCcySSgWSvwzqBs6rKTbsuYZPrkQT3khH7+jH5Tk8zqDpZ9VQE2SFkSbHZ
oCQdsMTH0S+cTnkcy2PhtxPyla4aJk4bBCuxfuOubkrdyxVj+mnTe6lFyL+y
S.IBklPRgHTtgKlZSXykBnoFRgdeRoDMRVqkU6d5XDK81ep50EXBou7hRt93
BNq3xo.ylI4qu5rKxs1+cFp51LTMEOSGiG9RLWyUZgb+Eau6kirNXPqD00bW
+SBrVnXksbGE.Gc07rzC7czi6pdGLpapfH9.n74CPY9nG77oGrO5gLe5A4gd
FSflGA8ZecbEQmsDZnGpIc9niGa2SuP1LVbj02u09YXiSoSHliRtuav1jD6Z
JjiMcyXzf4dbSiOagc19wheA9zX2jB
-----------end_max5_patcher-----------
|
|
|
Apr 12, 2013 at 9:55am
That property isn’t listed in the Live Object Model so i’m assuming its something that isn’t exposed to the API…
Cheers
D
|
|
|
Apr 12, 2013 at 11:08pm
It is listed in the Live Object Model it is a property of the Song.
Thanks,
Loudon
[attachment=220906,5418]
Attachments:
|
|
|
May 11, 2013 at 12:03pm
Any word on this. I love the patch. and videos.
|
|
|
May 20, 2013 at 9:08am
Maybe this should be reported as a bug?
|
|
|
May 20, 2013 at 9:32am
The same problem happens with midi_recording_quantization
|
|
|
May 20, 2013 at 9:42am
Sorry, I should have mentioned this sooner. I have reported this as a bug and Cycling 74 has confirmed that it is a bug. So, it is just a waiting game right now, hopefully it will be addressed in the next update.
Loudon
|
|
|
Jul 18, 2013 at 8:21am
Any word when this will be fixed.
|
|
|
Jul 18, 2013 at 9:20am
Nope, no word, and the latest bug fix updates didn’t fix it. I think it might help if more people submit a bug report? this is really frustrating for me and I can’t even find a work-around.
Loudon
|
|
|
Jul 18, 2013 at 7:11pm
i figured a work around but doent included max which is a bummer to me. your patch was crucial to my lemur template for live. worked great in 8 but havent been able to control since. im gonna start using clyph – x midi remote script
and make custom x-control functions.
|
|
|
Jul 19, 2013 at 3:49pm
live.observer is certainly broken, but live.object is still in the game.
live.observer does spit out a 0 (along with the bad number error) any time that the quantization is changed. perhaps the 0 could trigger a message “get clip_trigger_quantization”~[live.object] so you can get the necessary values for your patch (and lesson) to work.
I happened to add you on twitter earlier today, and your tag is set to “teach me something” … well I wouldn’t go anywhere near that far, but I hope this helps :)
|
|
|
Jul 19, 2013 at 3:59pm
Matpec! you are so right! Thank you. I will try this out this weekend and see how it goes. Thanks again.
|
|
|
Jul 19, 2013 at 4:15pm
np. your vids about this patch helped me get on my feet with max. helping out here is the very least I could do
|
|
|
Jul 21, 2013 at 6:02am
Worked perfectly! Here is the patch with your beautiful bugfix(even a little thanks in the comments in the patch Matpec).
This link will download the patch.
|
