save_dataset_statistics broken with DDSP 3.2.0? about ddsp HOT 6 OPEN

Granted, I am having this problem with version 3.5.0, thought perhaps issue might have been the same. I saw it, and tried it, but sadly to no avail. The default values of these parameters seem to match. I tried to match them manually in the notebook as well as changing them in both place to these values in your example, but still getting the same frame_size vs. hop_size error.

from ddsp.

I have the same exact problem.
I´m trying to run it locally, and I honestly dont know how it still runs in collab but it crashes here, with the same values.
I tried increasing the frame size to 512 and 320 (just to see if it works) and then I get another error:
File "...\ddsp\training\postprocessing.py", line 330, in get_stats max_list.append(np.max(x_i[m])) IndexError: boolean index did not match indexed array along dimension 0; dimension is 181 but corresponding boolean dimension is 980

I´m not that thrilled to see that this happened to you in March and there´s still no replys too.

from ddsp.

I just tried the same thing locally and I'm getting the same error.

from ddsp.

@sharp-trickster @theloni-monk I'm no longer working on this, but if I recall correctly the issue is the the TFRecordProvider must be initialized with the exact same arguments that the dataset was created with in ddsp_prepare_tfrecord, otherwise you get mysterious errors like this. For example,

data_provider = ddsp.training.data.TFRecordProvider(
    args.train_tfrecord_filepattern,
    # Make sure these arguments match what the dataset was created with!
    # sample_rate=44100,
    frame_rate=50,
    centered=True,
    with_jukebox=False,
)

Look for ddsp_prepare_tfrecord.py to see what the defaults are.

See also the updated script I made for my thesis.

from ddsp.

Anybody ever solved this?

from ddsp.

@olaviinha see my comment above, it's about the arguments to the TFRecordProvider not matching what the data was created with. The frame_rate and centered arguments must match, otherwise you get mysterious errors like this.

from ddsp.