torch-audiomentations should support torch.generator optionally, instead of always using the global seed.
Libraries that use pseudo-randomness and always interfere with the global seed are an anti-pattern, because they impede reproducibility.
A key use-case is this: You have validation set that is unrealistically "clean", but you want to add augmentations to simulate your test environment, which is more diverse. However, you want to deterministically introduce augmentations, so the validation set is the same every time.
The only workaround now is to with mucking with your global seed (that could have unintended consequences, and is easy to footgun on). The best solution is that torch-audiomentations can, optionally, use randomness independently from the global environment.
torch-audiomentations should support torch.generator optionally, instead of always using the global seed.
Libraries that use pseudo-randomness and always interfere with the global seed are an anti-pattern, because they impede reproducibility.
A key use-case is this: You have validation set that is unrealistically "clean", but you want to add augmentations to simulate your test environment, which is more diverse. However, you want to deterministically introduce augmentations, so the validation set is the same every time.
The only workaround now is to with mucking with your global seed (that could have unintended consequences, and is easy to footgun on). The best solution is that torch-audiomentations can, optionally, use randomness independently from the global environment.