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

Support file-like object in apply_effects_file #1166

Merged
merged 3 commits into from
Jan 29, 2021

Conversation

mthrok
Copy link
Collaborator

@mthrok mthrok commented Jan 8, 2021

The underlying implementation is same as load function. (both use apply_effects_fileobj) So this is just registering the C++ implementations, modifying frontend and adding test.

See also #1115

@mthrok mthrok mentioned this pull request Jan 8, 2021
6 tasks
@mthrok mthrok force-pushed the file-like-obj-sox-effects branch 2 times, most recently from cc0ece0 to ae837ec Compare January 15, 2021 23:35
@mthrok mthrok marked this pull request as ready for review January 19, 2021 15:51
@mthrok mthrok added this to the v0.8 milestone Jan 25, 2021
@mthrok mthrok force-pushed the file-like-obj-sox-effects branch from ae837ec to 4a85493 Compare January 25, 2021 20:54
@mthrok mthrok force-pushed the file-like-obj-sox-effects branch from 4a85493 to d8f8784 Compare January 27, 2021 19:30
Copy link
Contributor

@datumbox datumbox left a comment

Choose a reason for hiding this comment

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

LGTM!

torchaudio/sox_effects/sox_effects.py Outdated Show resolved Hide resolved
@mthrok mthrok merged commit ec1b3e3 into pytorch:master Jan 29, 2021
@mthrok mthrok deleted the file-like-obj-sox-effects branch January 29, 2021 17:43
@mthrok
Copy link
Collaborator Author

mthrok commented Jan 29, 2021

thanks!

@vincentqb
Copy link
Contributor

vincentqb commented Jan 29, 2021

@mthrok, can you confirm this is not breaking master here ? the error is blocking import D26150720.

@mthrok
Copy link
Collaborator Author

mthrok commented Jan 29, 2021

@vincentqb that failure is not originated from this. It is flaky in the occurrence but the same set of tests fail when it happens. I am hunting down the cause. and current hypothesis is that the underlying CCI environment is not consistent. Anyways it does not block the import you are working on.

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

Successfully merging this pull request may close these issues.

4 participants