Demoscene vs. Processing vs. Motion Design
category: general [glöplog]
I've just seen the Demoscene Outreach Reel by Scene.org. My question is: what is the difference between demoscene, Processing and motion design?
I've been thinking for a while about it and... I don't have a concrete/exact/easy answer. If anybody, after watching that reel ask us that question... how to answer?
Lets think in the coding part. I suppose some motion designers may code time to time, I'm not very sure about it, but processing people code. So, "demoscene is coded" is not a difference. Also, being an executable is not a difference... we have, for example, demopaja, and demos done in demopaja are demos too.
Then, the realtime part. Motion graphics doesn't use to be realtime, so, ok, there might be a difference here. But, what about Processing? Does it is realtime or not? I'm not sure about it. And... what does mean "realtime" in the new high-end demos? I can't run any of these in a realtime framerate on my computer, and I suppose it is the same for a lot of people... so, how to explain what "realtime" is?
Any ideas?
I've been thinking for a while about it and... I don't have a concrete/exact/easy answer. If anybody, after watching that reel ask us that question... how to answer?
Lets think in the coding part. I suppose some motion designers may code time to time, I'm not very sure about it, but processing people code. So, "demoscene is coded" is not a difference. Also, being an executable is not a difference... we have, for example, demopaja, and demos done in demopaja are demos too.
Then, the realtime part. Motion graphics doesn't use to be realtime, so, ok, there might be a difference here. But, what about Processing? Does it is realtime or not? I'm not sure about it. And... what does mean "realtime" in the new high-end demos? I can't run any of these in a realtime framerate on my computer, and I suppose it is the same for a lot of people... so, how to explain what "realtime" is?
Any ideas?
moron...
We have computers which can beat their computers.
Uncle-x, even if I don't use to write serious topics on the bbs, this is one was a serious question this time. Sorry if it didn't looked that way...
First, you start with a nectarine.
Next, bisect the nectarine until a trumpet and a pig come out.
Finally, learn what the hell you're talking about. Perhaps you could write a wikipedia article about it, then see who tries to edit it. Then, kill them! Read the newspaper articles about them and go to school where they went to school.
???
profit!!!!!
Next, bisect the nectarine until a trumpet and a pig come out.
Finally, learn what the hell you're talking about. Perhaps you could write a wikipedia article about it, then see who tries to edit it. Then, kill them! Read the newspaper articles about them and go to school where they went to school.
???
profit!!!!!
the question could have been serious, but the basic premise was morose... what is the point of comparing shit to crap and bull?
Uncle-x: I've just thought on it, and, for my surprise, I've not a clear answer.
I feel there is some difference... but I don't know where, I can't answer to my question clearly... I'm a curious person, so when I'm interested in something and I don't have an answer by myself, I ask.
Maybe for you is an easy answer or a moron question, that doesn't mean it is for me too. You are an awesome demoscener, with a lot of more experience in the field than me, so maybe you can answer my question (if you have an answer for it, of course).
I feel there is some difference... but I don't know where, I can't answer to my question clearly... I'm a curious person, so when I'm interested in something and I don't have an answer by myself, I ask.
Maybe for you is an easy answer or a moron question, that doesn't mean it is for me too. You are an awesome demoscener, with a lot of more experience in the field than me, so maybe you can answer my question (if you have an answer for it, of course).
well imo processing is nice platform for demos and intros
and about motion design, stiletto is a nice example ^_^
I mean... if you want, you can see demoscene in every little thing
and about motion design, stiletto is a nice example ^_^
I mean... if you want, you can see demoscene in every little thing
HARDCODE!!!!!!!!!!!!!
Demoscene vs. Processing
1,380,000 results vs. 287,000,000 results
Processing wins
Processing vs. Motion Design
287,000,000 results vs. 127,000,000 results
Processing wins again
But hey!
Unlike the others Demoscene IS culture, fun and friendship :)
1,380,000 results vs. 287,000,000 results
Processing wins
Processing vs. Motion Design
287,000,000 results vs. 127,000,000 results
Processing wins again
But hey!
Unlike the others Demoscene IS culture, fun and friendship :)
And unlike demoscene processing is an adverb. Or something.
pera: i have met those ppl :D
yeah. word.
Quote:
Unlike the others Demoscene IS culture, fun and friendship :)
yeah. word.
You may as well ask people about comparing live theater with cartoon movies and tv news shows, and ask which one really has 'acting' in it.
Besides being a culture, Demoscene is also a lifestyle.
The Demoscene is a worldwide collection of fuckups. No shared intrest at all. Just fuckups. Fuckups with keyboards.
and funny hats! keyboards and funny hats.
Quote:
Any ideas?
Oh, plenty.
Quote:
I can't run any of these in a realtime framerate on my computer, and I suppose it is the same for a lot of people..
But what you see is still "realtime" generated content (your machine is just not realtime enough!), buy new hardware and stop asking dump questions ;)
the demoscene could embrace others, the inverse is not true :)
Well, demos have to be two things that are key here: realtime, and coded.
'Realtime' is just realtime on the target platform - if the target is a really high end pc, you can't say it's not realtime because it runs slow on an old one, or you could say no recent demos are realtime because they don't run on a 386. That leads to another point though.. a lot of other stuff runs realtime, including some motion graphics stuff, and a lot of processing stuff, so there's a huge blurry area here.
'Coded': processing stuff is coded. If it's realtime (and non-interactive, with music, and running for a set time etc.) then it's a demo, really. I don't see how else you can see it. If it was done with directx/c etc. and released in a demo compo, there would be no difference at all, or at most it would just be a different style from what we're used to. A lot of motion graphics stuff is coded too, and if it runs realtime... well, I say it's also a demo.
The big difference really is the platform - if you made something in MEL that runs realtime, the platform would be maya. Processing is a platform too if you look at it that way. How about if a demo made in processing was made into a proper .exe though... it becomes a standard windows demo right?
I actually started work on a demo a bit like that before, using houdini as the platform, and writing the code in python, with the intention of releasing it in a wild compo some time (if anyone is considering it, avoid houdini - the python api is no where near complete, and the documentation is mostly missing ;( ).
Now, I do stuff using quartz composer on osx.. another nice grey area. It's a visual programming / motion graphics type tool, so it's very quick to make stuff with. It's also got a plug-in api so I can write effects etc. for it, and it can be wrapped in an executable to make it into a normal demo. I guess that sits right in the middle of all this stuff :)
'Realtime' is just realtime on the target platform - if the target is a really high end pc, you can't say it's not realtime because it runs slow on an old one, or you could say no recent demos are realtime because they don't run on a 386. That leads to another point though.. a lot of other stuff runs realtime, including some motion graphics stuff, and a lot of processing stuff, so there's a huge blurry area here.
'Coded': processing stuff is coded. If it's realtime (and non-interactive, with music, and running for a set time etc.) then it's a demo, really. I don't see how else you can see it. If it was done with directx/c etc. and released in a demo compo, there would be no difference at all, or at most it would just be a different style from what we're used to. A lot of motion graphics stuff is coded too, and if it runs realtime... well, I say it's also a demo.
The big difference really is the platform - if you made something in MEL that runs realtime, the platform would be maya. Processing is a platform too if you look at it that way. How about if a demo made in processing was made into a proper .exe though... it becomes a standard windows demo right?
I actually started work on a demo a bit like that before, using houdini as the platform, and writing the code in python, with the intention of releasing it in a wild compo some time (if anyone is considering it, avoid houdini - the python api is no where near complete, and the documentation is mostly missing ;( ).
Now, I do stuff using quartz composer on osx.. another nice grey area. It's a visual programming / motion graphics type tool, so it's very quick to make stuff with. It's also got a plug-in api so I can write effects etc. for it, and it can be wrapped in an executable to make it into a normal demo. I guess that sits right in the middle of all this stuff :)
processing is a platform, not a scene.
demos are anything we say they are.
demos are anything we say they are.
Conceptually the processing "scene" or whatever you call it is still very different from the demoscene, I think. And you can tell the difference between the productions just by looking at them.
Oh yeah, the 'scenes' are different. Not really that much perhaps though, there's certainly some 'community' i think, and meeting up with other people from the scene seems pretty common. I think the real difference is that we've been around much longer, and the demoscene came from piracy, where copy parties were common. Because of that we've got a tradition of parties, compos etc., and so a much stronger community.
One could also argue that the demoscene usually produces works that run from a self-contained executable, which is not the case with most Processing stuff, and certainly not with motion graphics. Also, the Processing stuff that I have seen (and been impressed by) has always been something that does not run in realtime but renders to frames which are then put together in some video package.
gloom: demos aren't so 'self contained' - they tend to need windows or whatever. A processing file is also pretty self contained and executable if you load it in processing, so it's not really that different - it's just another platform.