Open lucasgautheron opened 2 years ago
Ideally :
1) Existing metadata and annotations (vtc, lena, etc) should be cut accordingly.
2) recordings.csv
shouldn't be erased. I think having a sessions.csv
instead would be useful (you may want to work on your dataset at the longform level, or at the session-level)
Ideally :
- Existing metadata and annotations (vtc, lena, etc) should be cut accordingly.
recordings.csv
shouldn't be erased. I think having asessions.csv
instead would be useful (you may want to work on your dataset at the longform level, or at the session-level)
session_id
. For instance, some of ChildProject's features (like sampling) already allow the user to decide which level to work at. Do we need a separate metadata file for that?
Is your feature request related to a problem? Please describe.
Users may want to split LENA recordings into contiguous blocks, as in EL1000. This involves splitting the recordings in the metadata and splitting the audio accordingly.
Describe the solution you'd like
Implement a processor (in pipelines.processors)
lena_recording_num
date_iso
andstart_time
properly for each block (increment the original date by the correct amount for each block)session_id
andsession_offset
(what if they already exist?)