User Defined Value global store

stw · 8 May 2012

willzz32 wrote: Hi All

I was wondering if anybody would know a way to store a user defined value that would be saved when the presets are saved but not changed when a preset is changed.

For Example.

I want the user to be able to enter Global values within an exe (such as volume) and save them when the presets are saved but i do not what them to change as the presets change.

Any Ideas would be very much appreciated.

Cheers and thanks for the great forum.

Hi willzz32, use the "save text" and "text load" primitives to write and read global data. You could trigger the saving when the user sets any data and read it back e.g. with a "After load" trigger. Best destination for these data is one of the "system folders" provided by the "SysFolders" primitive. This outputs the paths to e.g. the users documents and program data folders. Other custom folders can be accessed through the CSLID. A list of these numbers and the paths can be found here: http://code.snapstream.com/api/bm11/Sna ... CSIDL.html

willzz32 · 8 May 2012

Hi stw

Thanks for the fast reply

Will the data be saved and loaded without the users having to do it manually. Would this data be tagged with the main preset save file so as to reload it automaticaly.

I am looking in to a midi control system with 127 cues(patches) but need 10 values to stay the same, eg hotkeys so i need to be able to store the preset files (save all) and have the hotkey numbers stored aswell and loaded with the preset file aswell(load all). The hotkeys define the preset number which can be entered by the user.

Hope this makes sense.

stw · 8 May 2012

willzz32 wrote: Will the data be saved and loaded without the users having to do it manually. Would this data be tagged with the main preset save file so as to reload it automaticaly.

You can determine when the triggers to save or read should be sent. As i posted in my last reply the typical method for your setting would be to fire a save trigger when the user actually changes any of that data and trigger a load when the app/plug is opened ("After load"). That way all data is loaded automatically and stays persistent when the application is opend.

trogluddite · 8 May 2012

It would also be quite simple to remove the extension from the preset file name, and put in a new one of your choice - so, for example, if you saved a preset bank "MyBank001.txt" you would automatically get a "preferences file" with the same name, e.g. "MyBank001.prf" etc. The two files would then be easy to keep "linked" to each other by loading/saving using the same name (and possibly folder) by default. Here's a couple of little helper modules to help with chopping and changing the file paths...

willzz32 · 8 May 2012

Hi trogluddite/ stw

Thanks so much for pointing me in the right direction thats exactly the thing i need. As you all know when youve spent weeks getting one part right it can make your brain a bit like mush, all thats needed is a little help in the right direction.

Thanks to alL