[Config window - Tag page]

(please move over the option/feature of your interest and then left click it...)

▲Top

> Accept current configuration

With this button you will accept and save current configuration.

▲Top

> Cancel configuration

With this button you will cancel current configuration and rollback to previous one.

▲Top

> Default configuration

With this button you will load the default configuration. NOTE - You need to press accept button to confirm the default configuration.

▲Top

> Associate CUE Splitter with .cue extension

With this button you can associate .cue file extension with CUE Splitter! So if you double-click over a .cue file from Windows explorer, it will be automatically loaded by CUE Splitter. NOTE - You need at least a "power user" account level to use this feature.

▲Top

> Write tags in Unicode format (where applicable)

If you check this option, when a tagging system can be written in both ANSI and Unicode format (actually only ID3v2 support this), Unicode format is used. If you uncheck this option, ANSI format is used. When ANSI format is selected, will be used the codepage selected in default codepage of Miscellaneous page. Today's players and taggers, fully support Unicode format, so this could be the preferred option. [Default = checked].

▲Top

> Write ID3v1 tag on generated MP3 files

If you check this option, ID3v1 tag is written at the end of each generated MP3 file. ID3v1 support only ANSI format. [Default = checked].

▲Top

> Write ID3v2 tag on generated MP3 files

If you check this option, ID3v2 tag is written at the beggining of each generated MP3 files, zero-padded into an 8 Kb block boundary. ID3v2 support both ANSI and Unicode format. [Default = checked].

▲Top

> Write FLAC tag on generated FLAC files

If you check this option, vorbis comment is written into metadata comment block of each generated FLAC file. Vorbis comment support only Unicode format (using UTF-8 encoding). [Default = checked].

▲Top

> Write APE tag on generated APE files

If you check this option, APEv2 tag is written at the end of each generated APE file. APEv2 support only Unicode format (using UTF-8 encoding). [Default = checked].

▲Top