You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi author,
I've been experimenting with encoding audio using your fantastic method, and I noticed that the RVQ (Residual Vector Quantization) values I obtain are integers like the follows:
I'm curious if this is expected behavior. Additionally, I'm interested in using these encoded features for downstream tasks, but I'm unsure about how to adjust these integer values for training purposes. Would it be appropriate to apply normalization techniques such as min-max scaling or Z-Score normalization? The distribution of these encoded feature values is unknown to me, so I'm seeking guidance on how to handle them effectively for training.
Any advice or suggestions on how to deal with these encoded feature values would be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi, these integers simply correspond to the indexes of the codebooks in the different quantizers.
I don't really think you will be able to do anything interesting only with these indexes. Trying to do something with the codewords associated with these indexes should be more interesting in my humble opinion.
Hi author,
I've been experimenting with encoding audio using your fantastic method, and I noticed that the RVQ (Residual Vector Quantization) values I obtain are integers like the follows:
I'm curious if this is expected behavior. Additionally, I'm interested in using these encoded features for downstream tasks, but I'm unsure about how to adjust these integer values for training purposes. Would it be appropriate to apply normalization techniques such as min-max scaling or Z-Score normalization? The distribution of these encoded feature values is unknown to me, so I'm seeking guidance on how to handle them effectively for training.
Any advice or suggestions on how to deal with these encoded feature values would be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: