Macros
The automatic macros substitution feature may be very handy when creating multiple files via Cinegy Convert. Naming such files in an automated manner helps to avoid file name conflicts and maintain the logical structure of the storage.
This article provides a comprehensive explanation of how to use different macros in Cinegy Capture software and where they are applicable.
Supported Macro Types
The following macro types are supported:
Type | Description |
---|---|
These macros are translated by the system into corresponding metadata values, taken, for example, from Cinegy Archive or a source file. |
|
These macros are translated by the system into corresponding Windows OS environment variable values. |
|
These macros are translated by the system into automatically generated values such as time, date, GUID, etc. |
Metadata Macros
The metadata macros allow fetching values from different objects. For example, the following logical groups can be named:
Please see the following sections for additional details on each metadata object source.
Source Macros
The following macros are supported:
Macro | Description |
---|---|
|
Translates into the full file name for file sources or the node name for Cinegy Archive sources. |
|
Translates into the file name without extension for file sources or the node name for Cinegy Archive sources. |
|
Translates into the file extension for file sources or the empty string for Cinegy Archive sources. |
|
Translates into the full file path without the file name for file sources or the location in the database for Cinegy Archive sources. |
|
Translates into the value of the defined custom metadata field. |
|
Translates into the video aspect ratio. |
|
Translates into the video TV format, including frame size, frame rate, and aspect ratio. |
|
Translates into the video frame rate. |
|
Translates into the video height value. |
|
Translates into the video width value. |
|
Translates into the bits per sample value of the corresponding audio track. |
|
Translates into the number of channels value, where X is the zero-based index of the corresponding audio track. |
|
Translates into the format of the corresponding audio track. |
|
Translates into the sample rate value of the corresponding audio track. |
Cinegy PCS Task Macros
The following macros are supported:
Macro | Description |
---|---|
|
Translates into the conversion task ID. |
|
Translates into the conversion task name. |
|
Translates into the conversion task priority as a numeric value. |
|
Translates into the conversion task priority name, e.g., High, Medium, Low, etc. |
|
Translates into the conversion task creation date and time. |
|
Translates into the conversion task processing start date and time. |
|
Translates into the application name that creates the conversion task. |
|
Translates into the computer name on which the conversion task is created. |
|
Translates into the application name in which the conversion task is processed. |
|
Translates into the computer name on which the conversion task is processed. |
Cinegy Archive Job Macros
The following macros are supported:
Macro | Description | ||
---|---|---|---|
|
Translates into the Cinegy Archive job node ID. |
||
|
Translates into the Cinegy Archive job node name. |
||
|
Translates into the name of the user who created the Cinegy Archive job node.
|
||
|
Translates into the Cinegy Archive job node creation date and time. |
||
|
Translates into the name of the user who edited the Cinegy Archive job node.
|
||
|
Translates into the Cinegy Archive job node editing date and time. |
||
|
Translates into the Cinegy Archive job node comment. |
||
|
Translates into the Cinegy Archive job node description. |
||
|
Translates into the Cinegy Archive job node error. |
||
|
Translates into the name of the custom metadata field created for the Cinegy Archive job node. |
The example below demonstrates a typical scenario of using additional characters with the {job.creator.name}
macro:
Suppose the target folder path is C:\Temp, and the job node creator name is defined as job.creator.name == Munich / user.
The file name is defined as: FileName == "Some Name" {job.creator.name}.
As a result, a file named user.mxf (or .mp4, etc.) will be created inside the folder Some Name Munich, and the full path to the file will be:
C:\Temp\Some Name Munich\user.mxf
A similar logic applies to the {job.modifier.name}
macro.
Cinegy Archive Roll Macros
The following macros are supported:
Macro | Description |
---|---|
|
Translates into the Cinegy Archive Roll node creation date and time. |
|
Translates into the name of the user who created the Cinegy Archive Roll node. |
|
Translates into the identifier created for the Cinegy Archive Roll node. |
|
Translates into the Cinegy Archive Roll node editing date and time. |
|
Translates into the name of the user who edited the Cinegy Archive Roll node. |
|
Translates into the Cinegy Archive Roll node name. |
Cinegy Archive Clip Macros
The following macros are supported:
Macro | Description |
---|---|
|
Translates into the Cinegy Archive clip node creation date and time. |
|
Translates into the name of the user who created the Cinegy Archive clip node. |
|
Translates into the identifier created for the Cinegy Archive clip node. |
|
Translates into the Cinegy Archive clip node editing date and time. |
|
Translates into the name of the user who edited the Cinegy Archive clip node. |
|
Translates into the Cinegy Archive clip node name. |
Environment Variables
Environment variables used as placeholder for various system paths, folder and file names, are also supported.
The syntax is as follows: {env.somevariable}
.
For example, the {env.USERPROFILE} environment variable represents the path to the folder containing user profile settings.
You can use environment variables when defining various paths and folders.
Important
|
For more details on supported environment variables, refer to the MSDN website. |
Automatically Generated Macros
The following macros are supported:
Macro | Description |
---|---|
|
Translates into the UID. The |
|
Translates into the time. The |
UID Format Specifiers
The following table shows the accepted format specifiers for the UID format parameter:
Specifier | Return value format | Example |
---|---|---|
|
32 digits |
00000000000000000000000000000000 |
|
32 digits separated by hyphens |
00000000-0000-0000-0000-000000000000 |
|
32 digits separated by hyphens, in braces |
{00000000-0000-0000-0000-000000000000} |
|
32 digits separated by hyphens, in parentheses |
(00000000-0000-0000-0000-000000000000) |
|
Four hexadecimal values in braces, where the fourth value is a subset of eight hexadecimal values that is also enclosed in braces |
{0x00000000,0x0000,0x0000, {0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00}} |
Time and Date Format Specifiers
The following table describes the standard date and time format specifiers:
Specifier | Return value format | Example |
---|---|---|
|
Short date |
4/14/2025 |
|
Long date |
Monday, April 14, 2025 |
|
Full date/time (short time) |
Monday, April 14, 2025 3:12 PM |
|
Full date/time (long time) |
Monday, April 14, 2025 3:12:57 PM |
|
General date/time (short time) |
4/14/2025 3:12 PM |
|
General date/time (long time) |
4/14/2025 3:12:57 PM |
|
Month/day |
April 14 |
|
Round-trip date/time |
2025-04-14T15:12:57.0000000-07:00 |
|
RFC1123 |
Mon, 14 Apr 2025 15:12:57 GMT |
|
Sortable date/time |
2025-04-14T15:12:57 |
|
Short time |
3:12 PM |
|
Long time |
3:12:57 PM |
|
Universal sortable date/time |
2025-04-14 15:12:57Z |
|
Universal full date/time |
Monday, April 14, 2025 3:12:57 PM |
|
Year and month |
April, 2025 |
Note
|
Time and date format macros are resolved and displayed according to the regional formatting settings specified for the current OS in the Control Panel (Control Panel → Region → Formats). |
Important
|
All examples are given for the en-US culture. Refer to the MSDN article for details about date and time representations for different cultures. |
The custom date and time format is also supported.
For example, hh:mm:ss tt will display 03:12:57 PM.
Important
|
For a full list of custom date and time format specifiers, refer to the MSDN article. |