Skip to content

no maxPitch and voicingCutoff constraints in eGeMAPS v01b config #86

@reichelu

Description

@reichelu

hi,

Flo today forwarded me the mail of an opensmile user who was wondering about high pitch outliers. While reconstructing the issue I observed higher pitch outlier values for opensmile eGeMAPSv01b LLDs than for ComParE LLDs. This is most likely due to a missing maxPitch constraint in the eGeMAPSv01b_core.lld.conf.inc. One can live with this of course. Only wanted to make sure that this missing maxPitch constraint is intended.

Furthermore, for eGeMAPSv01b as opposed to ComParE no voicingCutoff is specified. Do you know, whether the default used by the binary is the same as specified in the ComParE config ? This information I'd like to forward to the opensmile user.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions