Zoomquilt 2 (2007)
zoomquilt2.com
zoomquilt2.com
Thanks openseadragon devs
...but what caused way more trouble was the situation where the blocked all "alcohol" related sites and within five minutes he had a note from one of the CEOs... :D
Alternatively try doing `npm install zoomquilt`.
It seems like it is about 8 scenes that spawns the next scene in the vanishing point of the current scene.
And as far as I see, the functionality of both is the same. Sure version 2 may have higher resolution images and some hue transformations, but surely 16 years of hardware improvements can handle that without consuming a whole core.
Morning moan over. Also, this is first and foremost a piece of art, and this comment shouldn't take away from that. I just think this is an interesting comparison that is relevant on HN.
I can't even notice the load on the system - Chrome's task manager tells me it's using 10% CPU, and I'm running on a 4k monitor.
EDIT: just tested with Firefox on MacOS and it's incredibly choppy and CPU-hungry. the `drawImage` call always goes over budget for RAF, there are a ton of open issues about it: https://bugzilla.mozilla.org/show_bug.cgi?id=1602299
Drawing at half scale gets it back to 60ms with time to spare:
window_w = w * dpr / 2;
window_h = h * dpr / 2;(Ryzen 7 4800H, Windows 10 20H2, Firefox 84.0.1, 1080p screen)
The performance in Chrome is noticeably better than Firefox. The smaller the window size, the smoother the playback. Since it is only four images at once, whenever one image leaves the scene and a new one appears, there might be a small lag when the image is loaded into memory. I don't have a deeper understanding on how this could be optimized further for the browser.
For the Android OpenGL implementation I was able to take care of loading the images asynchronously before they enter the scene and freeing up the memory again after they leave the scene.
Happy to take suggestions on how this might be optimized further, as it would be interesting to work with even higher resolutions for future projects, but this quickly leads to much higher performance load and choppy playback on weaker machines.
Thanks for these, they are incredible!
[1] when devicePixelRatio > 1, in FF only. Gets me from 24ms to 7ms/frame here
Still this indeed gets my laptop's fans spinning in both Chrome and Firefox. I wonder why that is... I don't think you can do a lot wrong code wise here. Maybe the composition takes a software path, but why?