Some feature extractors not working in CLI version about meyda

[hughrawlinson]

Thanks! Does this happen on any wav at that sample rate? If so, it would be great if you could provide one.

The bug with Spectral Flux is known and we're working on that in the next major release. The problem is that the fix of that bug contains a breaking change, so we can't release it on the v5 version, and I've been slow merging it because I hadn't been able to get a code review. But we've made a beta available - if you install [email protected], you'll get a working spectral flux (though it is actually incorrect, but there'll be a -beta.3 soon with a fix to that.

But undefined for complex spectrum and loudness is definitely fishy and we'll look into it. Thanks for the report!

[hughrawlinson]

Also it looks like you're still using that temporary site for reference docs - I just wanted to let you know that we've published those improved docs to our regular site now :)

[Oortone]

Hello. I get this regardless of sample rate. Here are two example files at two different sample rates. Meyda reports the correct sample rate in both cases.
files.zip

Console output looks ok, but the files produced using --o flag are all filled with undefined.

[hughrawlinson]

ah ok! I'll take a look, thanks :)

[hughrawlinson]

Note for myself: This is likely because we don't distinguish between objects and arrays when rendering the output for csv here

[hughrawlinson]

@Oortone I think some of your problems would be solved if you got the output from meyda in json and then used something like this to convert the JSON to CSV in a more reliable way?

[Oortone]

OK, thanks. I might have a look at that. Although I don't think I need these features. Just happened to find the bug.

[hughrawlinson]

Ah cool, thanks!