What is the best practice for saving default values on a network? As a project gets more complex, this is really needed - connected to a button trigger, that loads everything back. I suppose a Table DAT would be a candidate, but… how?
It depends on where the values are going I guess? What are the values you are looking to be set? Are they in parameters, CHOP values, DAT entries?
A mix of things: mostly OP parameters (different types), mixed with CHOP values. these will be controlled via a OSC app. I know Lemur has scripts for this, but I’'d like to keep the defaulting ability inside TD.
Hi Rui,
For parameter values and perhaps DAT Cell values a DAT based or a dictionary saved in storage would be useful.
For a DAT solution i can see using a combination of 2 DATs:
- 1 DAT to save all the sources
- 1 DAT to save all the preset values
The sources DAT would hold the definition for each value which should be saved as a preset. As you see it here might not be complete and also is just an idea - when developing this system you might come up with a better structure. For example instead of saving all parameters of the “size” par in one line you could decide to list them separately as ‘sizex’ and ‘sizey’.
The second table would contain all the values for each preset in a row. The digits in the first row would be identifiers for which parameter these values belong to.
With a fairly extensive script and perhaps some custom parameters you could now build a little preset system which let’s you add/remove parameters and add/update/remove presets.
Recalling a preset would be as simple as going through the list of sources and pushing the associated values from the presets DAT onto them.
It would take me a little while to build this system so that’s why this is more of an idea layed out here. Maybe discussing it first we can come up with a more general solution.
For CHOP values coming in via OSC, the best would be to use a OSC Out to write these values back to the device or software sending OSC. The sender would then send you the new values and both sides are updated. If the sender is missing, I would suggest using a replace CHOP on the OSC In with the first input being all channels which should be coming from the sender and the OSC In CHOP reset so that all old values are removed.
Until the sender feeds new values, your system will use any values set via the first input of the Replace CHOP.
derivative.ca/wiki088/index. … place_CHOP
Hope this helps a bit
Markus
Thanks. I suppose what I’m missing is the syntax of inter-table communication. What I have is much cruder than what you’ve explained above…
preset-values.toe (5.05 KB)