| |
Raistlin
Registered: Mar 2007
Posts: 680 |
Screenshots of Interlace Pics
I’m interested to know what people’s thoughts are on screenshotting interlace pics…
On C64GFX, we do things a bit differently to CSDb. Generally, we care more about the original art than how it’s presented - so we’ll host logos with all the “extras” removed (scrollers, textual information, etc). But of course CSDb screenshots are of how things are actually released.
With interlace pics, it’s more complicated. In theory we should be displaying animations at 50fps (usually) switching between 2 screenshots.. but I’m lead to believe that that could cause battery drain and other problems on devices - plus the FPS probably wouldn’t be 50.
Some sort of blending was suggested.. or simply choosing alternate pixels and merging to create a full-res pic.
The latter is what I’ve tried with some pics .. eg. Some of Leon’s. It looks good and it looks like it’s true to the original creation - I’d hazard a guess that he simply drew these pics at full 320x200px resolution on most of these, actually, rather than drawing on C64 in an interlace editor?
Eg. https://c64gfx.com/image/168046
I toyed with the idea of blending the 1px offset pictures (frame 0 and frame 1).. but I’m not sure that that’s correct either.
Others have suggested some fairly complex blending schemes that presumably show more like it would be on CRT - and I think this is where the 1,000s of colours problem comes in (evident on many CSDb screenshots). This seems unfair since regular MC/HI screenshots don’t get the same treatment.
Anyway, interested to know thoughts… both for CSDb and for C64GFX.com |
|
... 71 posts hidden. Click here to view all posts....
|
| |
Jetboy
Registered: Jul 2006
Posts: 337 |
YEAH! Now we are talking!
Your new version of interlace, plus my version of css blending and we are ready to go!
btw. There are 2 versions of interlace with MC. With, and without 1 pixel horizontal scroll. It is important to keep that if we want the images to be as true to the original as possible. |
| |
Raistlin
Registered: Mar 2007
Posts: 680 |
Thanks to Gordian, we now have interlace pics interlacing on C64GFX :-)
Leon’s page is a great example of them: https://c64gfx.com/artist/1373/leon |
| |
Shine
Registered: Jul 2012
Posts: 369 |
Yeah indeed, thanks A LOT to Gordian!
I am not a big fan of interlaced pictures at all, but this result seems very suited! |
| |
Gordian
Registered: May 2022
Posts: 80 |
No at all, it was pleasure for me:)
P.S. We add also JS script which prevents flickering empty/black frame(s) when they are not fully loaded (sometimes one of the frames was loaded faster than the other one). |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Somehow on the website it doesnt look nearly as good (interlace stuttering all the time) as in the css anim in the thread :/ |
| |
Digger
Registered: Mar 2005
Posts: 437 |
Hmm doesn't seem to work in Safari nor Firefox on a Mac (e.g. https://c64gfx.com/image/160940), but Gordian's examples work fine.
Works in Chrome only.
@Groepaz: Yeah, I've been trying various techniques to remedy the stutter but nothing works. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
The previous css anim was working perfectly here :) |
| |
Raistlin
Registered: Mar 2007
Posts: 680 |
Updated again now (thanks again, Gordian) so should hopefully work. Fixed a few other bugs at the same time.
Thanks everyone - let me know if anything else is borked :-) |
| |
Gordian
Registered: May 2022
Posts: 80 |
@Digger, I've tested on MacOS Sequioa, FF 133.0 and Safari 18.0 (20619.1.26.31.6), works fine...
@All: We decided change the speed of animation to two times faster, because some of images look awful with standard speed, and much worse than in VICE.
background-image animation was change to <img> animation for SEO purposes and greater performance.
Stepped animation (my last example in this thread) was change to more linear (as previously), now it's more smoother and not jiggly. |
| |
soci
Registered: Sep 2003
Posts: 480 |
I'd be really nice if it could be improved by removing the "not-loaded" class from the container. Then it wouldn't be blank with javascript disabled. Asking for a friend :)
Also while it's flickering as intended at 60Hz it doesn't (or hardly) works at all at 50Hz. Actually it acts strange at any frame rate which (almost) divides 100.
That's a pity as on machines I actually do stuff the displays tend to run close to 50.12 Hz for some reason. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 - Next |
