2 ms·
It doesn't seem to do all that well on blueprint type line art.[1] It seems to do a lot better when it has areas to separate. Which is not surprising, consideri
by Animats 3y ago
It doesn't seem to do all that well on blueprint type line art.[1] It seems to do a lot better when it has areas to separate. Which is not surprising, considering the approach.
This is about as well as I was doing on scanned engineering drawings in 1983. I wrote Autodesk's CAD/Camera. 20 minutes of compute to process a drawing on an IBM PC/AT.
You can be too early. By now, a product in that space should be recognizing not just lines, but dimensions, and generating a properly dimensioned CAD model.
[1] https://github.com/visioncortex/vtracer/blob/master/docs/images/screenshot-01.png https://github.com/visioncortex/vtracer/blob/master/docs/ima...
- ska 3y ago> You can be too early. Yes, yes you can. I worked on a project than included hardware are related workflow for digitizing analog input to essentially a digital image processing workflow, just because the digital sensors weren't quite there yet. A few years later, they were.
- dylan604 3y ago>You can be too early. I can sympathize. In the early/mid-90s when Apple released QuickTimeVR, a buddy of mine and I tried to start an early VR real estate virtual tour company. Realtors of the time had no idea, and the internet was still too new for people to really grok the concept. Early DSLR writing to floppy disks just put that little cherry on top
- Animats 3y agoRight. I knew about convolution back then, but with an 80286, 640KB, no FPU, and E-size drawings at 300 DPI, there just wasn't enough compute power.