I am curious to know what causes artefacts on video files. Is it an error in the ripping process, or do they occur as a file is spread? Also as an overnet user (don't scoff!, am getting emuled up as soon as current downloads complete), is it these artefacts that overnet is seeing as "corruption" when it decides to dump parts?
By and large i have rarely had any artefact problems since using overnet, unlike the artefact hell which was kazaa, although the odd file will keep dumping corrupt parts, to the point where it regresses to less parts than i had at the start of the session, and i dump the file. :rage: It's wierd how it dosen't seem to work on a "what we have we hold" basis. Is this the case with emule, or not?

Thanks.

Artifacts can be caused by:
a) poor rip (ie old codec with low bitrate. divx3 is notoriously associated with artifacts)
b) low bitrate (even the best codec can't help if the bitrate is terrible)
c) error in the source
d) error during encoding
e) error / corruption during transfer (although this is not normally the case with ed2k//overnet as it redownloads bust parts, but ftp and irc especially [no error correction])
f) crap codec/ffdshow decoding. Always check this one, ffdshow is often the cause
g) hardware problem (not as common, but often the case on standalones and/or poor monitors)

In my experience, it's normally a/b/d or e, and not down to the emule/edonkey/overnet client. It's a case of being a flawed rip to begin with.