Skip to content

Unexpected behaviour report: novelty feature of steady input is not 0 #317

Description

@tremblap

Please tell us what you were doing! You can include code and files by drag and dropping them into the text area.

Gibert Nouno was exploring the values and pointed at a kernel-dependant offset of the novelty feature value. After a bit of scratching, it seems that MFCCs and Loudness do indeed produce an offset... which changes value when the kernel size is changed. This is true for steady sync'd sinewave, or digital silence in.

What was the expected result?

We were expecting 0.

What was the actual result?

a fixed offset.

What operating system were you using?

Mac

Operating system version

15.5

FluCoMa Version

1.0.8

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcontent

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions