I just posted the article[1] that I think prompted this script to be brought up.<p>What I did instead was to run images through an audio editing tool, which lets you apply echoes or do mindboggling
things like change the volume of the image.
The script can be found on github[2].<p>[1] <a href="http://memcpy.io/audio-editing-images.html" rel="nofollow">http://memcpy.io/audio-editing-images.html</a><p>[2] <a href="https://github.com/robertfoss/audio_shop/" rel="nofollow">https://github.com/robertfoss/audio_shop/</a>
There's a whole subreddit for things like this. <a href="https://www.reddit.com/r/glitch_art/" rel="nofollow">https://www.reddit.com/r/glitch_art/</a>
Now I wonder, what happens if you add sound effect, to change pitch, tone, or widen the sound stage. What would do to the decoded image?<p>I think the 2.00 bits/ pixel result looks quite more "analog" with a film grain effect to me.
I did something similar with Ogg Vorbis back in 2006.<p>There are also some results of experiments with the Opus codec posted in the comments.<p><a href="https://www.tablix.org/~avian/blog/archives/2006/01/lossy_compression/" rel="nofollow">https://www.tablix.org/~avian/blog/archives/2006/01/lossy_co...</a>
Not really related, but a while back I wrote a script to visualize/hear audio generation loss with different file formats:<p><a href="https://github.com/skratchdot/audio-generation-loss/tree/master/files/loop01" rel="nofollow">https://github.com/skratchdot/audio-generation-loss/tree/mas...</a><p>So, mp3s add a bunch of silence to the beginning of the file, and ogg files start to "chirp". I never got around to putting this info in a consumable, easy to understand format though. The videos in these folders just continuously re-encode a source file w/ a given lossy format.<p>See also: <a href="https://en.wikipedia.org/wiki/Generation_loss" rel="nofollow">https://en.wikipedia.org/wiki/Generation_loss</a>
They're both based on the DCT. Mp3 (and AAC and Vorbis and more) use a modified DCT which uses block overlapping to mitigate aberrations on the block boundary.<p>Its no surprise it works, however you wouldn't necessarily get "as good" compression as you would from an optimized DCT coder (JPEG etc) based on the data duplication (2x for the overlapping blocks).<p>See
<a href="https://en.wikipedia.org/wiki/Modified_discrete_cosine_transform" rel="nofollow">https://en.wikipedia.org/wiki/Modified_discrete_cosine_trans...</a>
<a href="https://en.wikipedia.org/wiki/Discrete_cosine_transform" rel="nofollow">https://en.wikipedia.org/wiki/Discrete_cosine_transform</a>
I wonder if it's possible to create a set of data that produces an actual image when compressed with JPEG and an actual music when compressed with MP3 (for example, a JPEG picture of pianist that also gives a MP3 piano piece).
Curious enough, years ago I've seen a blog post where the author used PNG lossless compression for FLAC audios.
Guess there should be a lot of room for improving both image and audio compression, even because we're still ending up using jpeg and mp3.
Is there a way to use image compression for MP3s?<p>I'd like to store music files in my phone's camera roll, and easily upload them to a website where some Javascript could decode and play them.
Now for big time shits-and-grins, add a deep learning GAN to generate a more refined signal during the decompression / upsampling stage.<p>That's something your Turbo Pascal code never attempted.
I think the question really is, does it do anything for file size? If there were a radical difference in total size, the quality degradation might be an interesting compromise.
I remember reading an article where file data (a ZIP file I believe) was converted into a bitmap image, and then it was compressed with PNG for another few % of compression.