cycling74/jit.mo

jit.mograph package

jit.mo's Issues

readme needs to be fleshed out

jit.mo.gen: fmod implementation

jit.mo.gen defines the following:

    static double mod_float64(double a, double b) {
        t_int32 n = (t_int32)(a/b);
        a -= n*b;
        if (a < 0)
            return a + b;
        return a;
    }

How does this differ from using double std::fmod(double,double); ?

ITM integration for attributes like speed

e.g. to set speed to 4n

one shot animation

package re-name

to avoid false expectations and law suits

FR: jit.mo.function - do not reset to start value in non-loop mode

When jit.mo.function finishes its loop, the final value is the start value instead of the end value. It seems like it should really stop at the end value. This would make line mode and saw mode much more useful.

Scale for jit.mo.join

Might be cool to have a global scale attr for jit.mo.join, similar to how speed functions.

needs package icon

test js functionality

help file overhaul

patchcordless binding of mo.gen and mo.join

add join-name and inlet-index attributes to mo.gen

jit.mo.gen: interpolation at the end of the function

e.g. to make the transition from end to beginning of a circle line up.

Ask Cory :-)

ref pages need to be authored

jit.mo.gen: is 'maxob_setup' neccessary?

I'm wondering if this code can/should be moved up into Min so that objects like this don't need to deal with this manually?

We could Skype too if what I'm suggesting isn't clear?

stop accum when context is disabled

Hi,

Hope you are all well and wish you a great new year.
I noticed the following:

[jit.time] keeps accumulating also when the context is disabled.
Therefore, if the output value of [jit.time] is 32.15748 at the moment that I disable the context (a.k.a. jit.world), re-enabling it after few seconds shows that [jit.time] starts outputting from a value higher than 32.15748, because it actually only stopped outputing, it did not stop accumulating.
I tried a workaround by sending an on/off message (bolean) to the [jit.time] as a consequence of turning on or off the context, and this still doesn't work. It looks like as soon as I turn off the context, the [jit.time] starts its counting without output and, while being off. Also, while the context is off [jit.time] doens't listen to a turn off message, I tried but when I re-nable the context, the output value of [jit.time] is nevertheless higher.

it is some time that I noticed this issue but only now it is becoming for me more and more of a bottleneck, as I am rendering images offline, without a costant fps because I am driving the render context with a custom "render bang" ==> the result is that I am downsampling the [jit.time] object.
Could this behaviour be improved, making the [jit.time] operations dependant on the actual render bang / fps?
I noticed now that the behaviour of [jit.time] ignores the context fps's setting.
This can be fixed by adjusting the [jit.time] speed according to the fps, but doesn't solve my issue.

Cheers,
Riccardo from Rotterdam

Jit.Mo package needs a launch patcher

FR: jit.mo.field mask outlet

Would be amazing to have a second outlet to pass the amount of the field's effect per-cell. This way any number of manipulations (scale/rotate for example could be driven by field amount)

jit.mo.gen: reference an audio buffer for the function

phase state not updated in attrui during animations

When using speed to animate a function, the phase value is not reflected in attached attruis.

jit.mo.join implicit context?

jit.mo connected objects don't seem to do anything unless sent a drawto attribute.

crash with jit.mo.join

So far I can only consistently reproduce this crash on OS 10.14. I'm using jit.mo 1.1.1, Max 8.0.6.

Steps to reproduce:

• Open the below patch
• Click the button

You might have to do this a few times for Max to crash. If doesn't crash, close the patch and copy/paste the code in again.

----------begin_max5_patcher----------
370.3ocqTEraCBCC8b3qHJmYU.EZg8qLUUEnYcAAInfoiop9uuDGPUqqaCM0
KF4WbreOaGNGPXk5QQOi9L8EJgbNfPPHG.YxmvZ4iUM7dLLV4..ZEKzeTG2v
aEfvrWn3kMBWHQSmoFZkpFAf2K9Jnd.tEsiCUuIUG2aDUfmM4EqhBoEac1jz
YKc2zMjGP1nKqepXlL9DCezI7ofUxUGYzctSuDD3LgKTkJw61TOmXPLhrhUK
gUJsrWPiou1n4v5DZRd11bZLa4pN4uTcbVD9IMC0cx80c5OpaKM22xAibjER
YO7NPqdUsVpr8fj7sY4ORkmDGiJOZyuo70+KkiYh0HU2tvirwg+01QudvTMm
3oFN8JeNH5AohCR6qgqwr1Gyca3KsNEKnNoeqNd4w65NIL8SAikvNWq0Fmad
H5JUdW7gJyHNImieChvM1gCXmLCFjVrwM9cMVq9fvnFj3DNvINaIwcFk82.8
cbuNvUqfKAeBmNuB1A
-----------end_max5_patcher-----------

CI Setup / Integration

FR: end of function bang

Would be great to have a loopnotify type message when ever the function finishes its cycle.

jit.mo.join with dim 1 returns a NaN

a jit.mo.join with dim 1 returns a NaN for computed planes:

----------begin_max5_patcher----------
443.3ocsU9saBBCEF+Z3ongqYDJDbxtZuGKFSENYqFokzVbXL9tu9GXpScvP
WhB47wgyW4W+Hr22KXEuEjAnWPug771664YkLBdc0dAUj1hMDossfJPJIuCA
gtqofVkUOtWoV.RfoHJJmsT.EJ2zmgShhCQooYlSYwliIZIzht6Sp1sAri56
IQTEePYu+WlBqohx1.J6hM4nHuQ0qh6TokV23qV+TZVumt9T6pAmgAAnElqb
v22bH7NoDivPwQ5eCPqLb7IOm4ISiVCNkoQqj7GLsXvm54dArVSUQTEHFhUy
SsOX4XyIb7DiVCOlynE9pzJ8Jz5WxVgc+ezTqhGIoLzqxZ.J0oMbeWanLnf2
vTmtgO.WcjnCHlnzz35sGyH3ZxkbE+7M4pFAKqHJAs8+htq4Z7lhviLZlk7P
hl2dLmgvzwhv7IQPqo1jzO9vgckazOGqRdinnevc1hNtzKAohxrj6jdLu0XZ
5p6bi0HSDYPmxe.FYWs3ALJsqo62oAgW9EN41zH00aAgrqaqI5T+ZtvTNOzV
RYtxXao.1R662oPD53oRmMaDtfa67YAtakWBBVC09Zruw4C9eQQqt+D
-----------end_max5_patcher-----------

jit.time.line incorrect timing

sending (start 0., end 1., interval 5000, speed 1, phase 0) to [jit.time.line] should ramp from 0 to 1 in 5 seconds according to help. however it takes approximately 500ms.
speed and time seem to be correlated incorrectly. from my tests it looks like the formula is

0.1*interval/speed ~= ramptime

the 0.1 seems arbitrary. here is a patch

----------begin_max5_patcher----------
1406.3ocyYssaiaCD8YmuBB8TagWWdQWKvVj12KZA5KEnYQ.sMcrBjnDjnyk
tX+26PRIG6XYKYaZmcePZEMkFdNyLGNCyWuYj2zhWD0dneA8unQi95MiFYFR
OvnlmG4kyeYVFu1LMuYE44Boxar82ThWTlwUUuhTKE0Bzm901erjqlsLU9v8
UhYJqQBwgSviQAw5qDbf9FEOAi9Ry6HWkmJyDJi0HuMXwJU6n3lQSmarbwzG
+DMwSO12t4F8kwmIVRkJQ0S7LDWNGUWJDvUgHGMqnpRjwUvyKJpzvEwmoVAS
TklKPEKLCUwyKmfDuTBfFl4TwR9SovzQq+re1LGy6n+NFK7Yxj6jESqgYrwK
cmDOg7S+P6a9ylo9ia7AZW6YoRwrhURC.B2O+GDyzTNi3ab.IT8s3ny2AD4R
GfkG3pzBYMpPh9ie+uHwnzDze92+CAXD+CDgE2DTkXuQhbUHVvofvbQcM+Aw
NHrVwqTH7jwHADiQf6qiNHX3eiah6f0cvXT4RNjXg6zYSaohJH4SpLj18cOi
cIqnDhINfZBGn9XSvQv9HKZmjEoCxhztVsyS8ZovZQOOzWbXjhk1PnF5xjHd
mDE.THBHOBbEg7ShYaLHMPOHEi8WOHvBsy7NowAXXd8PIIIzNI9fdiAYTSvG
IvPqQ9meLH9JECFrUHHYmHvtTVHFLSX1DtvDyM5YGJQhcbnzzUJUg7.HgEa1
ihDFaSJZudLNut.Rza1DjuE.UeuPxmlI1zauCHmxkObZ.kqTUqR6eyXBrm.H
xPHrC6xHaD.c+yoyUKMa1neqCQA5kwVaq50A2D3Xm7YGyS2U18jTX8sawRv1
7gXlqRK7cLiIEOCe2cqqCDTq5OYw2OtcqiiGdzNfGauvaQVAG1H3TwI75f0O
.hnLKhrNtnAlT.Exky2p5q9wH9jDDzP+zEE5U8qA918rbl320V66Dila88tN
Z9REL2q2zOLRqsyhnN0c5iu19yU4SOnmyOnowF7FQuziCnc34Xwe.4n6I3c1
R3KJF.GvL60XigOVNf0AGD5cHblJUs2tLBxsawzHHGbwDjo9e.N6dgOwVXMM
H4XhrOk8iHe.veeEpoqYZBxGpIqepgDYz0BoNp1pjqSoU5RHgJMGfq2Jp4SN
L9XC0Qe37Ymqa8XpZxyEUYyQ2ZCmPj9EwnFHSHDWIh0OlubkT1hoH7ENEl9c
TF7.a0ZPGtPCAFi2PIzAI5ggNNSu2Vt8aNvsqTK2FJti9sYrqT+186ZiXaxH
Atp+XF85HhqE2zcULwnleaaPuVpSGzCiXixQ2lUTTNjfbJMzJVvbTMrT5A09
7V+4mUjUTY+E7jDLIIDRNwSh0WXITRPjdSY7Vzm4kMak8t+LRF.pGeaNstXU
0rVy2dTwn2f3bQsJUZNikMlj9ry1XREUyElEJoSGoSMsl85xz3yxz5S076YS
eYH7nAXYsl7E.zCwz5CcBg2i5vfsj+GF89Np6ZZZ8A3drwy4oyKKfZBZDNBg
hcCzE6FXN7Uenb90OdM7IWnrM1PLsuCB7zmIyvBwImKcNDCgc.jFTR6GkPUR
2FlddovV2SuH9bcgICQI1AdvAIIcYx7FjXHwAXjMjMTYtfMYCI7v2EYdL1Yq
mCM4cozyYziX0cdkHNHK4BCMjXn3cLjs7adY4Shp5lYarAz7xi1h4iGadLUZ
ezz4nWk3oz14aZjviWA8inflQVUYVWduDZONTu7BHeTBs0ZkUAzAlrV8Z16K
4Wxysu5RQV4hzLw8Y7ohr1+7G.pVvWko1lIVTHUsuHfyeqJkm8VKI59r1psj
f0skr6+irQqR5Oac5+07Y08Y2xaia7KUBXFZTXVxMKwbX8k1p8zRull.0qw5
Rt0oY5U7lucy+CzRnU.L
-----------end_max5_patcher-----------

create tutorials for the package

output range of perlin function

For jit.mo.func using perlin as the function the range is around -.66 to .66. I know raw perlin noise output range is determined by dimensions [-sqt(D/4), sort(D/4)] so not clear where this range is coming from. In this case it would likely be better if the output range was scaled [-1,+1].

jit.mo.time @speed < 0 : output range is -3. -1.

jit.mo.time @mode function @speed -1
output range is -3. -1. (instead of -1. 1.)

I would expect it to stay in the same range [-1. 1.]

----------begin_max5_patcher----------
1191.3oc4YkriiaCD8rGf4ePPmsM3h01fbnmbI.AHmxoff.CYaZa1PRzfhZb
OYP92SQRI4ktsL8hZzNoOzhllj0qdEYUOQ+iO+oA9yDuvJ889h2e5MXvOfdF
X5S2yflNF3mm9x7rzRy.8SUJYE2eX82sQxJYEpTEWTLUxlqrqFEMYLZnGkln
efCP5GDxXj2e0LS9By5Il87HLoc8DUpLlR88ML6B46uaFkpumY51em4SUyWy
KVcYlV6Cl0ojox4Ef+0tfEUPG.BLNKduds.y1so2+4yeR+DdLzYxatHOGXqV
qoXuXPs+10rBuxML1BuexCM1Cr1lJkmLsXEyiW5MhN1aDd7Yocbfw2SL9NAa
XBB5TzNx+Bo1yu7tvenql+xqxT7xL9Bl7bTAlP2eaPD17.c.X2jJSyYJlbJq
Hclk.PsTR6dCy5MxrbPLXu4CCok3nuAAOois0Cuhs1t3StD.HWc.XYl.Vpyw
8AgFXNw.y25.XmD+dDXP2D3L33wEShmEbKEx7TyfCeeHUkX0J.3tsglDjXOC
17+KmUCOMqxgjSW4txN.V+lT0sJR3Ha1pH6YGRbmUjhtiEjbvx6JHoKAblhQ
5hFS2xWnVa1ipI+6LiVv1BjvqqR8LWMNWLVwyYdOkKVv7VVULWSzdOY2x4g8
dxVFaDZLw0bzn5GAcFShukroyEYBocznwSRP3jvglVwHZhtU.NJbRDDeN7D0
IyA2Al62rEcEb1JjYK7xE6BGNFBvQVwRjNi.TGRGeC005.DtPoz2QYE3I2fr
ht0Lf5GQCch3ONhFvA2rnAZRuoZnCz8wV0P3MKZHneTMD9HHZH1IMCA8fng3
+WoYvcICXrSRFnQejzLzEn62bEWzk1zTo3bWZC99eoMcY567k1XWX+LdwqtA
LC9zewQTZonRNuwEat2Ju8f3BVohWXn08F0D6fNcvyc6gcxdn6lAiu.+qcyf
TKip6q4wY.D5B.hua9az6q4bhdCNA8huC.fFcIan5kHbfSg3FfdOLXz6rAci
j0pVcJNWm3Jcyluwjk0Kh05PR+msUrhGZ+Luv9Ya4deI6a7loT2UpDxEqfDw
URaZ5WBqu1Rec0ZYAT2nFEZ+WaZSJ8iSZV.pHMy+qUK3heGJtTUN82XEU0Yo
A2dYJ7dVGwVyVsjmk0VocvtuBzPTWPotP7vl9OntLIYBFGqqFSwzHhoBMEZD
D.0QZoy5IgaqlG.0yIlp4gjnIAlVwDZ.U2Bc77H6rViJ.JBjALw1B5BenJ.f
WKVYq6QhPspszkdEaDxlXOL4jcynBjzKSWv0+BAsmtZh7MruUxNLjWUX09Zr
sy7vcqsgmeMMWjmNcMeEr4c0ZEawTg4mYn63T574fM2i4MuFIHAxvW0N+8Dm
qYYafsFroYoyXYivcCukBvP7+t9XmVm09uYVgpYYgCaeUxSy1SfhVo5A6nBp
imuUq6taZkM+yYUry4huJBn2wa0ehFG1teNQ2UOiTxCCRoOBH8WjLVwUD9sG
.o5+zsvgwPtrdFkjGBTR+fix+fkkI1dEg7XB7NmZ.FEiiMYlPAIA55W3iS4s
W5PhdTHTbO5Jj+63JzGFWQOS3w+Brve2J
-----------end_max5_patcher-----------

Jit.Mo needs a topic page for documentation

Opening inspector for jit.time.line, jit.mo.time and jit.mo.join crashes Max

If you open the inspector for jit.time.line, jit.mo.time or jit.mo.join, Max 8.0.2 will crash instantly.

jit.mo.time.line @loop 0 does not reach final destination

It looks like the phase never quite reaches 2.0 on @loop 0. Seems to stop at 1.999956.

----------begin_max5_patcher----------
630.3ocyVEraiBCD8L7Ufr1irHaS.R1S8+X0pHGvMwQfMxXZSUU+2W7XRZZC
sKAkrIWvgIC1u4My6Au56gVo1waPA+J32Addu564AgrA75u2CUw1kWxZfzPO
VpjsUnP2eoZMkbi4kZtaOPnv.zJlbMJ3O8ozksP1kD73j9f0LS9Fgb8RMO23
dzEzYQ3v.BN1sfsKTZD9vN8nRWwfrS6iHJ.LoVs8mzDzg8Vyp3FtdIWxVUBH
C+NXbPFPCsOZi4EWZHjMva991KgijQp3MMr078GuguCvHpdCqgG7CxWyUCyQ
z+MGk.KomRQGQHj4nAKZxEonuZiAymC8+XRJTowom2X.4lMFvLFcqXDMa6.x
xmEElMPMXK2yToLyQJwI.EQhOghrXA.USMmWfNklhiulCGeuh.eAEDDblSDf
AJII96TDwzqYQO09Odx8eWMSHy+59eoRUOT6mbMYBiZ85R9WxDBoYx1B80ry
Fzdcn9LM678.tLUtj+bG.NYteqvDUohLhJdToPxCdnwvzl.bTvCbYQ.oaETp
cQNzYrIlqZklik.CZzNc1LMywifFxZmLHcdP1jqJUZ2NfiVfIKRIgc+Zt8R7
BJIIqab7nM4lZyNVtffSoN6zridwyvxIv.a.8DMcJ5IX+g97m9BL.k13ejGZ
Ts578E59iM3cXVvaLBIyHTxiSh9gj1HJJ3xiEBEhFq1.pF7fcjQimjQfG62k
7eBOe5nt87S18EdruF3tBOz6L7DemM+LF9gjLQ73riX00Ow0M86I.kNC3sNe
+rP3VgzcK3niz7mD6yOAhvzclrlNG1Vsy0aW5Lj6QUEbsry+1ZN5aO427+qB
TqDD
-----------end_max5_patcher-----------

@dim attribute does not set dim of jit.mo.func

Dimensions of jit.mo.func cannot be set using in object attr, must be set using a message or jit.mo.join

Need tags and desc for abstractions

For example, when typing "jit.mo." in autocompletion the descriptions should come up for jit.mo.circle and friends.

In Max 5 you could add this in the patcher inspector for the abstraction. If this doesn't work anymore then we could manually write XML refpages.

jit.mo.gen: use a supplied/drawn function

jit.mo.func missing saw/phasor functype

It would be great to get a saw/phasor functype for jit.mo.func

Could just use "wrap" instead of "fold" as in the tri type.

fixed delta

[ from fb ]

What I would like is to go from @start 0. to @EnD 1. in N bangs and manually do these bangs. So using a @delta of 1/N would drive the output as I want but it's not the case. The internal timer keeps running which I didn't expect as automatic is set to 0.

The goal is to render the time loop in exactly N frames and save each frame as a single file.

S3 link needs to be updated

currently the S3 link thinks the prefix is jit.mograph, instead of jit.mo

jit.mo.time cannot be used in Javascript in Max

I would like to access jit.mo.time from within javascript, but the JitterListener doesn’t seem to catch it, nor it appears to have any “time” property that can be accessed