[flagged]
User Interfaces of the Demo Scene
31–40 of 83 posts
Re: User Interfaces of the Demo Scene
#32Not trying to be a jerk, but demoscene is one word afaik?
https://en.wikipedia.org/wiki/Demoscene
and everyone wrote it as a single word, here in comments to this article.
Re: User Interfaces of the Demo Scene
#33I first thought "Elite Sinus Producer" and "The Sinus Creator" were trackers specifically designed for creating nasal-sounding music; but of course the explanation for why the term "sinus" came to be used instead of "sine" is likely because many demosceners were from a native European background, and their language retained the Latin origin word instead of deprecating its usage in favour of "sine", as happened in Eng…
Can confirm it's sinus in Norwegian, Swedish, Danish, Dutch, French.
Can confirm all sceners call it sinus in Spain :)
Re: User Interfaces of the Demo Scene
#34Oh wow, great read! I was an amiga demo scene coder down here in Australia, spent many long nights in asm-one :) I had no idea there were tools for pre-calc lookup tables back then! Instead I just generated my own from code as I assumed everyone else was :D Using pre-calc sine tables freed up so many clock cycles. Big shout to all the sceners on here! I really do miss coding 68k asm sigh :)
Greetings from Spain!
We somehow got a copy of Defy diskmag, started swapping with Cro^Cydonia and got to enjoy Satisfaction Guaranteed by Pearl :)
I always did all my small tools and stuff in blitz basic 2, would dump binary file and incbin them in Devpac.
-- winden^TNC^Network
[ https://www.pouet.net/prod.php?which=14404 and https://www.pouet.net/prod.php?which=7645 ]
Re: User Interfaces of the Demo Scene
#35Not trying to be a jerk, but demoscene is one word afaik? https://en.wikipedia.org/wiki/Demoscene and everyone wrote it as a single word, here in comments to this article.
It can be either. In the demoscene, sceners just call it the scene.
They also like to agglutinate words, e.g. copyparty, sizecoding and so on.
You can split or join the word if you like.
Re: User Interfaces of the Demo Scene
#36> When a copy was finished (which could take some time), the program helpfully played a little "boing" sound.
And how that "boing" sound worked is interesting in itself. It's one of the few uses of Paula's "attached" mode, where the output of one sound channel is used to modulate the volume or pitch of another.
I put the full source code of the boing sound here: https://news.ycombinator.com/item?id=48174583
Re: User Interfaces of the Demo Scene
#37Not trying to be a jerk, but demoscene is one word afaik? https://en.wikipedia.org/wiki/Demoscene and everyone wrote it as a single word, here in comments to this article.
It can be either. In the demoscene, sceners just call it the scene . They also like to agglutinate words, e.g. copyparty , sizecoding and so on. You can split or join the word if you like.
I suspect that it, like the "sinus" mentioned elsewhere, may well be a result of the scene (at least at the start) being dominated by people natively speaking Northern European Germanic languages.
I started learning English about 43 years ago, and I still struggle with when words are combined or separate in English because it largely follows no logic while in Norwegian it carries meaning.
Re: User Interfaces of the Demo Scene
#38[dead]
Re: User Interfaces of the Demo Scene
#39Never been into building tracks, always the coder (assembler on 6502 and MC68000). Somebody should do a similar article about all the demo build tools like kkrieger, or modern ones like Tixl. Anyway…good old times :)
Re: User Interfaces of the Demo Scene
#40Another good one is the visual editor of .werkkzeug3 used to make .kkrieger which serves as an alternative interface to the typical node based shader editor. https://media.demozoo.org/screens/o/82/e2/a055.334456.png
Wow this looks like the Unreal Tournament interface somewhat