Ahhh, thank you! I was wondering what the seed corresponded to.
Pretty neat little thing! I was just trying to figure out if they were using some novel system to categorize procedural synths as "good", because that seems pretty useful! Still a neat little thing, though!
I still don't get it. What's an Opus codec glitch? I know roughly how things like jpg, flac, and mp3 work, and worked with Opus via ffmpeg/opusenc, but what makes some sounds a glitch? Can you only hear this when playing the data with certain decoders or so? The page and the posts don't say
This might be glitching in the sense of “glitch art”, where you deliberately corrupt a compressed file in small ways (flip a few bits here and there, for example) that propagate in interesting ways when decompressed.
On the projects page (https://suricrasia.online/projects/) it says "Make glitchy beats with randomly generated Opus protocol packets." So I guess it's random data fed into the opus decoder.
author here: this is correct. the opus protocol is so efficient, you can fill a packet with random data and it will still decompress into a sensible sound. this is where all the sounds come from
author here: they are randomly generated packets, extended using the packet loss concealment feature. you can fill a packet with random data and it will still decompress into a sensible sound, and that's where all the sounds in the drum machine come from
Fire
["Jpeg",75,125,[[42,8224,0],[43,8,0],[50,8192,10],[55,4010,7],[55,43690,8],[56,32768,11],[68,8224,8],[68,552,7],[73,8,9],[68,8224,8],[68,544,7]],[[-1,100,2]]]
18 comments
[ 2.9 ms ] story [ 44.6 ms ] threadPretty neat little thing! I was just trying to figure out if they were using some novel system to categorize procedural synths as "good", because that seems pretty useful! Still a neat little thing, though!
[["56ne","count","plenk","aaa","reck"],2,138,[[194,256,0],[140,4112,0],[281,64,5],[298,257,0],[397,4096,7],[396,8193,14],[393,1088,3]],[[-1,36,0],[476,-18,17],[476,-54,78]]]