Forgot your password?
typodupeerror
Education Graphics Programming

Ask Slashdot: How To Catch Photoshop Plagiarism? 284

Posted by timothy
from the when-google-images-isn't-enough dept.
First time accepted submitter jemenake writes "A friend of mine teaches electronic media (Photoshop, Premiere, etc.) at a local high-school. Right now, they're doing Photoshop, and each chapter in the book starts with an 'end result' file which shows what they're going to construct in that chapter, and then, given the basic graphical assets (background textures, photos, etc.), the students need to duplicate the same look in the final-result file. The problem, of course, is that some students just grab the final-result file and rename it and turn it in. Some are a little less brazen and they rename a few layers, maybe alter the colors on a few images, etc. So, it becomes time-consuming for her to open each file alongside the final-result file to see if it's 'too perfect.'" How to look for images closer than they should be to the original? Read on for more details.
jemenake continues: "When I first discovered that she was doing this, my first reaction was that there's got to be some automated way of catching the cheaters. Of course, my first idea of just doing MD5 hashes of each file won't work, since most kids alter the file a little bit.

A second idea I had was to alter the final-result file in a way that isn't obvious, like removing someone's shoelace, mis-spelling a word in the background, or removing/adding some dust-specks. (I know map publishers and music transcribers use this trick to catch copiers). But this still requires that she look for the alteration in each file. I'd think that Photoshop, after all these years, would have some kind of scripting language which also supports some digital watermarking, but I've just never dabbled in that realm.

And, of course, I guess another solution would be for her to not provide the end-result file in Photoshop format, but to export it as a flat image. But I'm still intrigued by the notion of being able to "fuzzily" compare two photoshop files or images to find the ones which are too similar in certain aspects (color histograms, where the edges are, level of noise, whatever).

Anybody else have any clever ideas for this?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: How To Catch Photoshop Plagiarism?

Comments Filter:
  • simple solution (Score:5, Informative)

    by wbr1 (2538558) on Tuesday November 13, 2012 @02:36PM (#41970937)
    distribute the final file as a watermarked png only. Require assignments to be turned in a multi layered psd files. Problem solved.
  • FindImageDupes (Score:5, Informative)

    by Ken_g6 (775014) on Tuesday November 13, 2012 @02:38PM (#41970971) Homepage

    From the manpage:

    findimagedupes [jhnc.org] compares a list of files for visual similarity.

    To calculate an image fingerprint:

              1) Read image.
              2) Resample to 160x160 to standardize size.
              3) Grayscale by reducing saturation.
              4) Blur a lot to get rid of noise.
              5) Normalize to spread out intensity as much as possible.
              6) Equalize to make image as contrasty as possible.
              7) Resample again down to 16x16.
              8) Reduce to 1bpp.
              9) The fingerprint is this raw image data.

    To compare two images for similarity:

              1) Take fingerprint pairs and xor them.
              2) Compute the percentage of 1 bits in the result.
              3) If percentage exceeds threshold, declare files to be similar.

    Of course, you shouldn't take its suggestions at face value every time, but it should help narrow your search for cheats.

  • Ummmmm (Score:5, Informative)

    by cultiv8 (1660093) on Tuesday November 13, 2012 @02:41PM (#41971033) Homepage
    2 mins of googling and I found this: ComparePSD [pixelnovel.com].

    ComparePSD compares two Adobe Photoshop PSD files for you and highlights the differences. Layer by layer. Effect by effect. Simple. And did we mention that ComparePSD is absolutely free?

  • Re:history (Score:5, Informative)

    by ColdWetDog (752185) on Tuesday November 13, 2012 @03:05PM (#41971453) Homepage

    Yep. PS does include a history function that can be written to the metadata. Bonus points for pulling out the metadata stream, running some regex on it and deciding if it was legit.

    Extra bonus points for not including the history in the image given to the students. And requiring it for a grade.

  • She could try... (Score:5, Informative)

    by AliasMarlowe (1042386) on Tuesday November 13, 2012 @03:14PM (#41971603) Journal

    Perceptual Image Diff [sourceforge.net] and Find Image Dupes [freecode.com] might be helpful. If she runs finddupes with a threshhold of .99 or so, then it is likely just trigger on nearly exact copies. At least, it should narrow down the ones she has to inspect in more detail. On the other hand, pdiff will detect exact or nearly exact copies by specifying how many pixels are allowed to differ (so it can be fooled by addition of random noise). While pdiff is available for Windows as well as Linux, it seems that finddupes is Linux only.

"Neighbors!! We got neighbors! We ain't supposed to have any neighbors, and I just had to shoot one." -- Post Bros. Comics

Working...