-
Notifications
You must be signed in to change notification settings - Fork 32
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
potential soundcloud fix? #192
Comments
I think this sounds like a great idea! I could potentially write a little Bash script that randomizes what the visualization would be, so users would just need to feed the script and get the MP4s out easily. |
😎 @iamdamosuzuki ! 😎 |
This sounds like a great idea! I can see pairing the artifacts' audio with what they might potentially look like on monitoring equipment/software being super helpful! |
Really great idea, I'm all for it (is there anything FFmpeg can't do?). |
This ffmpeg fix idea came about when we realized the IA embeds for audio were both boring and craptastic. Go ffmpeg! |
hi all,
I was chatting with @kellyhaydon, and we may have come up with a decent solution for consolidating our video and audio sample files on IA and eliminating our reliance on soundcloud.
the fix would be: transcoding the MP3s to video MP4s, while also adding fun FFmpeg visualizations that would cater to the particulars of the errors themselves. So, for example, instead of having our Audio Phase Error be the standard soundcloud visual with a separate pic of a phasescope, we would create an MP4 using FFmpeg's avectorscope or aphasemeter filters (maybe both!). See filter examples here:
https://trac.ffmpeg.org/wiki/FancyFilteringExamples;
https://trac.ffmpeg.org/wiki/Waveform;
https://video.stackexchange.com/questions/9644/how-do-i-turn-audio-into-video-that-is-show-the-waveforms-in-a-video.
It'll take some playing around with, and I might need a little assistance from my audio guru @privatezero, but I'd be happy to take a stab if everyone approves.
Please share any thoughts, positive or negative. Thanks!
The text was updated successfully, but these errors were encountered: