Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance CutSet.mix() randomness and data utilization #1315

Merged
merged 2 commits into from
Apr 3, 2024

Conversation

pzelasko
Copy link
Collaborator

@pzelasko pzelasko commented Apr 3, 2024

This PR is based on #1313 and #1314: huge thanks to @osadj and @kamirdin for your contributions! While I was reviewing the PRs I noticed some subtle errors and figured it will be quicker to just combine your work and fix it in one go.

@pzelasko pzelasko added this to the v1.23.0 milestone Apr 3, 2024
@pzelasko pzelasko mentioned this pull request Apr 3, 2024
@pzelasko pzelasko merged commit 393a72a into master Apr 3, 2024
11 checks passed
@pzelasko pzelasko deleted the feature/improve-noise-mix-randomness branch April 3, 2024 14:37
to_mix = next(mix_in_cuts)
to_mix = self._maybe_truncate_cut(to_mix, target_mixed_duration, rng)
Copy link
Contributor

@osadj osadj Apr 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pzelasko I just noticed this. We need to update the target duration for random sub-region selection in the while loop (like I had in the PR). Let's assume the target is 20s. The first noise cut is 10s long, and we enter the while loop. The second noise cut is 15s long so we can select a random sub-region of 10s from the 15s, however currently because we use the original target duration we select from 0. Do you agree?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense. Can you make the change and verify it works as expected in another PR? Ideally add a unit test that would have been broken before the change is made, it will help maintaining this bit of code in the future.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done #1317. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants