Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > C64 Pixeling > An update on ‘Pixel art in the C64 demoscene’
2024-02-01 16:54
Sander

Registered: Jan 2002
Posts: 493
An update on ‘Pixel art in the C64 demoscene’

Dear fellow sceners,

In response to the comments we received, we’ve made some changes to the document.
Our goal was always to find common ground to maintain the fun and integrity of our hobby.

What this is not:
- It’s not written to limit anyone (only to encourage openness)
- It’s not aimed at specific individuals (it’s a scene wide practice)

Read the document here

We’d really love to hear your thoughts on this update.
Please post them in this thread, be kind and keep it constructive and on-topic please.
 
... 127 posts hidden. Click here to view all posts....
 
2024-02-02 21:38
CreaMD

Registered: Dec 2001
Posts: 3036
Quote: Quote:
Maybe to a lot of people it doesn't. If people are transparent, the audience can decide.

To me this whole debate seems to be much more about curiosity than fairness by now. And as for that, when i am curious about how someone made this and that - i'll ask. I might get an answer (and often do), or not - and both is just fine. No one is obliged to tell anyone. Or even do it in advance.
Quote:
Unless I've missed something, C64 demos are not usually written in c++. There's a reason for that?

Not directly, sure. But all kinds of high level languages (including c++, i am sure) are used to produce the code in one way or another.


When we strictly talk about compo and the way it is presented. There is no way to know how it was made. You just see one picture after another. No time to ask anything.

That's why I think it's quite important (and it's not just about curiosity) to see how the picture was made. Is it original, derivative work (the author should be credited), is ai generated? Was it pixelled on native c64 tool from reference? Was it pixelled/drawn on crossplattform tool? Was it converted and then retouched? Such things. Most of the time, the process shouldn't affect the score, but in case of derivative work (if they are accepted as compo entries) people would least have chance to see the context. For online compo thus should be a requirement I think.

or party compos, it should be doable too, and in uniform way. You just need to wrap every image in presentation screen which shows all the info and after space, shows the compo entry. It shouldn't be hard to do C64 tool, and online tool capable of doing such packaging. I would call it "birthlist".
2024-02-02 21:42
ws

Registered: Apr 2012
Posts: 238
how about "optional/voluntary birthlist". hey magician, what's in that hat?
2024-02-02 21:47
CreaMD

Registered: Dec 2001
Posts: 3036
Quote: how about "optional/voluntary birthlist". hey magician, what's in that hat?

I think birthlist should be requirement. Stages can be, but doesn't necessarily have to be, part of that. If note about sources, process and tools is handed in (and then presented on big screen before each the entry in some uniform way), stages probably won't be that necessary.

Imagine someone submits entry with this birthlist: original sketch, converted, pixel retouched. Stages won't be necessary. Just one picture of original sketch.
2024-02-02 22:13
chatGPZ

Registered: Dec 2001
Posts: 11164
Those things are however totally up to whoever organizes the compo :) I don't see this happening myself, not in such strict sense anyway - as that is quite some extra burden for the organizers (and takes extra time to prepare and show - and verify).
2024-02-02 22:14
ws

Registered: Apr 2012
Posts: 238
Ok so, let's say we have all the things that should be done, the moral and ethical and philosophical parameters in line as a good, reusable ruleset for works that should be submitted to a compo. Let's say someone is not truthful and in a deceptive or creative way finds solutions to circumnavigate QC.
Then what? Within the time of the compo all the facts have to be proven wrong? It is okay to disrespect participants who have been "found out"?
Does a ruleset really help to educate "cheaters"? Or does it just justify retrospective criticism? What if i am just a troll who enters a very sophisticated trolly entry and i am only found out weeks later? Does that does that subsequently improve the value of my seemingly underestimated contribution?
- Again, i love philosophical questions, and since the scene is full of (very lovely) magic, trickery, eyewash and boom effects - how would it help to have a refined ruleset?
I suppose it is only being applied at one or two parties/compos at all, but: how do you fact check before the results are out? Because: who carez if anyone complains if the results are published? People are namevoting, people are voting anynomously.
Would it really make you feel better? Is it really only about fairness?
2024-02-02 22:16
Krill

Registered: Apr 2002
Posts: 2870
Quoting Deev
This is why there's a request for transparency. Because clearly some top-ranked artists are regularly taking shortcuts and yet everything is being judged the same. It doesn't feel like a level playing field.
Pretty sure that graphicians on this platform (at least) have never quite agreed on what's good practice and what's "cheating" or "taking shortcuts", long before AI or even wiring were serious business.

Transparency is a good thing, but it should remain optional.
And even when it isn't, you can lie about your process.

Quoting Deev
I expect if a tool came out that could do this better than a human can code asm (or even as good as), we might start to see some coders who wanted competitions that celebrated the traditional ways of doing things.
They'd be a minority, and they exist already. :)
2024-02-02 22:21
chatGPZ

Registered: Dec 2001
Posts: 11164
Reminds me how Graham explained to me at Mekka96 how using a crossassembler is lame, because libraries <3
2024-02-02 22:22
4gentE

Registered: Mar 2021
Posts: 121
@ws: I see this problem (and possible solution) like this. I live in an apartment building. I separate my waste. I’m sure that some of my neighbors do not. I still think it’s a good idea (separating recyclables from bio etc.). The number of people that do not separate is in decline.
2024-02-02 22:28
acrouzet

Registered: May 2020
Posts: 80
In the end I think the overall goal here should be encouraging more transparency in graphics. If there's more transparency, individuals can make judgments on what processes they prefer rather than attempting to enforce scene-wide rules. Like I said before, the scene is very decentralized, so rule enforcement coming from a single source may be very difficult.

I think what makes graphics conversion such a difficult topic is that converting graphics is much more automated than say, converting notes from a DAW into a music tool, which still requires you to create much of the work yourself.
2024-02-02 22:31
ws

Registered: Apr 2012
Posts: 238
oh man i almost searched my ass of to find this gem again.

School Of Life
Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
REBEL 1
hedning/G★P
Fred/Channel 4
Guests online: 63
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Mojo  (9.7)
4 Coma Light 13  (9.7)
5 Edge of Disgrace  (9.6)
6 Comaland 100%  (9.6)
7 Uncensored  (9.6)
8 No Bounds  (9.6)
9 Aliens in Wonderland  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Cubic Dream  (9.6)
3 Party Elk 2  (9.6)
4 Copper Booze  (9.6)
5 Rainbow Connection  (9.5)
6 It's More Fun to Com..  (9.5)
7 Dawnfall V1.1  (9.5)
8 Birth of a Flower  (9.5)
9 Daah, Those Acid Pil..  (9.5)
10 Quadrants  (9.5)
Top Groups
1 Nostalgia  (9.4)
2 Oxyron  (9.3)
3 Booze Design  (9.3)
4 Censor Design  (9.3)
5 Offence  (9.3)
Top Logo Graphicians
1 Sander  (9.9)
2 Facet  (9.5)
3 Mermaid  (9.4)
4 Pal  (9.4)
5 Shine  (9.3)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.051 sec.