Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About change yaml path #10

Closed
Kiri0824 opened this issue May 7, 2024 · 2 comments
Closed

About change yaml path #10

Kiri0824 opened this issue May 7, 2024 · 2 comments

Comments

@Kiri0824
Copy link

Kiri0824 commented May 7, 2024

hey, i download all your website dataset:DESED dataset, Weakly labeled data: 44.1kHz, multi-channel, Strongly labeled REAL data: 44.1kHz, multi-channel, Development data: 16kHz, multi-channel, Extra strongly-labeled data. But i dont't know how to change stage1.yaml and stage2.yaml. Are there any other data sets that need to be downloaded? or its enough. if enough, could you tell me the details about how to change yaml path.😭 Thank you so much!!!

@SaoYear
Copy link
Member

SaoYear commented May 8, 2024

Hi Kiri,

  1. The datasets provided in my personal site is NOT the full DCASE dataset. You should download some other datasets:
  • strongly-labeled synthetic dataset (generated by Scaper according to the DCASE task 4 intro, 10000 audio clips);
  • unsupervised 14412 audio clips;
  • If you want to use 2024 baseline dataset, download MAESTRO dataset;
  1. Once you downloaded this dataset, replace the following terms in yaml files:
  • weak_folder_44k: weak real dataset path
  • weak_folder: weak real dataset path + "_16k" postfix (the codes would automatically resample the wavform to 16k and save them to this path)
  • Similarly from the weak folder, change strong_folder - strongly real dataset; synth_folder - strongly synthetic folder; test_folder - strongly real development set and so force;

I would recommend you to run the dcase 2023 baseline first, by which you could know how the data is organized. And then run this repo.

@Kiri0824
Copy link
Author

Kiri0824 commented Jul 1, 2024

i think i solve this problem

@Kiri0824 Kiri0824 closed this as completed Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants