Closed njellinas closed 3 weeks ago
Since you know that cut == recording in your case, you can fix that manually before decomposition with
for cut in cuts:
cut.features.recording_id = cut.recording.id
Ok, I thought that something like this would be automatic but it's OK.
I run the command: compute_and_store_features on a CutSet and the resulting cuts contain features that do not include the corresponding recording_id and thus I cannot decompose them and save them separately because they do not contain recording information.