Yuroun ·
When I save a preset for the SFZ module with the preset manager, then the filepath and filename to the sfz file is saved within the preset. Is it possible to save relative paths instead of the full pathname and filename?
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Yuroun ·
When I save a preset for the SFZ module with the preset manager, then the filepath and filename to the sfz file is saved within the preset. Is it possible to save relative paths instead of the full pathname and filename?
CoreStyler ·
yes you can. Just make the preset manager and sfz loader to work in a relative path.. So, add the relative path in your OSM before the path used for the sfz loader and the preset manager. For example: Fixed path [string] C:\\program files\yoursynth\soudbanks\ [string].... this will be the path. connect it in a way that the selected file for example ..\example\sfzfile.sfz is automatically addedd after the fixed path into the OSM. So by that way, the plugin will load the file present into Fixed Path + Relative path.
Use the primitives [string] and [string add].
If you can't do that, post OSM plz.
Yuroun ·
CoreStyler wrote: So by that way, the plugin will load the file present into Fixed Path + Relative path.
Use the primitives [string] and [string add].
If you can't do that, post OSM plz.
I tried it between the preset name and the loader. It doesn't work. I have really no clue how to do what you said. 😊
CoreStyler ·
I added the way for load the files in a fixed path. The preset is saved as "instrument" and Relative path. You should just make it working correcly.. i used a knob for moving from the index.
Yuroun ·
CoreStyler wrote: I added the way for load the files in a fixed path. The preset is saved as "instrument" and Relative path. You should just make it working correcly.. i used a knob for moving from the index.
Thanks for your effort, but it's a very clumsy way to alter the path to a sfz-file or I don't understand it.
My solution for this problem is now the following. When my application is finished and ready for customers I create a package wiht Inno Setup. The installer will install the library to the user document folder. After installation it will call a small utility (preset parser) who replaces my folder with the users one in the preset files. It's also a clumsy way, but for me easier to maintain.
CoreStyler ·
You don't need to do that! Just use the primitive "sysfolder" added in 2.0.3/4 (don't remember exactly what version). This primitive is compilant with the CSIDL of Windows (xp, vista, seven) so it retreive the document and setting folder of the host computer automatically. for more http://msdn.microsoft.com/en-us/library ... 85%29.aspx Look that example.
If you want to add the entire sample bank to "Documents and Settings" folder with the installer, just point the SFZ player to load in the specific directory... by adding the primtive "sysfolder" and maybe [string add] \your folder. In that way, the primitive take from Windows (by API calls) the "sysfolder" ...\username\docu.... Include that path into the synth. Then create an intaller who use the same folder you put into the "add string" directory. (remember to add \ before).
If you know innoDB continue with it. But if you prefer a more simple solution look at : http://www.advancedinstaller.com/download.html The free edition is good enough 😉
Yuroun ·
CoreStyler wrote: Just use the primitive "sysfolder" added in 2.0.3/4 (don't remember exactly what version).
Thanks, that worked perfectly for me 🙂
CoreStyler wrote: If you know innoDB continue with it. But if you prefer a more simple solution look at : http://www.advancedinstaller.com/download.html The free edition is good enough 😉
Thanks. I looked at it, but I think that InnoSetup is more powerfull. Here's the feature list:
Key features:
Support for all versions of Windows in use today: 7, 2008 R2, Vista, XP, 2008, 2003, 2000, Me, 98, 95, and NT 4.0. (No service packs are required.) Extensive support for installation of 64-bit applications on the 64-bit editions of Windows. Both the x64 and Itanium architectures are supported. (On the Itanium architecture, Service Pack 1 or later is required on Windows Server 2003 to install in 64-bit mode.) Supports creation of a single EXE to install your program for easy online distribution. Disk spanning is also supported. Standard Windows 2000/XP-style wizard interface. Customizable setup types, e.g. Full, Minimal, Custom. Complete uninstall capabilities. Installation of files: Includes integrated support for "deflate", bzip2, and 7-Zip LZMA/LZMA2 file compression. The installer has the ability to compare file version info, replace in-use files, use shared file counting, register DLL/OCX's and type libraries, and install fonts. Creation of shortcuts anywhere, including in the Start Menu and on the desktop. Creation of registry and .INI entries. Running other programs before, during or after install. Support for multilingual installs, including right-to-left language support. Support for passworded and encrypted installs. Support for digitally signed installs and uninstalls. Silent install and uninstall. Unicode installs. (Windows 2000/XP or later) Integrated preprocessor option for advanced compile-time customization. Integrated Pascal scripting engine option for advanced run-time install and uninstall customization. Full source code is available (Borland Delphi 2.0-5.0 and 2009).
And it's totally free 😉
Wrote something here? To have a post removed or your name hidden, write to [email protected].