Experimental music from very short C programs

category: code [glöplog]
a bare-bones version of the previous one to see how small it can be:
t>>4|t*t*(t>>6&8^8)*(t>>11^t/3>>12)/(7+(t>>10& amp;t>>14&3))
added on the 2012-02-25 09:21:15 by yehar yehar
added on the 2012-02-25 16:31:50 by las las
sounds like a souped up version of one of glooms work lol.
added on the 2012-02-25 21:19:31 by rudi rudi
I still think there should be a more standardized instruction set, a few rules and a defined syntax not to mention some tools for wav/exe/playback/codefordemo and online playback tool.

Has anyone been working on something like this?
added on the 2012-02-26 10:46:15 by mu6k mu6k
I really like xpansive's piece :)
Got my No 4 smaller without really making it sound worse :)
((v=t/2^(t&64?63:0))>>v)/(1+(v>>v>>7))&t/32|(t>> 11)%8%3*t*t&15
added on the 2012-02-26 15:29:48 by yehar yehar
Oopsy. Sorry, some debug crud in that link, please use this instead:
((v=t/2^(t&64?63:0))>>v)/(1+(v>>v>>7))&t/32|(t>> 11)%8%3*t*t&15
added on the 2012-02-26 15:53:59 by yehar yehar
That's sweeeeeeeeeeeeet, mu6k! The detuned sound makes a great job at disguising any inexact note frequencies.
added on the 2012-02-26 21:59:48 by yehar yehar
xpansive, thats freaking unbelievable.
I think it's the one of the most impressive things since the beginning, it's in the spirit of the first ones, ultra simple formula, incredibly complex and long tune.
It's obviously not planned.

I feel there is some mathematical things to be discovered about this, maybe some kind of theory, like fractals. This should be able to lead to graphics too.

Replying to xpansive's with ONE MILLION alarm clocks:
added on the 2012-02-27 00:46:38 by yehar yehar
Thanks guys :)
Here's another one, quite a bit more deranged, though...
added on the 2012-02-27 04:43:28 by xpansive xpansive
Playing around some more with the t%t/ stuff...
(t%(t>>(t>>7&t>>2))<<2)|(t%(t/(t>>15&t> >6))>>4)
added on the 2012-02-28 02:10:14 by xpansive xpansive
added on the 2012-02-28 02:20:09 by vmuriel vmuriel

I think this C64 is creating something similar by mistake, by accidentally writing stuff to the SID registers because of some glitch. (Maybe dirty pin contacts on the 6502 or something.)
added on the 2012-03-04 01:55:14 by nitro2k01 nitro2k01