Hi everyone,
We have just issued Modalys 3.6 (rc2) officially.
I wanted to thank you so much for your help in this cycle. Your comments, thorough testing, time and suggestions have been precious !
Stay tuned for the next maintenance cycle, and as usual, don’t hesitate to report or submit anything.
Best,
Robert
Hey Robert,
I have tried loading the .obj example and I get these errors:
modalys~: sample rate switched from [5.21502e-310] to [0]. Please reload your modalys script.
*** ERROR: Lua controller error: [string “…”]:21: attempt to call field ‘create_mesh’ (a nil value)
The error happened in max version prior to yesterdays update.
Then I updated Max to 8.1.10 and it still happened.
I am on OS 10.14.6
Same errors happens with the parametric bell example:
*** ERROR: Lua controller error: …emiddio/Documents/Max 8/Packages/modalys/misc//tools.lua:159: attempt to call field ‘create_mesh’ (a nil value)
Hi Emiddio,
Please redownload the files once again!
You’re quicker than lightning! In fact some erroneous build was briefly available on the website, and was quickly fixed thereafter.
Please let me know if everything is back to normal on your side.
Robert
I am sorry hahahaa. re-testing now.
I hope you remember my visit in 2018, I have been waiting for this day, literally for 3 years! 
Ok, all good on my side!
I still get some notifications on the sample rate changing, but they work!
modalys~: sample rate switched from [1.9098e-312] to [1.9098e-312]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [6.95312e-310] to [6.95312e-310]. Please reload your modalys script.
Thank you Robert!
Do you get this sample rate thing for every patch?.. The numbers make no sense and I haven’t seen that message for some years now…
Could you please post a patch?
Which OS/machine are your running?
Robert
I am running a macbook pro Retina mid-2013. I do have a suspicion that this may relate to the fact that I am doing mixing/film work on 48khz on my Apollo Twin Card and this may or may not interfere with max?
Anyway, this happens on all patches in examples at the moment it seems. So I opened one by one most of examples in alphabetical order in Modalys/Packages/examples. This the sequence changes I got.
modalys~: sample rate switched from [6.95313e-310] to [6.95313e-310]. Please reload your modalys script.
modalys~: sample rate switched from [1.39032e-314] to [1.19692e-314]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [5.21502e-310] to [6.95313e-310]. Please reload your modalys script.
modalys~: sample rate switched from [5.21502e-310] to [6.95313e-310]. Please reload your modalys script.
modalys~: sample rate switched from [5.21502e-310] to [6.95313e-310]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [5.21502e-310] to [6.95313e-310]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: the number of specified signal outputs (=2) is greater than what the script requires (=1).
modalys~: sample rate switched from [1.26481e-321] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
mlys.lua: initialization
440
modalys~: sample rate switched from [4.24399e-314] to [5.21502e-310]. Please reload your modalys script.
Mystery solved: the sample rate change is probably real (related, as you say, to your current work and setup) but badly formatted by Max’ ‘post’ function. This will be worked around in 3.6.x…
In any case this is harmless for you!
Robert
Ok good to know!
On that note, is there a specific vector size that you recommend using when working on Modalys in Max?