The configuration

The appearance, part of the functions and how the metadata is displayed can be freely configured. The configuration is made ​​in the file dacapo.conf. This can be found at the home directory in the subdirectory .dacapo.

Linux example:
/home/username/.dacapo/dacapo.conf
Windows example:
C:\Documents and Settings\username\.dacapo\dacapo.conf

It is an XML-file whose format is explained in the following. For each parameter, see here. The file can be edited with any text editor. In case of a program update, the configuration file is also automatically updated. Thereby you lose any comments in this file.

Some parameters can be temporarily overridden during program call.

top

 

The structure of the file

According to XML parameter-values always have to be between an opening and a closing tag, thus directly between a ">" and "</". The Opening tag contains the parameter name and an attribute with a data type, which is explained below. It is generally written (with some exceptions) in lower case respectively lowerCamelCase.

The file is divided into several sections, these sections may be further subdivided again:

doku
Just for documentation purposes
version
For version reconciliation
gui
This section is used to configure the interface. It is further divided into the following chapters:
window
Valid if the program is running in windowed mode. Contains the same parameters as fullscreen.
fullscreen
Valid if the program is running in fullscreen mode. Contains the same parameters as window.
misc
Others, regardless of the mode - comprehensive
syncLyrics
How to handled the synchronized lyrics
metaData
How should the metadata be prepared
audio_engine
Information about audio output
debug
Where is to write the log file, and how detailed should be issued

The individual parameters within the chapters contain the attribute data type. Depending on this type is how the parameter is stored:

  • Parameter of type "int" can be specified as an integer.
    Example:
    <fontSize typ="int">25</fontSize>
  • Parameter of type "text" can be specified as an text. The characters "<" and ">" must not be used.
    Example:
    <language typ="text">english</language>
  • Parameters of the type "boolean" can be used as True/False. Where normally True stands for Yes and False for no.
    Example:
    <fullscreen typ="boolean">True</fullscreen>
  • Parameter of type "color" can be specified as RGB color space (eg 250,250,250 for white).
    Example:
    <lyricFontColor typ="color">255,165,0</lyricFontColor>
  • Parameter of type "dict" must be specified as a list, which means that here is another chapter given in the parameter.

 

top