Jean-Philippe Jullin

I'm posting there because I can't manage to create a standalone version of my patch, using MaxMSP 8.1.8 on Windows 10 Pro 64bits. 

I am not sure if that's because I am using Node.script and a .js file, as well as subfolders containing some .html, .json and audio files, or if that's linked with some Jitter OpenGL objects... But when I build the application (including folder & appicon), everything seems fine, but I cant' get the .exe to launch. I used the standalone object, only unchecking CEF support, Gen support, and Status window visible at startup. The .mxf is working fine, and even if Avast love to scan the .exe, it never works. I tried multiple times, sometimes changing some parameters, tweaking the standalone object, but nothing changes. 

The strangest thing is that I've already managed to get a .exe that worked with some previous versions of the same patch, but it was really random, I'd say it worked 1/5 (without changing anything). But as now it is 0/100, I thought maybe someone could help me here !

I linked my patch, but as you won't have the .js, .json and .html files you can download the full folder 

Demo_08.maxpat

Hi everyone,

I'm posting there because I can't manage to create a standalone version of my patch, using MaxMSP 8.1.8 on Windows 10 Pro 64bits.  

I am not sure if that's because I am using Node.script and a .js file, as well as subfolders containing some .html, .json and audio files, or if that's linked with some Jitter OpenGL objects... But when I build the application (including folder & appicon), everything seems fine, but I cant' get the .exe to launch. I used the standalone object, only unchecking CEF support, Gen support, and Status window visible at startup. The .mxf is working fine, and even if Avast love to scan the .exe, it never works. I tried multiple times, sometimes changing some parameters, tweaking the standalone object, but nothing changes. 

The strangest thing is that I've already managed to get a .exe that worked with some previous versions of the same patch, but it was really random, I'd say it worked 1/5 (without changing anything). But as now it is 0/100, I thought maybe someone could help me here !

I linked my patch, but as you won't have the .js, .json and .html files you can download the full folder here

Hi everyone,

I'm posting there because I can't manage to create a standalone version of my patch, using MaxMSP 8.1.8 on Windows 10 Pro 64bi

standalone-with-node-script-never-launches

Yes, and I just retried but it doesnt change anything

I forgot to mention but I sometimes get the error "The instruction to 0x00000000130006A2 uses the memory address 0x000000000040. The state of the memory cannot be read." when I launch the exe for the first time

I forgot to mention but I sometimes get the error "The instruction to 0x00000000130006A2 uses the memory address 0x000000000040. The state of the memory cannot be read."  when I launch the exe for the first time

As far as I remember node.js can't work without CEF Framework.

And there were some issues node not finding scripts

but last time I did use node in Standalone on Windows 10 that was with max 815

As far as I remember node.js can't work without CEF Framework.
And there were some issues node not finding scripts
if they were embedded in mxf file
but last time I did use node in Standalone on Windows 10 that was with max 815


posting unlockable patch would at least help someone to troubleshoot it

without having to loose time trying to do so, I usually place a toggle somewhere to

get out of presentation and unlock the patcher window to be resizeable and editable.

I can hack it in few seconds to show all stuff inside though, but just wanted to let you think about it.

From a brief look - you should use own preferences name in the standalone inspector.

Also must enable CEF because of Node script.

by the way language selection is inverted - english makes it french

languages in the textbutton shoud be reordered.

That memory error you mention is because in that standalone 

I would as first not use package as such.

And don't include anything into standalone, add stuff manually

After building the standalone, build only mxf again

that builds mxf free of anything else but the patch itself.

Then replace mxf from initial build with it.

I have built that Demo_08 app without problem 

only that nw.gwerb external is missing I did not bother looking for that reverb.

After building of the standalone, one has most work left to do -

delete all unneeded things, in first place Mac externals and libraries which get

included as part of for example VIDDLL or node packages.

cycling - ist that really difficult to add only platform specific stuff

would reduce standalone size and also time needed to get rid of it.

Then remove all unneeded externals, extensions , languages from CEF and so on.

at the end standalone can get down to reasonable size, 

even if one has to use that CEF Framework.

P.S.
posting unlockable patch would at least help someone to troubleshoot it
without having to loose time trying to do so, I usually place a toggle somewhere to
get out of presentation and unlock the patcher window to be resizeable and editable.
Same for all subpatches.
I can hack it in few seconds to show all stuff inside though, but just wanted to let you think about it.

From a brief look - you should use own preferences name in the standalone inspector.
Also must enable CEF because of Node script.
by the way language  selection is inverted - english makes it french
languages in the textbutton shoud be reordered.
That memory error  you mention is because in that standalone 
you don't have Jitter GL Extensions.
------
I would as first not use package as such.
And don't include anything into standalone, add stuff manually
into standalone folders.
After building the standalone, build only mxf again
using this line at top of build script :

that builds mxf free of anything else but the patch itself.
Then replace mxf from initial build with it.
-----
I have built that Demo_08 app without problem 
only that nw.gwerb external is missing I did not bother looking for that reverb.
-----
After building of the standalone, one has most work left to do -
delete all unneeded things, in first place Mac externals and libraries which get
included as part of for example VIDDLL or node packages.
cycling - ist that really difficult to add only platform specific stuff
into standalone ? 
would reduce standalone size and also time needed to get rid of it.
Then remove all unneeded externals, extensions , languages from CEF and so on.
at the end standalone can get down to reasonable size, 
even if one has to use that CEF Framework.

Another thing which is a bug - on Windows 10 Max 8 is not capable of storing Audio

settings if it does not have menu and is close disabled.

window flags menu, window flags close, window exec

Another thing which is a bug - on Windows 10  Max 8 is not capable of storing Audio
settings if it does not have menu and is close disabled.
One has to:
window flags menu, window flags close, window exec
and then quit Max after some delay.

Sorry for the locked patch, that's my first time sharing a patch and I didn't think about it. I will make sure it's easily unlockable in the future, thanks for mentioning it.

It's strange that I got this memory error because the Jitter GL Extensions seemed to be there before. Also I had no idea that the best would be to create another mxf and add everything by hand.

Anyway, after some hours I figured out how to relocate everything inside the resource folder, and now everything is working perfectly. In case anyone is having the same issue, I found 

 how to get the audiofiles path working in application.

Again a massive thanks for your time Source Audio !

Huge thanks for your time and help !

Sorry for the locked patch, that's my first time sharing a patch and I didn't think about it. I will make sure it's easily unlockable in the future, thanks for mentioning it.

It's strange that I got this memory error because the Jitter GL Extensions seemed to be there before. Also I had no idea that the best would be to create another mxf and add everything by hand.

Anyway, after some hours I figured out how to relocate everything inside the resource folder, and now everything is working perfectly. In case anyone is having the same issue, I found here how to get the audiofiles path working in application.

Again a massive thanks for your time Source Audio !


Standalone with Node.Script never launches