search

audeering / opensmile

The Munich Open-Source Large-Scale Multimedia Feature Extractor
https://audeering.github.io/opensmile/
Other
553 stars 74 forks source link

(MSG): No filename given #48

Closed op-Valar-Morghulis closed 2 years ago

op-Valar-Morghulis commented 2 years ago

image Thanks for your amazing software. I have encounter some messages when I was using opensmile to extact the feature of .wav file. I wondered what is the problem with my usage. Could you give me some advice on it ? The command I used looks like this: cd /content/drive/MyDrive/opensmile && ./SMILExtract -C /content/drive/MyDrive/opensmile/config/is09-13/IS09_emotion.conf -I /content/drive/MyDrive/audio_0.wav -O /content/drive/opensmile_extract/audio_0.txt

chausner-audeering commented 2 years ago

You can ignore those messages, they are normal and expected. They just say that some of the outputs (functionals in CSV and HTK format and all LLDs) are disabled because you did not specify output paths for them on the command-line.

op-Valar-Morghulis commented 2 years ago

You can ignore those messages, they are normal and expected. They just say that some of the outputs (functionals in CSV and HTK format and all LLDs) are disabled because you did not specify output paths for them on the command-line.

Thanks for your reply. So do those outputs affect the output features of .wav file ?

chausner-audeering commented 2 years ago

No, they do not affect the features. There are just different formats that the features can be output in (ARFF, CSV, HTK). You are using -O which outputs in the ARFF format. If you specify -csvoutput <path>, you'll get the features in CSV format, for example. See https://github.com/audeering/opensmile/blob/master/config/shared/standard_data_output.conf.inc.