FWIW, James from Vector Magic team emailed me back after taking a look at the issues we've brought here on this thread. He asked me to post his response on their behalf so here it is:
--------------------------------------------------------------------------------------------------------------
Hi [WunderCade],
Thanks for your email, and for your interest in our project. I took a
look at your forum discussion and I'd be happy to answer the questions
that I saw there. If you don't mind, would you be willing to post
them on my behalf?
1) There was some question about the comparisons
(
http://vectormagic.stanford.edu/vectorize/comparisons) and whether we
cherry picked them. We selected images that we thought fairly
demonstrated the differences between our algorithm and the algorithms
available in the Adobe and Corel products. In some cases all the
programs did essentially just fine and we avoided including those
images, since it is not very interesting to see essentially the same
result three times. In no cases from the 124 user-provided images we
tested did we find that the Adobe or Corel results were actually
better. An important thing to keep in mind here is that we did not
set out to solve all vectorization problems. We are mostly interested
in re-vectorization, where the original was at some time, and in some
sense, vector art. We have therefore restricted our sample set to
those examples. As noted on the comparisons page, we compared our
results against those of Adobe and Corel on 124 user-provided images
and in not a single case did they produce results that both used fewer
shape primitives and had a lower re-rendering error (measured in root
mean squared error).
2) As several posters noted, the site did experience some difficulty
in meeting user demand. This is because we were posted on Digg.com
and got flooded with Digg users. The site is back up now and should
be working fine.
3) The file size and image size restrictions are because we are having
to do all the processing on our servers, and given the high level of
user demand we've been seeing, we can't afford to process jobs that
are too large, as it will tie up one of our processors for too long.
That restriction may be relaxed at some point. How large are typical
scans that would be of interest to this community?
4) A user named zorg posted an interesting comparison. He seems to
have used different settings than I would have selected (indeed, if he
would provide a link to the result that he posted, I could perhaps
clarify which settings he might want to experiment with). Here is a
link to the result that I got when I tried his source image:
http://vectormagic.stanford.edu/vctr/vctr_flex?g=37532&k=j481UGXJRae6nNOe&p=gI've also attached the resulting EPS. The results are not perfect, of
course, but I also don't think that a low-res low-quality JPEG with
sub-pixel-width outlines is typical input. Indeed, most of our users
are providing much higher quality input and are getting much higher
quality output. It is also important to select the options correctly.
If you would be so kind as to post the attached EPS, I think it would
help clarify the issue. I would also be interested to see how well we
do on the same image, but at a slightly higher resolution and saved as
a PNG rather than a JPEG.
Regarding the broader issue of whether our tool is a substitute for
human vectorization, I would give the following remarks: Human
vectorization will always remain essential for difficult images in
which the quality of the input is too low for a computer to do the
tracing, or images that were not originally vector art in spirit, and
require judgement and interpretation to produce a good result. Our
tool is meant to help convert fairly clean, fairly high-quality
images, and to provide a starting point for marginal cases.
If you or any of the other posters have any further questions, please
feel free to email me at this address. We are always trying to
improve the tool and welcome constructive feedback that will help us
do just that!
Very Best,
James