cdak by Quite & orange (Final version) | 4k intro (FullHD 1080p HQ demoscene demo)

127K views · 15 years ago · demo · evergreen

A screen capture of "cdak" by Quite and orange, a demoscene 4k intro in which the whole real-time audiovisual piece fits in 4096 bytes of executable. This is the final version, at 1080p.

HN calls it possibly the best 4k demo ever made and the standard example of surprising creativity under tight size limits.

“possibly one of the best 4k demos ever made”

4 comments from Hacker News

s
@skrebbel2025 · in “MARS.EXE → COM (2021)”
The explanation is a great read. It reminds me of Unc's amazing explanation of how they did "cdak", possibly one of the best 4k demos ever made: link (for completeness, cdak pouet/download page: link - youtube capture: ▶ this video)
RecommendsView on HN
z
@zaf2015 · in “Cdak Best 4k Demo 2010”
Submitted the video to Hacker News.
RecommendsView on HN
s
@skrebbel2012 · in “Infinite complexity in 4096 bytes”
Just recently, in fact a new method came along: those raymarchers that many modern 4k intros are, are essentially a single pixel shader. The C code draws a single quad that fills the screen two-dimensionally, and calls the shader. The shader computes a colour for each pixel for each frame, on the GPU, using relatively simple math to describe the scene (geometric shapes, like intersections of spheres and cubes, for instance. or fractals, like in the OP). This means that instead of learning sizecoding, the opengl/d3d pipeline, mesh uploading, textures, getting along with the video bus speed, index buffers, geometry shaders, and so on, and so on, you can just learn GLSL and how a raymarcher works. Much like 20 years ago, getting something on screen quickly became easy again. It's not as easy as Processing, but it's not too far off either. For example, check out this video[1] about the Russian demogroup Quite (who made the amazing 4k intro "cdak"[2]. The video briefly shows (scroll to 20 minutes) how unc starts with the shader instead of with the C code, using vvvv[3], a tool for live prototyping realtime graphics. They only turn the non-shader parts of the vvvv "code" (block diagrams and envelopes) into C code when the intro starts looking like it's going to be releaseable. With such an approach, you get motivated real fast; focus on getting something on screen, worry about getting into a demoparty compo later. Or just don't worry about the C version at all, and make something cool that you'll never be able to pull off with any animation studio, and put it on vimeo :-) Oh, also check out this Pouet thread [4] about how Quite made "cdak" (but first see the intro!). It's one of those things that make you even more amazed when you get it. [1] link [2] link | ▶ this video [3] link [4] link
RecommendsView on HN
a
@amatecha2025 · in “Breaking into apartment buildings in five minutes on my phone”
There's definitely some truth to that. Consider the demoscene, where wildly creative stuff is typical made under certain limitations. For example, demos where the executable + resources is only 64kb [0] or 4kb [1] are often full of surprising creativity. That and of course demos made for primitive systems (by today's standards) like C64 [2] or Commodore Amiga [3]. [0] link [1] ▶ this video [2] link [3] link
CitesView on HN