shithub: aubio

--- a/doc/full.cfg

+++ b/doc/full.cfg

@@ -1,14 +1,14 @@

-# Doxyfile 1.6.1

+# Doxyfile 1.8.3.1

 # This file describes the settings to be used by the documentation system

-# doxygen (www.doxygen.org) for a project

+# doxygen (www.doxygen.org) for a project.

-# All text after a hash (#) is considered a comment and will be ignored

+# All text after a hash (#) is considered a comment and will be ignored.

 # The format is:

 #       TAG = value [value, ...]

 # For lists items can also be appended using:

 #       TAG += value [value, ...]

-# Values that contain spaces should be placed between quotes (" ")

+# Values that contain spaces should be placed between quotes (" ").

 #---------------------------------------------------------------------------

 # Project related configuration options

@@ -22,9 +22,9 @@

 DOXYFILE_ENCODING      = UTF-8

-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded

-# by quotes) that should identify the project.

+# The PROJECT_NAME tag is a single word (or sequence of words) that should

+# identify the project. Note that if you do not use Doxywizard you need

+# to put quotes around the project name if it contains spaces.

 PROJECT_NAME           = aubio

 # The PROJECT_NUMBER tag can be used to enter a project or revision number.

@@ -33,6 +33,19 @@

 PROJECT_NUMBER         = "0.4.0alpha full"

+# Using the PROJECT_BRIEF tag one can provide an optional one line description

+# for a project that appears at the top of each page and should give viewer

+# a quick idea about the purpose of the project. Keep the description short.

+PROJECT_BRIEF          =

+# With the PROJECT_LOGO tag one can specify an logo or icon that is

+# included in the documentation. The maximum height of the logo should not

+# exceed 55 pixels and the maximum width should not exceed 200 pixels.

+# Doxygen will copy the logo to the output directory.

+PROJECT_LOGO           =

 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)

 # base path where the generated documentation will be put.

 # If a relative path is entered, it will be relative to the location

@@ -112,7 +125,9 @@

 # only done if one of the specified strings matches the left-hand part of

 # the path. The tag can be used to show relative paths in the file list.

 # If left blank the directory from which doxygen is run is used as the

-# path to strip.

+# path to strip. Note that you specify absolute paths here, but also

+# relative paths, which will be relative from the directory where doxygen is

+# started.

 STRIP_FROM_PATH        = ../src

@@ -126,7 +141,7 @@

 STRIP_FROM_INC_PATH    =

 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter

-# (but less readable) file names. This can be useful is your file systems

+# (but less readable) file names. This can be useful if your file system

 # doesn't support long names like on DOS, Mac, or CD-ROM.

 SHORT_NAMES            = NO

@@ -181,6 +196,13 @@

 ALIASES                =

+# This tag can be used to specify a number of word-keyword mappings (TCL only).

+# A mapping has the form "name=value". For example adding

+# "class=itcl::class" will allow you to use the command class in the

+# itcl::class meaning.

+TCL_SUBST              =

 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C

 # sources only. Doxygen will then generate output that is more tailored for C.

 # For instance, some of the names that are used will be different. The list

@@ -207,22 +229,40 @@

 OPTIMIZE_OUTPUT_VHDL   = NO

-# Doxygen selects the parser to use depending on the extension of the files it parses.

-# With this tag you can assign which parser to use for a given extension.

-# Doxygen has a built-in mapping, but you can override or extend it using this tag.

-# The format is ext=language, where ext is a file extension, and language is one of

-# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,

-# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat

-# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),

-# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.

+# Doxygen selects the parser to use depending on the extension of the files it

+# parses. With this tag you can assign which parser to use for a given

+# extension. Doxygen has a built-in mapping, but you can override or extend it

+# using this tag. The format is ext=language, where ext is a file extension,

+# and language is one of the parsers supported by doxygen: IDL, Java,

+# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C,

+# C++. For instance to make doxygen treat .inc files as Fortran files (default

+# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note

+# that for custom extensions you also need to set FILE_PATTERNS otherwise the

+# files are not read by doxygen.

 EXTENSION_MAPPING      =

+# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all

+# comments according to the Markdown format, which allows for more readable

+# documentation. See http://daringfireball.net/projects/markdown/ for details.

+# The output of markdown processing is further processed by doxygen, so you

+# can mix doxygen, HTML, and XML commands with Markdown formatting.

+# Disable only in case of backward compatibilities issues.

+MARKDOWN_SUPPORT       = YES

+# When enabled doxygen tries to link words that correspond to documented classes,

+# or namespaces to their corresponding documentation. Such a link can be

+# prevented in individual cases by by putting a % sign in front of the word or

+# globally by setting AUTOLINK_SUPPORT to NO.

+AUTOLINK_SUPPORT       = YES

 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want

 # to include (a tag file for) the STL sources as input, then you should

 # set this tag to YES in order to let doxygen match functions declarations and

 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.

-# func(std::string) {}). This also make the inheritance and collaboration

+# func(std::string) {}). This also makes the inheritance and collaboration

 # diagrams that involve STL classes more complete and accurate.

 BUILTIN_STL_SUPPORT    = NO

@@ -238,10 +278,10 @@

 SIP_SUPPORT            = NO

-# For Microsoft's IDL there are propget and propput attributes to indicate getter

-# and setter methods for a property. Setting this option to YES (the default)

-# will make doxygen to replace the get and set methods by a property in the

-# documentation. This will only work if the methods are indeed getting or

+# For Microsoft's IDL there are propget and propput attributes to indicate

+# getter and setter methods for a property. Setting this option to YES (the

+# default) will make doxygen replace the get and set methods by a property in

+# the documentation. This will only work if the methods are indeed getting or

 # setting a simple type. If this is not the case, or you want to show the

 # methods anyway, you should set this option to NO.

@@ -262,6 +302,22 @@

 SUBGROUPING            = YES

+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and

+# unions are shown inside the group in which they are included (e.g. using

+# @ingroup) instead of on a separate page (for HTML and Man pages) or

+# section (for LaTeX and RTF).

+INLINE_GROUPED_CLASSES = NO

+# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and

+# unions with only public data fields will be shown inline in the documentation

+# of the scope in which they are defined (i.e. file, namespace, or group

+# documentation), provided this scope is documented. If set to NO (the default),

+# structs, classes, and unions are shown on a separate page (for HTML and Man

+# pages) or section (for LaTeX and RTF).

+INLINE_SIMPLE_STRUCTS  = NO

 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum

 # is documented as struct, union, or enum with the name of the typedef. So

 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct

@@ -278,16 +334,27 @@

 # For small to medium size projects (<1000 input files) the default value is

 # probably good enough. For larger projects a too small cache size can cause

 # doxygen to be busy swapping symbols to and from disk most of the time

-# causing a significant performance penality.

+# causing a significant performance penalty.

 # If the system has enough physical memory increasing the cache will improve the

 # performance by keeping more symbols in memory. Note that the value works on

-# a logarithmic scale so increasing the size by one will rougly double the

+# a logarithmic scale so increasing the size by one will roughly double the

 # memory usage. The cache size is given by this formula:

 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,

-# corresponding to a cache size of 2^16 = 65536 symbols

+# corresponding to a cache size of 2^16 = 65536 symbols.

 SYMBOL_CACHE_SIZE      = 0

+# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be

+# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given

+# their name and scope. Since this can be an expensive process and often the

+# same symbol appear multiple times in the code, doxygen keeps a cache of

+# pre-resolved symbols. If the cache is too small doxygen will become slower.

+# If the cache is too large, memory is wasted. The cache size is given by this

+# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,

+# corresponding to a cache size of 2^16 = 65536 symbols.

+LOOKUP_CACHE_SIZE      = 0

 #---------------------------------------------------------------------------

 # Build related configuration options

 #---------------------------------------------------------------------------

@@ -304,6 +371,11 @@

 EXTRACT_PRIVATE        = YES

+# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal

+# scope will be included in the documentation.

+EXTRACT_PACKAGE        = NO

 # If the EXTRACT_STATIC tag is set to YES all static members of a file

 # will be included in the documentation.

@@ -326,7 +398,7 @@

 # extracted and appear in the documentation as a namespace called

 # 'anonymous_namespace{file}', where file will be replaced with the base

 # name of the file that contains the anonymous namespace. By default

-# anonymous namespace are hidden.

+# anonymous namespaces are hidden.

 EXTRACT_ANON_NSPACES   = NO

@@ -372,7 +444,7 @@

 # in case and if your file system supports case sensitive file names. Windows

 # and Mac users are advised to set this option to NO.

-CASE_SENSE_NAMES       = YES

+CASE_SENSE_NAMES       = NO

 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen

 # will show members with their full class and namespace scopes in the

@@ -386,6 +458,12 @@

 SHOW_INCLUDE_FILES     = YES

+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen

+# will list include files with double quotes in the documentation

+# rather than with sharp brackets.

+FORCE_LOCAL_INCLUDES   = NO

 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]

 # is inserted in the documentation for inline members.

@@ -405,7 +483,13 @@

 SORT_BRIEF_DOCS        = NO

-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.

+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen

+# will sort the (brief and detailed) documentation of class members so that

+# constructors and destructors are listed first. If set to NO (the default)

+# the constructors will appear in the respective orders defined by

+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.

+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO

+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.

 SORT_MEMBERS_CTORS_1ST = NO

@@ -425,6 +509,15 @@

 SORT_BY_SCOPE_NAME     = NO

+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to

+# do proper type resolution of all parameters of a function it will reject a

+# match between the prototype and the implementation of a member function even

+# if there is only one candidate or it is obvious which candidate to choose

+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen

+# will still accept a match between prototype and implementation in such cases.

+STRICT_PROTO_MATCHING  = NO

 # The GENERATE_TODOLIST tag can be used to enable (YES) or

 # disable (NO) the todo list. This list is created by putting \todo

 # commands in the documentation.

@@ -450,15 +543,16 @@

 GENERATE_DEPRECATEDLIST= YES

 # The ENABLED_SECTIONS tag can be used to enable conditional

-# documentation sections, marked by \if sectionname ... \endif.

+# documentation sections, marked by \if section-label ... \endif

+# and \cond section-label ... \endcond blocks.

 ENABLED_SECTIONS       =

 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines

-# the initial value of a variable or define consists of for it to appear in

+# the initial value of a variable or macro consists of for it to appear in

 # the documentation. If the initializer consists of more lines than specified

 # here it will be hidden. Use a value of 0 to hide initializers completely.

-# The appearance of the initializer of individual variables and defines in the

+# The appearance of the initializer of individual variables and macros in the

 # documentation can be controlled using \showinitializer or \hideinitializer

 # command in the documentation regardless of this setting.

@@ -493,15 +587,27 @@

 FILE_VERSION_FILTER    =

-# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by

-# doxygen. The layout file controls the global structure of the generated output files

-# in an output format independent way. The create the layout file that represents

-# doxygen's defaults, run doxygen with the -l option. You can optionally specify a

-# file name after the option, if omitted DoxygenLayout.xml will be used as the name

-# of the layout file.

+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed

+# by doxygen. The layout file controls the global structure of the generated

+# output files in an output format independent way. To create the layout file

+# that represents doxygen's defaults, run doxygen with the -l option.

+# You can optionally specify a file name after the option, if omitted

+# DoxygenLayout.xml will be used as the name of the layout file.

-LAYOUT_FILE            =

+#LAYOUT_FILE            =

+LAYOUT_FILE = DoxygenLayout.xml

+# The CITE_BIB_FILES tag can be used to specify one or more bib files

+# containing the references data. This must be a list of .bib files. The

+# .bib extension is automatically appended if omitted. Using this command

+# requires the bibtex tool to be installed. See also

+# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style

+# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this

+# feature you need bibtex and perl available in the search path. Do not use

+# file names with spaces, bibtex cannot handle them.

+CITE_BIB_FILES         =

 #---------------------------------------------------------------------------

 # configuration options related to warning and progress messages

 #---------------------------------------------------------------------------

@@ -530,7 +636,7 @@

 WARN_IF_DOC_ERROR      = YES

-# This WARN_NO_PARAMDOC option can be abled to get warnings for

+# The WARN_NO_PARAMDOC option can be enabled to get warnings for

 # functions that are documented, but have no documentation for their parameters

 # or return value. If set to NO (the default) doxygen will only warn about

 # wrong or incomplete parameter documentation, but not about the absence of

@@ -545,7 +651,7 @@

 # $version, which will be replaced by the version of the file (if it could

 # be obtained via FILE_VERSION_FILTER)

-WARN_FORMAT            = "$file:$line: $text "

+WARN_FORMAT            = "$file:$line: $text"

 # The WARN_LOGFILE tag can be used to specify a file to which warning

 # and error messages should be written. If left blank the output is written

@@ -576,8 +682,9 @@

 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp

 # and *.h) to filter out the source-files in the directories. If left

 # blank the following patterns are tested:

-# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx

-# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90

+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh

+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py

+# *.f90 *.f *.for *.vhd *.vhdl

 FILE_PATTERNS          = *.h *.c

@@ -587,14 +694,16 @@

 RECURSIVE              = YES

-# The EXCLUDE tag can be used to specify files and/or directories that should

+# The EXCLUDE tag can be used to specify files and/or directories that should be

 # excluded from the INPUT source files. This way you can easily exclude a

 # subdirectory from a directory tree whose root is specified with the INPUT tag.

+# Note that relative paths are relative to the directory from which doxygen is

+# run.

 EXCLUDE                =

-# The EXCLUDE_SYMLINKS tag can be used select whether or not files or

-# directories that are symbolic links (a Unix filesystem feature) are excluded

+# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or

+# directories that are symbolic links (a Unix file system feature) are excluded

 # from the input.

 EXCLUDE_SYMLINKS       = NO

@@ -658,8 +767,8 @@

 # filter if there is a match.

 # The filters are a list of the form:

 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further

-# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER

-# is applied to all files.

+# info on how filters are used. If FILTER_PATTERNS is empty or if

+# non of the patterns match the file name, INPUT_FILTER is applied.

 FILTER_PATTERNS        =

@@ -669,6 +778,21 @@

 FILTER_SOURCE_FILES    = NO

+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file

+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)

+# and it is also possible to disable source filtering for a specific pattern

+# using *.ext= (so without naming a filter). This option only has effect when

+# FILTER_SOURCE_FILES is enabled.

+FILTER_SOURCE_PATTERNS =

+# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that

+# is part of the input, its contents will be placed on the main page (index.html).

+# This can be useful if you have a project on for instance GitHub and want reuse

+# the introduction page also for the doxygen output.

+USE_MDFILE_AS_MAINPAGE =

 #---------------------------------------------------------------------------

 # configuration options related to source browsing

 #---------------------------------------------------------------------------

@@ -687,7 +811,7 @@

 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct

 # doxygen to hide any special comment blocks from generated source code

-# fragments. Normal C and C++ comments will always remain visible.

+# fragments. Normal C, C++ and Fortran comments will always remain visible.

 STRIP_CODE_COMMENTS    = NO

@@ -771,7 +895,14 @@

 # The HTML_HEADER tag can be used to specify a personal HTML header for

 # each generated HTML page. If it is left blank doxygen will generate a

-# standard header.

+# standard header. Note that when using a custom header you are responsible

+#  for the proper inclusion of any scripts and style sheets that doxygen

+# needs, which is dependent on the configuration options used.

+# It is advised to generate a default header using "doxygen -w html

+# header.html footer.html stylesheet.css YourConfigFile" and then modify

+# that header. Note that the header is subject to change so you typically

+# have to redo this when upgrading to a newer version of doxygen or when

+# changing the value of configuration settings such as GENERATE_TREEVIEW!

 HTML_HEADER            =

@@ -783,21 +914,80 @@

 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading

 # style sheet that is used by each HTML page. It can be used to

-# fine-tune the look of the HTML output. If the tag is left blank doxygen

-# will generate a default style sheet. Note that doxygen will try to copy

-# the style sheet file to the HTML output directory, so don't put your own

-# stylesheet in the HTML output directory as well, or it will be erased!

+# fine-tune the look of the HTML output. If left blank doxygen will

+# generate a default style sheet. Note that it is recommended to use

+# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this

+# tag will in the future become obsolete.

 HTML_STYLESHEET        =

+# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional

+# user-defined cascading style sheet that is included after the standard

+# style sheets created by doxygen. Using this option one can overrule

+# certain style aspects. This is preferred over using HTML_STYLESHEET

+# since it does not replace the standard style sheet and is therefor more

+# robust against future updates. Doxygen will copy the style sheet file to

+# the output directory.

+HTML_EXTRA_STYLESHEET  =

+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or

+# other source files which should be copied to the HTML output directory. Note

+# that these files will be copied to the base HTML output directory. Use the

+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these

+# files. In the HTML_STYLESHEET file, use the file name only. Also note that

+# the files will be copied as-is; there are no commands or markers available.

+HTML_EXTRA_FILES       =

+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.

+# Doxygen will adjust the colors in the style sheet and background images

+# according to this color. Hue is specified as an angle on a colorwheel,

+# see http://en.wikipedia.org/wiki/Hue for more information.

+# For instance the value 0 represents red, 60 is yellow, 120 is green,

+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.

+# The allowed range is 0 to 359.

+HTML_COLORSTYLE_HUE    = 220

+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of

+# the colors in the HTML output. For a value of 0 the output will use

+# grayscales only. A value of 255 will produce the most vivid colors.

+HTML_COLORSTYLE_SAT    = 100

+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to

+# the luminance component of the colors in the HTML output. Values below

+# 100 gradually make the output lighter, whereas values above 100 make

+# the output darker. The value divided by 100 is the actual gamma applied,

+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,

+# and 100 does not change the gamma.

+HTML_COLORSTYLE_GAMMA  = 80

+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML

+# page will contain the date and time when the page was generated. Setting

+# this to NO can help when comparing the output of multiple runs.

+HTML_TIMESTAMP         = YES

 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML

 # documentation will contain sections that can be hidden and shown after the

-# page has loaded. For this to work a browser that supports

-# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox

-# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).

+# page has loaded.

 HTML_DYNAMIC_SECTIONS  = NO

+# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of

+# entries shown in the various tree structured indices initially; the user

+# can expand and collapse entries dynamically later on. Doxygen will expand

+# the tree to such a level that at most the specified number of entries are

+# visible (unless a fully collapsed tree already exceeds this amount).

+# So setting the number of entries 1 will produce a full collapsed tree by

+# default. 0 is a special value representing an infinite number of entries

+# and will result in a full expanded tree by default.

+HTML_INDEX_NUM_ENTRIES = 100

 # If the GENERATE_DOCSET tag is set to YES, additional index files

 # will be generated that can be used as input for Apple's Xcode 3

 # integrated development environment, introduced with OSX 10.5 (Leopard).

@@ -806,7 +996,8 @@

 # directory and running "make install" will install the docset in

 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find

 # it at startup.

-# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.

+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html

+# for more information.

 GENERATE_DOCSET        = NO

@@ -824,6 +1015,16 @@

 DOCSET_BUNDLE_ID       = org.doxygen.Project

+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely

+# identify the documentation publisher. This should be a reverse domain-name

+# style string, e.g. com.mycompany.MyDocSet.documentation.

+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher

+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.

+DOCSET_PUBLISHER_NAME  = Publisher

 # If the GENERATE_HTMLHELP tag is set to YES, additional index files

 # will be generated that can be used as input for tools like the

 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)

@@ -868,10 +1069,10 @@

 TOC_EXPAND             = NO

-# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER

-# are set, an additional index file will be generated that can be used as input for

-# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated

-# HTML documentation.

+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and

+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated

+# that can be used as input for Qt's qhelpgenerator to generate a

+# Qt Compressed Help (.qch) of the generated HTML documentation.

 GENERATE_QHP           = NO

@@ -893,20 +1094,24 @@

 QHP_VIRTUAL_FOLDER     = doc

-# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.

-# For more information please see

+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to

+# add. For more information please see

 # http://doc.trolltech.com/qthelpproject.html#custom-filters

 QHP_CUST_FILTER_NAME   =

-# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see

-# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.

+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the

+# custom filter to add. For more information please see

+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">

+# Qt Help Project / Custom Filters</a>.

 QHP_CUST_FILTER_ATTRS  =

-# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's

+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this

+# project's

 # filter section matches.

-# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.

+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">

+# Qt Help Project / Filter Attributes</a>.

 QHP_SECT_FILTER_ATTRS  =

@@ -917,17 +1122,31 @@

 QHG_LOCATION           =

-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at

-# top of each HTML page. The value NO (the default) enables the index and

-# the value YES disables it.

+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files

+#  will be generated, which together with the HTML files, form an Eclipse help

+# plugin. To install this plugin and make it available under the help contents

+# menu in Eclipse, the contents of the directory containing the HTML and XML

+# files needs to be copied into the plugins directory of eclipse. The name of

+# the directory within the plugins directory should be the same as

+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before

+# the help appears.

-DISABLE_INDEX          = NO

+GENERATE_ECLIPSEHELP   = NO

-# This tag can be used to set the number of enum values (range [1..20])

-# that doxygen will group on one line in the generated HTML documentation.

+# A unique identifier for the eclipse help plugin. When installing the plugin

+# the directory name containing the HTML and XML files should also have

+# this name.

-ENUM_VALUES_PER_LINE   = 4

+ECLIPSE_DOC_ID         = org.doxygen.Project

+# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)

+# at top of each HTML page. The value NO (the default) enables the index and

+# the value YES disables it. Since the tabs have the same information as the

+# navigation tree you can set this option to NO if you already set

+# GENERATE_TREEVIEW to YES.

+DISABLE_INDEX          = NO

 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index

 # structure should be generated to display hierarchical information.

 # If the tag value is set to YES, a side panel will be generated

@@ -935,9 +1154,18 @@

 # is generated for HTML Help). For this to work a browser that supports

 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).

 # Windows users are probably better off using the HTML help feature.

+# Since the tree basically has the same information as the tab index you

+# could consider to set DISABLE_INDEX to NO when enabling this option.

 GENERATE_TREEVIEW      = NO

+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values

+# (range [0,1..20]) that doxygen will group on one line in the generated HTML

+# documentation. Note that a value of 0 will completely suppress the enum

+# values from appearing in the overview section.

+ENUM_VALUES_PER_LINE   = 4

 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be

 # used to set the initial width (in pixels) of the frame in which the tree

 # is shown.

@@ -944,6 +1172,11 @@

 TREEVIEW_WIDTH         = 250

+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open

+# links to external symbols imported via tag files in a separate window.

+EXT_LINKS_IN_WINDOW    = NO

 # Use this tag to change the font size of Latex formulas included

 # as images in the HTML documentation. The default is 10. Note that

 # when you change the font size after a successful doxygen run you need

@@ -952,13 +1185,107 @@

 FORMULA_FONTSIZE       = 10

-# When the SEARCHENGINE tag is enable doxygen will generate a search box for the HTML output. The underlying search engine uses javascript

-# and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP)

-# there is already a search function so this one should typically

-# be disabled.

+# Use the FORMULA_TRANPARENT tag to determine whether or not the images

+# generated for formulas are transparent PNGs. Transparent PNGs are

+# not supported properly for IE 6.0, but are supported on all modern browsers.

+# Note that when changing this option you need to delete any form_*.png files

+# in the HTML output before the changes have effect.

+FORMULA_TRANSPARENT    = YES

+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax

+# (see http://www.mathjax.org) which uses client side Javascript for the

+# rendering instead of using prerendered bitmaps. Use this if you do not

+# have LaTeX installed or if you want to formulas look prettier in the HTML

+# output. When enabled you may also need to install MathJax separately and

+# configure the path to it using the MATHJAX_RELPATH option.

+USE_MATHJAX            = YES

+# When MathJax is enabled you can set the default output format to be used for

+# thA MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and

+# SVG. The default value is HTML-CSS, which is slower, but has the best

+# compatibility.

+MATHJAX_FORMAT         = HTML-CSS

+# When MathJax is enabled you need to specify the location relative to the

+# HTML output directory using the MATHJAX_RELPATH option. The destination

+# directory should contain the MathJax.js script. For instance, if the mathjax

+# directory is located at the same level as the HTML output directory, then

+# MATHJAX_RELPATH should be ../mathjax. The default value points to

+# the MathJax Content Delivery Network so you can quickly see the result without

+# installing MathJax.

+# However, it is strongly recommended to install a local

+# copy of MathJax from http://www.mathjax.org before deployment.

+MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest

+# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension

+# names that should be enabled during MathJax rendering.

+MATHJAX_EXTENSIONS     =

+# When the SEARCHENGINE tag is enabled doxygen will generate a search box

+# for the HTML output. The underlying search engine uses javascript

+# and DHTML and should work on any modern browser. Note that when using

+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets

+# (GENERATE_DOCSET) there is already a search function so this one should

+# typically be disabled. For large projects the javascript based search engine

+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.

 SEARCHENGINE           = YES

+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be

+# implemented using a web server instead of a web client using Javascript.

+# There are two flavours of web server based search depending on the

+# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for

+# searching and an index file used by the script. When EXTERNAL_SEARCH is

+# enabled the indexing and searching needs to be provided by external tools.

+# See the manual for details.

+SERVER_BASED_SEARCH    = NO

+# When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP

+# script for searching. Instead the search results are written to an XML file

+# which needs to be processed by an external indexer. Doxygen will invoke an

+# external search engine pointed to by the SEARCHENGINE_URL option to obtain

+# the search results. Doxygen ships with an example indexer (doxyindexer) and

+# search engine (doxysearch.cgi) which are based on the open source search engine

+# library Xapian. See the manual for configuration details.

+EXTERNAL_SEARCH        = NO

+# The SEARCHENGINE_URL should point to a search engine hosted by a web server

+# which will returned the search results when EXTERNAL_SEARCH is enabled.

+# Doxygen ships with an example search engine (doxysearch) which is based on

+# the open source search engine library Xapian. See the manual for configuration

+# details.

+SEARCHENGINE_URL       =

+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed

+# search data is written to a file for indexing by an external tool. With the

+# SEARCHDATA_FILE tag the name of this file can be specified.

+SEARCHDATA_FILE        = searchdata.xml

+# When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the

+# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is

+# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple

+# projects and redirect the results back to the right project.

+EXTERNAL_SEARCH_ID     =

+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen

+# projects other than the one defined by this configuration file, but that are

+# all added to the same external search index. Each project needs to have a

+# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id

+# of to a relative location where the documentation can be found.

+# The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ...

+EXTRA_SEARCH_MAPPINGS  =

 #---------------------------------------------------------------------------

 # configuration options related to the LaTeX output

 #---------------------------------------------------------------------------

@@ -976,6 +1303,9 @@

 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be

 # invoked. If left blank `latex' will be used as the default command name.

+# Note that when enabling USE_PDFLATEX this option is only used for

+# generating bitmaps for formulas in the HTML output, but not in the

+# Makefile that is written to the output directory.

 LATEX_CMD_NAME         = latex

@@ -992,10 +1322,10 @@

 COMPACT_LATEX          = NO

 # The PAPER_TYPE tag can be used to set the paper type that is used

-# by the printer. Possible values are: a4, a4wide, letter, legal and

+# by the printer. Possible values are: a4, letter, legal and

 # executive. If left blank a4wide will be used.

-PAPER_TYPE             = a4wide

+PAPER_TYPE             = a4

 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX

 # packages that should be included in the LaTeX output.

@@ -1009,18 +1339,25 @@

 LATEX_HEADER           =

+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for

+# the generated latex document. The footer should contain everything after

+# the last chapter. If it is left blank doxygen will generate a

+# standard footer. Notice: only use this tag if you know what you are doing!

+LATEX_FOOTER           =

 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated

 # is prepared for conversion to pdf (using ps2pdf). The pdf file will

 # contain links (just like the HTML output) instead of page references

 # This makes the output suitable for online browsing using a pdf viewer.

-PDF_HYPERLINKS         = NO

+PDF_HYPERLINKS         = YES

 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of

 # plain latex in the generated Makefile. Set this option to YES to get a

 # higher quality PDF documentation.

-USE_PDFLATEX           = NO

+USE_PDFLATEX           = YES

 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.

 # command to the generated LaTeX files. This will instruct LaTeX to keep

@@ -1035,10 +1372,19 @@

 LATEX_HIDE_INDICES     = NO

-# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.

+# If LATEX_SOURCE_CODE is set to YES then doxygen will include

+# source code with syntax highlighting in the LaTeX output.

+# Note that which sources are shown also depends on other settings

+# such as SOURCE_BROWSER.

 LATEX_SOURCE_CODE      = NO

+# The LATEX_BIB_STYLE tag can be used to specify the style to use for the

+# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See

+# http://en.wikipedia.org/wiki/BibTeX for more info.

+LATEX_BIB_STYLE        = plain

 #---------------------------------------------------------------------------

 # configuration options related to the RTF output

 #---------------------------------------------------------------------------

@@ -1070,7 +1416,7 @@

 RTF_HYPERLINKS         = NO

-# Load stylesheet definitions from file. Syntax is similar to doxygen's

+# Load style sheet definitions from file. Syntax is similar to doxygen's

 # config file, i.e. a series of assignments. You only have to provide

 # replacements, missing definitions are set to their default value.

@@ -1215,7 +1561,7 @@

 EXPAND_ONLY_PREDEF     = NO

 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files

-# in the INCLUDE_PATH (see below) will be search if a #include is found.

+# pointed to by INCLUDE_PATH will be searched when a #include is found.

 SEARCH_INCLUDES        = YES

@@ -1245,15 +1591,15 @@

 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then

 # this tag can be used to specify a list of macro names that should be expanded.

 # The macro definition that is found in the sources will be used.

-# Use the PREDEFINED tag if you want to use a different macro definition.

+# Use the PREDEFINED tag if you want to use a different macro definition that

+# overrules the definition found in the source code.

 EXPAND_AS_DEFINED      =

 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then

-# doxygen's preprocessor will remove all function-like macros that are alone

-# on a line, have an all uppercase name, and do not end with a semicolon. Such

-# function macros are typically used for boiler-plate code, and will confuse

-# the parser if not removed.

+# doxygen's preprocessor will remove all references to function-like macros

+# that are alone on a line, have an all uppercase name, and do not end with a

+# semicolon, because these will confuse the parser if not removed.

 SKIP_FUNCTION_MACROS   = YES

@@ -1261,22 +1607,18 @@

 # Configuration::additions related to external references

 #---------------------------------------------------------------------------

-# The TAGFILES option can be used to specify one or more tagfiles.

-# Optionally an initial location of the external documentation

-# can be added for each tagfile. The format of a tag file without

-# this location is as follows:

+# The TAGFILES option can be used to specify one or more tagfiles. For each

+# tag file the location of the external documentation should be added. The

+# format of a tag file without this location is as follows:

 # TAGFILES = file1 file2 ...

 # Adding location for the tag files is done as follows:

 # TAGFILES = file1=loc1 "file2 = loc2" ...

-# where "loc1" and "loc2" can be relative or absolute paths or

-# URLs. If a location is present for each tag, the installdox tool

-# does not have to be run to correct the links.

-# Note that each tag file must have a unique name

-# (where the name does NOT include the path)

-# If a tag file is not located in the directory in which doxygen

-# is run, you must also specify the path to the tagfile here.

+# where "loc1" and "loc2" can be relative or absolute paths

+# or URLs. Note that each tag file must have a unique name (where the name does

+# NOT include the path). If a tag file is not located in the directory in which

+# doxygen is run, you must also specify the path to the tagfile here.

 TAGFILES               =

@@ -1309,9 +1651,8 @@

 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will

 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base

 # or super classes. Setting the tag to NO turns the diagrams off. Note that

-# this option is superseded by the HAVE_DOT option below. This is only a

-# fallback. It is recommended to install and use dot, since it yields more

-# powerful graphs.

+# this option also works with HAVE_DOT disabled, but it is recommended to

+# install and use dot, since it yields more powerful graphs.

 CLASS_DIAGRAMS         = YES

@@ -1335,17 +1676,23 @@

 # toolkit from AT&T and Lucent Bell Labs. The other options in this section

 # have no effect if this option is set to NO (the default)

-HAVE_DOT               = YES

+HAVE_DOT               = NO

-# By default doxygen will write a font called FreeSans.ttf to the output

-# directory and reference it in all dot files that doxygen generates. This

-# font does not include all possible unicode characters however, so when you need

-# these (or just want a differently looking font) you can specify the font name

-# using DOT_FONTNAME. You need need to make sure dot is able to find the font,

-# which can be done by putting it in a standard location or by setting the

-# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory

-# containing the font.

+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is

+# allowed to run in parallel. When set to 0 (the default) doxygen will

+# base this on the number of processors available in the system. You can set it

+# explicitly to a value larger than 0 to get control over the balance

+# between CPU load and processing speed.

+DOT_NUM_THREADS        = 0

+# By default doxygen will use the Helvetica font for all dot files that

+# doxygen generates. When you want a differently looking font you can specify

+# the font name using DOT_FONTNAME. You need to make sure dot is able to find

+# the font, which can be done by putting it in a standard location or by setting

+# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the

+# directory containing the font.

 DOT_FONTNAME           = FreeSans

 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.

@@ -1353,10 +1700,9 @@

 DOT_FONTSIZE           = 10

-# By default doxygen will tell dot to use the output directory to look for the

-# FreeSans.ttf font (which doxygen will put there itself). If you specify a

-# different font using DOT_FONTNAME you can set the path where dot

-# can find it using this tag.

+# By default doxygen will tell dot to use the Helvetica font.

+# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to

+# set the path where dot can find it.

 DOT_FONTPATH           =

@@ -1363,7 +1709,7 @@

 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen

 # will generate a graph for each documented class showing the direct and

 # indirect inheritance relations. Setting this tag to YES will force the

-# the CLASS_DIAGRAMS tag to NO.

+# CLASS_DIAGRAMS tag to NO.

 CLASS_GRAPH            = YES

@@ -1385,6 +1731,15 @@

 UML_LOOK               = NO

+# If the UML_LOOK tag is enabled, the fields and methods are shown inside

+# the class node. If there are many fields or methods and many nodes the

+# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS

+# threshold limits the number of items for each type to make the size more

+# managable. Set this to 0 for no limit. Note that the threshold may be

+# exceeded by 50% before the limit is enforced.

+UML_LIMIT_NUM_FIELDS   = 10

 # If set to YES, the inheritance and collaboration graphs will show the

 # relations between templates and their instances.

@@ -1421,11 +1776,11 @@

 CALLER_GRAPH           = NO

 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen

-# will graphical hierarchy of all classes instead of a textual one.

+# will generate a graphical hierarchy of all classes instead of a textual one.

 GRAPHICAL_HIERARCHY    = YES

-# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES

+# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES

 # then doxygen will show the dependencies a directory has on other directories

 # in a graphical way. The dependency relations are determined by the #include

 # relations between the files in the directories.

@@ -1433,11 +1788,22 @@

 DIRECTORY_GRAPH        = YES

 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images

-# generated by dot. Possible values are png, jpg, or gif

-# If left blank png will be used.

+# generated by dot. Possible values are svg, png, jpg, or gif.

+# If left blank png will be used. If you choose svg you need to set

+# HTML_FILE_EXTENSION to xhtml in order to make the SVG files

+# visible in IE 9+ (other browsers do not have this requirement).

 DOT_IMAGE_FORMAT       = png

+# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to

+# enable generation of interactive SVG images that allow zooming and panning.

+# Note that this requires a modern browser other than Internet Explorer.

+# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you

+# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files

+# visible. Older versions of IE do not have SVG support.

+INTERACTIVE_SVG        = NO

 # The tag DOT_PATH can be used to specify the path where the dot tool can be

 # found. If left blank, it is assumed the dot tool can be found in the path.

@@ -1448,6 +1814,12 @@

 # \dotfile command).

 DOTFILE_DIRS           =

+# The MSCFILE_DIRS tag can be used to specify one or more directories that

+# contain msc files that are included in the documentation (see the

+# \mscfile command).

+MSCFILE_DIRS           =

 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of

 # nodes that will be shown in the graph. If the number of nodes in a graph

--- a/doc/web.cfg

+++ b/doc/web.cfg

@@ -1,14 +1,14 @@

-# Doxyfile 1.6.1

+# Doxyfile 1.8.3.1

 # This file describes the settings to be used by the documentation system

-# doxygen (www.doxygen.org) for a project

+# doxygen (www.doxygen.org) for a project.

-# All text after a hash (#) is considered a comment and will be ignored

+# All text after a hash (#) is considered a comment and will be ignored.

 # The format is:

 #       TAG = value [value, ...]

 # For lists items can also be appended using:

 #       TAG += value [value, ...]

-# Values that contain spaces should be placed between quotes (" ")

+# Values that contain spaces should be placed between quotes (" ").

 #---------------------------------------------------------------------------

 # Project related configuration options

@@ -22,8 +22,9 @@

 DOXYFILE_ENCODING      = UTF-8

-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded

-# by quotes) that should identify the project.

+# The PROJECT_NAME tag is a single word (or sequence of words) that should

+# identify the project. Note that if you do not use Doxywizard you need

+# to put quotes around the project name if it contains spaces.

 PROJECT_NAME           = aubio

@@ -33,6 +34,19 @@

 PROJECT_NUMBER         = "0.4.0alpha"

+# Using the PROJECT_BRIEF tag one can provide an optional one line description

+# for a project that appears at the top of each page and should give viewer

+# a quick idea about the purpose of the project. Keep the description short.

+PROJECT_BRIEF          =

+# With the PROJECT_LOGO tag one can specify an logo or icon that is

+# included in the documentation. The maximum height of the logo should not

+# exceed 55 pixels and the maximum width should not exceed 200 pixels.

+# Doxygen will copy the logo to the output directory.

+PROJECT_LOGO           =

 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)

 # base path where the generated documentation will be put.

 # If a relative path is entered, it will be relative to the location

@@ -112,7 +126,9 @@

 # only done if one of the specified strings matches the left-hand part of

 # the path. The tag can be used to show relative paths in the file list.

 # If left blank the directory from which doxygen is run is used as the

-# path to strip.

+# path to strip. Note that you specify absolute paths here, but also

+# relative paths, which will be relative from the directory where doxygen is

+# started.

 STRIP_FROM_PATH        = ../src

@@ -126,7 +142,7 @@

 STRIP_FROM_INC_PATH    =

 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter

-# (but less readable) file names. This can be useful is your file systems

+# (but less readable) file names. This can be useful if your file system

 # doesn't support long names like on DOS, Mac, or CD-ROM.

 SHORT_NAMES            = NO

@@ -181,6 +197,13 @@

 ALIASES                =

+# This tag can be used to specify a number of word-keyword mappings (TCL only).

+# A mapping has the form "name=value". For example adding

+# "class=itcl::class" will allow you to use the command class in the

+# itcl::class meaning.

+TCL_SUBST              =

 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C

 # sources only. Doxygen will then generate output that is more tailored for C.

 # For instance, some of the names that are used will be different. The list

@@ -207,22 +230,40 @@

 OPTIMIZE_OUTPUT_VHDL   = NO

-# Doxygen selects the parser to use depending on the extension of the files it parses.

-# With this tag you can assign which parser to use for a given extension.

-# Doxygen has a built-in mapping, but you can override or extend it using this tag.

-# The format is ext=language, where ext is a file extension, and language is one of

-# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,

-# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat

-# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),

-# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.

+# Doxygen selects the parser to use depending on the extension of the files it

+# parses. With this tag you can assign which parser to use for a given

+# extension. Doxygen has a built-in mapping, but you can override or extend it

+# using this tag. The format is ext=language, where ext is a file extension,

+# and language is one of the parsers supported by doxygen: IDL, Java,

+# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C,

+# C++. For instance to make doxygen treat .inc files as Fortran files (default

+# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note

+# that for custom extensions you also need to set FILE_PATTERNS otherwise the

+# files are not read by doxygen.

 EXTENSION_MAPPING      =

+# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all

+# comments according to the Markdown format, which allows for more readable

+# documentation. See http://daringfireball.net/projects/markdown/ for details.

+# The output of markdown processing is further processed by doxygen, so you

+# can mix doxygen, HTML, and XML commands with Markdown formatting.

+# Disable only in case of backward compatibilities issues.

+MARKDOWN_SUPPORT       = YES

+# When enabled doxygen tries to link words that correspond to documented classes,

+# or namespaces to their corresponding documentation. Such a link can be

+# prevented in individual cases by by putting a % sign in front of the word or

+# globally by setting AUTOLINK_SUPPORT to NO.

+AUTOLINK_SUPPORT       = YES

 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want

 # to include (a tag file for) the STL sources as input, then you should

 # set this tag to YES in order to let doxygen match functions declarations and

 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.

-# func(std::string) {}). This also make the inheritance and collaboration

+# func(std::string) {}). This also makes the inheritance and collaboration

 # diagrams that involve STL classes more complete and accurate.

 BUILTIN_STL_SUPPORT    = NO

@@ -238,10 +279,10 @@

 SIP_SUPPORT            = NO

-# For Microsoft's IDL there are propget and propput attributes to indicate getter

-# and setter methods for a property. Setting this option to YES (the default)

-# will make doxygen to replace the get and set methods by a property in the

-# documentation. This will only work if the methods are indeed getting or

+# For Microsoft's IDL there are propget and propput attributes to indicate

+# getter and setter methods for a property. Setting this option to YES (the

+# default) will make doxygen replace the get and set methods by a property in

+# the documentation. This will only work if the methods are indeed getting or

 # setting a simple type. If this is not the case, or you want to show the

 # methods anyway, you should set this option to NO.

@@ -262,6 +303,22 @@

 SUBGROUPING            = YES

+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and

+# unions are shown inside the group in which they are included (e.g. using

+# @ingroup) instead of on a separate page (for HTML and Man pages) or

+# section (for LaTeX and RTF).

+INLINE_GROUPED_CLASSES = NO

+# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and

+# unions with only public data fields will be shown inline in the documentation

+# of the scope in which they are defined (i.e. file, namespace, or group

+# documentation), provided this scope is documented. If set to NO (the default),

+# structs, classes, and unions are shown on a separate page (for HTML and Man

+# pages) or section (for LaTeX and RTF).

+INLINE_SIMPLE_STRUCTS  = NO

 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum

 # is documented as struct, union, or enum with the name of the typedef. So

 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct

@@ -278,16 +335,27 @@

 # For small to medium size projects (<1000 input files) the default value is

 # probably good enough. For larger projects a too small cache size can cause

 # doxygen to be busy swapping symbols to and from disk most of the time

-# causing a significant performance penality.

+# causing a significant performance penalty.

 # If the system has enough physical memory increasing the cache will improve the

 # performance by keeping more symbols in memory. Note that the value works on

-# a logarithmic scale so increasing the size by one will rougly double the

+# a logarithmic scale so increasing the size by one will roughly double the

 # memory usage. The cache size is given by this formula:

 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,

-# corresponding to a cache size of 2^16 = 65536 symbols

+# corresponding to a cache size of 2^16 = 65536 symbols.

 SYMBOL_CACHE_SIZE      = 0

+# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be

+# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given

+# their name and scope. Since this can be an expensive process and often the

+# same symbol appear multiple times in the code, doxygen keeps a cache of

+# pre-resolved symbols. If the cache is too small doxygen will become slower.

+# If the cache is too large, memory is wasted. The cache size is given by this

+# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,

+# corresponding to a cache size of 2^16 = 65536 symbols.

+LOOKUP_CACHE_SIZE      = 0

 #---------------------------------------------------------------------------

 # Build related configuration options

 #---------------------------------------------------------------------------

@@ -304,6 +372,11 @@

 EXTRACT_PRIVATE        = NO

+# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal

+# scope will be included in the documentation.

+EXTRACT_PACKAGE        = NO

 # If the EXTRACT_STATIC tag is set to YES all static members of a file

 # will be included in the documentation.

@@ -326,7 +399,7 @@

 # extracted and appear in the documentation as a namespace called

 # 'anonymous_namespace{file}', where file will be replaced with the base

 # name of the file that contains the anonymous namespace. By default

-# anonymous namespace are hidden.

+# anonymous namespaces are hidden.

 EXTRACT_ANON_NSPACES   = NO

@@ -372,7 +445,7 @@

 # in case and if your file system supports case sensitive file names. Windows

 # and Mac users are advised to set this option to NO.

-CASE_SENSE_NAMES       = YES

+CASE_SENSE_NAMES       = NO

 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen

 # will show members with their full class and namespace scopes in the

@@ -386,6 +459,12 @@

 SHOW_INCLUDE_FILES     = YES

+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen

+# will list include files with double quotes in the documentation

+# rather than with sharp brackets.

+FORCE_LOCAL_INCLUDES   = NO

 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]

 # is inserted in the documentation for inline members.

@@ -405,7 +484,13 @@

 SORT_BRIEF_DOCS        = NO

-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.

+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen

+# will sort the (brief and detailed) documentation of class members so that

+# constructors and destructors are listed first. If set to NO (the default)

+# the constructors will appear in the respective orders defined by

+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.

+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO

+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.

 SORT_MEMBERS_CTORS_1ST = NO

@@ -425,6 +510,15 @@

 SORT_BY_SCOPE_NAME     = NO

+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to

+# do proper type resolution of all parameters of a function it will reject a

+# match between the prototype and the implementation of a member function even

+# if there is only one candidate or it is obvious which candidate to choose

+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen

+# will still accept a match between prototype and implementation in such cases.

+STRICT_PROTO_MATCHING  = NO

 # The GENERATE_TODOLIST tag can be used to enable (YES) or

 # disable (NO) the todo list. This list is created by putting \todo

 # commands in the documentation.

@@ -450,15 +544,16 @@

 GENERATE_DEPRECATEDLIST= YES

 # The ENABLED_SECTIONS tag can be used to enable conditional

-# documentation sections, marked by \if sectionname ... \endif.

+# documentation sections, marked by \if section-label ... \endif

+# and \cond section-label ... \endcond blocks.

 ENABLED_SECTIONS       =

 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines

-# the initial value of a variable or define consists of for it to appear in

+# the initial value of a variable or macro consists of for it to appear in

 # the documentation. If the initializer consists of more lines than specified

 # here it will be hidden. Use a value of 0 to hide initializers completely.

-# The appearance of the initializer of individual variables and defines in the

+# The appearance of the initializer of individual variables and macros in the

 # documentation can be controlled using \showinitializer or \hideinitializer

 # command in the documentation regardless of this setting.

@@ -493,15 +588,27 @@

 FILE_VERSION_FILTER    =

-# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by

-# doxygen. The layout file controls the global structure of the generated output files

-# in an output format independent way. The create the layout file that represents

-# doxygen's defaults, run doxygen with the -l option. You can optionally specify a

-# file name after the option, if omitted DoxygenLayout.xml will be used as the name

-# of the layout file.

+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed

+# by doxygen. The layout file controls the global structure of the generated

+# output files in an output format independent way. To create the layout file

+# that represents doxygen's defaults, run doxygen with the -l option.

+# You can optionally specify a file name after the option, if omitted

+# DoxygenLayout.xml will be used as the name of the layout file.

-LAYOUT_FILE            =

+#LAYOUT_FILE            =

+LAYOUT_FILE = DoxygenLayout.xml

+# The CITE_BIB_FILES tag can be used to specify one or more bib files

+# containing the references data. This must be a list of .bib files. The

+# .bib extension is automatically appended if omitted. Using this command

+# requires the bibtex tool to be installed. See also

+# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style

+# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this

+# feature you need bibtex and perl available in the search path. Do not use

+# file names with spaces, bibtex cannot handle them.

+CITE_BIB_FILES         =

 #---------------------------------------------------------------------------

 # configuration options related to warning and progress messages

 #---------------------------------------------------------------------------

@@ -530,7 +637,7 @@

 WARN_IF_DOC_ERROR      = YES

-# This WARN_NO_PARAMDOC option can be abled to get warnings for

+# The WARN_NO_PARAMDOC option can be enabled to get warnings for

 # functions that are documented, but have no documentation for their parameters

 # or return value. If set to NO (the default) doxygen will only warn about

 # wrong or incomplete parameter documentation, but not about the absence of

@@ -545,7 +652,7 @@

 # $version, which will be replaced by the version of the file (if it could

 # be obtained via FILE_VERSION_FILTER)

-WARN_FORMAT            = "$file:$line: $text "

+WARN_FORMAT            = "$file:$line: $text"

 # The WARN_LOGFILE tag can be used to specify a file to which warning

 # and error messages should be written. If left blank the output is written

@@ -576,8 +683,9 @@

 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp

 # and *.h) to filter out the source-files in the directories. If left

 # blank the following patterns are tested:

-# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx

-# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90

+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh

+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py

+# *.f90 *.f *.for *.vhd *.vhdl

 FILE_PATTERNS          = *.h

@@ -587,9 +695,11 @@

 RECURSIVE              = YES

-# The EXCLUDE tag can be used to specify files and/or directories that should

+# The EXCLUDE tag can be used to specify files and/or directories that should be

 # excluded from the INPUT source files. This way you can easily exclude a

 # subdirectory from a directory tree whose root is specified with the INPUT tag.

+# Note that relative paths are relative to the directory from which doxygen is

+# run.

 EXCLUDE                = ../src/aubio_priv.h \

                          ../src/mathutils .h \

@@ -608,8 +718,8 @@

                          ../src/utils/scale.h \

                          ../src/utils.h

-# The EXCLUDE_SYMLINKS tag can be used select whether or not files or

-# directories that are symbolic links (a Unix filesystem feature) are excluded

+# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or

+# directories that are symbolic links (a Unix file system feature) are excluded

 # from the input.

 EXCLUDE_SYMLINKS       = NO

@@ -673,8 +783,8 @@

 # filter if there is a match.

 # The filters are a list of the form:

 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further

-# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER

-# is applied to all files.

+# info on how filters are used. If FILTER_PATTERNS is empty or if

+# non of the patterns match the file name, INPUT_FILTER is applied.

 FILTER_PATTERNS        =

@@ -684,6 +794,21 @@

 FILTER_SOURCE_FILES    = NO

+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file

+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)

+# and it is also possible to disable source filtering for a specific pattern

+# using *.ext= (so without naming a filter). This option only has effect when

+# FILTER_SOURCE_FILES is enabled.

+FILTER_SOURCE_PATTERNS =

+# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that

+# is part of the input, its contents will be placed on the main page (index.html).

+# This can be useful if you have a project on for instance GitHub and want reuse

+# the introduction page also for the doxygen output.

+USE_MDFILE_AS_MAINPAGE =

 #---------------------------------------------------------------------------

 # configuration options related to source browsing

 #---------------------------------------------------------------------------

@@ -702,7 +827,7 @@

 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct

 # doxygen to hide any special comment blocks from generated source code

-# fragments. Normal C and C++ comments will always remain visible.

+# fragments. Normal C, C++ and Fortran comments will always remain visible.

 STRIP_CODE_COMMENTS    = NO

@@ -786,7 +911,14 @@

 # The HTML_HEADER tag can be used to specify a personal HTML header for

 # each generated HTML page. If it is left blank doxygen will generate a

-# standard header.

+# standard header. Note that when using a custom header you are responsible

+#  for the proper inclusion of any scripts and style sheets that doxygen

+# needs, which is dependent on the configuration options used.

+# It is advised to generate a default header using "doxygen -w html

+# header.html footer.html stylesheet.css YourConfigFile" and then modify

+# that header. Note that the header is subject to change so you typically

+# have to redo this when upgrading to a newer version of doxygen or when

+# changing the value of configuration settings such as GENERATE_TREEVIEW!

 HTML_HEADER            =

@@ -798,21 +930,80 @@

 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading

 # style sheet that is used by each HTML page. It can be used to

-# fine-tune the look of the HTML output. If the tag is left blank doxygen

-# will generate a default style sheet. Note that doxygen will try to copy

-# the style sheet file to the HTML output directory, so don't put your own

-# stylesheet in the HTML output directory as well, or it will be erased!

+# fine-tune the look of the HTML output. If left blank doxygen will

+# generate a default style sheet. Note that it is recommended to use

+# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this

+# tag will in the future become obsolete.

 HTML_STYLESHEET        =

+# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional

+# user-defined cascading style sheet that is included after the standard

+# style sheets created by doxygen. Using this option one can overrule

+# certain style aspects. This is preferred over using HTML_STYLESHEET

+# since it does not replace the standard style sheet and is therefor more

+# robust against future updates. Doxygen will copy the style sheet file to

+# the output directory.

+HTML_EXTRA_STYLESHEET  =

+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or

+# other source files which should be copied to the HTML output directory. Note

+# that these files will be copied to the base HTML output directory. Use the

+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these

+# files. In the HTML_STYLESHEET file, use the file name only. Also note that

+# the files will be copied as-is; there are no commands or markers available.

+HTML_EXTRA_FILES       =

+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.

+# Doxygen will adjust the colors in the style sheet and background images

+# according to this color. Hue is specified as an angle on a colorwheel,

+# see http://en.wikipedia.org/wiki/Hue for more information.

+# For instance the value 0 represents red, 60 is yellow, 120 is green,

+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.

+# The allowed range is 0 to 359.

+HTML_COLORSTYLE_HUE    = 220

+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of

+# the colors in the HTML output. For a value of 0 the output will use

+# grayscales only. A value of 255 will produce the most vivid colors.

+HTML_COLORSTYLE_SAT    = 100

+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to

+# the luminance component of the colors in the HTML output. Values below

+# 100 gradually make the output lighter, whereas values above 100 make

+# the output darker. The value divided by 100 is the actual gamma applied,

+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,

+# and 100 does not change the gamma.

+HTML_COLORSTYLE_GAMMA  = 80

+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML

+# page will contain the date and time when the page was generated. Setting

+# this to NO can help when comparing the output of multiple runs.

+HTML_TIMESTAMP         = YES

 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML

 # documentation will contain sections that can be hidden and shown after the

-# page has loaded. For this to work a browser that supports

-# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox

-# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).

+# page has loaded.

 HTML_DYNAMIC_SECTIONS  = NO

+# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of

+# entries shown in the various tree structured indices initially; the user

+# can expand and collapse entries dynamically later on. Doxygen will expand

+# the tree to such a level that at most the specified number of entries are

+# visible (unless a fully collapsed tree already exceeds this amount).

+# So setting the number of entries 1 will produce a full collapsed tree by

+# default. 0 is a special value representing an infinite number of entries

+# and will result in a full expanded tree by default.

+HTML_INDEX_NUM_ENTRIES = 100

 # If the GENERATE_DOCSET tag is set to YES, additional index files

 # will be generated that can be used as input for Apple's Xcode 3

 # integrated development environment, introduced with OSX 10.5 (Leopard).

@@ -821,7 +1012,8 @@

 # directory and running "make install" will install the docset in

 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find

 # it at startup.

-# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.

+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html

+# for more information.

 GENERATE_DOCSET        = NO

@@ -839,6 +1031,16 @@

 DOCSET_BUNDLE_ID       = org.doxygen.Project

+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely

+# identify the documentation publisher. This should be a reverse domain-name

+# style string, e.g. com.mycompany.MyDocSet.documentation.

+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher

+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.

+DOCSET_PUBLISHER_NAME  = Publisher

 # If the GENERATE_HTMLHELP tag is set to YES, additional index files

 # will be generated that can be used as input for tools like the

 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)

@@ -883,10 +1085,10 @@

 TOC_EXPAND             = NO

-# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER

-# are set, an additional index file will be generated that can be used as input for

-# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated

-# HTML documentation.

+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and

+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated

+# that can be used as input for Qt's qhelpgenerator to generate a

+# Qt Compressed Help (.qch) of the generated HTML documentation.

 GENERATE_QHP           = NO

@@ -908,20 +1110,24 @@

 QHP_VIRTUAL_FOLDER     = doc

-# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.

-# For more information please see

+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to

+# add. For more information please see

 # http://doc.trolltech.com/qthelpproject.html#custom-filters

 QHP_CUST_FILTER_NAME   =

-# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see

-# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.

+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the

+# custom filter to add. For more information please see

+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">

+# Qt Help Project / Custom Filters</a>.

 QHP_CUST_FILTER_ATTRS  =

-# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's

+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this

+# project's

 # filter section matches.

-# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.

+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">

+# Qt Help Project / Filter Attributes</a>.

 QHP_SECT_FILTER_ATTRS  =

@@ -932,17 +1138,31 @@

 QHG_LOCATION           =

-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at

-# top of each HTML page. The value NO (the default) enables the index and

-# the value YES disables it.

+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files

+#  will be generated, which together with the HTML files, form an Eclipse help

+# plugin. To install this plugin and make it available under the help contents

+# menu in Eclipse, the contents of the directory containing the HTML and XML

+# files needs to be copied into the plugins directory of eclipse. The name of

+# the directory within the plugins directory should be the same as

+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before

+# the help appears.

-DISABLE_INDEX          = NO

+GENERATE_ECLIPSEHELP   = NO

-# This tag can be used to set the number of enum values (range [1..20])

-# that doxygen will group on one line in the generated HTML documentation.

+# A unique identifier for the eclipse help plugin. When installing the plugin

+# the directory name containing the HTML and XML files should also have

+# this name.

-ENUM_VALUES_PER_LINE   = 4

+ECLIPSE_DOC_ID         = org.doxygen.Project

+# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)

+# at top of each HTML page. The value NO (the default) enables the index and

+# the value YES disables it. Since the tabs have the same information as the

+# navigation tree you can set this option to NO if you already set

+# GENERATE_TREEVIEW to YES.

+DISABLE_INDEX          = NO

 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index

 # structure should be generated to display hierarchical information.

 # If the tag value is set to YES, a side panel will be generated

@@ -950,9 +1170,18 @@

 # is generated for HTML Help). For this to work a browser that supports

 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).

 # Windows users are probably better off using the HTML help feature.

+# Since the tree basically has the same information as the tab index you

+# could consider to set DISABLE_INDEX to NO when enabling this option.

 GENERATE_TREEVIEW      = NO

+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values

+# (range [0,1..20]) that doxygen will group on one line in the generated HTML

+# documentation. Note that a value of 0 will completely suppress the enum

+# values from appearing in the overview section.

+ENUM_VALUES_PER_LINE   = 4

 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be

 # used to set the initial width (in pixels) of the frame in which the tree

 # is shown.

@@ -959,6 +1188,11 @@

 TREEVIEW_WIDTH         = 250

+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open

+# links to external symbols imported via tag files in a separate window.

+EXT_LINKS_IN_WINDOW    = NO

 # Use this tag to change the font size of Latex formulas included

 # as images in the HTML documentation. The default is 10. Note that

 # when you change the font size after a successful doxygen run you need

@@ -967,13 +1201,107 @@

 FORMULA_FONTSIZE       = 10

-# When the SEARCHENGINE tag is enable doxygen will generate a search box for the HTML output. The underlying search engine uses javascript

-# and DHTML and should work on any modern browser. Note that when using HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP)

-# there is already a search function so this one should typically

-# be disabled.

+# Use the FORMULA_TRANPARENT tag to determine whether or not the images

+# generated for formulas are transparent PNGs. Transparent PNGs are

+# not supported properly for IE 6.0, but are supported on all modern browsers.

+# Note that when changing this option you need to delete any form_*.png files

+# in the HTML output before the changes have effect.

+FORMULA_TRANSPARENT    = YES

+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax

+# (see http://www.mathjax.org) which uses client side Javascript for the

+# rendering instead of using prerendered bitmaps. Use this if you do not

+# have LaTeX installed or if you want to formulas look prettier in the HTML

+# output. When enabled you may also need to install MathJax separately and

+# configure the path to it using the MATHJAX_RELPATH option.

+USE_MATHJAX            = YES

+# When MathJax is enabled you can set the default output format to be used for

+# thA MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and

+# SVG. The default value is HTML-CSS, which is slower, but has the best

+# compatibility.

+MATHJAX_FORMAT         = HTML-CSS

+# When MathJax is enabled you need to specify the location relative to the

+# HTML output directory using the MATHJAX_RELPATH option. The destination

+# directory should contain the MathJax.js script. For instance, if the mathjax

+# directory is located at the same level as the HTML output directory, then

+# MATHJAX_RELPATH should be ../mathjax. The default value points to

+# the MathJax Content Delivery Network so you can quickly see the result without

+# installing MathJax.

+# However, it is strongly recommended to install a local

+# copy of MathJax from http://www.mathjax.org before deployment.

+MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest

+# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension

+# names that should be enabled during MathJax rendering.

+MATHJAX_EXTENSIONS     =

+# When the SEARCHENGINE tag is enabled doxygen will generate a search box

+# for the HTML output. The underlying search engine uses javascript

+# and DHTML and should work on any modern browser. Note that when using

+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets

+# (GENERATE_DOCSET) there is already a search function so this one should

+# typically be disabled. For large projects the javascript based search engine

+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.

 SEARCHENGINE           = YES

+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be

+# implemented using a web server instead of a web client using Javascript.

+# There are two flavours of web server based search depending on the

+# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for

+# searching and an index file used by the script. When EXTERNAL_SEARCH is

+# enabled the indexing and searching needs to be provided by external tools.

+# See the manual for details.

+SERVER_BASED_SEARCH    = NO

+# When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP

+# script for searching. Instead the search results are written to an XML file

+# which needs to be processed by an external indexer. Doxygen will invoke an

+# external search engine pointed to by the SEARCHENGINE_URL option to obtain

+# the search results. Doxygen ships with an example indexer (doxyindexer) and

+# search engine (doxysearch.cgi) which are based on the open source search engine

+# library Xapian. See the manual for configuration details.

+EXTERNAL_SEARCH        = NO

+# The SEARCHENGINE_URL should point to a search engine hosted by a web server

+# which will returned the search results when EXTERNAL_SEARCH is enabled.

+# Doxygen ships with an example search engine (doxysearch) which is based on

+# the open source search engine library Xapian. See the manual for configuration

+# details.

+SEARCHENGINE_URL       =

+# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed

+# search data is written to a file for indexing by an external tool. With the

+# SEARCHDATA_FILE tag the name of this file can be specified.

+SEARCHDATA_FILE        = searchdata.xml

+# When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the

+# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is

+# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple

+# projects and redirect the results back to the right project.

+EXTERNAL_SEARCH_ID     =

+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen

+# projects other than the one defined by this configuration file, but that are

+# all added to the same external search index. Each project needs to have a

+# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id

+# of to a relative location where the documentation can be found.

+# The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ...

+EXTRA_SEARCH_MAPPINGS  =

 #---------------------------------------------------------------------------

 # configuration options related to the LaTeX output

 #---------------------------------------------------------------------------

@@ -991,6 +1319,9 @@

 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be

 # invoked. If left blank `latex' will be used as the default command name.

+# Note that when enabling USE_PDFLATEX this option is only used for

+# generating bitmaps for formulas in the HTML output, but not in the

+# Makefile that is written to the output directory.

 LATEX_CMD_NAME         = latex

@@ -1007,10 +1338,10 @@

 COMPACT_LATEX          = NO

 # The PAPER_TYPE tag can be used to set the paper type that is used

-# by the printer. Possible values are: a4, a4wide, letter, legal and

+# by the printer. Possible values are: a4, letter, legal and

 # executive. If left blank a4wide will be used.

-PAPER_TYPE             = a4wide

+PAPER_TYPE             = a4

 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX

 # packages that should be included in the LaTeX output.

@@ -1024,18 +1355,25 @@

 LATEX_HEADER           =

+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for

+# the generated latex document. The footer should contain everything after

+# the last chapter. If it is left blank doxygen will generate a

+# standard footer. Notice: only use this tag if you know what you are doing!

+LATEX_FOOTER           =

 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated

 # is prepared for conversion to pdf (using ps2pdf). The pdf file will

 # contain links (just like the HTML output) instead of page references

 # This makes the output suitable for online browsing using a pdf viewer.

-PDF_HYPERLINKS         = NO

+PDF_HYPERLINKS         = YES

 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of

 # plain latex in the generated Makefile. Set this option to YES to get a

 # higher quality PDF documentation.

-USE_PDFLATEX           = NO

+USE_PDFLATEX           = YES

 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.

 # command to the generated LaTeX files. This will instruct LaTeX to keep

@@ -1050,10 +1388,19 @@

 LATEX_HIDE_INDICES     = NO

-# If LATEX_SOURCE_CODE is set to YES then doxygen will include source code with syntax highlighting in the LaTeX output. Note that which sources are shown also depends on other settings such as SOURCE_BROWSER.

+# If LATEX_SOURCE_CODE is set to YES then doxygen will include

+# source code with syntax highlighting in the LaTeX output.

+# Note that which sources are shown also depends on other settings

+# such as SOURCE_BROWSER.

 LATEX_SOURCE_CODE      = NO

+# The LATEX_BIB_STYLE tag can be used to specify the style to use for the

+# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See

+# http://en.wikipedia.org/wiki/BibTeX for more info.

+LATEX_BIB_STYLE        = plain

 #---------------------------------------------------------------------------

 # configuration options related to the RTF output

 #---------------------------------------------------------------------------

@@ -1085,7 +1432,7 @@

 RTF_HYPERLINKS         = NO

-# Load stylesheet definitions from file. Syntax is similar to doxygen's

+# Load style sheet definitions from file. Syntax is similar to doxygen's

 # config file, i.e. a series of assignments. You only have to provide

 # replacements, missing definitions are set to their default value.

@@ -1230,7 +1577,7 @@

 EXPAND_ONLY_PREDEF     = NO

 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files

-# in the INCLUDE_PATH (see below) will be search if a #include is found.

+# pointed to by INCLUDE_PATH will be searched when a #include is found.

 SEARCH_INCLUDES        = YES

@@ -1260,15 +1607,15 @@

 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then

 # this tag can be used to specify a list of macro names that should be expanded.

 # The macro definition that is found in the sources will be used.

-# Use the PREDEFINED tag if you want to use a different macro definition.

+# Use the PREDEFINED tag if you want to use a different macro definition that

+# overrules the definition found in the source code.

 EXPAND_AS_DEFINED      =

 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then

-# doxygen's preprocessor will remove all function-like macros that are alone

-# on a line, have an all uppercase name, and do not end with a semicolon. Such

-# function macros are typically used for boiler-plate code, and will confuse

-# the parser if not removed.

+# doxygen's preprocessor will remove all references to function-like macros

+# that are alone on a line, have an all uppercase name, and do not end with a

+# semicolon, because these will confuse the parser if not removed.

 SKIP_FUNCTION_MACROS   = YES

@@ -1276,22 +1623,18 @@

 # Configuration::additions related to external references

 #---------------------------------------------------------------------------

-# The TAGFILES option can be used to specify one or more tagfiles.

-# Optionally an initial location of the external documentation

-# can be added for each tagfile. The format of a tag file without

-# this location is as follows:

+# The TAGFILES option can be used to specify one or more tagfiles. For each

+# tag file the location of the external documentation should be added. The

+# format of a tag file without this location is as follows:

 # TAGFILES = file1 file2 ...

 # Adding location for the tag files is done as follows:

 # TAGFILES = file1=loc1 "file2 = loc2" ...

-# where "loc1" and "loc2" can be relative or absolute paths or

-# URLs. If a location is present for each tag, the installdox tool

-# does not have to be run to correct the links.

-# Note that each tag file must have a unique name

-# (where the name does NOT include the path)

-# If a tag file is not located in the directory in which doxygen

-# is run, you must also specify the path to the tagfile here.

+# where "loc1" and "loc2" can be relative or absolute paths

+# or URLs. Note that each tag file must have a unique name (where the name does

+# NOT include the path). If a tag file is not located in the directory in which

+# doxygen is run, you must also specify the path to the tagfile here.

 TAGFILES               =

@@ -1324,9 +1667,8 @@

 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will

 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base

 # or super classes. Setting the tag to NO turns the diagrams off. Note that

-# this option is superseded by the HAVE_DOT option below. This is only a

-# fallback. It is recommended to install and use dot, since it yields more

-# powerful graphs.

+# this option also works with HAVE_DOT disabled, but it is recommended to

+# install and use dot, since it yields more powerful graphs.

 CLASS_DIAGRAMS         = YES

@@ -1350,17 +1692,23 @@

 # toolkit from AT&T and Lucent Bell Labs. The other options in this section

 # have no effect if this option is set to NO (the default)

-HAVE_DOT               = YES

+HAVE_DOT               = NO

-# By default doxygen will write a font called FreeSans.ttf to the output

-# directory and reference it in all dot files that doxygen generates. This

-# font does not include all possible unicode characters however, so when you need

-# these (or just want a differently looking font) you can specify the font name

-# using DOT_FONTNAME. You need need to make sure dot is able to find the font,

-# which can be done by putting it in a standard location or by setting the

-# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory

-# containing the font.

+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is

+# allowed to run in parallel. When set to 0 (the default) doxygen will

+# base this on the number of processors available in the system. You can set it

+# explicitly to a value larger than 0 to get control over the balance

+# between CPU load and processing speed.

+DOT_NUM_THREADS        = 0

+# By default doxygen will use the Helvetica font for all dot files that

+# doxygen generates. When you want a differently looking font you can specify

+# the font name using DOT_FONTNAME. You need to make sure dot is able to find

+# the font, which can be done by putting it in a standard location or by setting

+# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the

+# directory containing the font.

 DOT_FONTNAME           = FreeSans

 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.

@@ -1368,10 +1716,9 @@

 DOT_FONTSIZE           = 10

-# By default doxygen will tell dot to use the output directory to look for the

-# FreeSans.ttf font (which doxygen will put there itself). If you specify a

-# different font using DOT_FONTNAME you can set the path where dot

-# can find it using this tag.

+# By default doxygen will tell dot to use the Helvetica font.

+# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to

+# set the path where dot can find it.

 DOT_FONTPATH           =

@@ -1378,7 +1725,7 @@

 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen

 # will generate a graph for each documented class showing the direct and

 # indirect inheritance relations. Setting this tag to YES will force the

-# the CLASS_DIAGRAMS tag to NO.

+# CLASS_DIAGRAMS tag to NO.

 CLASS_GRAPH            = YES

@@ -1400,6 +1747,15 @@

 UML_LOOK               = NO

+# If the UML_LOOK tag is enabled, the fields and methods are shown inside

+# the class node. If there are many fields or methods and many nodes the

+# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS

+# threshold limits the number of items for each type to make the size more

+# managable. Set this to 0 for no limit. Note that the threshold may be

+# exceeded by 50% before the limit is enforced.

+UML_LIMIT_NUM_FIELDS   = 10

 # If set to YES, the inheritance and collaboration graphs will show the

 # relations between templates and their instances.

@@ -1436,11 +1792,11 @@

 CALLER_GRAPH           = NO

 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen

-# will graphical hierarchy of all classes instead of a textual one.

+# will generate a graphical hierarchy of all classes instead of a textual one.

 GRAPHICAL_HIERARCHY    = YES

-# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES

+# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES

 # then doxygen will show the dependencies a directory has on other directories

 # in a graphical way. The dependency relations are determined by the #include

 # relations between the files in the directories.

@@ -1448,11 +1804,22 @@

 DIRECTORY_GRAPH        = YES

 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images

-# generated by dot. Possible values are png, jpg, or gif

-# If left blank png will be used.

+# generated by dot. Possible values are svg, png, jpg, or gif.

+# If left blank png will be used. If you choose svg you need to set

+# HTML_FILE_EXTENSION to xhtml in order to make the SVG files

+# visible in IE 9+ (other browsers do not have this requirement).

 DOT_IMAGE_FORMAT       = png

+# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to

+# enable generation of interactive SVG images that allow zooming and panning.

+# Note that this requires a modern browser other than Internet Explorer.

+# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you

+# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files

+# visible. Older versions of IE do not have SVG support.

+INTERACTIVE_SVG        = NO

 # The tag DOT_PATH can be used to specify the path where the dot tool can be

 # found. If left blank, it is assumed the dot tool can be found in the path.

@@ -1463,6 +1830,12 @@

 # \dotfile command).

 DOTFILE_DIRS           =

+# The MSCFILE_DIRS tag can be used to specify one or more directories that

+# contain msc files that are included in the documentation (see the

+# \mscfile command).

+MSCFILE_DIRS           =

 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of

 # nodes that will be shown in the graph. If the number of nodes in a graph

--- a/python/lib/gen_pyobject.py

+++ b/python/lib/gen_pyobject.py

@@ -477,7 +477,7 @@

 """ % {'funcname': method_name, 'objname': name,

         'out_type': out_type, 'setter_args': setter_args, 'parse_args': parse_args }

-        shortname = method_name.split(name+'_')[-1]

+        shortname = method_name.split('aubio_'+name+'_')[-1]

         method_defs += """\

   {"%(shortname)s", (PyCFunction) Py%(method_name)s,

     METH_VARARGS, ""},

@@ -493,7 +493,7 @@

             "get method has more than one parameter %s" % params

         getter_args = "self->o"

         returnval = "(PyObject *)" + aubiovectopyobj[out_type] + " (tmp)"

-        shortname = method_name.split(name+'_')[-1]

+        shortname = method_name.split('aubio_'+name+'_')[-1]

         method_defs += """\

   {"%(shortname)s", (PyCFunction) Py%(method_name)s,

     METH_NOARGS, ""},

--- a/src/pitch/pitchyinfft.c

+++ b/src/pitch/pitchyinfft.c

@@ -1,5 +1,5 @@

/*

-  Copyright (C) 2003-2009 Paul Brossier <piem@aubio.org>

+  Copyright (C) 2003-2013 Paul Brossier <piem@aubio.org>

   This file is part of aubio.

@@ -30,10 +30,9 @@

   fvec_t *win;        /**< temporal weighting window */

   fvec_t *winput;     /**< windowed spectrum */

-  cvec_t *res;        /**< complex vector to compute square difference function */

   fvec_t *sqrmag;     /**< square difference function */

   fvec_t *weight;     /**< spectral weighting window (psychoacoustic model) */

-  cvec_t *fftout;     /**< Fourier transform output */

+  fvec_t *fftout;     /**< Fourier transform output */

   aubio_fft_t *fft;   /**< fft object to compute square difference function */

   fvec_t *yinfft;     /**< Yin function */

   smpl_t tol;         /**< Yin tolerance */

@@ -58,9 +57,8 @@

   aubio_pitchyinfft_t *p = AUBIO_NEW (aubio_pitchyinfft_t);

   p->winput = new_fvec (bufsize);

   p->fft = new_aubio_fft (bufsize);

-  p->fftout = new_cvec (bufsize);

+  p->fftout = new_fvec (bufsize);

   p->sqrmag = new_fvec (bufsize);

-  p->res = new_cvec (bufsize);

   p->yinfft = new_fvec (bufsize / 2 + 1);

   p->tol = 0.85;

   p->win = new_aubio_window ("hanningz", bufsize);

@@ -98,43 +96,50 @@

 aubio_pitchyinfft_do (aubio_pitchyinfft_t * p, fvec_t * input, fvec_t * output)

   uint_t tau, l;

+  uint_t length = p->fftout->length;

   uint_t halfperiod;

-  smpl_t tmp, sum;

-  cvec_t *res = (cvec_t *) p->res;

-  fvec_t *yin = (fvec_t *) p->yinfft;

-  l = 0;

-  tmp = 0.;

-  sum = 0.;

+  fvec_t *fftout = p->fftout;

+  fvec_t *yin = p->yinfft;

+  smpl_t tmp = 0., sum = 0.;

+  // window the input

   for (l = 0; l < input->length; l++) {

     p->winput->data[l] = p->win->data[l] * input->data[l];

-  aubio_fft_do (p->fft, p->winput, p->fftout);

-  for (l = 0; l < p->fftout->length; l++) {

-    p->sqrmag->data[l] = SQR (p->fftout->norm[l]);

+  // get the real / imag parts of its fft

+  aubio_fft_do_complex (p->fft, p->winput, fftout);

+  // get the squared magnitude spectrum, applying some weight

+  p->sqrmag->data[0] = SQR(fftout->data[0]);

+  p->sqrmag->data[0] *= p->weight->data[0];

+  for (l = 1; l < length / 2; l++) {

+    p->sqrmag->data[l] = SQR(fftout->data[l]) + SQR(fftout->data[length - l]);

     p->sqrmag->data[l] *= p->weight->data[l];

+    p->sqrmag->data[length - l] = p->sqrmag->data[l];

-  for (l = 1; l < p->fftout->length; l++) {

-    p->sqrmag->data[(p->fftout->length - 1) * 2 - l] =

-        SQR (p->fftout->norm[l]);

-    p->sqrmag->data[(p->fftout->length - 1) * 2 - l] *=

-        p->weight->data[l];

-  }

-  for (l = 0; l < p->sqrmag->length / 2 + 1; l++) {

+  p->sqrmag->data[length / 2] = SQR(fftout->data[length / 2]);

+  p->sqrmag->data[length / 2] *= p->weight->data[length / 2];

+  // get sum of weighted squared mags

+  for (l = 0; l < length / 2 + 1; l++) {

     sum += p->sqrmag->data[l];

   sum *= 2.;

-  aubio_fft_do (p->fft, p->sqrmag, res);

+  // get the real / imag parts of the fft of the squared magnitude

+  aubio_fft_do_complex (p->fft, p->sqrmag, fftout);

   yin->data[0] = 1.;

   for (tau = 1; tau < yin->length; tau++) {

-    yin->data[tau] = sum - res->norm[tau] * COS (res->phas[tau]);

+    // compute the square differences

+    yin->data[tau] = sum - fftout->data[tau];

+    // and the cumulative mean normalized difference function

     tmp += yin->data[tau];

     yin->data[tau] *= tau / tmp;

+  // find best candidates

   tau = fvec_min_elem (yin);

   if (yin->data[tau] < p->tol) {

-    /* no interpolation */

-    //return tau;

-    /* 3 point quadratic interpolation */

+    // no interpolation, directly return the period as an integer

+    //output->data[0] = tau;

+    //return;

+    // 3 point quadratic interpolation

     //return fvec_quadint_min(yin,tau,1);

     /* additional check for (unlikely) octave doubling in higher frequencies */

     if (tau > 35) {

@@ -159,8 +164,7 @@

   del_aubio_fft (p->fft);

   del_fvec (p->yinfft);

   del_fvec (p->sqrmag);

-  del_cvec (p->res);

-  del_cvec (p->fftout);

+  del_fvec (p->fftout);

   del_fvec (p->winput);

   del_fvec (p->weight);

   AUBIO_FREE (p);