For some time we have had the request from numerous users to implement the possibility to create templates (similar to the table format templates described here) for conversion in exporting from a Digas table into filesystem, e.g. drag and drop to the desktop.

This is now possible with the 2012.2.0 Release of DBM by using a new section in the DigaSystem registry named:  "Digas|FileSystemExport|AudioTemplates".

This section has two values: - "Default": Name of a default template, which will be selected as the initial choice, when the user converts an audio file with target "File System" - "Predefined": A list of audio templates, which will also be filled into the audio template drop-down list, when the user converts an audio file with target "File System". This is effectively the same as the "Allowed" parameter for database table templates, but it has been renamed to better reflect its purpose. In general, the user can export any format they want to the file system. This differs from the table specific AudioTemplates in that these templates are not meant to implement a restriction, but to simplify the selection of frequently-used formats. To convert a database entry's audio file, the user has to choose "Convert audio" from the context menu, and select "Export to Filesystem" as a target. This was already possible in previous versions of DBM. The new feature is that the contents of the template drop-down box are changed depending on the target ("Table" or "File System"). Also, when "File System" is the target, the fields for the audio parameters are never disabled and can be changed at will. This is different from the "Table" target, where only those parameters, which are not specified in the template, can be edited. Note that audio templates can also define settings for normalization. Therefore, normalization is automatically also supported for file system exports.

NOTES Media files are always exported "as is", when using either Drag&Drop to the Windows Explorer or using the "Export" context menu item! For Drag&Drop, the reason is straight-forward: It's simply not possible in Windows' drag&drop mechanism that the drop source (DBM) initiates a significant user interaction (opening a file format selection dialog), and therefore delay, once the drop target (Explorer) has signaled that it wants to receive data. Audio conversion is, by design, NOT a part of the "Export" workflow. When exporting to a table, you are not presented with an audio conversion option. Instead, DBM only checks if the source format is allowed in the target table. Only if the source format doesn't match, is the user requested to select from the possible target formats. However, for export to the file system, ALL formats are allowed! Therefore, if one applies the same logic applying to tables, audio conversion is never necessary. So we decided to be consistent in the workflow logic, and for the time being, there will be no user-selected audio conversion in the "Export" option.