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

Wrong/Invalid track_ids in Slakh dataset #585

Open
zyinmatrix opened this issue Mar 10, 2023 · 2 comments
Open

Wrong/Invalid track_ids in Slakh dataset #585

zyinmatrix opened this issue Mar 10, 2023 · 2 comments

Comments

@zyinmatrix
Copy link

I notice there are some wrong/invalid track_ids for multiple multitrack objects in the Slakh dataset.

In the screenshot, I loaded the dataset to be the 'baby' version of Slakh. For the multitrack "Track00014", the track_ids include "S11". However, there is actually no track "Track00014_S11". I double-checked by downloading the baby slakh dataset from their website, which does not include "Track00014_S11".

Screen Shot 2023-03-06 at 11 14 38 AM

There are also other multitrack containing invalid track_ids, such as 'Track00015-S06', 'Track00016-S12', 'Track00016-S14', and so on. Hope you can fix them soon! Thanks :)

@harshpalan
Copy link
Collaborator

Hello @zyinmatrix, thanks for contributing to mirdata, we will look into this.

@harshpalan
Copy link
Collaborator

Hi @zyinmatrix, the track_ids you mentioned have the midi file but not the audio, so by the design of the dataset, the track_ids are valid. Please let us know if you have any other questions.

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