As you are probably aware, the entire DAVID company, team and product range has been integrated into HP Inc.
This forum is now read-only. Relevant content has been migrated to HP and merged into HP's Support Forums on November 1, 2016.

To start new discussions for 3D Scanning, please register and post your new topic at the HP Support Forums

Hal, do you mean by non linear alignement the capacity to deform a little each scan to get a best matching like a "scan distortion killing machine" ? or am i wrong ?.Lately i had to use some "Mesh deformation" (MLS) to clean-close a scanned object due to distortion and it would be great if implemented !

PS : Moog from your screenshot it seem that you don't have "Microsoft .NET Framework 4.0" installed...(viewtopic.php?f=16&t=5480) i had this kind of white UI the first time i launch David without Framework 4.0 installed

There seems to be a problem handling virtual COM port pairs as you get them using comOcom .

If there is a virtual ComPortPair (COM1<>Com2) you might enable DAVIDs communication to read/write to COM1. You might use TestCom 0.9 to open COM2.Now, if COM2 is already opened when you restart DAVID all works fine.But if you forgot to open COM2 before starting DAVID, DAVID freezes trying to open COM1....(Using two instances of TestCom 0.9 on both ports, there is no problem opening a single port with the other still closed)

If you plug in a real serial device (maybe Arduino at COM3) you may enable DAVID to write/read to that port. As soon as this port isn´t available any more (for you unplugged Arduino) DAVID falls back to the next port automatically. If this next port is a part of a virtual pair without running application on the other end DAVID freezes now.

I am moving to Seven 64Bit in a while on this workstation but I am receiving some PC, there will be an extra Laptop with a quadro card I'll keep for myself, in 4-5 days I am going to test it too on 7/64pro.

Unluckily microsoft produces a lot of "new" stuff and seems that will never end to do one toroughly, but who cares, usually the last days of their most succesfully good OS are also the best, endly one isolate the workstation and might keep it as long as it is useful as last "state of the art release build", ( sigh).

You have great positive feedback from everyone here especially about the new algorithm, everyone who tried told me it is just amazingly great, also everyone is pretty happy about the language translation

Well, I am looking forward to go 64bit with DavidThe 64 bit should become a truly standing ovation.

I was waiting it .... ehhhmm.. from the beginning... , you do not imagine how happy I am about this.. maybe you remeber I asked info about it long ago...

The first 64Bit processor was launched by IBM in 1961, after 52 YEARS, we still are looking at the early rising of the 64bit computing for the masses Isn'it incredible compared to the feeling we have on how technolgy is fast developed?

anybody able to use ImageGrabber or MovieGrabber in SL? Any hints welcome.

The built in pattern generator requires a streaming cam to be calibrated before a projector calibration sequence is projected (which could be recorded with a still image or movie cam).Do I always have to run a second cam tograb the right images in the right order?Also saving the patternsequence (via RMB click on projection) does not save anything (to make a slide show). Switching the patterns manually (via RMB menue) and grabbing these gives another order than the patterns seems to be needed now.Also my homemade PatternGenerator fails due to the unknown expected order

Sorry, there are two bugs. 1. Save Pattern Sequence does not save in the selected folder, but instead into the application folder. So you need write access there. We have fixed this for the next version.2. Scanning with ImageGrabber should work, but calibration not. We are working on it. If you want to calibrate with pre-recorded images, please use version 3.5 or older.

It seems nobody has been using the ImageGrabber for some time...

The pattern order: Is the same as before. During LIVE scanning DAVID does project in a different order (mix of CL and PS images, and mixed horizontal/vertical) so it can auto-detect transitions more robustly. But when you use the ImageGrabber, the images must be in the old "well-ordered" order. Like "Save Pattern Sequence" does.

checked whether I could simply copy and paste calibresults to the settings directory.Comparing the files I found while 3.5 and lower ProjectorSetup.xml lists many phase error values, 3.7 fills this only with many zeros.When I copy a 3.5 ProjectorSetup.xml to 3.7, 3.7 has no problems, but overwrites these phase errors closing it.Either these values aren´t used any longer or they are forgotten to write into the file.

Calibrated ImageGrabber in 3.5 and copied the mentioned files to 3.7(Noticed that these versions gave slightly different angles of intersection using the same setup with a streaming cam, so to copy/paste these files might result in distortions)Processing images of 3456x2304 from my EOS gave remarkable details. Scans are pretty big (the scan of my empty corner is at 14,5 millions tris), but DAVID 64bit could handle them (at least a few).

A thing I noticed with the Image- and VideoGrabber:If one cancels the file picker dialog without selecting any file, the picker can not be opened once again here. One has to go to Hardwarekonfiguration and load something with a different source. After that, one can use the canceled grabber again.

As you can see on the comparison screenshot below there are a few differences in the UI between the 32 and 64 bit versions.

The Selection part (rectangle, polygon, ..) on the x64 version does not work for me as I cannot "activate" it like on the 32 bit version. I can choose what form of selection I want to use but It simply would not let me use it on anything on the x64 version.

x64 is working just fine for scanning but still has a long way to go when compared to the 32 bit version.But I am confident that the above mentioned issues will get fixed in time.

MagWeb wrote:Comparing the files I found while 3.5 and lower ProjectorSetup.xml lists many phase error values, 3.7 fills this only with many zeros.

Yes, sorry, that's just temporary. The phase error values will come back in the next version.

A thing I noticed with the Image- and VideoGrabber:If one cancels the file picker dialog without selecting any file, the picker can not be opened once again here. One has to go to Hardwarekonfiguration and load something with a different source. After that, one can use the canceled grabber again.

Yes, I know. But you don't have to select a different source, you can directly select the same grabber again.Not ideal, but for now we'll have to keep it that way.