Chunk File

Performs file operations on chunks such as import and export.

Settings

chunk name

Name of the chunk.

In chunk modules, the chunk name is case sensitive. This means that MYCHUNK is not equivalent to mychunk or MyChunk.

can be a RegEx (Regular Expression)
see regular expression.

  • ^a.* match any string starting by "a"
  • (?i)^a match any string starting by "a" or "A" (case insensitive)
  • .*a$ match any string ending by "a"
  • .*\d$ match any string ending by a number "1","2","3", etc.
  • .at matches any three-character string ending with "at", including "hat", "cat", "bat", "4at", "#at" and " at" (starting with a space).
  • [hc]at matches "hat" and "cat".
  • [^b]at matches all strings matched by .at except "bat".
  • [^hc]at matches all strings matched by .at other than "hat" and "cat".
  • ^[hc]at matches "hat" and "cat", but only at the beginning of the string or line.
  • [hc]at$ matches "hat" and "cat", but only at the end of the string or line.
  • \[.\] matches any single character surrounded by "[" and "]" since the brackets are escaped, for example: "[a]", "[b]", "[7]", "[@]", "[]]", and "[ ]" (bracket space bracket).
  • s.* matches s followed by zero or more characters, for example: "s", "saw", "seed", "s3w96.7", and "s6#h%(>>>m n mQ".
  • [hc]?at matches "at", "hat", and "cat".
  • [hc]*at matches "at", "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on.
  • [hc]+at matches "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on, but not "at".
  • cat|dog matches "cat" or "dog".
  • \\ to search the \ char (backslash)

item names

Names of the items to retrieve or on which the operation is performed, expressed as a comma-text.

In chunk modules, the item names are case sensitive. This means that item1 is not equivalent to Item1 or ITEM1.
To avoid mismatch between names and RegEx ^, ., $, *, +, ?, (, ), [, ], {, }, \, | are not allowed in the names.

can be a RegEx (Regular Expression)
see regular expression.

  • ^a.* match any string starting by "a"
  • (?i)^a match any string starting by "a" or "A" (case insensitive)
  • .*a$ match any string ending by "a"
  • .*\d$ match any string ending by a number "1","2","3", etc.
  • .at matches any three-character string ending with "at", including "hat", "cat", "bat", "4at", "#at" and " at" (starting with a space).
  • [hc]at matches "hat" and "cat".
  • [^b]at matches all strings matched by .at except "bat".
  • [^hc]at matches all strings matched by .at other than "hat" and "cat".
  • ^[hc]at matches "hat" and "cat", but only at the beginning of the string or line.
  • [hc]at$ matches "hat" and "cat", but only at the end of the string or line.
  • \[.\] matches any single character surrounded by "[" and "]" since the brackets are escaped, for example: "[a]", "[b]", "[7]", "[@]", "[]]", and "[ ]" (bracket space bracket).
  • s.* matches s followed by zero or more characters, for example: "s", "saw", "seed", "s3w96.7", and "s6#h%(>>>m n mQ".
  • [hc]?at matches "at", "hat", and "cat".
  • [hc]*at matches "at", "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on.
  • [hc]+at matches "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on, but not "at".
  • cat|dog matches "cat" or "dog".
  • \\ to search the \ char (backslash)

export direct

Exports chunks given by chunk name to a file.

chunk name can be a comma-text to export several chunks in the file. The item names field is ignored; all items of the chunks are exported.

import direct

Imports chunk data given by chunk name from a file.

It'll fill all the chunks given by the section headers of the chunk file [chunk-name$item-name].
chunk name can be a comma-text, containing the chunk names to import. Leave it empty to import all chunks from the file.
item names can be a comma-text, containing the item names to import. Leave it empty to import all items from the chunks.

root folder

Folder where the dialogs opens by default.

filename

Name of the file to import or export.

processing

Send a 1 value when the module is processing the operation (load, save, get etc).

A flow-from-1-to-0 must be used to trigger something when the operation is completed or canceled.

display errors

Displays various errors that may occur during chunk operations.

clear chunk before import

When enabled, clears the chunk before importing data into it. This ensures that any existing data in the chunk is removed prior to the import operation.

export mode

  • When set to rewrite file, the export operation will overwrite the existing file with the new chunk data.

  • When set to update file, the export operation will modify the existing file by adding or updating only the specified chunks, leaving other data in the file intact.

Common errors

Error: "invalid chunk name" / "invalid file name" Export is aborted if chunk name or filename is empty. Make sure both are set before triggering the export.

Import without "clear chunk before import" merges data When clear chunk before import is disabled, imported items are merged into the existing chunk. Items with the same name are overwritten, but other items remain. This can leave stale data behind. Enable clear chunk before import to start fresh.

"Update file" export can accumulate orphaned data In update file mode, the export only overwrites sections matching the exported chunk names. Other sections in the file remain intact. If those chunks have since been deleted or renamed, the file will contain orphaned data that gets re-imported next time. Use rewrite file for a clean export.

Chunk name with commas is treated as multiple chunks Both import and export support multiple chunk names as a comma-text. If your chunk name accidentally contains a comma, it will be interpreted as two separate chunk names.

Common Settings

info

show manual

Opens the web browser to display information or help about the selected object, if it exists.

For more details about information/help creation, see create-help-file.

description

Description of the module for internal help purposes only. The description is not displayed in the interface.

ID's

visible only in god mode, see setup-panel-tab-expert.

unique ID

Current private ID for this control used to identify the object.

preset ID

Current private preset ID for this control used for presets.

recreate ID

If you experience difficulties in Polyphonic mode, try to recreate new id(s) with this button.

repair ID s

Each Patch shared on the local network uses its own ID (identification number). If you experience issues of Patches that don't send information to the good target, this button will rebuild all these id's.

Object Remote Address

absolute

Absolute remote address. see objects-address.

local

Local to the current patch remote address. see objects-address.

user addr

User defined remote address. see objects-address.

See also

version 7.0.250121

Edit All Pages