Make save or save as great again in a standalone patch
Hi all,
When i created a standalone patch on my mac, save and save as ar greyed in the menu and impossible to use.
How i can resolved that issue please?
Thank for your answers.
E
up
help needed please :)
Standalone can not save anything from standard dialog
beside text if it gets opened or created new.
I f you need to store something that gets created or changed in the
standalone itself, like coll, text or anything else, you must use save, write
or other apropriate messages to that objects
Hi Source Audio
Thank you for your answer, "beside text if it gets opened or created new" doesn't work. The copied application doesn't open :(
My Initial max msp patch is a sampler directed toward many vst~. I use the objects pattstorage / Preset combined with json exports.
But it is impossible in the standalone app, to save the chosen plugins and find them when reopen the app.
I don't know why.
E
I don't think I can help you with infos you provide.
What on earth means
"the copied application does not open "
If you store something out of standalone, then read it
using loadbang when app starts.
To be able to do so, you must have that stored stuff in
the search path of the standalone, or use absolute path to
directory where you want that infos to be stored / recalled from.
"the copied application does not open " Sorry.. .I'm tired
I have tried to duplicate the standalone application , with the hope that it should be like a "save as" but that doesn't work, the new application doesn't open.
"If you store something out of standalone, then read it using loadbang when app starts. To be able to do so, you must have that stored stuff in the search path of the standalone, or use absolute path to directory where you want that infos to be stored / recalled from. "
Below i share the max msp patch.
It work well.
But If i use it in a standalone application, even of i store my presets and reload them, the saved plugins won't be reopen.
you probably copied standalone app in the same directory as original one.
That renamed it.
Standalone must keep same name as mxf file inside, otherwise it won't auto open mxf
------------
But now to your real problem :
you have to read help file for preset object,
add write and read messages to it to be able to export
and import presets.
In max, preset can embed it's data into patcher, but NOT in the standalone.
Means in plain text :
if you store some presets in the patch and SAVE THE PATCH
they will remain in the patch. ( if it is set so in the preset inspector)
When you build a standalone, it would copy whatever is in the patch
also into mxf file, but later it can't be restored in the same way because
mxf file is not changeable.
--------------
You have to clear all plugins from the menus, and scan them
in the standalone, otherwise you have a list there with the plugins
which maybe do not exist, or have totaly different order
and so embeded presets make no sense.
Same for the playlist - clear it.
Do you know what does preset object store ?
index of selected menu item , or it's stored item ?
Preset object is not proper storage for plugin name.
--------------
Add a standalone object to the patch and configure it properly.
anyway the menus are not connected to vst objects so what is the sense of this all ?
If you want to use that you must connect menu output to plug $1 message to load that plugin from menu.
same for bypass and mute toggles - what are they doing unconnected in the patch ?
And disable snapshots for vst objects.
First thank you a lot for your time and help! It's precious!
"you have to read help file for preset object, add write and read messages to it to be able to export and import presets."
If you open my patch you will see that i have already done that : there are "write" an "read " connected to the preset object. They are trigged by textbuttons.
"on max, preset can embed it's data into patcher, but NOT in the standalone."
I knew that : it's why i use "write" and "read" messages to save and reload presets with the standalone.
I have just triggered them with texbuttons.
"Means in plain text : if you store some presets in the patch and SAVE THE PATCH they will remain in the patch. ( if it is set so in the preset inspector) When you build a standalone, it would copy whatever is in the patch also into mxf file, but later it can't be restored in the same way because mxf file is not changeable."
Thank's for the explanation.
"You have to clear all plugins from the menus, and scan them in the standalone, otherwise you have a list there with the plugins which maybe do not exist, or have totaly different order and so embeded presets make no sense."
Sure! It is why I use a subpatcher called "p scan plug" that provided those abilities. It send messages
for each vst~.
"Do you know what does preset object store ? index of selected menu item , or it's stored item ? Preset object is not proper storage for plugin name."
In my patch "preset" object is associated with a dedicated "Pattstorage" object and a "autopattr @autoname"...
It seems I need to learn more about that : for me, with that combination, the preset store a pattstorage json file with all It need to be recall / reload later. I thought It was Ok for plugins name... So what I have to use for that please?
"Add a standalone object to the patch and configure it properly."
I have done that but I am not 100%,sure with the configurations I have choosen. I use Standalone help tutorial to try to understand.
"anyway the menus are not connected to vst objects so what is the sense of this all ? If you want to use that you must connect menu output to plug $1 message to load that plugin from menu. same for bypass and mute toggles - what are they doing unconnected in the patch ?"
Sorry but I don't understand you : they are connected together. Maybe have you opened the patch only in présentation mode ?
"And disable snapshots for vst objects." Ok I 'll do that.
EBBE
sorry but in the patcher you posted it is not connected at all.
try to load it yourself
also there is no pattrstorage in there
Externals and subpatcher files for Untitled1:
Max Object comment.mxo
MSP64 Object ezdac~.mxo
MSP64 Object live.gain~.mxo
Max Object message.mxo
Max Object number.mxo
Max Object panel.mxo
MSP64 Object playlist.mxo
Max Object prepend.mxo
MSP64 Object sfrecord~.mxo
Max Object textbutton.mxo
Max Object toggle.mxo
Max Object umenu.mxo
Max Object setplugpath.mxo
MSP64 Object vst~.mxo
this is all I get when listing externals and patchers...
Maybe you have some packages installed that I'm missing
I can imagine you had patcher in presentation mode
while executing copy compressed ...
That copies only things that are included in presentation.
Explains why the rest is missing.
You miss few important things here,
as first autopattr argument @autoname is missing a value
defaul is 0, but I guess you wanted 1.
Next is to activate "Pattr Stores Symbol" for vst select menus in inspector
or by pattrmode 1 message
That would store menu item into preset.
pattrstorage needs no preset object to function
but you do it whatever way you want.
When standalone starts, you should first scan plugins,
when that is done load stored presets file from disk and recall a preset
----------
You must read help files of objects you use to understand
how they work
P.S:
at the end this all has nothing to do with the initial question you asked in this topic.
I don't use any pattr stuff because it does sometimes more than one wants it to.
I stick with old fashioned coll for any storage, and that is perfect
for all my needs.
Hi source audio!
"You miss few important things here, as first autopattr argument @autoname is missing a value defaul is 0, but I guess you wanted 1. Next is to activate "Pattr Stores Symbol" for vst select menus in inspector or by pattrmode 1 message That would store menu item into preset. pattrstorage needs no preset object to function but you do it whatever way you want. When standalone starts, you should first scan plugins, when that is done load stored presets file from disk and recall a preset"
Thank you very must for all those advices! it's really helpful.
I will try all of that.
"P.S: at the end this all has nothing to do with the initial question you asked in this topic."
Yes , but I know now that is impossible to do.
"I don't use any pattr stuff because it does sometimes more than one wants it to. I stick with old fashioned coll for any storage, and that is perfect for all my needs."
I keep that in mind :)
Thank you again.
EBBE