It turns out that this is not the problem, which is good for everyone, since we don't need to release new software to make this work, if you're experiencing the problem that lalo was having. If you are seeing similar issues and used to have Pluggo installed on your computer, do a search on your hard drive for the file "js32mt.dll". You probably have an old copy in windows/system32/ (while you're looking, make sure that maxapi.dll, maxaudio.dll, maxplug.dll and/or jitlib.dll are not lurking in windows/system32 as well -- this would only be the case if you had some old version of Pluggo installed).jeremydb wrote:OK, I think I know what the problem is -- jsliveapi was (probably) accidentally compiled in such a way that it requires Microsoft's .NET framework installed. I don't see the issue on my machine because it's installed as part of the development tools I use. I'm investigating and will post a link to a new build shortly, assuming that this is the problem.lalo wrote:hi jeremy,jeremydb wrote:
The posts in the Max window indicate that the Max object which contains the "definition" of the JS LiveAPI Object couldn't be found or loaded somehow.
Can you please look in your Max application folder (usually at c:/program files/cycling '74/max 5.0/), inside the "Cycling '74/jsextensions" folder, and let me know if there is a file called "jsliveapi.mxe"? If not, could you please search your hard drive for this file and let me know where it is (if it is there)?
Thanks
Jeremy
yes i have the jsliveapi.mxe inside c:/program files/cycling '74/max 5.0/Cycling '74/jsextensions folder.
hope we get it solved soon
a.
jb
If you do, remove it/them, restart Max/Live and everything should be up and running. The only copies you need for M4L are in Max 5.0/support.
Jeremy