-
Notifications
You must be signed in to change notification settings - Fork 53
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
Audio support #7
Comments
Thanks, Spencer--I hadn't realized that you were the maintainer of AudioIO! It would definitely be good to coordinate. I also might not get to that soon, but will ping you when I do. (Others should definitely feel free to chime in!) |
Hi, |
I'm working on a new set of abstractions that I'm hoping will make audio easier to incorporate into other packages in a uniform way without pulling in all the AudioIO stuff. See ssfrr/AudioIO.jl#48 for some initial discussion. Hopefully by the end of this week I should be announcing an initial package more publicly. |
Awesome! On Tue, Sep 15, 2015 at 9:27 AM, Spencer Russell notifications@github.com
|
Is there any news on this? It's been years, AudioIO.jl seems dead... are there plans to include getting also the audio from videos? Are there any ways to achieve this right now in Julia? |
This seems like a good time to suggest that there should be some commonality and interoperability between AudioIO and VideoIO.
For instance, using VideoIO to strip out the audio should return the same sort of audio object as AudioIO gives you when you open a file. Currently that's an
AudioFile
but there should be something more abstract.Another example would be if you set up a signal processing chain using AudioIO you could apply that to the sound track of a video, either during realtime playback or as an offline rendering operation.
There are lots of pieces in the AudioIO API that are either not yet designed or still changable, so this is a good time to make sure we're aligned.
There isn't any particular rush on this from my end, but if folks want to chat about how those interfaces should look I'm here.
The text was updated successfully, but these errors were encountered: