This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
tfrecord features #52
Comments
Hi! Thanks so much for your interest! Sorry for the late reply.
|
I am also trying to make tfrecords from guitar solos. Occasionally it's polyphonic but it's rare. Did anyone get some tfrecord generation code working or more info about the data format? |
Hi @vivienseguy , unfortunately I don't have the code for generating the tfrecord. I think you could look into some of the dataset format details explained in this issue and the issue that mentioned this issue. (#59). You could try to generate your tfrecord dataset in the same format with the same keys. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, I'm very interested in your amazing work. Took a deep look at the urmp tfrecord datasets, I found something a bit confusing for me. Could you be so kind to help?
{"audio", "f0_confidence", "f0_hz", "f0_time", "id", "instrument_id", "loudness_db", "note_active_frame_indices", "note_active_velocities", "note_offsets", "note_onsets", "orig_f0_hz", "orig_f0_time", "power_db", "recording_id", "sequence"}
. However, some of them don't include{"orig_f0_hz", "orig_f0_time"}
in their tfrecord data. Why is this so and does such an inconsistency influence the model training?Thank you very much for your help in advance.
The text was updated successfully, but these errors were encountered: