Forums > MaxMSP

Phasor~ lock bug? (was wait~ & transport @lock 1)

December 14, 2011 | 12:59 pm

Please see attached patch.
Why does a phasor~ @lock 1 create issues with delta~ ?
I notice that in the phasor~.help sub-patch [p using phasor~ with a metro] a delta~ of < ~-0.5 is used as a trigger, instead of <~0. Why is that? It does seem to work better, but you can still hear irregularities at higher rates,
cheers
Roger

(Max 5, OS 10.6, btw)

----------begin_max5_patcher----------
1430.3oc0as0aihCE94zeEVQ8gYzzlw9XysUqzd4k4ev9xpQqb.2T1RvQfSa
mYzze6KXCoMsIDGvf59RIlPHemuy24lI8GWLa9R4ihx4neA82nYy9wEyloOU
8Il0rd1707Giy3k5Kadrb8ZQtZ9Ul2SIdToOuLNlWlJy4YnOcu.UtI8NQI59
zxzkYBzCopaQatkWJKdB86Yx36Pj1aQVZtHVtMWeeflSdiLWkyWKz26+nHkm
0d4a3p3aSyW8OEhXkA4gf2B7UHVTX8AheT8AJaAF80lOT910o4YBk1FHu36n
L865uCBT8YLmNMwXPK+2qgv4OeCjaUs2Ab8I+4EWT+mqrj3xEOTcKeCukI4I
qEkkH.29dluH021HLl2746riyhV7M7AyiVeHPyJ.1ArRvgYEROXkxX4FwScY
DgXsQD3q8sT7tCG1Lf2hWxN7FyyheVpgclu8lLY0M4n9up2lWEwflujmupmN
SpmViS.MA3gclyz6vNSnGzPsNluR7FMtRrdiDcIw0B7VNwvF9D8hvSoLrfSX
tSfOARi.il.BAGKM.2IMNVYiqwK7POHKtqDsrhXDEnO7vse6293UnkaUnRUZ
VFJWpPqjxDz0UWCu50YoUbPU0kpWeCur9CUvUhxEGrhBsWUTH5Tmzn.slJxj
CJb3bJwycUTNV3FdgqCzBB0wVz.ckDJrvyMAZDvcAZGiMpUXiEeXjGNjOvti
ONR+FwYow28zQIjxzUUsv02FNvl9v7zrCi3pDQQtiUDeOgG2U+FdQM8RRMlR
6estai.2EfexliB07EB.ZuaNx2cv8X43gEnuHQUu6Fdwt3yyRXw.scRMc1G4
rJbrIo8dco8iEvMf59jldhYZuuu6p6Ogs2SaB2LYN5W68NbHsplNTxbKcVGL
Cn1kvfcNCabIuzXHidE.QxJwScahc2O5WD4h64yOIKz3a8LpznyQXFcHcI0c
sidDp4WeB0QyScVazBRwzrfue6tSzEo.1RJditdIQjo3OMZrhgNnAlz.NRp.
QiNsnPKQjSFFkVODxfxtG7B8hKxtSmfo5HKzsYhV2ux8dfYT9.c9Ce2Y5X2U
oPIWsJSbT++d98CYhglIKCX8rPAL9EJ9TG569qqarb.Bed1I.6fMsY7mcpcC
rI4udOrccVwPyl0B5X+1MgXv0JHieVwRQVkUTSRPeYmSJfhLC8X1uuvSD5Ps
e3a++WsqefoWYpoyY+.WkjjvF81rDOto.8gKSIetZnkO94KSAWuAMMjSyVhR
vmXqHNicngN5gPay2viuqyLuc1XweIJR34bzeJyR5hhXlROLcpFOSBGxv0Og
it7QUvyK2HKT1vQW8hns29hCcUCqeMnYRVHvYRtCSnQtiPq2875Iev9fGptv
V+RbaovyGap7iiLy5S5V4cFc.3OUc.LVk8a5CzncX9tZDQKdbV5uB8CN4U+Z
.zvr976SVkxsEwsVc6CEF8LRSDkpzbtJUl+hKhr+EcaZRhP+9sndcZxFYU.Y
CHPe8ftNqwTzHfIehWcKqzpRWUGp6Tqc0.QaUbNhcJvRmTBrFRdm.RgSKhHV
3RilVHQsQkwlVLwr.SdmIl.pQqSM6HQ.4sq.hN0kODsa0PsDeKrDv+LigwFr
iM6bdELaWMTzZUFmZzBSWVPKfDEl1DyXaooIDS1jY4U.ezwjUh+n2eX5biGa
h.M6xYXSz4dqZxrDBDWkYwpz1jIka0ggjSgooGR32UPxiYa1CxjgoPafD87f
D3Q0Z8flcJkra0.AqMEoBlT5yVD8Na1AuoU2aiFK7by75qy0FwpOvvrcql.v
NwCyfszidFx9fH8TfLyCrJfX9gOs2Jp44e6SME0pWMTCAFMCo4Q12B88W4bC
A.a6se5xDAL2Wui5qCqHM++ID5sa0PAqMQYvPF8rZwOu3+HHN7YB
-----------end_max5_patcher-----------

December 15, 2011 | 11:38 am

Bump (with pictures to attract attention ;-)

OK, so the above was at a signal vector of 256, whereby I couldn’t go above ~ 43 bpm before the locked phasor freaked out.
At a signal vector size of 64, I can get up to about 180 bpm before it all goes pear-shaped – but the clock is out by 11 ms @ 120 bpm (see pics).
The theoretical period is 125 ms; a free running phasor~ gets close enough, but with the locked phasor~ it’s around 114!
I know timer isn’t sample accurate, but shouldn’t the error still be the same for both the free running and the locked phasor~? So why is the locked phasor~ so far out?
Is it possible to get an accurate clock this way from a transport locked phasor~, or should I just give up?
Cheers
Roger


December 19, 2011 | 8:57 pm

Bump (with a ‘please’).

Perhaps if I make it more formally a bug report? Even if it’s just to tell me I’m doing something incredibly stupid, or going crazy, I’d appreciate a reply.

I was about to give up on this, because I couldn’t reproduce it on my iMac, whereas I can every time on my MacBook – but then I noticed my MacBook was at 48kHz, whereas my iMac was at 44.1 Hz.

Switching to 48kHz, I can reproduce.

Expected behaviour; a click from a phasor~ using [delta~] – [< ~ 0.] – [edge~] should produce an accurate, steady tempo, whether or not it’s @lock 1, at any (reasonable) sample rate.

Observed behaviour; At a sample rate of 48KHz, @lock 1 phasor~ has a frequency limit, depending on signal vector size, above which the tempo goes crazy. Furthermore, even below that limit, the measured tempo is out by several milliseconds from the theoretical value.

Method – see patch below.
Max 5.1.8 , OS 10.6.8 2.1 GHz Core 2 Duo MacBook and 3.06GHz Core i3 iMac

Cheers
Roger


----------begin_max5_patcher----------
1611.3ocya0zbiZCF9ryuBML4P2oNd02.scl1tW1ScldpWZ6zAaTbnACd.4j
r6Na9sWgD1waisPXCJ9hwBKiezCOueJ7WtZRv7xmD0Afe.7mfIS9xUSlnOUy
IlzNdRvpjmVjmTqmVvhxUqDExfolOSJdRpOehDTms7gZ.mBVjWt3dvbgZthZ
vlhZYx7bAHYd4CB.JJbFE7ge+21dIxyJTybSg95faO45D4h6xJV9OUhERC9h
H3Yvo.DgpOvXMGZF.961uTwlUYE4BoFon1SdaYgrHYkPixesJKIO3koWtQtc
9v1ylkpmY47+8FRbvdWj5rOquHHELZN6Wu5plWlNTDGlwsybT9rnvixbDaLG
pgqhfFhSefFMlDW3.RbJlnNYo3UD2O9WUo0qA0Up0BDB6qbBGZnCR3KbSiB6
vjBtmjB5.jBa6TMyS9o0BCTBB18i5A9ZqXquDVHUa+ESz7Ecz4KJ7Bhu3zSj
tZcWEFN95qH+vWEhGU+buhtjf4f5fiyGTHZO6MhVEggCkSH7A3C9Q4i4IEKC
lNv7xs4kJLYiA35EMMj2bfGN9L.8nLfBrIxFJPSEdPdHdZcE363JG0vYu+5L
z6TufsPV3Hs4ClZ7RiQ1Yqgv9g3G6mN0ILBaOcBKZ70InKGchLaknxF4Xran
LsffDNrxhCPNXR2jiu0GQujxhIatQUdfYuAxiiEUVJVstDbMpa9AgzRDtIrS
zH54.SuP7bDhMpAiuSeHMvuARiiUI0MvYLvikU2WqpfRJEp3MOd2m942MELe
ipHKYVdNnnTBVVVlBtQMGUoWKyyTrnpVK06uMot4KUkHE0y5cMVFpmDZjawi
eQVHlGJxBNylbKp0ILoM4V1HangvuskDznvbfOhC8Ee.eSS4eQd1h6e1Bgvg
r8BVSQCq+nCPHwGkOTkwUntPCIqH9bZxBaKeVrY4aJYlx19pc8PmF9gAm.Xq
WTtVXCrQHSB2XhoLM3tCmIb4ACnOd7LvGKApOccRkvVsVQFNGa5Yw.GI7.qR
ZvnatoBnlZpb8nKaBKVeaCpa5.GN5FbX60XOjlacpfww5BlnP9.qfQQmhDVk
zgrrvl2QTrQitqWHtbyp6fBnttmLfU0mtTXO..2DQT66iYtwD2K83GEEhGRb
uV1Na5ywElwCo05O8LvZxSbnIKANe69XXiZv8kZNfvfcRAGGTRIUjKSbQvXJ
rus4OCmf4Pdvhe6okldmhbvsdauSoieGgvcZFk0TRjGppCMSmlIXksv8LS+A
QgZ+Lb5nGtm.Gv38xxkKyst7hBMKO5fFo.e7HEl6tCmB+6spuaWeXbzKENMp
85EC6XkO5Iys9tj5xpmAnBvun2zWa7COJ1vOZmilxKG2XEnK.uh0hbECzPRX
6pmXSkK781k6iqdHCPY2beVlY26qDxj.I2W6qD5haektNC8dU0NcsoRaYJpo
FW33uoRHxaZGZ1TrNYw81XDrQtfLalfwMCpWZm+PTklTj.9PYdpyRnHq9em5
M2vxpjh50kURGx9xXegvC7dNEe.UiKryz8r1d8aNzr7Ag1z87lJefbLCzDXy
Zx9l38v1raQ1Ue3SS8cnv+d0At8L.rwOsY5YTbTtGJQjN.g80SQuwI+umrP8
Rr47eKYUWtoZw1el1lJAdYQlJpkYEIxrxh8lSySS0dS5trzTQw9IquJKccox
BnECGIYVWgDwAHgIWlPBcQAoXuRRXWfTyy+fOwDyk6bT+hIWr4Zba5Q0DxEL
w5GjBigMEW11PxPDZu1StcjoMkbU3HV6nycg.GsEB0z3iVn+siF9EhKBW+5D
zEDgh5Gj3HtQiP0GfrciNWirXG0A9i+bAQgWjHxe9ghbQi0y.sThVigIwlmT
G5tQmqAA0Ez5WG4DWbj62XvZHgtrfjKjjmyTg6.l3806Zn1epYWLhfnWOBiL
+mLvuLxGKDrmSME4Blf9ESPW8d3QL4RRGXuBITrqzD1eXh6ZF78wXs07DRLO
Jsg6Fctn0kvTrdVCTyS6i1Yh4AmmD85QstV333gx0BxI+19sZtFOKrNfTj2Q
D0kbntrfDgbRJPLxbHFsaz4lbfS8wnmprV7Q3ZyZZHd2HOjwL4TyX17+9Mlr
az4FewEWQjd53jQ0bZ6CgFEA2M5bEB7Kubo4ibtzpAe8p+C..bykS
-----------end_max5_patcher-----------

December 19, 2011 | 9:38 pm

Hi Roger,

Sorry for not seeing this sooner

I can reproduce in Max 6 as well.

We’ll have a look at it.

Cheers

Andrew


December 21, 2011 | 5:27 pm

And the story is….

phasor~ @lock requires Scheduler in Audio Interrupt

Seems to work fine with that on here

-A


December 21, 2011 | 8:04 pm

Not here :-(
Cheers
Roger

[attachment=179911,3108]

Attachments:
  1. Phasorlockthing.jpg

December 21, 2011 | 9:02 pm

Ah yes I can see it in 5.1.9 too. But not in 6.

Sorry – I would say there is no chance this will be addressed.

-A


December 22, 2011 | 11:56 am

OK, thanks for looking.
Time to move to Max 6, then!
Cheers
Roger


Viewing 8 posts - 1 through 8 (of 8 total)