RobinSchmidt
ToolChain initial release
ooookayy...i have now packaged it all up for manual installation - and put it on temporary page on my website: http://www.rs-met.com/freebies_new.html Elan, if you can make installers from that, that would be nice. meanwhile, i'll try to address some final polishing (there are still some quirks, no showstoppers though)
Do you want me to send out Toolchain to my 600 subscriber e-mail list?
Edit: I mean send a link to your website along with description?
also, about the installer.
You will want to setup the paths for the installer creators so it can pull all the files from around you computer to package them so you don't have to manually drag files around. You know? So instead of sending me install files, you need to have the program know where the install files are. Ill create the first installer but then you should take the scripts and update locations of files for you.
Do you want me to send out Toolchain to my 600 subscriber e-mail list? Edit: I mean send a link to your website along with description?
sure, why not - but not yet. only when it's the final version. i'm still fixing some warts.
Ill create the first installer but then you should take the scripts and update locations of files for you.
yes, i guessed so.
somehow, i actually like the grayscale gui. using scope for a product picture looks also good - but there could be some more action on the screen (higher glow, maybe) :-) ....maybe something with a nice 3D synth
...i'm currently working on a hidden feature to take easy screenshots of editors (ctrl+alt+click will save a screenshot). that will make it convenient to create product pictures. no need to deal cropping the image and stuff like that
so, how do you get rid of the plugin window? i guess, it's possible to write a script for that for an image editor?
you can't use user folder for mac, unless you never want to offer a standalone.
you can't use user folder and non-user folder in the same installer
the correct location is to not use the user folder anyway.
user folder is for user-created content, user-created samples and presets that the application itself handles, not the installer
again that's why I've been saying for months you need to create a preset browser to handle all this.
what has this to do with standalone vs plugin? has a standalone version different permissions than the plugins? i just added a standalone build version for ToolChain. seems to work here. also, the audio-options menu looks complete again.
actually I don't know at all how to install to user folder. Not even Jim Credland could tell me how.
Standalone should go in application folder (and there's no user applications folder) btw... ill get you exact paths in a sec
component: Library/Audio/Plug-Ins/Components
standalone: Applications/ OR Applications/RS-MET
presets and samples: Library/Audio/Presets/RS-MET/ToolChain/etc.
you can also put presets with the application folder btw
Edit: in that case you would want Applications/RS-MET/Toolchain/etc.
what is the process of making an installer on mac anyway? i've just looked at your M-Ref.pkgproj - it certainly doesn't look like anything that anyone would write by hand, so which tool is used for this?
here's the packages file (you open with macpkg and build, similar to inno setup)
wait I think i gave you the wrong software, try this: http://s.sudre.free.fr/Software/Packages/about.html
ok - i can build the installer on windows. there's a problem: the installer allows the user to select/browse for the directory where the support files will be installed. can i prevent this, i.e. fix the folder without giving the user the option to browse? because, if the user actually does that and lets the presets be installed into a different folder, the plugin will not find them
edit: also: it says "Unknown" for the publisher (no big deal, but would be nice if that would work)
hmm...on the mac, when i use your script, the presets are not being installed (when i run the installer, the preset (sub)package is grayed out). i changed the script such that the presets become part of the AU package and install the presets now into Users/Shared/RS-MET ...that seems to work...however, i have no idea if that is a standard practice.
i have not much time left - have soon to visit family for christmas dinner. sooo - i guess, i'll just release the manual release package today. figuring out all the details of where and how to install needs some more careful consideration.
anyway, thank you and merry christmas! :-)
I can do all the necessary things for the installer btw, just send me the files.
how did you get the installer to use user folder?
you should have preset separate/toggleable because you don't yet separate user and factory presets, so if user made any changes to presets, it will get overwritten.
send me your non working scripts as well
i could fix the mac-script myself
how did you get the installer to use user folder?
the Users/Shared folder appears in the packages tool as possible installation target - probably because it's not user-specific but accessible to all users
you should have preset separate/toggleable because you don't yet separate user and factory presets, so if user made any changes to presets, it will get overwritten.
i actually think, if the user modifies a factory preset, he would save it under a new name - in this case, the new file will remain upon re-installation, right? ...or will the installer replace the whole folder contents (i.e. delete the existing folder and put the new one in)? anyway, i have it now in two packages anyway: "ToolChain (AU)" and "ToolChain (Data)"
it will replace files that share the same name
you can remove the option to have paths customizable in inno setup
search for the term: promptifolder remove it
ok, thanks! will do that.
edit: oh - i just realized that it just asks for the plugin-folder path not for the data-folder path. weird...did i miss something yesterday? anyway...so it's actually all good. the plugin folder should be customizable