Amiga Demo Screenshot Collection
category: general [glöplog]
During the course of my collecting of Amiga demos, I sought to take screenshots of all of them from WinUAE, to put a picture to the prod, as a picture paints a thousand words and also because it's a simple way to show off the Amiga's graphical prowess and makes for useful art for media files.
So as of today, I have screenshots from 788 assorted Amiga demos (OCS/ECS and AGA) in PNG format, with a resolution of 752x574 for the PAL demos. The screenshots consist almost all of title screens, or memorable images from each demo when no obvious title is available.
So here they are - enjoy!
https://drive.google.com/file/d/1d0nHiWgBD5prTkWGjvNJwzUO24pwNDv6/view?usp=sharing
So as of today, I have screenshots from 788 assorted Amiga demos (OCS/ECS and AGA) in PNG format, with a resolution of 752x574 for the PAL demos. The screenshots consist almost all of title screens, or memorable images from each demo when no obvious title is available.
So here they are - enjoy!
https://drive.google.com/file/d/1d0nHiWgBD5prTkWGjvNJwzUO24pwNDv6/view?usp=sharing
Cool!
A thought: Would it make sense to team up with z5 and integrate them into ada.untergrund.net somehow (even as a separate list)? Screenshots on ADA are very lowres unfortunately (160x128)..
A thought: Would it make sense to team up with z5 and integrate them into ada.untergrund.net somehow (even as a separate list)? Screenshots on ADA are very lowres unfortunately (160x128)..
I wouldn't know how to do that, arm1n, but that's why I'm making them available, someone who has the skills could do it.
Good stuff, saved! I'd probably split it into two sub directrories, OCS and AGA, given the great number of entries. It's sometimes hard to tell from a screenshot alone.
Quote:
Good stuff, saved! I'd probably split it into two sub directrories, OCS and AGA, given the great number of entries. It's sometimes hard to tell from a screenshot alone.
I could do that easily, by seeing which demo uses an AGA or OCS config on WinUAE, but it would take some time to do. I'll have a look, maybe link to an updated zip with separate folders.
You could also contribute the screenshots to Demozoo if any of them are missing there. No help from admins needed, you just log in and upload them.
Cool!
Quote:
Good stuff, saved! I'd probably split it into two sub directrories, OCS and AGA, given the great number of entries. It's sometimes hard to tell from a screenshot alone.
With my ADLaunch menu system, and having to use AGA WHDLoad for OCS demos, I've long since given up differentiating between OCS or ECS, as long as they run. Does it matter what chipset they use? I would've thought Pouet.net or Demozoo would have that info.
ECS isn't a thing really. Sometimes productions have bugs under OCS and end up as ECS accidentally, because they were coded and tested against an A500+ or A600, for example. The number of productions intentionally targeting ECS is probably a single-digit figure. It would seem appropriate to me to just label it OCS.
Sorry, bifat, I meant to say I've long since given up differentiating between OCS and AGA. I mean, it's all Amiga, and what does it matter? It's also confusing because some demos are marked as both AGA and OCS, meaning it's enhanced for AGA but will still run in OCS.
I have one configuration each for OCS and ECS, and four for AGA, but WHDLoad is the problem, I have a lot of demos using that, and while most are OCS, some are AGA, but since I run all my WHDLoad stuff on an AGA config, it doesn't matter to me what chipset it uses.
What I could do to assist is to put all of the actual OCS/ECS demos in one folder, and leave everything else as AGA, and do my best to put the WHDLoad demos in the right place, although if I remember, I did set some OCS/ECS demos to run in an AGA config, if only for the HDD access or other reasons like memory.
I have one configuration each for OCS and ECS, and four for AGA, but WHDLoad is the problem, I have a lot of demos using that, and while most are OCS, some are AGA, but since I run all my WHDLoad stuff on an AGA config, it doesn't matter to me what chipset it uses.
What I could do to assist is to put all of the actual OCS/ECS demos in one folder, and leave everything else as AGA, and do my best to put the WHDLoad demos in the right place, although if I remember, I did set some OCS/ECS demos to run in an AGA config, if only for the HDD access or other reasons like memory.
It's entirely up to you, that was just a suggestion. It's not really important, especially if it means hassle.
You have long since given up differentiating, and I haven't really started watching AGA demos. I'm not using WHDLoad either on my main machine, an A3000. :-)
You have long since given up differentiating, and I haven't really started watching AGA demos. I'm not using WHDLoad either on my main machine, an A3000. :-)
Cool, no worries.
Quote:
The number of productions intentionally targeting ECS is probably a single-digit figure.
There are some that unintentionally target it though, like "OCS" prods that require more than 512 kB chip memory...
Quote:
Cool!
A thought: Would it make sense to team up with z5 and integrate them into ada.untergrund.net somehow (even as a separate list)? Screenshots on ADA are very lowres unfortunately (160x128)..
I contacted z5 on ADA, and funnily enough, he hasn't gotten back to me yet. And my link for the zip file was omitted upon posting, which I find strange.
Yeah, this requires some patience, i think. Things on ADA currently seem quite in hibernation (no new forum posts since quite a while)..
Thanks for sharing these Foebane72, as demo (game) launcher front ends evolve this pack is much appreciated from my end. And I can also appreciate the usefulness to websites and more. Great stuff, thank you.
@keito: You're very welcome! :)
Here are 36 additional Amiga demos that I've just added to my collection over the last two days:
https://drive.google.com/file/d/1h5ZbUTnA03zmM9fl596UuKiD6dbiQKKx/view?usp=sharing
https://drive.google.com/file/d/1h5ZbUTnA03zmM9fl596UuKiD6dbiQKKx/view?usp=sharing
The links are already dead. We have failed as a community.
Quote:
The links are already dead. We have failed as a community.
Well, I did remove them less than 24 hours before you posted, because I've updated them since, I don't like using my personal cloud storage to host them with the sharing aspect and everything and I'd rather send them as email attachments to anyone who requests them.
If anyone still wants these, then if you'd like, just send your email address and I'll happily send them to you, latest files included.
I'm re-hosting an updated version of the Amiga demo screenshot archive on Amazon Drive, which will only last for one more year it seems.
As a bonus, I'm including my Atari 8-Bit demo screenshots too, as I'm a Jay Miner hardware fan:
Amiga Demo Screenshot Collection (2022.12.20)
Atari 8-Bit Demo Screenshot Collection (2022.12.20)
As a bonus, I'm including my Atari 8-Bit demo screenshots too, as I'm a Jay Miner hardware fan:
Amiga Demo Screenshot Collection (2022.12.20)
Atari 8-Bit Demo Screenshot Collection (2022.12.20)
Hey, thanks! These are pretty good. For anyone wondering, there are 840 @ 35 MiB. File names look like this:
For the following production:
Foebane72's screenshots would be nice for a catalog-like setting (like a MAME front-end but for demos), because they are mostly title screens (as mentioned). This is different from pouët's screenshots, which tend to feature mid-demo action.
One thing that might have been nice would be the pouët ID somewhere in the file name (e.g. the 25651 above), as that would facilitate downloading.
Thank you again for sharing these.
Code:
FUNK DEF @ traktor.png
For the following production:
Code:
# NO GLÖPS.
pouet.net/prod.php?which=25651
# WOW I AM SO SHOCKED AND OFFENDED JEEZ.
Foebane72's screenshots would be nice for a catalog-like setting (like a MAME front-end but for demos), because they are mostly title screens (as mentioned). This is different from pouët's screenshots, which tend to feature mid-demo action.
One thing that might have been nice would be the pouët ID somewhere in the file name (e.g. the 25651 above), as that would facilitate downloading.
Thank you again for sharing these.
@ MARCEPS: You're welcome :)
Quote:
Foebane72's screenshots would be nice for a catalog-like setting (like a MAME front-end but for demos), because they are mostly title screens (as mentioned). This is different from pouët's screenshots, which tend to feature mid-demo action.
One thing that might have been nice would be the pouët ID somewhere in the file name (e.g. the 25651 above), as that would facilitate downloading.
I have such a front-end I developed over the last two years, I call it ADLaunch, and I use it all the time for most of the stuff I do on PC. It works for games and tracker music and even YouTube links as well as demos on several formats (with emulators). And yes, as for the Pouet IDs, I have all of those as well. ADLaunch can produce HTML documents which are links to those prods on Pouet, so that's sorted, too.
ADLaunch has changed a lot in the last several months, but I'm not sure about distribution as to Kickstart ROMS, ClassicWB distros and other ROMS and things like that. It can be configured, but would require several changes from my system to another's.
That sounds awesome. I use a text menu for that, but I've toyed with the idea of making a hintchar- and image-based alternative someday. The fewer keystrokes, the better.
Are ADLaunch's HTML documents compiled ahead of time (as opposed to generated on the fly)?
Are ADLaunch's HTML documents compiled ahead of time (as opposed to generated on the fly)?