File Export

facilitates effect creation and design by providing intuitive user interface elements. After completing effect design, the information must be exported in a form useable by the . The Export feature allows several different ways to save and access effect data. C Code, Java, BREW and IVT files contain effect information in IVT format. SKM, MP4 and K3G files contain effect information in Streaming Samples format. The reads IVT data from the exported files. Files can be exported in languages other than those that use the ANSI character set (such as English and European languages that use nearly identical alphabets). It is possible to export files in languages such as Russian, Korean, Japanese, etc.

Note: Although projects can contain links to Multimedia files, these links do not persist in any of the Exported files. Multimedia links are provided as an aid for effect design and are not embedded in IVT data.

IVT Data

IVT data is the native format used by the . This compact binary format contains information about Basis and Timeline effects. Through the , an application can access all the effects contained in the IVT data. All the Export types write out IVT data. The difference between the Export types is how the data can be accessed.

To Export IVT data, select File from the main menu and then select Export. The Export submenu provides the following file output choices: IVT, SKM, MP4, K3G, C Code, Java, BREW and IVT files.

Any Timeline effects that exist in the file will be exported first in the IVT data. This means that if the IVT data contains a single Timeline effect and several basis effects, the Timeline effect is guaranteed to be at index 0 in the IVT data. This is a useful optimization for applications that simply need to locate and play a single Timeline effect within an IVT data block.

IVT File

A file containing raw IVT data.

Any application environment with file system access can use one or several IVT files. With this export method, changes can be made to the effect parameters. Any changes to the IVT file can then be felt in the end user application without recompiling the application source.

Applications that do not have access to the platform file system, should embed IVT data in the application source.

Basis effect magnitudes may be adjusted slightly when exporting and importing IVT files.

SKM File

To export an SKM file, select a file to write to or enter a new filename from the Export To dialog box. If a new filename is provided, then a new SKM file is created containing audio and video from the original SKM file, including the effects in the Timeline. If an existing SKM file is selected, it is overwritten with the audio and video data from the SKM referenced in the Timeline coupled with the effect data from the Timeline.

validates the data being saved. If the Export To operation fails, an error or warning messages appears. Refer to the Troublingshooting section for a complete list of error and warning messages.

The data embedded in the SKM file contains all the necessary information to render the Timeline correctly, but to keep the SKM file size to a minimum for the streaming process to the handset, the information that is listed below is stored differently and unnecessary information is omitted.

It is recommended that data is saved to an IVS file for editing rather than reopening the SKM file. If changes need to be made to the file, edit the effect by opening the IVS file, editing the file and exporting the file again as an SKM file.

MP4 File

To export an MP4 file, select a file to write to or enter a new filename from the Export To dialog box. If a new filename is provided, then a new MP4 file is created containing audio and video from the original MP4 file, including the effects in the Timeline. If an existing MP4 file is selected, it is overwritten with the audio and video data from the MP4 referenced in the Timeline coupled with the effect data from the Timeline.

validates the data being saved. If the Export To operation fails, an error or warning messages appears. Refer to the Troublingshooting section or a complete list of error and warning messages.

The data embedded in the MP4 file contains all the necessary information to render the Timeline correctly, but to keep the MP4 file size to a minimum for the streaming process to the handset, the information that is listed below is stored differently and unnecessary information is omitted.

It is recommended that data is saved to an IVS file for editing rather than reopening the MP4 file. If changes need to be made to the file, edit the effect by opening the IVS file, editing the file and exporting the file again as an MP4 file.

K3G File

To export an K3G file, select a file to write to or enter a new filename from the Export To dialog box. If a new filename is provided, then a new K3G file is created containing audio and video from the original K3G file, including the effects in the Timeline. If an existing K3G file is selected, it is overwritten with the audio and video data from the K3G referenced in the Timeline coupled with the effect data from the Timeline.

validates the data being saved. If the Export To operation fails, an error or warning messages appears. Refer to the TroublingShooting section for a complete list of error and warning messages.

The data embedded in the K3G file contains all the necessary information to render the Timeline correctly, but to keep the K3G file size to a minimum for the streaming process to the handset, the information that is listed below is stored differently and unnecessary information is omitted.

It is recommended that data is saved to an IVS file for editing rather than reopening the K3G file. If changes need to be made to the file, edit the effect by opening the IVS file, editing the file and exporting the file again as a K3G file.

C Code

For C applications, writes out .c and .h files with IVT data embedded in the source code. The IVT data is stored in a byte array that can be accessed using the . Using this type of exported data, the effect information is hard coded into the C application. Any changes to the IVT data must be recompiled into the application.

This export method is useful when developing in C for a target platform that does not have file system access.

WIPI applications written in C using the GIGA interface to the can also use the C code exported from .

Java Code

For Java applications, can export IVT data into a .java file. The IVT data is stored in a class with a byte array member. The byte array contains all of the effect information from the exported project. The effect information can be accessed through the .

Any changes made to the project will not be reflected in the Java applet until the revised data is exported into a .java file and built into the applet.

This export method is useful for developing an application with Java.

BREW Code

can also export IVT data to C files that can be used by BREW applications. Since global variables are illegal on the BREW platform, the byte array containing the IVT data is declared const. Just like in other C applications, when this exported code is used, the effect information is hard coded into the C application. Any changes to the IVT data must be recompiled into the application.

This export method is useful when developing BREW applications, however, IVT files may also be used since BREW devices have a file system.