EDIT: We can be generous and say 40kb for sake of adding more colours / etc.
Source code for 4kb demoscene production “Elevated” released
31–40 of 154 posts
Re: Source code for 4kb demoscene production “Elevated” released
#32Does this mean that lots of 3:30 minutes 1080p videos could be compressed into 4kb? EDIT: We can be generous and say 40kb for sake of adding more colours / etc.
Re: Source code for 4kb demoscene production “Elevated” released
#33Re: Source code for 4kb demoscene production “Elevated” released
#34Does this mean that lots of 3:30 minutes 1080p videos could be compressed into 4kb? EDIT: We can be generous and say 40kb for sake of adding more colours / etc.
Why would you think that? https://en.wikipedia.org/wiki/Procedural_generation https://en.wikipedia.org/wiki/Demoscene https://en.wikipedia.org/wiki/Real-time_computer_graphics
Re: Source code for 4kb demoscene production “Elevated” released
#35Most programming jobs must feel terribly boring for anyone who managed to write that.
Re: Source code for 4kb demoscene production “Elevated” released
#36also impressive: https://en.wikipedia.org/wiki/.kkrieger
http://www.pouet.net/prod.php?which=67106 / https://www.youtube.com/watch?v=qRVTI2y0BBg
Re: Source code for 4kb demoscene production “Elevated” released
#37Earlier quoted context omitted.
Why would you think that? https://en.wikipedia.org/wiki/Procedural_generation https://en.wikipedia.org/wiki/Demoscene https://en.wikipedia.org/wiki/Real-time_computer_graphics
Sorry, I thought it was obvious, but the question is: Could procedural generation be used to achieve amazing compression rates given a currently impossible to code algorithm?
Re: Source code for 4kb demoscene production “Elevated” released
#38Earlier quoted context omitted.
Why would you think that? https://en.wikipedia.org/wiki/Procedural_generation https://en.wikipedia.org/wiki/Demoscene https://en.wikipedia.org/wiki/Real-time_computer_graphics
Sorry, I thought it was obvious, but the question is: Could procedural generation be used to achieve amazing compression rates given a currently impossible to code algorithm?
Re: Source code for 4kb demoscene production “Elevated” released
#39Earlier quoted context omitted.
How much harder would it be if software rendered or on a simple GPU from the late 90's? Their executable still 4KB? No?
>How much harder would it be if on a simple GPU from the late 90's It would be impossible since pixel shaders didn't exist until the 2000's ;-) As for software rendering: Since a pixel shader is essentially a program executed for every pixel, it's trivially portable to the CPU: Just turn it into a function and call it for every pixel on the screen. Making it fast is another matter altogether though.
[1] https://people.csail.mit.edu/ericchan/bib/pdf/p289-hanrahan.... [2] http://www.cs.unc.edu/~olano/papers/pxflshading.pdf [3] http://www.cs.unc.edu/~pxfl/papers/high-speed_rendering.pdf
Re: Source code for 4kb demoscene production “Elevated” released
#40Earlier quoted context omitted.
Why would you think that? https://en.wikipedia.org/wiki/Procedural_generation https://en.wikipedia.org/wiki/Demoscene https://en.wikipedia.org/wiki/Real-time_computer_graphics
Sorry, I thought it was obvious, but the question is: Could procedural generation be used to achieve amazing compression rates given a currently impossible to code algorithm?
It's the pigeonhole principle; there are only a few long videos possibly encodable as short programs because there are only a few short programs in the first place. To get compression performance, one has to target an ever smaller subset of possible videos, which eventually starts becoming an AI-complete problem.