The average movie uses 24fps and lasts about 90 minutes.
That's 129,600 frames, give or take, with each frame being one line.
Not one of their prints appears to contain 129k lines. Also the idea is really dumb. Who is this for?
(, Sun 2 Jan 2022, 14:08, Reply)
It's pointless, but I like pretty generative stuff.
Then I saw they're doing NFTs, and have never done Derek Jarman's Blue for the arthouse LOLs.
(They don't say it's each frame, but a sample every 10 seconds - thecolorsofmotion.com/faq)
(, Sun 2 Jan 2022, 14:20, Reply)
Then I retract some of what I said, but I'm going to remain somewhat cunty about it.
(, Sun 2 Jan 2022, 15:18, Reply)
(, Sun 2 Jan 2022, 16:50, Reply)
from.. thecolorsofmotion.com/faq
How does this all work?
We take a movie, then we extract the frames at at a regular interval based on the length of the movie (For a 1h30 movie, it's around once every 10 seconds). Next, we calculate the average color of each of those frames. Finally we stack those colors as thin bars from top to bottom in chronological order. The result is a color timeline of the movie.
But like, how does it really work?
Ah! The nitty gritty. The entire process of extracting the movie data and generating the prints is automated using a bunch of node script. To extract the images, we use a node wrapper around ffmpeg, then a series of custom scripts extract the average colors. The frames are uploaded to amazon S3 and the color data stored in mongoDB. Relevant movie data is pulled for each movie using an unofficial IMDB api. The generation of the print files is also automated, using a node canvas wrapper.
if each frame was a pixel then a 360 x 360 picture would do 129,600 frames
(, Sun 2 Jan 2022, 21:08, Reply)